Font Licensing Guide

Commercial vs Personal Font Licenses

Font licenses are not interchangeable. Using a personal-use font in a paying client project or business website is copyright infringement, even if you downloaded it legally. The trigger for upgrading from personal to commercial is any form of revenue or business activity attached to the work, not the quality of the project or the size of the audience.

What Personal-Use Means

A personal-use license grants permission to install and use a typeface exclusively for non-commercial, private purposes: school assignments, hobby design, personal journals, or creative experiments that generate no revenue. The qualifier is not who sees the result - it is whether any economic activity is attached to it. "Free for personal use" does not mean "free for any use." A personal blog with advertising, a monetized YouTube channel, or a newsletter with paid sponsorships is commercial under most EULAs.

What Commercial Means

A commercial license grants permission to use a typeface in contexts tied to revenue generation, business promotion, or client deliverables. Commercial licenses are not monolithic. Most foundries sell several distinct tiers, each covering a specific deployment channel: desktop (installation + print), web (@font-face delivery, capped by pageviews), app (binary embedding), and ebook/PDF (document distribution). Buying one tier does not grant rights in another. Use our font license checker to inspect a font file's embedded metadata and verify which deployment channels your license actually covers.

Side-by-Side Comparison

When You Must Upgrade

Any of the following almost universally require a commercial license:

How to Read a Font EULA

A font EULA is a legally binding contract. Pay particular attention to the Restrictions and Modifications clauses, since they govern whether you can legally convert or subset a font file (covered in detail below).

Common Licensing Mistakes

Web Embedding Restrictions

Font licensing for the web operates under entirely different rules than desktop use. A desktop license grants nothing when it comes to serving fonts to a browser. Every visitor who loads a page retrieves the font file - that is fundamentally different from a single designer installing on their workstation. Foundries treat web use as a separate commercial right, often priced by traffic volume.

Web vs Desktop License Rights

The most common font licensing mistake is assuming a desktop license covers web use. It does not. A web license grants the right to host font files on a server and serve them to browsers via CSS - this distributes the font file itself to every visitor. Web delivery also requires the correct format; WOFF2 is the modern standard and offers the best balance of compression and browser support.

@font-face and Format Conversion

Using @font-face to serve a font means distributing the file to every visitor - the license must explicitly permit this. Look for "web font license," "embedding in web pages," or "@font-face permitted." If the EULA only discusses installation on computers, it is desktop-only.

Self-Hosting Permissions

Self-hosting means serving font files from your own infrastructure rather than a foundry CDN or service. It is technically straightforward but legally requires explicit permission. Some foundries require their hosted service for usage tracking; others permit or encourage self-hosting. When self-hosting is permitted, use our webfont generator to produce optimised WOFF2 files ready for deployment.

CDN and Third-Party Hosting

CDN licensing implications vary by license type. For a deeper comparison of trade-offs, see our guide to self-hosted fonts vs CDN delivery.

Pageview Caps and Traffic Tiers

Commercial web font licenses are almost always tiered by traffic volume. Tier names and boundaries vary by foundry, but a typical structure looks like:

Pageview definitions in font licenses do not always match analytics definitions. Most count any request that serves the font; some count unique pageviews. Bots and crawlers usually do not count, but verify in your EULA. If you self-host, you are responsible for tracking against the licensed limit. Exceeding the cap is a contract breach - upgrade proactively before crossing into the next tier. For variable traffic (media sites, viral content), buy at least one tier above your typical monthly traffic to avoid spike-driven overages.

CORS and Technical Compliance

CORS is a technical, not licensing, concern - but configuring it correctly also acts as a practical enforcement layer for domain-restricted licenses. Without proper CORS headers, browsers block cross-origin font requests. If you encounter CORS errors, our guide to fixing CORS errors for web fonts walks through server-side configuration.

Nginx configuration:

location ~* \.(woff|woff2|ttf|otf|eot)$ {
    add_header Access-Control-Allow-Origin "https://www.yourdomain.com";
    add_header Access-Control-Allow-Methods "GET, OPTIONS";
    add_header Cache-Control "public, max-age=31536000";
    expires 1y;
}

Apache .htaccess:

<FilesMatch "\.(woff|woff2|ttf|otf|eot)$">
    Header set Access-Control-Allow-Origin "https://www.yourdomain.com"
    Header set Access-Control-Allow-Methods "GET, OPTIONS"
    Header set Cache-Control "public, max-age=31536000"
</FilesMatch>

For commercial fonts, restrict CORS to your specific origin or a whitelist of your domains - not wildcard - to prevent hotlinking that could exhaust your pageview tier. For OFL/Apache 2.0 fonts where redistribution is permitted, wildcard origins are acceptable. Always add crossorigin="anonymous" to <link rel="preload"> tags for fonts so the browser reuses the cached response from the @font-face fetch.

Modification & Subsetting Rights

"Modification" in a font license covers a broader range of actions than most people expect. Glyph editing is obvious modification. So is renaming, merging, or changing metrics. But the legal definition extends to actions that feel technical or even automatic - subsetting, format conversion, hinting changes, axis locking on variable fonts.

Font software is protected by copyright. Even technically simple operations - running a font through a compression tool, stripping unused OpenType features - may require explicit permission. Always check your specific license before any change.

OFL Modification Rules

The SIL Open Font License is the most widely used open-source font license and one of the most permissive on modification. It explicitly permits glyph editing, subsetting, format conversion, merging, and redistribution including commercially as part of a software bundle. The two key restrictions are the Reserved Font Name clause and the copyleft requirement.

Reserved Font Name (RFN): When an author designates a font name as reserved, you cannot use that name for any modified version. If you fork Lato or Inter, you must rename your derivative. Internal use without redistribution may not require renaming, but check the specific license; when in doubt, rename.

Copyleft: Any modified OFL font you distribute must also be released under the OFL. You cannot relicense a derivative under a more restrictive commercial license. This applies only when distributing modified font files - using an OFL font in a commercial product, embedding it in a website, or including it in an app does not trigger the copyleft.

Subsetting Legality

Subsetting removes characters your project does not use, often reducing file size by 50-80%. From a technical standpoint, it is a form of modification. Whether it is permitted depends entirely on your license.

A common misconception is that because subsetting is so widely practiced, it must be universally accepted. Many foundries tacitly accept it because enforcement is impractical - but tacit acceptance is not legal permission. If your EULA says "you may not modify the font software" and contains no web exception, subsetting is technically a violation even if no foundry has ever enforced it. Our font subsetter performs the technical operation, but the legal right to subset depends on your license.

Commercial Modification Restrictions

Variable Font Axes

Variable fonts contain a continuous design space defined by axes (weight, width, slant). For implementation details and performance trade-offs, see our guide on variable font performance.

Using axes through CSS is not modification. Setting font-weight: 350 or font-variation-settings uses the font as designed.

body {
  font-family: 'Inter Variable', sans-serif;
  font-weight: 350;
  font-variation-settings: 'wdth' 85, 'opsz' 18;
}

Extracting a static instance is modification. Generating a standalone weight-500 OTF from a variable font produces a new file. Permitted under OFL; usually not under commercial licenses (some explicitly prohibit it because foundries sell static instances separately). Programmatically locking an axis in the binary is also modification.

Rasterization vs Embedding

Rasterizing text into a static image, PDF, or other format where characters are no longer separate text objects is generally not modification. The font produces output but the output does not contain font data. Logos as PNGs, exported presentations, social media images - all permitted by virtually all commercial licenses.

Embedding in a PDF or e-book includes actual font data (or a subset). This is a different question requiring its own permission. Most desktop EULAs cover PDF embedding from your design app, but server-side PDF generation, redistributable documents, and ebook embedding (ePub, MOBI) often require separate license tiers. Check for clauses on document distribution, ebook rights, and server-side generation.

Open Source Font Licenses

"Open source font" carries two meanings. First, the source files are publicly available. Second - and more practically relevant - the license grants broad rights to use, redistribute, and often modify without paying or asking permission. This is fundamentally different from "free to download" - a font can be free to download while still being restrictively licensed (personal-use only, no commercial, no embedding). Open source means the license is genuinely permissive in a legally specific way.

Most fonts in the Google Fonts catalogue are open source under either OFL or Apache 2.0. Open source fonts also exist on GitHub, Font Squirrel's "100% Free" category, and dedicated foundries like Omnibus-Type and Production Type. The ecosystem now includes variable, color, and non-Latin fonts at professional quality.

SIL Open Font License (OFL)

The OFL was designed specifically for fonts and is the dominant open-source font license. It grants four core freedoms: use in any project (commercial OK), study/modify, redistribute, and distribute modified versions. No fees, no contact required.

Reserved Font Name (RFN)is the part that catches people off guard. If you modify Roboto or Inter and the name is reserved, you must rename your derivative. This protects the original author's reputation while keeping the font available for community improvement.

The standalone-sale prohibition means you cannot sell the font file by itself as the product. You can sell software, apps, templates, or bundles that include the font - just not the font alone.

Attribution is not required in your final product under the OFL. No credit line in your website footer or app About screen. However, if you redistribute the font files themselves (in a GitHub repo or downloadable template), include the original copyright notice and full OFL text alongside.

Apache 2.0 for Fonts

Apache 2.0 was created for software but applies cleanly to fonts. It is more permissive than OFL in three ways:

• No copyleft - derivatives can be released under any license, including proprietary
• No Reserved Font Name concept - rename your derivative anything
• No restriction on selling the font as a standalone product

Attribution requirements: include the original copyright notice, Apache 2.0 license text, and any NOTICE file when distributing the source form (the font files). In the "object form" (your compiled website, app binary, finished design), attribution is not required. For most web work, OFL and Apache 2.0 behave almost identically.

Creative Commons

Creative Commons is a family of licenses, not one license. "Creative Commons font" tells you almost nothing without the variant. CC was designed for creative works (photos, illustrations, writing), not specifically for fonts, which creates edge cases.

When you encounter a CC font, always check the variant. Anything containing "NC" (NonCommercial) or "ND" (NoDerivatives) imposes serious restrictions. For fonts specifically, OFL and Apache 2.0 are usually safer choices than CC because they were designed with fonts in mind.

Public Domain

Public domain is a legal status, not a license. A font enters the public domain when copyright expires, when the creator explicitly waives rights, or when the work was never eligible for copyright. CC0 is the most legally robust mechanism for dedicating a new font to the public domain - informal "this is public domain" declarations may not be enforceable in all jurisdictions.

License Comparison Table

Quick reference for the five most common open-source / free font license types. To verify embedded license metadata of any font file, use our font license checker.

Google Fonts License Guide

Google Fonts are unambiguously free for commercial use. Every font in the catalogue is released under either the SIL Open Font License or Apache 2.0 - both approved open-source licenses. Google does not charge for the fonts or for traffic served through its CDN. There are no subscription tiers, pageview limits tied to payment, or hidden licensing walls at commercial scale.

Apache 2.0 vs OFL on Google Fonts

Most Google Fonts use OFL; some (notably Roboto and variants) use Apache 2.0. Both allow commercial use, web embedding, modification, and redistribution. For typical users, the practical difference is zero. The distinction matters mainly if you are building fonts - OFL requires derivatives stay OFL, Apache 2.0 has no such requirement.

Commercial and Client Use

No fees, royalties, special permissions, or paperwork required. You can use any Google Font on a business website that sells products or services, in client deliverables (including handing the font files to the client), embedded in mobile apps distributed on App Store or Google Play, in commercial e-books, and in advertising of any kind.

No pageview limits or domain restrictions - a meaningful advantage over tiered commercial fonts. You will never need to upgrade a tier because traffic grew. Use the same fonts across unlimited client projects without additional licenses.

For agencies, this means using Google Fonts as the typographic foundation for client work with no licensing handoff. The client receives full open-source rights automatically. One consideration: if a client wants a custom typeface based on an OFL Google Font, the derivative must comply with OFL (also open-source). For proprietary derivatives, start with an Apache 2.0 font or a permissive commercial font.

Attribution Requirements

Neither OFL nor Apache 2.0 requires visible attribution in your website, app, or product. No "Font by [Designer]" or "Powered by Google Fonts" required. Attribution is required only when redistributing the font files themselves - typically satisfied by including the OFL.txt or LICENSE.txt file alongside the fonts.

Self-Hosting vs Google CDN

The original CDN advantage was cross-site cache sharing - a font cached on one site loaded instantly on another. That advantage no longer exists. Since Chrome 86 (October 2020), browsers partition caches by site origin. Firefox and Safari made similar changes. Today, self-hosting has clear advantages: no extra DNS lookups for fonts.googleapis.com and fonts.gstatic.com, full control over caching headers, fonts served over the same HTTP/2 connection as your other assets, precise preloading, and no third-party data dependency.

Tools like google-webfonts-helper and our own webfont generator simplify conversion. The full setup takes under ten minutes for a typical project. Migrating an existing project: remove the Google Fonts <link> tag, add self-hosted @font-face declarations, upload the files. CSS font-family names stay the same.

Privacy and GDPR Caveats

Loading Google Fonts via CDN sends visitor IP addresses to fonts.googleapis.com and fonts.gstatic.com. In January 2022, the Munich Regional Court I ruled that loading Google Fonts from Google's CDN without user consent violated GDPR by transferring personal data to a US company without an adequate legal basis. The site operator was ordered to pay €100 in damages and stop using the CDN.

The ruling is from a single German court and not binding EU-wide, but reflects a broader regulatory direction. Self-hosting eliminates the GDPR concern entirely - no requests to Google's servers, no IP transmission, no data sharing.

Beyond GDPR, banking, healthcare, and government clients often have security policies prohibiting any external resource loading - making self-hosting a hard requirement regardless of privacy considerations.

Font Piracy Risks

Font licensing is one of the most routinely misunderstood areas of copyright law. Designers know fonts are software protected by copyright, but the practical implications of using an unlicensed font are rarely considered until a cease-and-desist arrives. Foundries have become increasingly aggressive in IP enforcement, aided by automated scanning that detects unlicensed web font usage across millions of sites without human intervention.

What Counts as Font Piracy

Font piracy is the use, distribution, or embedding of font software without a valid license. In the US, the software code that renders glyphs is copyright-protected, while the abstract letterform design generally is not (some EU jurisdictions extend protection to the design itself). Either way, every font use is governed by an EULA.

"Free to download" ≠ "free to use commercially" ≠ "legally distributed." Many fonts on unauthorized sites were originally free from the foundry but carry restrictions. In many cases the fonts are simply stolen commercial fonts with the license documentation removed - the absence of a license file is itself a red flag. Legitimate fonts always include a license text file or EULA.

Even with good faith on the designer's part, organizational liability does not disappear. An employee installing a pirated font on a company computer creates liability for the employer. The copyright holder can pursue the company, not just the individual.

Legal Consequences and Fines

Copyright infringement claims for fonts follow the same framework as any software copyright case. The US Copyright Act provides for both actual damages and statutory damages. Statutory damages are particularly significant - they require no proof of specific financial harm.

Once a foundry sends a cease-and-desist, any continued use becomes willful by definition, opening the door to the $150,000 per work figure. Attorney fees are an additional burden - in copyright cases, the prevailing party may be awarded fees, and litigation costs typically exceed legitimate licensing by 50× or more. This asymmetry is why most cases settle out of court with retroactive licensing fees plus a penalty.

EU jurisdictions have similar frameworks. The EU Copyright Directive provides for injunctions, damages, and disgorgement of profits. The UK has both civil damages and criminal penalties for commercial-scale infringement. German courts have been particularly active.

DMCA Takedowns and Cease-and-Desist

Before litigation, foundries typically use two enforcement mechanisms: DMCA takedown notices filed with web hosts/CDNs, and cease-and-desist letters sent directly to infringers.

Cease-and-desist letters identify the infringement, demand cessation, and often request an accounting of all uses. Typical response deadlines are 10-14 days. Ignoring a C&D does not make the problem go away - it eliminates the chance to resolve before litigation and demonstrates actual notice (supporting a willfulness finding).

Some foundries include retroactive licensing fees in the initial C&D, often 2-5× standard price as a penalty. While frustrating, negotiated settlements are almost always preferable to litigation. Engage an IP attorney to respond, even if you believe the claim lacks merit.

Common Piracy Sources

How to Audit Your Compliance

A font compliance audit inventories every font your organization uses and confirms each has a valid license covering its actual use. Repeat whenever new projects launch, when designers join or leave, and when new fonts are introduced.

Agency & Client Font Licensing

Font licensing gets complicated the moment a third party is involved. Most font EULAs were not written with agency workflows in mind, which creates real gaps. The core issue: licenses grant rights to a specific person or organization. Your client is a different entity, and their use of the deliverable is legally distinct from yours.

Who Owns the Font License

Whoever uses the font needs a license for that use. In agency work, this typically means two separate licenses at different stages.

The agency needs a license for design work in Figma, Illustrator, Sketch - a desktop license. The client needs their own license for production: a web font license for the live site, an app embedding license for distributed apps, a desktop license if their team will edit source files.

Who pays is a business negotiation, not a legal requirement. Some agencies include font procurement as a quote line item; others provide a list of required licenses for clients to purchase directly. The license must be held by the entity using the font.

Sublicensing Rules

In font licensing, sublicensing is almost universally prohibited. Most commercial EULAs say: "This license is non-transferable and may not be sublicensed." You cannot buy a license and grant your client usage rights under it.

Some foundries offer agency or studio licenses at higher tiers, allowing fonts across multiple client projects. The agency still holds the license - this is not sublicensing. Even with an agency license, the client typically needs their own for production use.

Open-source fonts (OFL, Apache 2.0) sidestep this problem entirely. No restrictions on who can use the font - the simplest choice for client work.

Project Scope and License Tiers

Map deliverables to use types. Most foundries sell licenses by use type: desktop, web, app, ebook, server. A single project may need multiple types.

Scope changes are a common source of licensing problems. A website rebrand may expand to a mobile app six months later - each new deliverable may require an additional license type. When recommending fonts, factor in licensing costs from the start. A premium typeface might cost significantly more once you account for the web tier the client's traffic requires, plus a desktop license for their team, plus an app license for a companion app. Sometimes an open-source alternative is the more pragmatic recommendation.

Font File Handoff Procedures

Protecting Yourself as an Agency

Liability can come from foundry claims for unlicensed use, or client disputes over font costs and compliance. Both can be minimized with documentation and clear contracts.

Periodically audit your own font library. Many studios accumulate fonts over years without consistent licensing for current usage. Run an audit matching every installed font to a purchase record, and retire or re-license fonts without documentation. Our font license checker inspects embedded metadata to identify license type, restrictions, and embedding permissions.

Client Contract Language

A well-drafted font licensing clause is the most effective protection available. It creates clear expectations before the project starts, assigns responsibility explicitly, and gives you a documented basis if a dispute arises.

For clients unfamiliar with font licensing, plain-language explanation works better than legal boilerplate. A short paragraph in your kickoff documentation: "Every typeface we use is someone's intellectual property. During design we use our own licenses. When we hand the project over to you, you'll need your own licenses for the fonts on your live site or in your apps. We'll give you everything you need to buy the right ones." Building these conversations into onboarding reduces friction at handoff.