Buying a font feels like buying a stock photo or a plugin: you pay, you download, you use it. Then a client asks you to put the logo on a t-shirt, or a developer drops the font file into a mobile app, and suddenly you are outside the terms you agreed to without ever reading them.

This is font licensing explained the way it should have been from the start: no legalese, no scare tactics, just what each license type covers, where the limits usually sit, and the exact questions to ask a foundry before you spend a client’s money.

The one-sentence version

When you buy a font, you are not buying the font. You are buying a limited permission to use a software file in specific ways, for a specific number of people or page views, for a specific period of time. That permission lives in the EULA (End User License Agreement).

Everything else in this article is a detail of that sentence.

Quick reference: the main font license types

License type	What it lets you do	Usual unit of measurement	Typical trap
Desktop	Install the font on a computer and make static artwork: print, packaging, PDFs, images, social posts	Seats (users or workstations)	Sharing the file with a client or a freelancer
Webfont	Serve WOFF/WOFF2 files on a website so live text renders in the font	Monthly page views, sometimes domains	Traffic growth pushing you past the tier you bought
App	Embed the font inside a mobile or desktop application binary	Per app title, sometimes per install or per platform	Assuming desktop covers the app UI
ePub / digital publication	Embed fonts in ebooks, digital magazines, interactive PDFs	Per title or per number of issues	Confusing PDF embedding with ePub embedding
Server	Install on a server that generates artwork automatically (personalisation tools, PDF generators, print-on-demand)	Per server or per tool	Product configurators quietly running on a desktop license
Broadcast / video	Titles and motion graphics in TV, film, streaming and paid ads	Per production or per campaign budget	Big-budget ad campaigns using a basic desktop seat
Logo / trademark	Use the letterforms inside a logo you intend to register as a trademark	One-off fee, sometimes tied to company size	Many EULAs stay silent, so you must ask
Corporate / enterprise	Bundles several use types for a whole organisation	Employee count or revenue band	Renewal terms and agencies not being covered

Desktop licenses: the one everyone thinks they have

A desktop license lets you install the font file on a machine and use it in design software. The output is usually static: a poster, a packaging dieline, a logo lockup, a PDF, a JPEG for Instagram.

What a “seat” actually means

Most foundries sell desktop licenses per seat. A seat is normally one named user or one workstation. If you are a solo freelancer, one seat covers your laptop and, in many EULAs, a second personal machine you also work on. If you are a studio of five designers all using the same typeface, you usually need five seats.

Watch for these variations:

• Per user vs per computer: some foundries count humans, some count machines. It matters if your team works on a desktop and a laptop.
• Contractors and freelancers: many EULAs let you temporarily extend a seat to a contractor working on your project, many do not. This is one of the most common breaches in small studios.
• Perpetual vs subscription: a perpetual desktop license usually lets you keep using the version you bought forever. A subscription stops when you stop paying, which can be a problem for archived artwork you need to reopen in three years.

What desktop usually does not cover

• Uploading WOFF files to a website
• Embedding the font in an app or a game
• Installing it on a server that auto-generates artwork
• Handing the font file to your client so their in-house team can use it
• Sometimes: using the letterforms in a registered trademark

Webfont licenses: the page-view maths

A webfont license gives you the right to serve font files (typically WOFF2) from a website so that live, selectable text renders in the typeface. It is a different technical file and a different legal permission from desktop.

How page views are counted

Most foundries price webfonts in monthly page-view tiers. Common brackets look like this:

Tier	Typical monthly page views	Who it fits
Small	Up to 10,000 to 50,000	Portfolio sites, local businesses
Medium	100,000 to 500,000	Growing SMEs, content sites
Large	1 million to 10 million	Ecommerce, media, SaaS
Unlimited / enterprise	Negotiated	Large brands and platforms

Two important nuances:

1. Some licenses are one-time, some are annual. A one-time purchase for a given tier means you own that tier forever, but if the site outgrows it you must upgrade. An annual license expires and must be renewed, or you have to remove the fonts.
2. Page views are usually counted across all domains covered by the license. A staging site, a landing-page subdomain and a campaign microsite may all count, and some EULAs require each domain to be declared.

Self-hosting vs foundry hosting

If you self-host, you upload the files to the client’s server and the foundry trusts your reporting. If the foundry hosts (a CDN or a service like Adobe Fonts or Monotype Fonts), the counting is automatic and usage is often throttled or cut off at the limit. Self-hosting gives you performance control, hosted services give you compliance peace of mind.

Where webfont breaches happen

• A site is launched with fonts that were only licensed for desktop use because someone converted a TTF to WOFF with an online tool. Converting a desktop file into a webfont is almost always a breach, even if it works technically.
• Traffic doubles after a successful campaign and nobody revisits the tier.
• The same license is reused on a second client project.
• The font is loaded on the client’s ecommerce platform, help centre and email templates, when the license covered one domain.

App licenses: the one that bites developers

An app license covers embedding the font inside application software: iOS and Android apps, desktop software, kiosks, games, smart TV interfaces, in-car displays.

The key distinction is technical: if the font file travels inside the app bundle and is read by the app at runtime, you need an app license. If the app simply shows a PNG you exported in Illustrator, your desktop license normally covers that image.

Pricing models you will see:

• Per app title: one fee for one app, often with a separate fee for iOS and Android versions
• Per number of installs or downloads: tiers like 100,000 or 1 million installs
• Annual vs perpetual: annual is increasingly common, which means budgeting for it in the client’s maintenance contract

The classic accident: a designer delivers a UI kit with fonts attached in a shared folder, the dev team installs them, ships the app, and nobody ever bought an app license. When the foundry notices (and they do run audits), the invoice lands on the client, who then looks at the agency.

What about free fonts and subscription services?

Open source fonts (SIL Open Font License)

Google Fonts and many independent releases use the SIL OFL. In practice this means you can use them for commercial work, on the web, in apps, in logos, and you can even modify them. The main conditions are:

• You cannot sell the font files on their own
• If you modify and redistribute, the derivative must keep the OFL and cannot use a reserved font name
• Attribution rules vary by font, so read the accompanying licence text

Careful with “free” fonts from aggregator sites. “Free for personal use” is extremely common and means exactly what it says: no client work, no commercial output, no logos. Download sites frequently strip the original licence file, so if you cannot find the terms, treat the font as unlicensed.

Subscription libraries

Services bundled with a creative subscription typically cover desktop and web use for as long as your subscription is active. They usually do not automatically cover app embedding, broadcast or server use, and your right to use the fonts ends when the subscription ends. For a brand identity that must survive a decade, a perpetual license from the foundry is usually the safer route.

How to read a font EULA in 10 minutes

You do not have to read every clause. Use this order and you will catch 95% of the risk. There’s a good explainer over at typetype.org.

1. Find the definitions section. Look up how they define “user”, “seat”, “workstation”, “licensee” and “affiliate”. This tells you who is actually allowed to touch the file.
2. Find the permitted uses list. Usually a short bullet list. Anything not listed is generally not allowed.
3. Find the prohibited uses list. Scan for: modification, conversion to other formats, redistribution, third-party transfer, logo or trademark use, server installation, merchandise sold with the letterforms as the product.
4. Check the term. Perpetual or annual? Does it auto-renew? What happens to existing artwork when it lapses?
5. Check the transfer clause. Can you buy on behalf of a client and transfer the license to them? Many foundries allow it, some require the client to purchase directly.
6. Check the upgrade clause. What happens when the client’s traffic or headcount grows? Do you pay the difference or the full new tier?
7. Check the audit and penalty clause. Some EULAs allow the foundry to request usage proof and charge retroactive fees, sometimes at a multiple of list price.
8. Check the modification clause if you plan to tweak letterforms for a logo. Outlined and heavily redrawn letters are usually fine, editing and re-saving the font file usually is not.
9. Check embedding rules for PDFs. Most allow embedding for viewing and printing. Fewer allow editable PDFs that pass the font to a third party.
10. Save a PDF of the EULA and the invoice in the project folder, with the date and the version you bought.

The 10 most common accidental breaches (and how to avoid them)

• Emailing the font files to the client so they can edit a template. Fix: they buy their own seats, or you deliver outlined files and packaged PDFs.
• Uploading fonts to a shared cloud drive that the whole company can access. Fix: keep fonts in a managed font app with controlled access.
• Converting a desktop font to WOFF with an online converter. Fix: buy the webfont license, which is often a separate SKU.
• Buying one seat and installing across the studio. Fix: count actual humans, buy that many seats.
• Using “free for personal use” fonts in client work. Fix: keep a vetted internal list of genuinely commercial-safe free fonts.
• Putting a licensed typeface in a logo without checking trademark clauses. Fix: ask the foundry in writing before presenting the concept.
• Ignoring page-view growth after launch. Fix: set a calendar reminder to review analytics against the license tier twice a year.
• Letting a developer embed fonts in an app because they were in the brand folder. Fix: put a README licence file in every brand asset delivery.
• Selling merchandise where the letterform is the product (vinyl lettering, engraved signs, laser-cut letters). Many EULAs restrict this. Fix: ask about a merchandising or extended license.
• Keeping fonts after a subscription ends and reopening old artwork. Fix: archive outlined versions of key artwork before the licence lapses.

Buying fonts for a client project: who should own the license?

This is the question that saves the most money and the most awkward conversations.

The client should own the license whenever the font will live on in their brand. You are a temporary user; they are the long-term one. If you buy in your own name, you may legally be the licensee, which means the client is technically unlicensed the day you stop working together.

A clean process looks like this:

1. Identify every use case before you buy: print, web, app, video, signage, internal documents, email.
2. Get a quote from the foundry that covers all of them, in the client’s legal entity name.
3. Have the client purchase directly, or purchase on their behalf with written confirmation that the licence is issued to them.
4. Buy yourself a separate designer seat if you need the font to actually produce the work.
5. Deliver a one-page licence summary document with the brand guidelines: which fonts, which licences, which tiers, renewal dates, and who to contact.

That last deliverable is a genuine differentiator for a small studio. Most clients have never received one.

What to ask a foundry before you buy

Foundries are small businesses and most reply quickly and helpfully. Copy and adapt this list:

• Does the desktop licence allow use of the letterforms in a registered trademark or logo? Is there an extra fee?
• Is the licence perpetual or annual? What happens to artwork already produced if we stop renewing?
• Can the licence be issued in our client’s name and transferred later?
• Can we extend a seat temporarily to a freelancer or external contractor?
• Are staging, development and subdomain sites included in the webfont licence?
• How are page views counted and what happens if we exceed the tier? Is the upgrade prorated?
• Does the webfont licence allow self-hosting, and do you provide subsetting rights for performance?
• Is app embedding included, and is it per platform or per title?
• Are social media graphics, paid ads and video covered by the desktop licence, or do we need a broadcast licence?
• Do you allow modification of the font files (for example custom ligatures or a bespoke ampersand)?
• Can we get a trial licence for pitch and concept work before the client commits?
• What are your terms for print-on-demand or personalisation tools that generate artwork server-side?

Get the answers by email, not by phone. An email is documentation.

What actually happens if you use a font without a licence

Realistically, nothing happens for a long time, and then it happens all at once. Foundries and their representatives use web crawlers that detect font files served from a domain, compare them against purchase records, and send a compliance letter. For apps and printed work, tip-offs and manual checks are more common.

Outcomes usually escalate like this:

1. A polite email asking you to confirm your licence
2. An invoice for the correct licence, sometimes backdated
3. A settlement demand that can be several times the list price
4. Legal action, which is rare but real for large-scale commercial use

The cost of compliance is almost always a small fraction of the cost of a settlement. That is the whole argument.

A practical font-licensing workflow for small studios

1. Keep a font register. A simple spreadsheet: font name, foundry, licence type, seats or tier, purchase date, expiry, client, invoice link.
2. Scope licences at proposal stage. Add a line item called “font licensing (estimate, billed at cost)” so it never becomes a surprise.
3. Use a two-list system for concepts: a safe list (open source and fonts you already own) and a wish list (fonts requiring purchase before production).
4. Never ship raw font files in a client handover unless the licence explicitly allows it.
5. Review annually. Check traffic tiers, seat counts, expiry dates, and whether any client outgrew their licence.

Five habits, roughly one hour a year, and font licensing stops being a background anxiety. Font licensing FAQs tackles the same question from another angle.

FAQ

How can I tell if a font is free for commercial use?

Look for the licence file included with the download, usually named OFL.txt, LICENSE.txt or similar. Fonts released under the SIL Open Font License or Apache License are commercial-safe. If the only wording you can find is “free for personal use”, “demo” or “free download”, it is not licensed for client work. When in doubt, go to the designer’s own site rather than an aggregator.

Can I use a font commercially if I bought it?

Usually yes, but only in the ways your specific licence allows. A desktop licence covers static output like print and images. It does not automatically cover websites, apps, servers, broadcast or logo trademarking. Check the permitted uses list in the EULA.

Does a desktop licence let me put the font on a website?

No, in almost every case. Web use requires a separate webfont licence with its own file formats and its own page-view limits. Converting a desktop file yourself does not create the right to use it online.

How do foundries know if I am using a font without a licence?

For websites, automated crawlers detect font files served from a domain and match them against licence records. For apps, files inside the bundle can be inspected. For print, tip-offs, portfolio posts and case studies are common triggers. Detection is far more systematic than most designers assume.

Who should buy the font licence, me or my client?

The client, whenever the font becomes part of their brand. You can buy on their behalf, but the licence should be issued in the client’s legal entity name. Buy your own designer seat separately so you can produce the work. The piece Font licensing explained for designers and brands makes a good next read.

What is the “three font rule”?

It is a design convention, not a legal one: limit a layout to around three typefaces (or three families) to keep hierarchy clear and the composition coherent. It has nothing to do with licensing, but it does reduce how many licences you need to buy.

What happens if my webfont traffic exceeds the tier I bought?

You are out of compliance until you upgrade. Most foundries handle it commercially: you pay the difference or move to a higher tier. Problems arise only when the overage runs for years and the foundry bills retroactively.

Can I use a licensed font in a logo?

Sometimes. Many EULAs allow logo use outright, some require an additional fee for trademark registration, and a few prohibit it. Because a logo is permanent and expensive to change, ask the foundry in writing before you present the concept.

Need help getting this right on a brand project?

At Joxa Design we scope font licensing at the start of every identity and web project, buy in the client’s name, and hand over a clear licence summary with the brand guidelines. If you are unsure what your current fonts actually allow, get in touch and we will review your setup before it becomes an invoice you did not plan for.