Embedding a Font in Your App Isn't Covered by Your Desktop Licence. Here's Why That Matters.

Your Desktop License won't cover it.

There's a widespread assumption in software development that once you've bought a font, you've bought it. It's sitting in your assets folder, it renders beautifully in your UI, it ships with the app. What's the problem?

The problem is that standard font licences — desktop licences, webfont licences, even most broad commercial licences — don't include the right to distribute a font as part of a software product. Embedding is treated differently, and almost every major foundry has a separate licence category for it. It's called a software embedding licence, sometimes an app licence or OEM licence depending on the foundry. And it's one of the most routinely skipped steps in product development.

What "embedding" actually means When a font is embedded in software, it's being bundled into something that gets distributed to end users. That's true whether it's a native mobile app, a desktop application, a SaaS platform, a game, or firmware built into a physical device. The font isn't just being used to create something — it's being shipped as part of a product, potentially to millions of people.

Foundries draw a hard line here. From their perspective, every installation of your software is another distribution of their font. That's a fundamentally different proposition to a designer using the same font on their own machine to make marketing materials, which is all a desktop licence actually covers.

The OEM category — and why it exists OEM stands for Original Equipment Manufacturer. In the context of font licensing, it's used to describe situations where fonts are redistributed as part of a larger product — hardware, software, embedded systems. It's the category that covers things like operating systems shipping with a set of pre-installed fonts, or a hardware device displaying text using a bundled typeface.

Most independent software companies won't need a true OEM licence — that tends to apply at significant commercial scale. But the principle is the same. If your product ships with a font inside it, you need a licence that explicitly permits distribution. App embedding licences typically fill that role for most modern software products.

How these licences are usually structured Unlike desktop licences, which are priced per seat, embedding licences tend to be priced around distribution volume — the number of installations, the number of end users, or occasionally a flat fee for unlimited distribution. Pricing models vary enormously between foundries, which makes it one of the harder licence categories to compare and budget for.

Some foundries price embedding licences as a one-time fee. Others charge annually. A few tie the cost to app store category or whether the app is free or paid — logic being that a paid app generating revenue represents greater commercial value derived from the font. None of this is standardised, which is part of why it gets complicated.

PDF distribution is a related but separate issue Worth flagging separately: embedding fonts into PDFs that get distributed externally — reports, proposals, marketing documents, product brochures — also falls outside standard desktop licence terms for most foundries. Some licences include PDF embedding; many don't. If your business regularly distributes PDF documents that will be opened by people outside your organisation, that's worth checking specifically.

The same logic applies to ePub and digital publishing. Fonts embedded in ebook files need their own licence category. Desktop and webfont licences don't cover it.

What happens if you don't get it right In practice, many software products ship with unlicensed embedded fonts simply because no one thought to check. It rarely causes problems immediately — font foundries don't monitor every app on the market in real time. But it does create a genuine liability that sits in the background. If the product gets acquired, goes through due diligence, or attracts the attention of a foundry with a compliance programme, the conversation becomes uncomfortable fast.

Retrofitting the correct licence after the fact is possible, but the negotiating position is weaker. And depending on how long the product has been on the market, the foundry may seek to account for historical distribution in the licence fee.

The simplest way to handle it Before a font goes into a product — before it's in the design system, before the engineers touch it — confirm that your licence covers software embedding. Check the EULA directly. If it doesn't mention app or software distribution rights explicitly, assume it doesn't cover it and contact the foundry or a licensing adviser before going further.

Switching fonts at the design stage is a minor inconvenience. Switching them post-launch, or negotiating an emergency licence under pressure, is considerably more disruptive. The check is worth doing early.