Font Licensing for Creative Teams: Track Typeface Rights Before Handoff

Font Licensing for Creative Teams: Track Typeface Rights Before Handoff

Posted 11/18/26
6 min read

Fonts are licensed assets, yet they travel inside files as if they were free. A desktop license quietly becomes a web or app deployment, and the license an agency holds rarely passes to the client. Here is how to record type, holder and scope for every typeface, so rights travel with the work.

  • Why every file handoff can quietly breach a font license
  • The four license scopes and who should hold each one
  • A font record and a handoff checklist you can adopt this week

The Asset Nobody Tracks

Images get rights metadata. Music gets licenses. Fonts get installed. FontFabric's guide to enterprise font licensing says it plainly: each handoff is a potential font license infringement, and most organizations have no process to identify those. The license sits unchanged while the scope of usage evolves.

The pattern is familiar. An agency designs a brand identity with fonts it licensed for its own desktops, delivers finished files, and the client approves them. In FontFabric's description, when an external agency executes a rebrand, the font licenses typically sit with the agency. Months later the client's in-house team opens a template in InDesign, or a developer embeds the font on the website, and nobody has checked whether the license covers it.

Four Scopes, and Why They Do Not Transfer Automatically

Font licenses are not one-size-fits-all. Monotype's font licensing guide lays out the common types: open source, web, desktop, app, and commercial or embedding permissions, and it notes that desktop licenses may limit use to specific devices or numbers of users. For asset teams, four scopes matter most:

  • Desktop. Creating work in design software, often limited by users or devices.
  • Web. Showing the font as live text on a website through webfont files. As Fontbros explains, live web text generally requires a webfont license, while static artwork may be covered by a desktop license.
  • App. Embedding the font inside an app or ebook, which a desktop or webfont license does not cover.
  • Other. Broadcast, video and logo use, plus subscription services with their own terms. Resistenza's guide for agencies notes that Adobe Fonts covers desktop and web use under the subscriber's account terms and generally does not cover app embedding or broadcast distribution.

Transfer is the sticking point. One foundry's help pages say that if an agency or developer bought a font itself, that license cannot be transferred for the client's use and the font files cannot be shared, and that web and app licenses should be bought by the end user who owns and controls the site or app. The same foundry advises that a client who must use the fonts should acquire its own license alongside the agency's. Terms vary by foundry, which is the point: you have to look.

Resistenza makes the same practical observation. Once an agency delivers brand files and the client's in-house team starts using the font, even just opening a brand template in InDesign, the client needs its own desktop license.

The Font Record

Treat each typeface as an asset with a record, the way you would a stock image. A workable set of fields, as a starting point:

  1. Family and styles. The exact family and styles in use.
  2. Foundry and source. Where it comes from, with the license document attached.
  3. License holder. Agency, client, or a subscription account. The question the other fields depend on.
  4. Scope. Desktop, web, app or other, with the limits the license sets, such as users, domains, page views or downloads. FontFabric notes that web and app licenses are separate types with separate pricing, often based on page views, downloads or deployment scope.
  5. Term and renewal. Expiry or subscription renewal dates.
  6. Transfer terms. Whether the license can be transferred, or whether the client must buy its own.
  7. Where used. The projects and templates that depend on it.

Infinum's design handbook shows how an agency can run this in practice. Project documentation specifies the license type required (desktop, webfont or app), points to a folder with the license and font files, and tells designers to ask the project manager whether the client holds the right license when the origin of a file is unclear. Our pieces on usage rights for marketing assets and on automating rights expiry apply to typefaces as much as to photos.

A Handoff Checklist

The Graphic Designers of Canada's IP worksheet gives the discipline. Before delivery, verify that font licenses match the client's actual use: desktop, web, app and number of users. At handoff, review which rights transfer, which the designer keeps and which third-party licenses the client will manage, and highlight renewal dates and client responsibilities. Resistenza adds that either model of who buys the license works as long as it is addressed, not assumed, and recommends stating it in the project agreement or the brand guidelines handoff.

A checklist for the file package:

  • The fonts used, with the license type each destination needs: print, web, app, video.
  • Who holds each license today, and who must hold it after delivery.
  • Subscription fonts flagged as such, with login and renewal requirements.
  • A named fallback for any font the client cannot license.
  • A line in the handoff document stating all of the above.

Our piece on the real cost of creative team handoffs explains why this kind of detail is the first thing to go missing.

Make the Record Travel

A record in a spreadsheet will be out of date by the next project. Attach the fields to the template and the brand kit, so anyone opening a template sees which fonts it uses and what they are licensed for. Our guide to building a template library teams actually use covers where such metadata belongs.

A brand portal can keep copies from drifting into email, as in our piece on portals for external partners. One caution applies. Foundries restrict sharing, and the Production Type help page quoted above calls sharing outside the permitted cases a breach of its license terms, so a portal should distribute font files only where the license allows it, and otherwise point each party to where it obtains its own license. When assets, templates and rights live in one environment, as on the MTM platform, the license sits next to the file it governs.

What to Do This Month

List the typefaces behind your five most-used templates. Find the license for each and fill the seven fields. Mark any where the holder is an agency or a former employee, or where the scope does not match the use. Fix those first, then add the font line to your handoff checklist. A quarter of that discipline turns a hidden liability into a tracked asset.

FAQ

Can an agency pass its font license to the client? Not automatically. Terms vary by foundry, and some say a license bought by an agency cannot be transferred for the client's use and that fonts cannot be shared. Check the license, and plan for the client to buy its own where needed.

Is a desktop license enough for a website? Generally no. Live web text generally requires a webfont license, while static artwork may be covered by a desktop license. FontFabric names a desktop license used for web or app deployment as one of the common gaps.

Do subscription fonts like Adobe Fonts solve this? They simplify desktop and web use under the subscriber's account terms, but they generally do not cover app embedding or broadcast distribution. Check the terms for your actual use, and for what happens when the client is not on the same account.

Who should own the font record? The person who owns rights metadata for other assets. Designers fill the fields at project start, and the project manager checks them at handoff.

Is this legal advice? No. It is operational guidance for asset teams. Font license terms differ by foundry and by license, so read the actual license, and ask legal when a use is unclear or high-stakes.

Sources