Typefaces, T&Cs and the Client Who Wants the Fonts: A Licensing Reality Check

Fonts are the bit of a design project everyone notices and nobody wants to budget for. The client loves the headline face; the developer needs the web files; the printer wants outlines; and somewhere in the middle you are staring at a foundry licence PDF wondering whether ‘one desktop user’ includes the accountant who opens the PDF once. Welcome to type licensing: the unglamorous admin that can still derail a perfectly good job.

Where UK freelancers usually get caught

The same handful of problems come up again and again.

• Sending font files with final artwork. Most desktop licences cover installing the font on your machine, not passing the font to a client. The client may need their own licence.
• Assuming an Adobe Fonts subscription travels with the work. If you use Adobe Fonts, check the terms carefully: the client often cannot keep using the font after your subscription or project arrangement ends unless they license it themselves.
• Treating a web licence as a one-off. Web licences are usually measured by pageviews, domains or both. A licence that feels generous at launch can look thin once a campaign lands.
• Forgetting that app, ebook, broadcast and outdoor use are separate. A desktop licence does not cover embedding a font in an app, a TV ad or a cinema spot.
• Handing over editable files without thinking. Live text in an InDesign or Illustrator file may require the client to have the font licence. Many foundries do not allow you to simply transfer the font.
• Trusting the word ‘free’. Some free fonts are free for personal use only, or free for commercial use but not embedding. Always check the actual licence file.

The licence types in plain English

Desktop: install the font on a set number of computers, often one to five users. It does not usually cover web, app or broadcast use.

Web: use the font on a website via @font-face. The licence normally sets out pageview limits, domains and sometimes subdomains. Buy headroom if you expect traffic to grow.

App: embed the font in an iOS, Android or software product. This is often priced per app, per platform or per product, and it is rarely included in a desktop licence.

Broadcast: use the font in TV, cinema, streaming ads or other moving-image work. Sometimes priced by campaign, territory and duration.

Client handover or transfer: a separate permission to pass font files or rights to a client. Many foundries do not offer this at all, which is why outlined artwork or a client-owned licence is often the cleaner route.

A plain-English checklist before you hit ‘buy’

• Will the client need to edit text after handover?
• Where will the type appear: web, app, print, social, packaging, TV, outdoor, ebook?
• Who needs to install the font, and how many users is that really?
• What traffic or pageview limit does the web licence allow?
• Do you need to hand over font files, or only artwork?
• Does the licence allow embedding, outlining or modification?
• Is there a subscription, renewal or upgrade trap?
• Can you get written confirmation from the foundry or authorised reseller?
• Have you saved the licence PDF and purchase receipt in the project folder?

Contract wording that saves the awkward email

You do not need to become a licensing lawyer. You do need a clause that makes responsibilities clear. Something like this is a sensible starting point:

Typefaces and fonts supplied or recommended by [Studio] are licensed to [Studio] only unless expressly stated. Where final artwork contains outlined type, no font software is transferred. If the Client requires editable files, installation, web embedding, app embedding or broadcast use, the Client is responsible for purchasing the appropriate licence from the foundry or authorised reseller. [Studio] can provide a list of required fonts and licence links on request. Font licence costs are not included in the fee unless itemised in the project quote.

For files you do pass over, a second short clause helps:

Any font files provided to the Client are supplied solely for the project named above and may not be shared, resold or used in other projects.

This is not legal advice, and high-value or unusual projects deserve proper review. But it stops the classic ‘can you just send the fonts?’ email from becoming a silent liability.

Cheaper licensed alternatives that still look good

If the budget is tight, open-source type is your friend. Families such as Inter, Source Sans 3, IBM Plex Sans and Serif, Libre Franklin, Work Sans, DM Sans, Manrope, Fraunces and Newsreader are released under licences such as the SIL Open Font License, which generally allows commercial use and embedding. Check the licence for each family, but these are much easier to hand over without drama.

Google Fonts is another practical route, especially for web work. Check the licence for the specific family, and consider self-hosting if privacy, performance or long-term stability matter.

Fontshare offers a growing library of fonts free for commercial use, but read the terms for app, web and embedding use rather than assuming every use is covered.

Finally, do not overlook smaller independent foundries and resellers with flexible tiers. A modest web licence with sensible pageview headroom is often cheaper than a late scramble to upgrade after launch.

How to protect the project without derailing it

Add font licensing to the kickoff conversation, not the final week. Ask whether the client already has brand fonts and licences. If they supply fonts, get written confirmation that they are licensed for the intended use. If you are recommending a new typeface, show the licence cost as a separate line so nobody feels ambushed.

Then keep the paperwork with the project. A simple folder containing the licence PDF, receipt and a one-page summary of what is covered will save future-you a tedious afternoon. The aim is not to turn every job into a legal seminar. It is to make sure the type looks good, the client can use it lawfully, and you are not the one left holding the invoice.