Font License Audit Checklist: How to Clear Fonts Before a Website or Campaign Launch
A font license audit helps you confirm that every typeface in a website, brand system, app, social campaign, or client handoff is being used within the permissions you actually purchased or received. This checklist gives you a repeatable way to identify fonts, locate the controlling license, match permissions to the project, record evidence, and resolve gaps before launch.
Overview
Finding a font is not the same as clearing it for use. A font download may include files for personal or evaluation use, while commercial projects can require different permissions. Even when a typeface is described as free, the relevant question is whether its license covers your specific activity, distribution method, audience, and team structure.
Start the audit by treating each font file as a project asset with its own record. Collect the font family name, individual styles, file formats, source, download date, purchaser or account holder, and the license document associated with the files. Do not rely on a filename, a marketplace label, a search result, or a designer's memory as the only evidence.
The license audit should cover both production and publication. A designer may use a desktop font to create artwork, but a website may need a webfont license. An app may require permission to embed the font in software. A client handoff may require the client to obtain its own seats or license rather than receiving the designer's files. These are separate questions, even when the same typeface is involved.
For broader font-selection context, see Best Sites to Download Fonts Safely Without License Confusion and the checklist in How to Choose a Font for a Logo.
What to track
Create a font register in a shared spreadsheet, project-management tool, or document repository. Give every family a row and link directly to the license text, receipt, or official terms. Record the exact version or package where available; font files can be redistributed or replaced under different terms.
| Audit item | Question to answer | Evidence to keep |
|---|---|---|
| Source | Where did the font come from, and is the source authorized? | Foundry page, provider page, or official download record |
| License type | Is the font covered by an open license, a marketplace license, a subscription, or a custom agreement? | License document, terms page, receipt, or account record |
| Desktop use | Can the listed people or devices install the font to create artwork? | Seat count, user list, invoice, and license terms |
| Web use | Can the font be served through the planned domain or webfont host? | Web license terms, domain details, and implementation notes |
| App or software embedding | Can the font be embedded in an app, game, ebook, or other distributed software? | Embedding clause or separate app license |
| Social and advertising | Does the permission cover campaign graphics, paid ads, videos, thumbnails, and exported files? | Commercial-use wording and campaign record |
| Logo and trademark use | Can the typeface be used to create a logo or registered brand mark? | Foundry guidance and any logo-specific restrictions |
| Client handoff | May the client receive font files, or must the client license them directly? | Handoff terms, client license, and delivery inventory |
| Limits | Are there restrictions based on seats, pageviews, domains, impressions, revenue, geography, or distribution? | Relevant limit clauses and a project estimate |
Pay special attention to the word “embedding.” A font included in a website, app, template, document, or digital product may be treated differently from a font used only to export a flat image. Likewise, a desktop license may permit creation of a logo without permitting the distribution of the font files to a client or contractor. If a term is unclear, pause the handoff and ask the foundry or license provider for written clarification.
Separate the fonts used in final output from fonts installed temporarily for exploration. Remove unapproved files from shared libraries and production systems, then note the replacement font or cleared alternative. If the project uses variable fonts, record the variable font file and its license separately when the provider supplies separate files or terms. The guide Variable Fonts for Web Design can help with the technical side of formats and delivery, but licensing still depends on the applicable terms.
Cadence and checkpoints
Run the first audit when a font enters the project, not on launch day. At intake, save the official license and determine whether the intended use is desktop, web, app, social, logo, or a combination. This early check prevents a team from building a complete identity around a font that cannot be delivered in the required format.
Run a second check at design approval. Compare the font register with the files actually used in brand boards, templates, mockups, video projects, and campaign exports. Check every weight and style, including italic, condensed, variable, and alternate files. A family can contain files obtained from more than one source, so do not assume that one cleared style clears every file.
Run a production check before publishing. Confirm the domains, app packages, repositories, CDN or hosting arrangements, and distribution channels against the license record. Verify that only approved webfont files are deployed and that old or test fonts are not still loaded by the site.
Run a handoff check before delivering source files. List the font files separately from design files, state who owns each license, and identify anything the client or new team must purchase. Do not send font files merely because they are included in a project folder. A clean handoff makes the permission boundary visible.
For an ongoing library, schedule a quarterly review and a lighter monthly check for active launches. Recheck the official license page whenever a provider changes its account system, subscription model, file package, or delivery method. Keep a dated note of the review so another editor or designer can see what was verified and when.
How to interpret changes
Not every change requires replacing a font. First classify the change: a new project use, a new distribution channel, a change in team size, a new domain, a license update, or a change in the font files themselves. Each category points to a different action.
- New use: A font cleared for editorial graphics may need a separate review before use in a website, app, downloadable template, or logo.
- New people: Recalculate seats when freelancers, contractors, subsidiaries, or client teams receive access. Record the responsible license holder.
- New channel: Review web, app, video, print, social, and advertising permissions independently rather than treating “commercial use” as a universal approval.
- Changed terms: Save the version of the terms used for the decision and ask the provider whether existing purchases or projects are affected.
- Unclear evidence: Mark the font as pending, restrict its use, and choose a cleared substitute if the launch cannot wait.
Do not interpret a vague “free for commercial use” statement as permission for every possible workflow. It may still be necessary to check redistribution, embedding, modification, trademark, or attribution language. Open-license fonts can also have notices or obligations that should remain with the files and project records.
Licensing and accessibility are different audits. After a font is cleared, review readability, size, spacing, and contrast separately. The Font Accessibility Checklist and Contrast Checker Tools Compared are useful follow-up resources.
When to revisit
Revisit this checklist before every website launch, rebrand, campaign, app release, client handoff, and major template update. For active design libraries, schedule a quarterly audit; for dormant projects, review the record when work resumes. A six-month terminology and link review is also sensible for editorial resource pages, or sooner if a major provider changes its license documents or marketplace policies.
Use this practical closeout sequence:
- Inventory every font file used in the final design and production environment.
- Locate the official license, receipt, or permission record for each family and style.
- Mark the intended uses: desktop, web, app, social, advertising, logo, print, and handoff.
- Check seats, domains, pageview or distribution limits, embedding rules, and client ownership.
- Save screenshots or downloaded documents with the project record when permitted and appropriate.
- Resolve gaps through a new license, written clarification, removal, or a cleared replacement.
- Record the reviewer, date, decision, and next review trigger.
A font register is most valuable when it remains current. Treat it as part of the launch checklist rather than an administrative task completed once. That habit reduces last-minute substitutions, makes client handoffs clearer, and gives your team a defensible record of how each font was approved.
