How to License a Font: What Designers Need to Know Before a Project Goes Live

Font licensing is easy to ignore while a design is still in Figma. It becomes much harder to ignore when the website is ready to launch, the app is waiting for release, or the client asks whether the font can be used in ads. A font is not just a visual asset; it is software with usage terms.

This guide explains how to think about font licenses before the final handoff. You will learn the difference between common license types, how to map usage, what questions to ask a client, and how to avoid the most common legal and production mistakes.

What a Font License Actually Covers

Ownership vs. Permission

A font license defines how the font files may be used. Buying a font usually does not mean buying ownership of the typeface. It means buying permission to use it under certain conditions. Those conditions may depend on where the font is installed, whether it is embedded on a website, used in a mobile app, included in a video, or distributed through a server.

Why Designers Need to Check Terms

Designers do not need to become lawyers, but they do need to understand enough to protect their clients and themselves. A beautiful font choice can become a problem if the license does not match the project.

Step 1: Map the Use Cases Before Buying

Current and Future Media

Start with a simple question: where will this font appear? List every current use: logo, print, packaging, website, app, social images, digital ads, videos, eBooks, presentations, product UI, or templates. Then list likely future use. A startup may begin with a landing page and later need an app, paid ads, pitch decks, and product documentation.

• Current use: logo, print assets, packaging, website, product UI, social images, ads, video, presentations, and templates.
• Near-future use: app release, paid campaigns, localization, partner materials, investor decks, or documentation.
• Operational use: who will install the files, who will embed them, and who will maintain them after handoff.
• This map helps you choose the correct license from the start. It also gives the client a clear view of why font licensing is not a random extra cost.

Step 2: Learn the Main License Types

Common License Categories

Desktop licenses usually cover installation on workstations for creating static assets such as logos, print layouts, images, and packaging. Webfont licenses cover embedding fonts on websites and often depend on monthly page views. App licenses cover embedding fonts in software or mobile applications. Digital ads, video and broadcasting, eBooks, games, server use, and unlimited use may require separate licenses.

Every foundry defines its own terms, so always read the actual agreement. The category names may look similar across websites, but the details can differ.

Step 3: Count the Right Metric

Metrics That Usually Change the Price

Different licenses measure different things. A desktop license may be priced by the number of computers where the font is installed. A webfont license may depend on page views. An app license may depend on the number of applications, not users. A video license may depend on the number of videos. Digital ads may depend on impressions.

Counting the wrong metric can lead to under-licensing. Before buying, ask the client for realistic numbers and choose a tier that covers the expected use.

Step 4: Check Who Is Allowed to Use the Font

People Who May Touch the Files

A common workflow involves a client, design agency, freelance designer, developer, printer, and marketing contractor. The license should clarify who may install or handle the font files. Some licenses allow transfer to a client under specific conditions; others require the client to buy their own license.

• Client-side users who will continue the brand after handoff.

• Agency or freelance users who need temporary access during production.

• Developers, printers, media teams, or contractors who may receive font files or webfont packages.

If contractors need access, ask the foundry before sharing files. Never send font files casually in a project folder without checking the license. That small shortcut can create a compliance problem.

Step 5: Think About Web and App Embedding

Web and app use are often misunderstood because the font is not simply installed on one designer’s computer. It is embedded into a product that users access. That is why webfont and app licenses are usually separate from desktop licenses.

Foundries such as TypeType provide licensing routes for desktop, web, app, video, eBook, server, and other use cases, which makes it easier to match the license to the project. If you are comparing commercial fonts or planning to buy fonts online, review the licensing section before final approval.

Step 6: Plan for Custom and Corporate Needs

Some companies outgrow standard licenses. A global brand may need unlimited use, contractor access, custom distribution, or a bespoke corporate typeface. In that case, a custom license may be more practical than many separate small licenses.

Custom font design can also change the licensing conversation. If a company commissions a bespoke typeface, the contract should define ownership, exclusivity, allowed modifications, distribution, updates, and third-party use.

Step 7: Keep a License Record

What the Archive Should Contain

Create a simple archive for every font: foundry name, font name, license type, invoice, license agreement, number of seats or views, covered domains or apps, purchase date, and renewal or upgrade notes. Store it where the client or in-house team can find it later.

• Font family, foundry, selected styles, and exact file formats.

• License type, invoice, agreement, purchase date, and renewal or upgrade notes.

• Covered users, domains, applications, assets, contractors, and internal owner for future questions.

This is especially important when teams change. A future designer should not have to guess whether a font can be used in a campaign or a product update.

How to Choose Between Standard and Custom Licensing

When Standard Terms Are Enough

A standard license is usually enough when the project has clear boundaries: a defined number of workstations, one website, one app, or a known set of campaign assets. It is faster to approve, easier to price, and often the most practical choice for small and medium projects.

A custom license becomes more useful when the project has unusual distribution, multiple teams, long-term contractor access, or unclear future use. If the brand expects to scale quickly, negotiate broader terms early instead of rebuilding the license structure after launch.

How to Explain Licensing Costs to Clients

Connect Cost to Risk Management

Clients sometimes see font licensing as a small technical detail because they compare it with buying stock images or downloading software. Explain that the cost depends on how widely the font will be used and how many people, products, websites, or assets will depend on it.

It also helps to connect the price to risk management. A properly chosen license protects the launch, makes future production easier, and prevents last-minute replacements that can damage the typography system.

How to Prepare a Client Licensing Brief

A licensing brief helps the client understand what they are approving before the project goes live. It does not need to be long: one page is usually enough to list the selected font, the planned media, the license type, the metric used for pricing, and any restrictions the team should remember.

This brief is especially useful when the person approving design is not the person who will manage production. A brand manager, developer, legal specialist, and future designer should all be able to read the same document and understand where the font can be used without asking the original designer to reconstruct the decision later.

What to Do When the Project Expands

A font license should be revisited whenever the project moves into a new medium. A website that later becomes a mobile app, a local campaign that turns into paid digital advertising, or a brand identity that grows into video content may require additional permissions even if the same typeface is already approved.

Build this review into the workflow. Before launching a new channel, check whether the existing license covers the new use case, whether the usage metric has changed, and whether new contractors need access. Treat license expansion as normal project maintenance, not as an emergency.

Common Mistakes to Avoid

Visual Approval Is Not Enough

• Do not assume that a free download is free for commercial use.
• Do not use a desktop font file on a website unless the license allows it.
• Do not share files with developers or contractors without checking transfer rules.
• Do not forget ads, videos, or apps.
• Do not wait until launch week to solve licensing.
• Another common mistake is approving typography only from a visual mockup. A font can look right in the layout and still be wrong for the planned media if the license does not cover embedding, traffic, distribution, or third-party access.

Checklist

Before Launch

• Font name, foundry, selected styles, and file formats are final.
• All use cases are mapped, including web, app, ads, video, templates, and future channels.
• License type, metric, covered domains/apps/assets, and contractor permissions are confirmed.
• Invoices, agreements, upgrade notes, and the contact person for future license questions are archived.

Licensing Details to Confirm Before Handoff

Summary

• Map every place where the font will appear before choosing a license, including current media and realistic future uses such as apps, ads, videos, templates, and product interfaces.
• Match the license type to the medium: desktop use, website embedding, app integration, digital advertising, video, eBook, server access, corporate use, or custom distribution.
• Count the correct pricing metric before approval, because workstations, page views, applications, videos, impressions, and server access are usually calculated in different ways.
• Check who may handle the font files: the client, agency, freelance designer, developer, printer, marketing contractor, or any future in-house team that will maintain the brand system.
• Plan for growth early if the brand may expand into new markets, languages, platforms, or campaigns; upgrading later is possible, but it is easier when the first license record is clear.
• Keep invoices, license agreements, covered domains, apps, seats, and contact details in a shared archive so future teams do not have to guess what is legally allowed.
• Contact the foundry before launch whenever standard terms do not clearly fit the project; a short clarification can prevent under-licensing, file-sharing mistakes, or costly redesigns.

FAQ

Can I use a desktop license for a website?

Usually no; websites typically need a webfont license.

Can a client use a font I bought?

Only if the license allows transfer or third-party use.

Are Google Fonts always safe for commercial work?

They are generally open source, but you still need to follow the license terms.

Do I need a license for a logo?

Yes, the font used to create the logo must be properly licensed for that use.

What if the standard license does not fit?

Contact the foundry about a custom license.