Commercial Fonts for Client Work: Verify Sources in 3 Tiers

Choose a font source and match its license to the deliverable#

For client work, start with a source that identifies the font and its license. Google Fonts is useful for open-source families, Adobe Fonts for subscription-based design workflows, and foundries or authorized marketplaces for paid licenses matched to a particular use.

The three tiers below are a review workflow, not a ranking of design quality or a guarantee of legal safety. A small foundry can have excellent terms; a familiar platform can still require a license your project does not include.

A roundup helps you discover a style. It does not establish permission to install the font, embed it in a product or send its files to a client. Follow the link to a legitimate source and read the terms for the copy you will use.

Separate font software from the artwork it produces. A finished logo image, an editable design, a live website and an app that contains font files can involve different rights. Choose the source after identifying those deliverables.

Trace the family to its publisher or an authorized distributor. Keep the source and license together. An old license can still be the valid license for the copy you obtained; a newer page date is not itself proof that an earlier grant has disappeared.

Read the applicable license for the planned use. Resolve missing or contradictory permission before relying on the font in a final deliverable. Do not promise to transfer font files merely because you can install them.

Keep the license supplied with the font, source URL, file or version identification and any receipt. For a subscription or paid product, note the license owner and scope. A dated copy of the terms helps explain the decision, but does not expand the rights granted.

Tier 1: Google Fonts and Adobe Fonts for familiar workflows#

These libraries offer published licensing information. Their models differ, so choose according to the files and deployment the client needs.

Read the license for the actual copy and use. Check new requirements when the project adds a website, editable template, app or another party who needs font access.

A file offered only for personal, non-commercial use is not cleared for an ordinary paid client project. Find the commercial terms or choose another font.

Google Fonts: open-source families for commercial work#

Google Fonts says its fonts are released under open-source licenses and can be used in commercial projects. Keep the family’s license file rather than assuming every family uses identical terms. Its library metadata recognizes OFL, Apache 2 and Ubuntu Font License variants.

For a font under the SIL Open Font License, commercial use and embedding are permitted, subject to its conditions. When redistributing the font software, retain its copyright notice and license. Modified fonts must respect any Reserved Font Names, and font software cannot be sold by itself. The license does not require your resulting document or artwork to adopt the OFL.

Adobe Fonts: design access with specific handoff limits#

Adobe’s licensing FAQ allows commercial design work. A client receiving rasterized artwork or properly embedded documents does not need its own font license for that output. A client needing direct font access to edit the design needs its own licensed access. App embedding is outside the standard Adobe Fonts license.

Do not package Adobe font files with the client’s editable design. Adobe’s packaging guidance requires collaborators who need the fonts to have their own access. State this in the delivery note rather than sending a font folder as a convenience.

Plan a client website’s ongoing font access#

If ongoing editable use will outlast a subscription, choose licensed perpetual access or an appropriate open-source alternative. Adobe says existing outlined, rasterized or properly embedded output continues to display after cancellation; live editable text may lose access to the font.

For Adobe web fonts, use the supplied embed code. A client website must load the fonts through the client’s own Creative Cloud subscription. Self-hosting requires a separate appropriate license from the foundry or authorized reseller. Agree who maintains that access before handoff.

Tier 2: MyFonts and independent foundries for specific licenses#

A paid purchase can give you the exact family and deployment rights you need, but the license type and owner matter. Read the family’s EULA and purchase scope before paying; a receipt for a desktop product does not automatically cover every embedded use.

Use the publisher or marketplace to match the actual font file, license, owner and intended deployment. The review is more specific than “paid equals commercial.”

MyFonts’ licensing FAQ distinguishes desktop, webfont, app, digital-ad and electronic-document licenses and links each family’s EULA. Review the actual foundry terms. When purchasing for a client, enter the client’s name as the license owner as instructed at checkout; a designer’s existing license should not be assumed transferable.

For independent foundries, compare the metrics as well as the license names. For example, MCKL describes desktop licensing by users, web licensing by monthly visitors and app licensing by monthly users. Other sellers use different metrics. Those examples are not universal thresholds.

Check restrictions on redistribution, modification, client access and deployment. If the needed use is not covered, ask the seller about the correct license or choose a font with suitable terms. A complex but clear EULA is not automatically a bad source.

For each approved font, keep a short project record:

Family and files; publisher or authorized source; applicable license and receipt if purchased; license owner; permitted uses; client handoff instructions. Store the license text with the record, and set a renewal or usage review only when the grant requires it.

Worked handoff example: a client needs a logo, an editable brochure and a website. With an Adobe Fonts design, deliver the outlined logo and properly embedded PDF, explain the client’s own font access for editing, and arrange the client-owned web project. Do not send packaged font files or assume those rights cover an app. With an OFL font, permitted redistribution can instead include the license and copyright notices. Match the final plan to the actual font license.

Related: A Guide to Font Licensing for Freelance Designers.

Tier 3: unclear-origin downloads need verification#

A free price is not the red flag: open-source fonts can be fully suitable for paid work. The concern is a file whose owner, source or license cannot be established. Avoid an unauthorized repost of a paid font even if the download installs successfully.

If you cannot establish permission, use a licensed alternative or seek clarification. Saving a screenshot of an unsupported “commercial use” badge does not fix the missing grant.

A mirror can distribute an open-source font legitimately when it complies with the license. Verify the source and included terms rather than rejecting every mirror or treating every download site as equally reliable.

Keep a usable library and clear delivery notes#

Start with the deliverable and the people who need to use or edit it. Choose an open-source library, subscription workflow or paid license that fits, then retain the applicable terms and handoff instructions.

Check language coverage, required weights and readable rendering at the intended size as well as licensing. A font can be licensed correctly and still be unsuitable for the audience or format.

Keep the license record with the project. Review it when the use changes or a term requires renewal, rather than treating every later website update as a reason to discard a valid prior license.