Choosing and Licensing Brand Fonts: What Every Team Should Know

A fast-growing company we spoke to received an unexpected email from a font foundry: their brand typeface was installed on far more machines than their licence allowed, and embedded in an app they'd shipped to 200,000 users. The bill to put it right ran into five figures. The typeface had been chosen for its looks. Nobody had read the licence.

Brand fonts are where design and law meet, and teams routinely get the design half right and the legal half badly wrong. This guide covers both: how to choose typefaces that hold up in the real world, and how to license them so you don't get a surprise invoice.

Choosing brand fonts that actually work

The most beautiful typeface is worthless if it fails in the places your brand actually lives. Choose for durability, not just for the specimen sheet.

Prioritise legibility at real sizes. Your font will render at 13px in a table cell and on a phone screen in sunlight, not just at 96px in a mock-up. Test candidates at 12–16px body sizes on an actual screen before committing.

Check the weight and style range. A brand needs a working set — typically at least Regular, Medium, Semibold and Bold, plus italics. A typeface with only two weights will force compromises within months. Confirm the weights you need exist and are individually licensed (foundries often price per weight).

Cover your character needs. If you operate in multiple markets, check the typeface supports the accents, currency symbols and scripts you use. A font missing the characters for a language you sell in is a hidden trap.

Plan for two typefaces at most. A display or heading face plus a workhorse body face is plenty. Every extra typeface multiplies licensing cost and consistency risk. Pairing a distinctive heading font with a clean, highly legible body font (something in the vein of Inter, Söhne or Source Sans) is a reliable formula.

Documenting these choices is a core section of any real set of brand guidelines, alongside your logo and colour rules.

The licensing types you must understand

This is where the money and the risk live. Font licences are almost always sold by use case, and buying one does not grant the others. The main categories:

• Desktop licence. Lets you install the font on a set number of computers to create static artwork — brochures, slides, PDFs. Usually priced per number of users or workstations. Exceeding the seat count is the most common violation.
• Web licence (webfont). Lets you serve the font on a website, typically priced by monthly pageviews or domains. A desktop licence does not let you put the font on your site.
• App / embedding licence. Required to embed a font inside a mobile or desktop application, often priced per app or per number of installs. This is what caught the company in our opening story.
• ePub / broadcast / server licences. Needed for embedding in e-publications, on-screen graphics, or serving fonts dynamically from your own server.

Read each licence for two clauses in particular: the modification clause (can you edit the font's outlines, e.g. to make a custom ligature?) and the transfer clause (can your agency or printer use the font on your behalf?). Many teams unknowingly breach the latter by emailing font files to a freelancer.

Web fonts, hosting and performance

For websites you generally have three routes. Self-hosting the licensed webfont files gives you the most control and privacy but requires you to hold a webfont licence and manage the files. Foundry-hosted services (like a foundry's own CDN) bundle the licence with delivery. Free libraries such as Google Fonts offer open-licence typefaces (usually SIL Open Font License) you can use without per-view fees — a genuinely good option if a suitable face exists, and one that sidesteps most licensing risk entirely.

Whatever you choose, always define a fallback stack so the page still looks intentional if the brand font fails to load:

font-family: "Söhne", "Helvetica Neue", Arial, sans-serif;

Set font-display: swap so text stays visible while the webfont loads, rather than showing a blank flash. And pick a fallback with similar metrics to your brand font to minimise the visible reflow when it swaps in.

Document the type system, not just the font

A font name isn't a system. Your guidelines should specify a working type scale with real numbers so nobody guesses:

• H1: 32px / 40px line-height, Semibold
• H2: 24px / 32px, Semibold
• H3: 20px / 28px, Medium
• Body: 16px / 24px, Regular
• Caption: 13px / 18px, Regular

Add rules for tracking (letter-spacing), maximum line length (aim for 60–75 characters for body text), and which weights are permitted where. This is the difference between a typeface and a typographic system that stays consistent as it scales.

Why type drift is so hard to catch

Fonts drift more quietly than logos or colours. Someone builds a slide in a font that isn't installed, so their machine silently substitutes Arial. A web page loads a fallback because a licence lapsed. A partner rebuilds your headline in a "close enough" free font. None of these throw an error — they just look slightly, cumulatively off-brand.

Spotting the wrong typeface by eye is genuinely hard, especially across sans-serifs. This is one reason teams use HasMyBrandChanged: you record your approved fonts once in a Brand Blueprint, then check any uploaded asset — or a live web page — against it in under a minute. Type and layout are AI-reviewed with confidence levels and the findings are drawn on the artwork, while logos and colours are measured precisely (colour by CIE Lab ΔE). It catches the substituted or unlicensed-looking font that a busy reviewer would miss.

The font you licensed only protects the brand if it's the font that actually renders.

A quick licensing checklist

Before you adopt a typeface, confirm:

1. Which use cases you need — desktop, web, app, server — and that you've licensed each.
2. The seat count and pageview tiers, with headroom for growth.
3. Whether agencies and printers are covered to use it on your behalf.
4. The character sets and weights you require actually exist.
5. A documented fallback stack for every environment.

Get the choice and the licence right together, and your typography becomes an asset rather than a liability. For the broader picture on holding every element steady as you grow, read brand consistency across channels and, if you're inheriting a messy setup, how to run a brand audit.

Not sure whether the right fonts are actually shipping on your assets? Set your brand fonts as a Blueprint and check every asset in a minute.