Licensing a font for commercial use is less about finding a single “commercial use” label and more about matching the font’s license to every way your project will use it. This guide includes a scenario-based comparison, a reusable pre-launch checklist, and an onboarding workflow for clearing fonts used in client work, websites, apps, publications, and brand systems.
Overview
A font license is permission to use specific font software under specific conditions. The permission may cover installing the files on a computer, embedding them in a website, placing them inside an app, using them in an eBook, or distributing them through a product. These uses are not automatically interchangeable.
Start by separating two questions:
- What are you creating? For example, a logo, website, social campaign, mobile app, PDF, game, SaaS product, or physical package.
- How will the font files be used? Will the files remain with your design team, be hosted on a server, be embedded in software, or be delivered to a client or customer?
The foundry, type designer, marketplace, or hosting provider’s end-user license agreement (EULA) controls the answer. “Free font” does not necessarily mean unrestricted use, and a font that is suitable for a logo may still require a separate license for web hosting or app embedding. Keep the EULA, receipt, invoice, license scope, and any correspondence together in a project record.
Before choosing a typeface, you can also review its glyph coverage and layout behavior with the font testing checklist. For multilingual projects, check language support before purchasing; a license cannot compensate for missing characters or unsuitable fallback fonts.
Checklist by scenario
Use this table as a starting point, not as a substitute for reading the current EULA. Vendors may use different names for similar permissions, and one project may need more than one license.
| Scenario | Usually relevant permission | Questions to answer |
|---|---|---|
| Design files, print, social graphics, and client presentations | Desktop or install license | Who may install the font? How many users or devices are covered? May the client edit the files? |
| Website using hosted font files | Webfont or hosted-web license | Which domains are covered? Is self-hosting allowed, or must the provider host the files? Are page views, traffic, or domains part of the terms? |
| Mobile, desktop, game, or other software | App, software, or embed license | Is the font embedded in the application? Can users extract or modify it? Does each product, platform, or title require coverage? |
| eBook or digital publication | ePub or digital-publication license | Is the font embedded in a fixed-layout or reflowable file? May the file be distributed commercially? Are previews or samples treated differently? |
| Server-side rendering, SaaS, or automated image generation | Server, cloud, SaaS, or render license | Does a server create images or documents for multiple users? Are generated outputs permitted? Is the font file exposed to customers or only used internally? |
| Typeface distributed with hardware, software, or a bundled product | OEM, product, or branding license | Is the font shipped with a device or product? Does the license cover resale, geographic distribution, product variants, and long-term support? |
| Logo or wordmark | Often desktop use, subject to the EULA | Can the font be converted to outlines? Does the license restrict trademark, logo, or merchandise use? Is a separate license needed for continuing text use? |
A reusable pre-launch checklist
- Record the font family, styles, file formats, foundry, vendor, and version or download date.
- Save the current EULA and purchase receipt in a shared, access-controlled project folder.
- List every planned output: print, PDF, website, app, eBook, video, packaging, product, or SaaS feature.
- List everyone who needs access: internal designers, contractors, client staff, developers, printers, and production partners.
- Confirm the license type for each output and the number of users, domains, products, or installations involved.
- Check whether variable-font files, webfont formats, desktop files, and static styles are covered by the same terms.
- Confirm whether self-hosting is permitted and whether a hosted provider has separate account or domain requirements.
- Remove unlicensed copies from shared drives, repositories, build systems, and production servers.
- Document any approval, upgrade, renewal, or exception required before launch.
- Assign an owner who can answer licensing questions after the project is delivered.
What to double-check
Client ownership and access
A client paying for design work does not automatically receive the font software. If the client must edit source files, build new pages, or maintain the brand internally, determine whether the client needs its own license. Your team’s desktop license may cover your work without covering the client’s future installations.
Web hosting and domain scope
Do not assume that a desktop license permits uploading font files to a website. Review whether the web license covers the exact domains, subdomains, staging environments, and campaign microsites involved. If a hosted service is used, confirm how domain authorization, project access, and font loading are handled. If self-hosting is required, verify the permitted file formats and any restrictions on redistribution.
Embedding and file exposure
Embedding a font in an app, eBook, game, or downloadable template can give recipients access to the font data. Look for provisions about extraction, modification, redistribution, and obfuscation. A PDF, design template, or software product may need different permission from a flattened image that contains only rendered text.
Variable fonts and related files
Variable fonts can combine multiple design axes in one file, but their technical format does not determine the license by itself. Check whether the purchased license includes the variable version, whether web and app permissions differ, and whether the file may be modified or subsetted. For implementation details, see this guide to variable fonts for web design.
Brand systems and logo use
Record whether the typeface is being used only to create outlined artwork or will remain as editable text in brand templates. Logo work should also be tested for spacing, distinctive letterforms, and future language needs. Our logo font evaluation checklist can help separate visual suitability from licensing scope.
Common mistakes
- Relying on a marketplace badge: Treat labels such as “commercial use” as a starting point. Open the specific EULA attached to the font and vendor.
- Assuming one purchase covers every use: Desktop, web, app, ePub, and server use may be separate permissions.
- Sharing font files with a whole team: Limit access to licensed users and check whether contractors or client employees need separate coverage.
- Uploading fonts to a public repository: Source-control systems, design libraries, and build pipelines can unintentionally expose font files.
- Forgetting staging and campaign domains: A website launch may involve preview URLs, subdomains, regional sites, and short-lived landing pages.
- Confusing rendered artwork with font software: An image containing text is different from distributing an editable document or font file.
- Failing to preserve records: A receipt without the applicable EULA, font name, and project scope may be difficult to interpret later.
- Ignoring replacement fonts: If a fallback font is supplied for missing glyphs or a platform limitation, audit that font separately.
For a broader pre-launch review, use the font license audit checklist. It complements, rather than replaces, the terms supplied by the rights holder.
When to revisit
Make font licensing part of the project workflow instead of a one-time download decision. Revisit the record before each launch, major redesign, seasonal campaign, or handoff to a new client team. Review it again when a website adds a domain, an app adds a platform, a SaaS feature begins generating documents, or a brand expands into packaging, merchandise, or new regions.
Also check the current EULA whenever you buy a new family, move from self-hosting to a hosted provider, adopt a variable font, change vendors, or replace a typeface. License summaries and pricing can change, so avoid copying old assumptions into a new project. A quarterly audit is a practical interval for active design libraries, while smaller projects can review their records at each release or delivery milestone.
To finish, create a simple font register with five fields: font and version, rights holder or vendor, license type, approved uses, and proof of purchase. Link each entry to the project and assign an owner. Before release, compare the register with the actual files in design tools, repositories, servers, and deliverables. If the intended use is not clearly covered, pause the launch and ask the rights holder or a qualified legal professional for clarification. That small checkpoint is easier to repeat than a post-launch cleanup.
