Font Audit: Inventory Typefaces and Match Them to Their Uses - Yenra

Define scope and identify the exact asset

Choose a manageable boundary: one website, a client handoff, an application release, or a design team’s workstations. Include fonts loaded by websites and hosted services, document templates, packaged project folders, and build assets as well as installed desktop fonts.

Record family and style, internal or PostScript name where available, version, file format, file location or hosting service, and project owner. A filename alone can hide differences between versions or similarly named families. A file hash can help identify identical bytes during an inventory, while ownership and permitted use still require separate evidence.

Use the font audit worksheet for one asset-and-use combination at a time. If one family is used on a desktop, a website, and inside an app, record those uses separately so the evidence can be evaluated for each.

Match evidence to the way the font is used

Scroll the table horizontally on a small screen. Keyboard users can focus the table region and use the arrow keys.

Apply a provider’s guidance only to the fonts and service it covers. For example, Adobe Fonts’ licensing FAQ distinguishes finished artwork from client access to font software and explains limits on packaging or embedding. It also says that separately installed fonts follow their own agreements.

For Adobe-hosted web fonts, the web-font terms specify the supported embed-code method and discuss client subscriptions and self-hosting. A working font in a browser establishes that it loads; the permission question comes from the applicable terms.

Openly licensed fonts also carry conditions. The SIL Open Font License project provides the OFL text and guidance. Locate the license distributed with the exact font and retain it with your evidence, especially when redistribution or modification is involved.

Worked example: a design becomes a website

This method avoids guessing permission from a file extension, a familiar family name, or an old invoice for a different use. Keep the exact question and supplier response together so the next reviewer can understand the decision.

Resolve gaps while preserving production behavior

1. Attach the purchase, subscription, or open-license evidence to the inventory record.
2. Record the relevant agreement version and the scope of use it addresses.
3. Mark unresolved questions as pending, with an owner and next action.
4. Obtain the appropriate permission or select a documented alternative where needed.
5. Test substitutions in staging: line breaks, pagination, missing glyphs, numerals, weight, and layout can all change.
6. After an approved transition, update deployment records and retain the decision history.

Keep automated discovery read-only at first. A scanner can list files and locations, but licensing conclusions depend on agreements, account ownership, and real uses. AI can help organize records or draft supplier questions; a responsible person should verify the underlying terms and resolve consequential ambiguity with the supplier or appropriate adviser.

Revisit the record when a font version changes, a new website domain is added, an app ships, a subscription ends, or a project moves to a client. Use the logo handoff workflow to make the final artwork and editable-source requirements explicit.