Understanding Font Licensing: What Can You Legally Use?

A client sends you a brand guide that specifies a typeface, along with a ZIP file of OTF files their previous designer "had lying around." You convert them to WOFF2, drop them into the site, and launch. Six months later the client receives an email from the foundry's licensing team asking for proof of a web license, along with an invoice that is several times what the license would have cost up front. This situation is common, and it almost always comes from the same misunderstanding: owning a font file is not the same as having permission to use it everywhere.

This article explains how font licensing actually works, the main license types you will encounter, what open-source licenses like the SIL Open Font License allow, how to read a license agreement for the clauses that matter, and how to keep records so you can prove compliance. It is practical guidance for designers and developers, not legal advice; for high-stakes situations, read the actual license and ask the foundry or a lawyer.

What Is a Font License?

A font is software. When you "buy a font," you are almost never buying the typeface design or the file itself. You are buying a license: a contract that grants you specific rights to use the font software under specific conditions. The foundry, or type designer, keeps ownership.

That has two important consequences:

1. The license defines what is allowed. Anything the license doesn't explicitly permit is generally not permitted.
2. Different uses need different licenses. Installing a font on your computer to design a poster, embedding it on a website, bundling it in a mobile app, and using it in a logo are often covered by separate license types, each with its own terms and pricing.

In many jurisdictions, including the United States, the design of a typeface (the shapes of the letters) has limited or no copyright protection, but the font software that draws those shapes is protected as a computer program. That's why licensing focuses on the files and how they are distributed, and why redrawing a typeface from scratch is legally different from copying its files. Don't read too much into that distinction, though: many typeface names are trademarked, some designs are protected by design patents or design rights, and foundries enforce their software rights actively.

The Main License Types

Commercial foundries split licenses by use. Names vary, but these categories are close to universal:

License type	What it covers	Usually priced by
Desktop	Installing on computers to create static output: print, images, PDFs, logos	Number of users or computers
Web	Embedding with @font-face on websites	Monthly pageviews or domains
App	Embedding in mobile or desktop applications	Number of apps or titles
ePub / digital publication	Embedding in ebooks and digital magazines	Number of titles
Server / SaaS	Fonts used on a server to generate output for customers (for example, a custom print or PDF generator)	Negotiated
Broadcast / video	On-screen use in film, TV, streaming, or ads	Production or campaign
Enterprise	Broad, organization-wide use across many media	Negotiated

The key takeaway is that a desktop license does not cover web use. Converting a desktop OTF file to WOFF2 and serving it from your site is a classic violation, even if you paid for the desktop license.

What Web Licenses Typically Include

Web licenses usually set conditions like these:

• Pageview limits, such as 10,000, 100,000, or 1,000,000 pageviews per month, with upgrades required as traffic grows.
• Named domains where the font may be served. Staging and development domains are often allowed; check.
• File protection requirements, such as not making the font files directly downloadable as installable fonts, or serving them only to pages on licensed domains.
• Format restrictions, such as allowing only the web font formats supplied by the foundry and forbidding conversion or modification.
• Self-hosting vs. hosted service, with some licenses permitting self-hosting and others requiring the foundry's hosted CSS.

Some foundries sell perpetual web licenses with a one-time fee for a pageview tier; others sell subscriptions. Read the license to find out which you have.

Logos and Brand Use

Using a font to design a logo usually falls under the desktop license, because the logo is static artwork. Most foundries allow it, but some restrict trademark registration of logos that consist only of unmodified type, or require an extended license. Check before your client files a trademark.

Open-Source and Free Font Licenses

Free fonts come with licenses too, and some are far more permissive than others.

The SIL Open Font License (OFL)

The SIL Open Font License 1.1 is the most common open font license and covers the vast majority of fonts on Google Fonts. It allows you to:

• Use the font for any purpose, commercial or personal, in print, on the web, in apps, in logos, and in products.
• Embed it in websites, PDFs, documents, and software.
• Redistribute the font, including bundled with other software.
• Modify the font and distribute modified versions.

The conditions are short:

1. You can't sell the font by itself. Bundling it with software is fine; selling the font files alone is not.
2. Reserved Font Names. If the font declares a Reserved Font Name, modified versions can't use that name. This matters if you subset or otherwise alter a font and redistribute it.
3. Derivatives must stay under the OFL. Modified fonts must be released under the same license.
4. Keep the copyright notice and license with any redistributed copies.

For web developers, the practical meaning is: OFL fonts are free to self-host, subset, and serve on commercial sites. Subsetting for your own site is generally considered acceptable; the Reserved Font Name concern mainly applies when you distribute modified files as fonts in their own right. Many projects avoid any ambiguity by giving their subsets a different internal family name.

Apache License 2.0

Some fonts, including older Google releases such as earlier versions of Roboto and Open Sans, use the Apache License 2.0. It is also permissive, allowing commercial use, modification, and redistribution, with requirements to preserve notices and state changes.

"Free for Personal Use"

This is where people get into trouble. Many fonts on free font sites are labeled free for personal use only. That means:

• No commercial websites, including your own business site or a client site.
• No logos, products, or marketing materials for a business.
• Sometimes no web embedding at all.

"Personal use" is narrow. A blog with ads, a portfolio you use to get work, or a nonprofit's site may all count as commercial depending on the license wording. If a font is free for personal use and you need it for a commercial project, buy the commercial license.

Public Domain and CC0

A few fonts are dedicated to the public domain or released under CC0. These carry essentially no restrictions, though trademarks on the name may still apply.

Licenses for Font Services

Font subscription and hosting services have their own terms layered on top.

• Google Fonts: The fonts are open source (mostly OFL), so you can self-host them or use the Google Fonts API. Privacy is a separate question from licensing, discussed in whether Google Fonts are GDPR-compliant.
• Adobe Fonts: Included with Creative Cloud subscriptions. Web use is through Adobe-hosted web projects; you generally can't download and self-host the files. When the subscription ends, the license to use the fonts on the web ends too. The setup is covered in how to use Adobe Fonts on your website.
• Monotype, Fontstand, and other subscriptions: Terms vary widely. Some grant perpetual rights to output created during the subscription; few allow continued web serving after cancellation.

Subscription models are convenient, but they create an ongoing dependency. If your client's site depends on a font tied to your personal subscription, the site breaks when you cancel.

How to Read a Font License: The Clauses That Matter

Font licenses are often called EULAs (end user license agreements). They're usually short enough to read in ten minutes. Look for these points:

1. Licensee: Who holds the license? It should be the client or organization that owns the site, not the freelancer who built it.
2. Permitted media: Desktop, web, app, ePub, broadcast. Is your use listed?
3. Limits: Pageviews, users, domains, apps, or titles.
4. Hosting: Can you self-host? Must you use a hosted service? Must files be protected?
5. Modification: Can you subset, convert formats, or alter metrics? Many commercial licenses forbid modification, but some allow subsetting for web performance.
6. Term: Perpetual or subscription? What happens if you stop paying?
7. Transfer: Can the license move to a client, a new owner, or a new company after an acquisition?
8. Territory and audit rights: Some licenses allow the foundry to audit usage.

Write the answers down. That summary becomes your record.

Practical Rules for Designers and Developers

These habits prevent nearly every licensing problem:

• License in the client's name. The client owns the site and should own the license. Buy it on their account or transfer it to them at handoff.
• Check the source of every font file. Files from a brand folder, a coworker, or an old project come with no proof of license. Trace them to a purchase.
• Match the license to the medium. Website needs a web license. Mobile app needs an app license. Ads in video need a broadcast license.
• Track pageview tiers. A site that grows past its tier needs an upgrade.
• Prefer open fonts when budget or simplicity matters. OFL fonts remove the paperwork entirely, and the quality gap has narrowed dramatically. The trade-offs are explored in free vs. premium fonts.
• Keep license files with the project. Store the license PDF or text and the receipt in the repository or the project's documentation.

A simple way to keep records in a codebase is a fonts manifest next to the files:

{
  "fonts": [
    {
      "family": "Inter",
      "files": ["public/fonts/inter-var.woff2"],
      "license": "SIL Open Font License 1.1",
      "source": "https://github.com/rsms/inter",
      "licensee": "n/a (open source)"
    },
    {
      "family": "Example Serif",
      "files": ["public/fonts/example-serif-regular.woff2"],
      "license": "Foundry Web License, 250k pageviews/month",
      "source": "Invoice #2026-0412",
      "licensee": "Client Company Ltd"
    }
  ]
}

You can also inspect the license and copyright fields embedded in a font file with fontTools:

pip install fonttools
python3 -c "
from fontTools.ttLib import TTFont
f = TTFont('example.woff2')
for rec in f['name'].names:
    if rec.nameID in (0, 7, 8, 13, 14):
        print(rec.nameID, rec.toUnicode())
"

Name IDs 0, 7, 8, 13, and 14 hold the copyright, trademark, manufacturer, license description, and license URL. These fields are informational, not proof of a license, but they tell you who made the font and where to find its terms.

Font Licensing FAQ

Conclusion

Font licensing feels complicated mainly because the word "font" covers several different rights. Once you treat a font as licensed software, the logic becomes clear: the license defines who may use the font, in which media, at what scale, and under what conditions. Desktop, web, app, and other uses are separate, and owning the file never grants rights the license doesn't.

For most web projects, the decision is straightforward. Use openly licensed fonts when they meet the design need, and when a commercial typeface is the right choice, buy the correct web license in the client's name, respect its pageview and hosting terms, and keep the paperwork with the project. That small amount of diligence costs far less than an audit letter.

Here are some useful references for going deeper on font licensing:

1. SIL International: SIL Open Font License — the full text of the OFL and its official FAQ.
2. Google Fonts: Google Fonts FAQ — licensing and usage questions for the Google Fonts library.
3. Adobe: Adobe Fonts licensing — what Adobe Fonts subscriptions allow for web, desktop, and apps.
4. Google Fonts Knowledge: Google Fonts Knowledge — articles on type, including how open font licensing works.
5. Microsoft Typography: The name table — reference for the copyright and license fields embedded in font files.