Font licensing in one paragraph
Font licensing is the legal agreement between a type foundry (or designer) and you, the user, that defines exactly how a font file may be installed, used, shared and distributed. When you buy a font, you are not buying the typeface itself. You are buying a limited permission to use a piece of software (the font file) under specific conditions: how many computers, how many website visitors, whether it can be embedded in an app, whether it can appear in a logo, and whether it can be handed over to a client.
Get it right and nobody ever thinks about it again. Get it wrong and you can receive a compliance letter demanding retroactive fees, sometimes years after a project shipped. This guide breaks down every license type designers realistically encounter, with a practical checklist you can run before a font ever touches a client file.
Why fonts are licensed at all (the typeface vs font file distinction)
This trips up almost everyone, including experienced designers.
- A typeface is the design: the shapes of the letters. In many jurisdictions, including the United States, the visual design of letterforms is weakly protected or not protected at all by copyright.
- A font file (.otf, .ttf, .woff2) is software. Software is protected by copyright almost everywhere. It can also carry patents, trademarks on the name, and an End User License Agreement (EULA).
That is the hinge the whole industry turns on. You are licensing software, and the EULA is the contract. The EULA always beats your assumptions. Two fonts that look nearly identical can come with wildly different terms, and the same foundry can change terms between product versions.
The main font license types at a glance
| License type | What it covers | Usually metered by | Typical trap |
|---|---|---|---|
| Desktop | Installing the font locally to create print, packaging, PDFs, static images, social posts, logos | Number of users / seats / installs | Sharing the file with a freelancer or a printer |
| Webfont | Serving the font to browsers via @font-face or a hosted CDN | Monthly pageviews or unique visitors, per domain | Traffic growth blowing past the tier you paid for |
| App / embedding | Bundling the font inside a mobile app, desktop app, game or device firmware | Per app title, per platform, per number of installs | Assuming a desktop license covers the build |
| ePub / digital publication | Embedding fonts in ebooks, interactive PDFs, digital magazines | Per title or per number of copies distributed | Editable PDFs counting as distribution of the font |
| Broadcast / video | TV, streaming, cinema, paid advertising, motion graphics | Per production, per campaign, per audience size or media spend | A “simple” YouTube ad triggering a broadcast tier |
| Server | Installing the font on a server that generates artwork automatically (PDF generators, personalisation tools, print-on-demand) | Per server, per CPU, per year | Dev team installs the font on a rendering server with no license at all |
| Logo / trademark | Using letterforms inside a registered trademark or wordmark | Flat extended fee, sometimes negotiated | Foundries that explicitly forbid trademark registration |
| Enterprise / corporate | All of the above bundled for a whole organisation and its agencies | Headcount, annual subscription | Agencies assuming they are covered when they are not named |
Desktop licenses: the one everybody thinks they have
A desktop license lets you install the font on a defined number of machines and use it to create static output: brochures, business cards, packaging, posters, exported JPEGs, Instagram carousels, a print-ready PDF.
What a desktop license typically allows
- Installing on a set number of computers (often 1, 5 or 20 seats)
- Producing printed and physical materials, including items you sell
- Exporting flattened or outlined artwork
- Creating images used on a website or social media (because the font file itself is never served to the visitor)
What it almost never allows
- @font-face on a live website
- Embedding in an app or a game
- Installing on a shared server or a cloud rendering pipeline
- Emailing the .otf to a printer, a freelancer or the client
That last point causes more accidental breaches than anything else. If your printer needs the font, either send outlined vectors, send a properly embedded print PDF (check that the EULA permits embedding for output), or ask the printer to license their own copy.
Seat counting, in practice
Seats usually mean people or devices, not simultaneous users. A studio of eight designers where five occasionally open the file still needs enough seats to cover every installation. Laptops, desktops and home machines all count in most EULAs.
Webfont licenses: metered, domain-bound and easy to outgrow
A webfont license covers serving font files to browsers, whether self hosted with @font-face or delivered from the foundry’s CDN. Three variables define almost every webfont agreement:
- Traffic volume. Sold in tiers of monthly pageviews or unique visitors. Popular tiers start at 10,000 or 50,000 and climb from there.
- Domain restriction. Many licenses cover a single domain. Staging subdomains, landing page domains and country variants may each need to be declared.
- Delivery method. Some foundries require their hosted service; others allow self hosting but insist the files sit behind a path that is not publicly browsable.
A successful campaign is the most common way to breach a webfont license. If a site jumps from 40,000 to 400,000 monthly pageviews, the license does not stretch automatically. Set a calendar reminder to review traffic against your tier every quarter.
Self hosting vs hosted service
| Factor | Self hosted | Foundry hosted |
|---|---|---|
| Performance control | Full, you control caching and preload | Dependent on their CDN |
| Compliance tracking | You must self report traffic | Tracked automatically |
| Privacy and GDPR | Cleanest option, no third party request | Requires a check on data transfers |
| Risk if it lapses | Font keeps rendering, breach continues silently | Font stops loading, you notice immediately |
App and embedding licenses
The moment a font file is packaged inside something a user downloads, you are distributing software. That needs an app license, sometimes called an embedding or OEM license.
You need one when the font is bundled in:
- iOS, Android or cross platform mobile apps
- Desktop software and Electron builds
- Video games and game engines
- Kiosks, ATMs, car dashboards, appliance screens and other embedded devices
- Templates or digital products you sell to other people
Pricing is usually per application title and per platform, occasionally scaled by install count. A common misunderstanding: designing app screens in Figma is desktop use, shipping the build with the font inside is app use. Two different licenses, two different budgets.
Broadcast, video and advertising licenses
Motion work is where costs escalate fastest. A broadcast license may be required for television, streaming platforms, cinema, out of home digital displays and paid video advertising. Foundries price it by production, by campaign duration, by territory or by audience reach.
The grey area is social video. Organic content posted to your own channel is often covered by a desktop license because the output is a rendered video file, not a font file. As soon as there is paid media spend behind it, check the EULA again. Several foundries treat paid advertising as a separate use class regardless of platform.
Logo and trademark use: the clause nobody reads
You are typically allowed to set a logo in a licensed font under a standard desktop license, because the output is vector artwork. The complication arrives when the client wants to register the wordmark as a trademark.
Three positions exist in the market:
- Permitted without extra fee. Common among open source fonts and some independent foundries.
- Permitted with an extended logo license. A one-off fee, often a multiple of the base price.
- Not permitted at all. A handful of foundries forbid trademark registration outright, especially for fonts with highly distinctive letterforms.
Because a logo is the single hardest asset to change later, check the trademark clause before you present the concept, not after the client falls in love with it. Customising the letterforms substantially is a common practical solution, and it produces a stronger mark anyway.
Free fonts: free does not mean unrestricted
There are at least four categories hiding behind the word “free”. It is argued more carefully on onlinelabels.com.
| Category | Commercial use | Key conditions |
|---|---|---|
| SIL Open Font License (most Google Fonts) | Yes, desktop, web, app, all uses | Cannot be sold on its own; modified versions must not use reserved names; keep the license file with the font |
| Apache 2.0 (some Google Fonts) | Yes | Attribution and notice requirements |
| “Free for personal use” | No | Any client work, any revenue generating project requires a paid upgrade |
| Free demo or trial weights | No | Often limited character sets, evaluation only |
Also be wary of free font aggregator sites that repackage commercial fonts without permission. If a font that normally costs a few hundred euros per weight is offered free with no foundry name attached, it is almost certainly pirated, and downloading it puts the liability on you.
Subscription platforms: Adobe Fonts, Google Fonts, Canva and Monotype
Adobe Fonts
Fonts activated through a Creative Cloud subscription are licensed for personal and commercial use, covering desktop and web for the fonts included in your plan. The important constraints: the license lives with the active subscription, you generally cannot hand the font files to anyone else, and you cannot embed the files in an app or sell them on. When a subscription lapses, the fonts deactivate and live documents can break. For a client brand that must survive independently of your agency’s subscription, buy a perpetual license instead.
Google Fonts
The library is open source, which makes it the safest default for most web and product work. You may self host, modify and ship the files inside apps. Keep the license file alongside the fonts when you redistribute them, and do not release a modified version under a reserved font name.
Design platforms and templates
Fonts inside platforms such as Canva, Figma, Wix or Squarespace are licensed for use within that platform. That permission does not travel. Downloading the file and installing it locally, or reusing it on a different site, is outside the terms in most cases.
Monotype, MyFonts and foundry subscriptions
Subscription libraries are excellent for exploration and volume work, but read the termination clause. Some allow you to keep using work created during the subscription; others require you to stop using the typeface entirely when you cancel. For a permanent brand identity, perpetual licensing remains the lower risk route.
Client work: who actually buys the license?
Short answer: the client should own the license in their own name. The font license is part of the brand asset package, not part of your studio overhead.
Practical model that works well:
- You license or trial the font for exploration under your own desktop seats.
- You present the direction with the licensing cost and the required use classes clearly itemised.
- The client purchases the license in the client entity’s name, for the use classes they actually need.
- You receive the files under the terms of that license, or you are named as an authorised contractor if the EULA supports it.
- You document everything in a handover sheet.
Add a line to your contracts stating that font licensing is a third party cost, that the client is responsible for maintaining it, and that your studio is not liable for usage beyond the licensed scope after handover.
How to check a font license before you use it: the 8 point audit
- Find the actual EULA. Not the marketing page. The PDF or text file that came with the download, or the version on the foundry site dated to your purchase.
- Identify every use class the project needs. Print, web, app, video, server, logo, ebook. Write them down before you shop.
- Count the seats honestly. Everyone who will install the font, including contractors and the client’s internal team.
- Estimate web traffic 12 months out, not today’s numbers.
- Search the EULA for the trigger words: logo, trademark, embed, server, broadcast, redistribute, modify, transfer, subcontractor, pageviews.
- Check the modification clause if you plan to customise glyphs or subset the file. Subsetting for web performance is forbidden by some foundries.
- Confirm the term. Perpetual, annual or tied to a subscription.
- Keep the receipt. Invoice, order number, EULA version and purchase date, stored somewhere that survives staff turnover.
If any clause is ambiguous, email the foundry. Independent foundries answer quickly and are usually flexible. A short email thread confirming permission is worth far more than an assumption, and it becomes your evidence if anyone questions the usage later.
What actually happens if you use a font outside its license
Font compliance enforcement is a real and active business. Larger foundries and their partners run automated detection that crawls websites, inspects CSS, scans PDFs and reads font metadata embedded in published files. Here is the typical sequence. This write-up is worth a look.
- Detection. A crawler flags a font file on your domain or in a public PDF with no matching license record.
- Contact letter. You receive an email or letter, often from a legal firm acting for the foundry, listing the detected usage and requesting evidence of a license.
- Evidence request. They may ask how many machines have the font installed, how long the site has used it and what traffic it receives. You are not obliged to over-share, but ignoring the letter rarely helps.
- Settlement demand. Typically the cost of the license you should have bought, backdated across the period of unlicensed use, plus administrative or legal fees. Amounts range from a few hundred to five figures depending on the scale of use.
- Escalation. Unresolved cases can lead to formal copyright infringement claims, takedown requests or court action, though most settle before that point.
The commercial damage beyond the invoice
- Emergency rebranding or site restyling on a deadline
- Pulled print runs and packaging already in a warehouse
- A client who blames the agency and does not renew
- Indemnity clauses in your own contract pointing the bill back at you
Note that the party who published the work is usually the one contacted, but agency contracts frequently include warranties that all assets are properly licensed. That makes the studio the ultimate payer.
The five most common accidental breaches
- A font bundled with software (Office, Adobe apps, a plugin, a theme) reused outside that software’s terms
- Fonts inherited from a previous agency with no paperwork at all
- A “free for personal use” display font in a paid client logo
- A desktop-only license used with @font-face because it technically works
- A webfont license bought for one domain, then copied to a campaign microsite
Building a font licensing system that scales
Compliance fails because of process, not ignorance. A few habits remove almost all the risk.
- Keep a font register. A simple spreadsheet: font name, foundry, license type, seats, domains, purchase date, invoice link, expiry, project.
- Store EULAs with the font files in your asset library, not in someone’s inbox.
- Maintain an approved list of fonts your team can use freely (open source plus your owned licenses) and require a sign off for anything outside it.
- Add a licensing line to project kickoff. One question: which use classes does this project need?
- Review annually. Traffic tiers, seat counts, expiring subscriptions and staff changes.
- Use font management software if your team is above roughly ten designers. It tracks installs and flags unlicensed activations automatically.
- Brief developers explicitly. Development teams routinely install fonts on build servers with no idea a license is involved.
How much does font licensing cost?
There is no single answer, but these ranges reflect the current market and help with budgeting.
| Scenario | Indicative cost |
|---|---|
| Single weight, desktop, 1 to 5 seats, independent foundry | 30 to 90 EUR |
| Full family, desktop, small studio | 200 to 900 EUR |
| Webfont, up to 250k monthly pageviews | 80 to 500 EUR per family |
| App embedding, one title, one platform | 300 to 3,000 EUR |
| Broadcast campaign | 500 to 10,000 EUR and up |
| Corporate license, mid-sized company, annual | 2,000 to 25,000 EUR |
| Custom typeface commission | 15,000 EUR and up |
Put those numbers next to a retroactive settlement and the maths is obvious. Licensing is one of the cheapest forms of insurance in a design project.
Quick decision guide
- Print, packaging, static images, PDFs to view: desktop license
- Live website with real text: webfont license, sized to traffic, per domain
- Font file shipped inside a downloadable product: app or embedding license
- Font rendered automatically by a server: server license
- Paid video or TV: broadcast license
- Registered wordmark: check the trademark clause, budget for an extended license
- Not sure: email the foundry and keep the reply
FAQ
Do I need a license to use a font?
Yes, every font comes with a license, including free ones. The question is never whether a license exists but what it permits. Fonts that arrive with your operating system or design software are licensed for use within that environment, which is not the same as an unrestricted commercial license.
Is a desktop license enough for a website?
Only if the font appears as flattened images or outlined vectors. If the browser downloads a font file to render live text, you need a webfont license.
Can I use a font in a client logo?
Usually yes for creating the artwork under a standard desktop license. Registering that logo as a trademark is a separate question and some EULAs require an extended license or forbid it entirely. Check before presenting.
Are Google Fonts really free for commercial use?
Yes. The library is released under open source licenses, mainly the SIL Open Font License, which permits commercial desktop, web and app use. You cannot sell the fonts themselves, and modified versions must not carry reserved names.
Does my Adobe Creative Cloud subscription cover client work?
Adobe Fonts are licensed for personal and commercial use, including desktop and web, while your subscription is active. You cannot pass the font files to a client or a contractor, and embedding in apps or products for redistribution is not covered. For a permanent brand asset, buy a perpetual license from the foundry.
What if I inherited fonts from a previous agency?
Treat them as unlicensed until proven otherwise. Ask for the invoice and the EULA. If nothing exists, either license the fonts properly or replace them. Continuing to publish with them keeps the liability alive.
Can I modify a font I licensed?
It depends entirely on the EULA. Open source fonts under the OFL allow modification with naming conditions. Many commercial licenses prohibit modification, including subsetting for web performance, without written permission.
How do foundries find unlicensed use?
Automated crawlers that inspect website CSS and font files, metadata embedded in published PDFs and documents, and reports from designers and foundry partners. Detection is far more systematic than most teams expect.
Final word
Font licensing is not complicated once you stop thinking about “buying a font” and start thinking about buying permission for specific uses. Define the use classes at the start of the project, read the EULA for the trigger words, put the license in the client’s name and keep the paperwork. Ten minutes of checking protects a project that took months to build.
If you would like help auditing the typography across your brand, website and product, the team at PixelBright can review your current usage and put a clean licensing register in place.