What Actually Happens During a Font Audit?

Most organisations don't have a clear picture of which fonts they're using, let alone whether they're properly licensed. An audit fixes that — and it's usually less complicated than people fear.

The phrase "font audit" tends to land in one of two ways. Either people assume it's a highly technical process involving specialist software and weeks of billable hours, or they assume it's straightforward and they've basically already done it because they remember buying a licence at some point. Neither is usually accurate.

In practice, a font audit is a structured review — methodical rather than complicated. The goal is simple: understand exactly which fonts an organisation is using, in which environments, and whether the licences in place actually cover that usage. What makes it interesting is that the answer is almost never what people expect.

Why audits are worth doing before something goes wrong There's a tendency to treat licensing compliance as something to deal with reactively — if no one's complained, the assumption is everything's fine. That's understandable, but it's not quite how font licensing works. Foundries own the intellectual property in their typefaces, and unlicensed use is an infringement whether or not anyone has flagged it yet. The risk doesn't disappear because it hasn't surfaced.

The more common trigger for an audit is a specific event: a rebrand, a platform migration, a merger or acquisition where the incoming party wants to understand IP exposure, or a direct approach from a foundry. But the organisations in the strongest position are always the ones who've reviewed things proactively — because they get to choose the timeline and the outcome, rather than responding under pressure.

Step one: mapping what's in use Before you can assess anything, you need an accurate picture of what's actually there. That means going through every environment where fonts appear — the website, any apps or software products, internal document templates, presentations, marketing materials, packaging, digital advertising, broadcast assets. The scope is usually broader than people initially think.

One thing that comes up regularly: fonts that no one currently on the team chose. They were inherited from a previous agency, embedded in a template that's been in circulation for years, or carried over from a legacy brand without much thought. Fonts accumulate quietly over time, and an audit tends to surface a few surprises.

Step two: tracing the licence history Once there's a clear inventory of what's in use, the next stage is working out what's covered. This means locating the original licence agreements — which can involve going through old invoices, checking platform subscription histories, or contacting foundries directly to confirm purchase records.

It's worth noting that "I have a licence" and "my licence covers this use" are two different things. A lot of compliance issues don't involve people who never licenced a font at all — they involve people who licenced it for one context and then used it in another without realising the terms don't extend that far. Desktop licences that don't cover web use are probably the most common example, but there are plenty of others.

Step three: comparing usage against licence terms This is where the detail matters. Each licence gets assessed against actual usage: the number of desktop users covered, the web traffic volume relative to any page-view limits, whether the font is embedded in software or an app, whether it's being distributed in any form such as a PDF or ePub, and the nature of the commercial context.

Common gaps: a desktop licence used in a web environment, a webfont licence that's exceeded its page-view tier as the site has grown, an app embedding that was never separately licenced, or a brand font used across subsidiary companies without a multi-entity agreement. None of these are unusual. Most of them are fixable without drama once they're identified.

Step four: the report At the end of the process, there's a written summary covering three things: what's fully in order, where the gaps are, and what needs to happen to close them. That last part is important — the output isn't just a list of problems, it's a practical path to resolution. In most cases, that means identifying the specific licence type required, the right channel to purchase it through, and a realistic timeline for getting there.

Where the gap involves a font that's genuinely difficult or expensive to properly licence, it's sometimes worth having an honest conversation about whether that typeface is the right long-term choice — and what the alternatives look like. That's not always the conclusion, but it's a useful thing to know before committing further.

How long does it actually take? A focused audit for a single brand with a handful of typefaces across two or three environments can be completed in a matter of days. Larger organisations — multiple subsidiaries, extensive software products, a long brand history — will naturally take longer. In those cases it usually makes sense to prioritise: start with the highest-risk areas, work outward from there.

The thing most people say at the end of an audit is that it was less complicated than they'd expected. Not because the licensing landscape is simple — it genuinely isn't — but because once you know exactly where you stand, everything else becomes much more manageable