Client Font Licensing for Agencies

Who Owns the Font License

The short answer: whoever uses the font needs to hold a license for that use. In agency work, this typically means two separate licenses are required at different stages of a project.

The agency needs a license to use the font during design. This covers the work inside design applications like Figma, Adobe Illustrator, or Sketch. A standard desktop license covers this phase. If the agency produces print-ready PDFs or other deliverables with fonts embedded, the desktop license typically covers that too, though some EULAs impose limits on PDF embedding.

The client needs their own license to publish and maintain the final product. Once the project is live, the client is the entity using the font in production. A website served to visitors, an app distributed in the App Store, a brochure printed for distribution, all of these require licenses held by the client, not the agency.

Who pays for client licenses is a business negotiation, not a legal requirement. Some agencies include font procurement as a line item in their quotes and purchase on the client's behalf. Others provide a list of required licenses and ask clients to purchase them directly. The key is that someone has to buy the license, and that someone must be the client, since the license needs to be held by the entity using the font.

A common misconception is that a "commercial" license covers client work. It does not. Commercial licenses allow the purchaser to use a font in projects that generate revenue, but they do not extend usage rights to third parties such as clients. For a clear breakdown of what commercial licenses do and do not cover, see our guide to commercial vs personal font licenses.

Sublicensing Rules

Sublicensing means granting another party the right to use something you are licensed to use. In software terms, many open-source licenses permit sublicensing. In font licensing, it is almost universally prohibited.

Most commercial font EULAs contain explicit language along the lines of: "This license is non-transferable and may not be sublicensed." This means you cannot buy a license and grant your client usage rights under it. Your license covers you and your organization, no one else.

Some foundries offer agency or studio licenses at higher tiers that include rights to use fonts across multiple client projects. These are not the same as sublicensing rights, as the agency still holds the license, but they do allow the agency to use a single license across client work without needing to purchase a new license for each project. Check the foundry's pricing page for "agency," "studio," or "multi-client" license options.

Even with an agency license, the client still needs their own license once the project is live and they are the entity serving the font. The agency license covers the design and build phase; it does not extend to production use by the client.

Open-source fonts (released under the SIL Open Font License or Apache 2.0) sidestep this problem entirely. These licenses allow anyone to use, modify, and distribute the font freely, including for commercial purposes. There are no restrictions on who can use the font or how many entities can use it simultaneously, which makes open-source fonts a straightforward choice for client work.

Project Scope and License Tiers

Determining the right license tier requires mapping the deliverables to the use types the font will be put to. Most foundries sell licenses by use type: desktop, web, app, e-book, and server. A single project may require multiple license types if the deliverables span different uses.

Scope changes are one of the most common sources of licensing problems in agency work. A project that starts as a simple website rebrand may expand to include a mobile app six months later. Each new deliverable may require an additional license type. Build this into your project management: whenever scope expands to include a new output format or distribution channel, revisit the font licensing requirements. Web deployment in particular carries rules around pageview caps, domain restrictions, and self-hosting rights that are distinct from desktop use; our guide to font embedding restrictions covers all of these in detail.

When recommending fonts to clients, factor in licensing costs from the start. A premium typeface might cost significantly more once you account for the web license tier the client's traffic requires, plus a desktop license for their internal team, plus an app license if there is a companion app. Sometimes an open-source alternative with similar visual characteristics is the more pragmatic recommendation.

Font File Handoff Procedures

How you handle font files at project delivery is one of the most practically important aspects of client font licensing, and one of the most frequently mishandled. The wrong approach can expose you to liability for unauthorized distribution.

For web projects, the handoff typically includes a codebase with CSS referencing font files. If you are using a hosted service like Adobe Fonts or fonts.google.com, the handoff is simple: the client connects their own subscription or uses the free Google Fonts CDN under the same open license. If the font is self-hosted, the client needs their own valid web font license before the font files go on their server. If you specified open source fonts under the OFL or Apache 2.0 throughout the project, you can include the font files directly in the delivery package without any additional licensing steps.

One practical approach is to include a "Font Licensing Summary" document as a standard part of every project delivery. This document lists every font in the project, its license status (commercial or open-source), what the client needs to purchase, and where to buy it. This creates a clear record and demonstrates professional diligence.

Protecting Yourself as an Agency

Font licensing liability in agency work can come from two directions: claims from foundries for unlicensed use, and disputes with clients over font-related costs or compliance issues. Both can be minimized with good documentation practices and clear contract terms.

It is worth periodically auditing your own font library. Many studios accumulate fonts over years, and not all of them may have licenses that cover current usage. Run an audit that matches every installed font to a purchase record, and retire or re-license fonts that do not have documentation. Our font license checker can inspect the embedded metadata in any font file to identify its license type, usage restrictions, and embedding permissions, which is a useful starting point for a compliance audit.

If a client later discovers they need a font license and claims they were not informed, your documentation and contract language will be your primary protection. Courts and foundries respond well to evidence of good-faith compliance efforts. Agencies that have clear records and transparent client communication are in a far stronger position than those that handle font licensing informally.

Client Contract Language

A well-drafted font licensing clause in your client contract is the most effective protection available. It creates clear expectations before the project starts, assigns responsibility explicitly, and gives you a documented basis if a dispute arises later.

A comprehensive font licensing clause should cover four elements: specification (what fonts will be used), responsibility (who purchases which licenses), handoff (what happens to font files and licensing at project end), and ongoing compliance (who maintains licenses after delivery).

For clients who are unfamiliar with font licensing, a brief explanation in plain language is more effective than legal boilerplate. Consider including a short paragraph in your project kickoff documentation that explains: "Every typeface we use is someone's intellectual property. During design we use our own licenses. When we hand the project over to you, you'll need your own licenses for the fonts on your live site or in your apps. We'll give you everything you need to buy the right ones."

Building font licensing conversations into your onboarding process reduces friction at handoff. Clients who are informed at the start of a project about upcoming licensing requirements are far less surprised by them at the end.