Can You Use Commercial Fonts on Your Website Without a License?

You find the perfect typeface for a landing page, check the foundry's price for a web license, and wince. Then you notice the same font is available on a "free fonts" site, or already installed on your Mac, or sitting in a theme you bought years ago. It is tempting to conclude that nobody will notice, or that having the file means you can use it. Both assumptions are wrong more often than people expect, and the consequences land on whoever owns the website.

This article answers the question directly, then works through the scenarios people actually ask about: fonts that came with your operating system, fonts bundled with design tools and themes, trial versions, files from download sites, and screenshots of text. It also covers how foundries find unlicensed use, what happens when they do, and how to fix a site that is already using a font it shouldn't. For the underlying license types themselves, see understanding font licensing. This is practical guidance, not legal advice.

The Short Answer

No. If you embed a commercial font on a website, meaning you serve the font file to visitors' browsers through @font-face or a hosting service, you need a license that permits web use. Without one, you are distributing licensed software without permission, which is copyright infringement and usually a breach of whatever license you do hold.

The reason is technical as much as legal. When a browser renders your page in a web font, it downloads the font file to the visitor's device. Every pageview is a copy of the font being distributed. That is why web licenses are priced by pageviews, and why a desktop license, which covers installing the font on your own computers, does not stretch to cover it.

There are a few situations where you can legitimately display a commercial typeface on a website without buying a web license. They are narrower than most people hope, and they are covered below.

Scenarios That Are Not Allowed

Converting a Desktop Font to a Web Font

You own a desktop license, so you run the OTF through a converter, get a WOFF2 file, and serve it. This is the most common violation. Desktop licenses almost universally exclude web embedding, and many also prohibit converting or modifying the files. Paying for one license does not entitle you to the uses covered by another.

Fonts From "Free Font" Download Sites

Many free font aggregators host commercial fonts that were uploaded without permission, or list fonts that are free for personal use only. The download being free has no bearing on whether the use is licensed. If a font appears on a well-known foundry's site at a price, a free copy elsewhere is almost certainly unauthorized.

Fonts From a Client's Brand Folder

A brand folder or a previous agency's project files often contain font files. Those files may have been licensed to the previous agency, licensed only for desktop use, or not licensed at all. Ask the client for the license documentation. If they don't have it, they need to buy it.

Fonts Installed With Design Software

Fonts that come with tools like Microsoft Office or older versions of design software are generally licensed for use within that software and for creating documents. Their licenses typically do not permit extracting the files and embedding them on a website. Some explicitly forbid it.

Trial or Demo Fonts

Foundries offer trial versions so you can test a typeface in mockups. Trial licenses usually forbid any published or commercial use, and trial files are often deliberately incomplete, with missing characters or limited weights. Using one on a live site is unlicensed use, even if you plan to buy it later.

Fonts Ripped From Another Website

Web fonts are downloadable by design: open developer tools, find the WOFF2 request, and save it. The license for that file belongs to the site that bought it, limited to their domains and pageviews. Using it on your site is infringement, and the file may contain embedded metadata or unique identifiers that tie it back to the original licensee.

Scenarios That Are Allowed

Relying on Fonts Already Installed on the Visitor's Device

You can list any font name in a CSS font-family stack without a license, because you are not distributing anything. If the visitor already has the font installed, their browser uses their local copy under their license.

body {
  font-family: "Segoe UI", "Helvetica Neue", Arial, sans-serif;
}

This is exactly how a system font stack works. Helvetica Neue, Segoe UI, and SF Pro are all commercial typefaces, but referencing them by name is fine. What you cannot do is serve those files yourself. Apple's license for SF Pro, for example, restricts it to designing interfaces for Apple platforms and does not grant web embedding rights.

The limitation is obvious: visitors without the font installed see the fallback, so you lose control over the result.

Text Rendered Into Images, SVGs, and Logos

Most desktop licenses allow you to create static artwork, such as a logo, a banner, or a social image, and use that artwork anywhere, including on websites. A PNG of a headline set in a commercial font is generally covered by the desktop license, because the image contains pixels, not font software.

SVG needs more care. Converting text to outlined paths is static artwork. An SVG that references or embeds the font file, for example through @font-face inside the SVG or a base64-encoded font, is distributing the font and needs a web license.

Don't use images of text as a workaround for body copy or headings. It fails WCAG 1.4.5 (Images of Text) for anything that isn't a logo or essential presentation, it can't be resized cleanly, and search engines and screen readers can't read it as text.

Fonts Under Open Licenses

Many high-quality typefaces are open source under the SIL Open Font License, which allows commercial web use, self-hosting, and modification. Some commercial foundries also release individual families or weights under open or free-for-commercial-use licenses. These need no purchase, just compliance with the license's simple conditions.

Fonts Licensed Through a Service You Pay For

If you use a subscription service like Adobe Fonts, web use is covered for as long as the subscription is active and you use the service's hosted delivery. Downloading the files and self-hosting them is usually not permitted.

How Foundries Find Unlicensed Fonts

People assume nobody checks. Foundries do, and it's easier than you might think.

• Automated crawlers scan the web for font files and match them against known fonts using file hashes, name table data, and glyph outlines.
• Embedded metadata in font files includes the foundry name, version, and sometimes licensee-specific identifiers. A copied file often carries the original buyer's details.
• Font detection extensions and services let anyone, including foundry staff, see which fonts a page uses.
• Licensing enforcement firms work on behalf of large type libraries, sending notices in bulk.

You can see exactly what a page loads in your browser's developer tools by filtering the Network panel for fonts, and you can inspect a file's embedded metadata with fontTools:

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

Name IDs 0, 8, 9, 11, 13, and 14 hold the copyright notice, manufacturer, designer, vendor URL, license description, and license URL. If the result names a commercial foundry and you can't match it to a purchase, you have a problem to solve.

What Happens If You Are Caught

The usual sequence is mild at first, but it isn't free:

1. A notice or audit request asks you to show a valid license for the font on a specific domain.
2. A settlement offer follows if you can't. This is typically the license fee you should have paid, often for a higher tier, plus back fees or a penalty multiplier. Amounts several times the original license cost are common.
3. Escalation to formal legal claims is possible if notices are ignored, particularly for large companies or repeated infringement.

The liability usually falls on the site owner, even if a freelancer or agency installed the font. That is a strong reason for agencies to get licensing right: a client who receives an infringement notice is unlikely to hire you again.

How to Audit and Fix a Site With Unlicensed Fonts

If you inherit a site or realize your own site is using fonts you can't account for, work through this checklist:

1. List every font file the site serves. Check the Network panel, search the codebase for @font-face, and look at third-party CSS.

grep -rn "@font-face" ./src ./public --include=*.css --include=*.scss
find ./public -type f \( -name "*.woff2" -o -name "*.woff" -o -name "*.ttf" -o -name "*.otf" \)

2. Identify each family and its source. Use the name table data and any purchase records.
3. Match each to a license that covers web use, the correct domain, and the current traffic level.
4. For anything unlicensed, choose one of three fixes:
   • Buy the correct license in the site owner's name. Contacting the foundry proactively usually costs far less than responding to an enforcement notice.
   • Replace it with an openly licensed alternative. Many commercial typefaces have close open counterparts, and switching is mostly a CSS change.
   • Fall back to a system font stack if neither option is practical right now.
5. Remove the unlicensed files from the server and repository, not just from the CSS. Files that remain publicly accessible are still being distributed.
6. Record the result with license documents stored alongside the project.

When you swap fonts, check that the replacement's metrics are close enough to avoid layout changes. The guide to size-adjust and font metric overrides shows how to tune fallback metrics so the switch doesn't cause layout shift.

Commercial Font Licensing FAQ

Conclusion

Using a commercial font on a website without a license isn't a gray area: serving the file to visitors is distribution, and distribution requires a web license. Desktop licenses, trial files, files from download sites, client brand folders, and files saved from other websites don't change that. The legitimate exceptions are referencing fonts that visitors already have installed, using static artwork such as logos and images, and choosing openly licensed fonts.

If you're unsure about a site you run or built, audit it now. List every font file, match each to a license, and buy, replace, or remove whatever doesn't check out. The fix is usually a short afternoon of work, and it costs a fraction of what an enforcement notice will.

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

1. SIL International: SIL Open Font License — the most common license for fonts you can use commercially for free.
2. Google Fonts: Google Fonts FAQ — confirms commercial use of fonts in the Google Fonts library.
3. Adobe: Adobe Fonts licensing — what is and isn't allowed with an Adobe Fonts subscription.
4. W3C: Understanding Success Criterion 1.4.5: Images of Text — why images of text aren't a substitute for web fonts.
5. Apple Developer: Fonts for Apple platforms — where Apple publishes SF Pro and its usage terms.