By Mehdi HassanWhat is font licensing and why does a brand need it?
Font licensing is the legal permission a foundry grants you to use its typeface in defined ways. When you buy a font, you don't buy the font itself; you buy a license, governed by an end-user license agreement (EULA), that says where, how and by how many people it can be used. Using a font outside that scope is a license breach, even if you paid for it.
For a startup, the risk usually isn't a lawsuit on day one. It's an awkward discovery later: during fundraising due diligence, an acquisition, a rebrand, or when a new agency asks for the font files and nobody can find a license. Type is part of the identity system covered in our framework on how to choose brand colors, and it needs the same paperwork as your logo files.
This is practical guidance, not legal advice. Every foundry writes its own EULA, so always read the actual agreement for each font you use.
What font licenses does a brand need?
Most brands need two or three license types, depending on where the font appears. Foundries split rights by medium because each medium distributes the font differently: a desktop file stays on a computer, a web font is served to every visitor, and an app font is bundled into software that thousands of people install.
License type | What it covers | Usually priced by | Who needs it |
|---|---|---|---|
Desktop | Installing the font to design documents, decks, print and images | Number of users or computers | Designers, marketing, anyone making assets |
Web | Serving the font on a website with CSS font-face | Monthly pageviews or domains | Any brand using the font on its site |
App | Embedding the font inside a mobile or desktop app | Number of apps or titles | Products that ship the font in a build |
Digital ads | Using the font inside banner and display ads | Ad impressions or campaigns | Teams running HTML5 ad campaigns |
Video and broadcast | Using the font in videos, motion and broadcast | Production or audience size | Brands producing video at scale |
Server or SaaS | Using the font on servers to generate documents or images for users | Custom quote | Products that render PDFs, cards or images |
Pricing models and terms vary widely, so check each foundry's current license page. Some sell bundles that cover several uses, and some offer a single all-uses license for larger companies.
Is a font license for a logo different?
Using a font to create a logo is usually covered by a standard desktop license, because you're creating an image or outlined artwork rather than distributing the font file. Most foundries allow this. A minority restrict it, require an extended license, or limit using the font in a registered trademark, which is why you read the EULA before you file.
There's a second issue people miss: you can't own the letterforms of a typeface someone else drew. If your wordmark is a commercial font typed out in one weight, a competitor could set their name in the same font. Strong wordmarks modify spacing, letter shapes or details so the result is distinctly yours, which also makes the trademark stronger. It's one of the quiet differences between a designer-made logo and a generated one, as we discuss in AI logo generator vs hiring a designer.
Do free and open-source fonts need a commercial font license?
Most free fonts on Google Fonts are released under the SIL Open Font License (OFL) or the Apache License, which allow commercial use on the web, in apps, in print and in logos without paying or registering. That's why open-source fonts are such a good fit for early-stage brands; our list of free fonts for branding covers the best options by role.
The OFL has a few conditions worth knowing. You can't sell the font files on their own, modified versions may need a different name if the original uses a Reserved Font Name, and the license text should travel with the font files if you redistribute them. Fonts from free download sites are a different story: many are free for personal use only, and a commercial license is a separate purchase.
- Safe to assume free for commercial use: fonts downloaded from Google Fonts, with the license file checked.
- Check carefully: fonts from aggregator sites labelled free, which often mean personal use only.
- Never assume: fonts copied from another computer, a template or a design tool's library.
Who should own font licenses after a branding project?
The company should own every font license, in its legal name, with invoices on file. Licenses are typically non-transferable, so a font a designer or agency bought under its own account doesn't become yours when the project ends. If a designer used their license to design your logo, that's normal, but your team will still need its own licenses to keep producing assets and to run the website.
Agree this before the project starts. A good brief names which fonts are candidates, who buys the licenses, and in what scope. We recommend clients buy licenses directly, so the account, receipts and renewal emails stay with the company. Licenses belong in the handoff alongside logo files and guidelines, because, as we argue in what is branding, a brand is a system you keep running, not a file you receive once.
Shortlist with licensing in mind
Before falling for a commercial typeface, check the foundry's web, app and logo terms and whether pricing scales with your expected traffic.
Buy in the company name
Create the foundry account with a shared company email, not a personal or agency address, and pay with a company card.
Match scope to use
Buy desktop seats for the people who make assets, a web license sized to your traffic, and app licenses only if the font ships in a build.
Record everything
Add each font to a register with license type, scope, invoice, account owner and any renewal or traffic limit.
Review at milestones
Recheck scope when traffic grows, a native app launches, or you hire more designers, because these often push you past the original tier.
What do startups get wrong about web font licenses?
The most common web font license mistake is self-hosting a desktop font file on the website. A desktop license doesn't cover serving the font to visitors, even if the file technically works. The second is outgrowing a pageview tier and never upgrading, which is easy to miss after a successful launch.
Other mistakes we see often: an agency that bought the web license on its own account, an app built with fonts licensed only for the web, and design files using fonts nobody on the team has a license for. Each of these is cheap to fix early and expensive to discover in due diligence. Self-hosting licensed fonts correctly also affects performance, which our guide to web font performance covers.
Hypothetical example: a startup that outgrew its type licenses
For example, suppose a seed-stage SaaS company chose a commercial typeface for its brand. The freelance designer bought a desktop license on their own account, used it to make the logo, and set up the website with the same font files.
Two years later, the company launches a mobile app and hires an in-house designer. In preparing for a funding round, the team finds that no license exists in the company's name, the website has never had a web license, and the app needs an app license too.
The fix is straightforward: buy desktop seats, a web license sized to current traffic and an app license in the company's name, then record them in a font register. It's the same work they'd have done at the start, only later and under deadline pressure. This is an illustration, not a client case.
How do you keep a font register for your brand?
A font register is a simple table that records every typeface your brand uses and the rights you hold for each. It's quick to set up and saves a lot of digging later. Keep it next to your brand guidelines and update it whenever you add a font, a product or a team member who makes assets.
Each row should include the font family and weights, the foundry, the license type and scope, the account and owner, the invoice or license file, and any limits like pageviews or seats. If you use open-source fonts, record the license name and keep the license text with the font files. When you move from guidelines to a live website, our guide on translating a brand identity into a website shows where type rules fit in the handoff.
