Do I Need a Separate Licence to Use a Font on My Website?

Yes, almost certainly. And the desktop licence you already paid for almost definitely doesn't cover it.

This is probably the most common misconception in commercial font licensing. A brand buys a typeface, the designer installs it, it goes on the website. Nobody thinks twice. Then at some point — during a rebrand, a due diligence process, a routine legal review — someone asks the question. And the answer is not what anyone was hoping for.

A desktop licence covers installation on a set number of machines for use in creating documents, graphics, and print materials. That's the scope. It doesn't extend to the web, it doesn't extend to apps, and it doesn't extend to anything that involves distributing the font file itself — which is exactly what happens when a font loads in a browser.

Why web use is treated differently When a font is used on a website, the font file gets delivered to every single visitor's browser. Depending on your traffic, that means the file is effectively being distributed thousands — sometimes millions — of times a month. Foundries have always treated that as a fundamentally different right from desktop installation, and they licence it separately as a result.

Webfont licences are typically structured around monthly page views. You'll see tiers: 0–100k, 100k–500k, 1 million and above. The logic is that distribution scales with traffic, so the licence cost scales accordingly. Some foundries sell perpetual webfont licences; others require annual renewals. Some bundle web rights into a broader licence; most don't. The terms vary significantly depending on the foundry.

Self-hosting vs. using a font service There are two main routes for getting a font onto a website. You either self-host the font files on your own server, or you use a platform like Adobe Fonts, Fontsmith, or Fonts.com that serves them for you.

If you're using a subscription font service, the webfont licence is usually included — but it's worth confirming which fonts are covered and under what terms. It's also worth noting what happens if the subscription lapses. A lot of websites continue using fonts from a service that was cancelled years ago. The font still renders because it's cached, but the licence is gone.

Self-hosting is where things get more complicated. Many foundries explicitly prohibit self-hosting in their standard webfont agreements. Others allow it but with conditions — no CDN distribution, specific file format requirements, single-domain restrictions. "Webfont licence" doesn't automatically mean you can host the files wherever you like. That's a separate question, and it's worth checking.

What about Google Fonts? Google Fonts are released under open licences — typically the SIL Open Font Licence — which permit free commercial web use without restriction. If you're embedding them via Google's standard method, you're covered. No page-view tiers, no renewal dates, no usage limits.

That said, "free to download" and "free to use commercially on a website" aren't the same thing. There are plenty of font download sites that look legitimate but are hosting commercial fonts without proper authorisation, or distributing them under fabricated licence terms. The source matters.

What actually happens when it goes wrong Foundries are generally not in the business of litigation. What tends to happen is a compliance notice — a letter or email flagging unlicensed use and requesting that it be rectified. That usually means purchasing the correct licence, sometimes with a backdated fee to account for the period of unlicensed use.

For a brand that's been running an unlicensed webfont for two or three years on a reasonably trafficked site, that cost can be significant. And if the font is central to the brand identity — which it often is, by the time anyone notices — there's no easy way to just swap it out while the issue gets resolved.

Getting this right before it becomes someone else's agenda is almost always the simpler path.

A straightforward first step Pull together a list of every font your website uses. Check each one against whatever licence documentation you have. If you don't have documentation — which is common, particularly for fonts inherited from previous agencies or designers — track down the original source and confirm the terms directly.

If you're not sure what your licences actually cover, or you've inherited a brand with an unclear history, it's worth getting that reviewed. It's rarely as complicated as it sounds from the outside