Adobe Fonts License for Client Work

Adobe Fonts for Client Work: What You Can Hand Over

You can use Adobe Fonts in commercial work for yourself or a client, and you can hand over anything that has the type outlined, rasterised or properly embedded, such as a PDF, JPEG or PNG. What you cannot hand over is the font itself. If a client needs to open and edit live text, they need their own licence, and the same goes for a printer or collaborator who opens your working file. That is the position in Adobe's font licensing FAQ, which we read as an Internet Archive snapshot dated October 17, 2026.

Most questions about Adobe Fonts are really questions about a handoff: what file leaves your hands, and what can the person who receives it do with it? The test that sorts nearly every case is whether the font data travels with the file. Outlined or rasterised artwork carries none, an embedded PDF carries font data for display and not for editing, and a working InDesign or Word file depends on the recipient owning the font. The FAQ also rules out a few uses entirely, such as packaging fonts for a print bureau or embedding them in an app. Nothing here replaces advice from a lawyer, and the site-wide disclaimer covers the rest.

What the archived FAQ shows, and what stayed out of reach

Adobe's help pages returned an "Access Denied" error (HTTP 403) when we requested them directly on October 22, 2026, so we did not read the live page that day. The FAQ has since moved: the old address now redirects to helpx.adobe.com/fonts/web/font-licensing/font-licensing.html, and a second check on October 23, 2026 reached it with browser headers and found the answers we quote matching the archived copy. Our quotations come from the snapshot. Instead we read the Internet Archive's copy of the Font licensing FAQs at helpx.adobe.com/fonts/using/font-licensing.html, snapshot 20261017112716 (October 17, 2026), via web.archive.org/web/20261017112716/https://helpx.adobe.com/fonts/using/font-licensing.html. The snapshot shows the page as "Last updated on Mar 27, 2026."

Two limits follow from that, and we want you to know them before relying on anything below.

• We read the FAQ answers, not the underlying Terms of Use. The FAQ links to Adobe's Terms of Use, and the Terms are the binding text. We tried the Adobe legal URL we expected and it did not resolve, so we have no first-hand reading of the Terms. Where this guide says "Adobe's FAQ says", it means exactly that.
• The snapshot flattened the FAQ's question headings. The answers were intact, but the collapsible question titles were not. So we describe each answer in our own words and do not put words in Adobe's mouth about what the question was.

Adobe's web fonts have their own section of the help centre ("For web font usage, visit the web fonts section", the FAQ says), and we did not read it. This guide therefore does not cover embedding Adobe Fonts in a website, and we leave website rules to Adobe's own web fonts pages.

Re-read the live FAQ before you rely on any answer for a contract or a product. Licence pages change, and an archived page is evidence of what was published, not of what is published now.

The principle behind every answer

The FAQ's opening is short: "Adobe Fonts offers thousands of fonts from over 150 type foundries as part of your Creative Cloud subscription. All fonts are licensed for personal and commercial use." It then limits itself: the licensing information "applies to any fonts added through your Adobe account." Fonts that are installed in the Fonts folder on your computer "are licensed under their own end-user agreements", and those FAQs do not apply to them.

From the answers that follow, one idea does most of the work. The licence is attached to the person who added the font through an Adobe account, not to the artwork. So the question to ask of any file is whether the recipient can use the font software itself, or only a picture of what the font produced. A picture of the font (outlined shapes, pixels, embedded and subsetted font data inside a viewable document) travels freely. The font software does not.

That one idea explains why a PDF is fine and an InDesign package is not, why a logo in vector outlines is fine and a Word document with live text is not, and why a printer asking for your fonts is asking for something the licence does not let you give.

The handoff matrix

This table compresses the FAQ answers by deliverable. Each row is expanded in the sections after it.

The rest of this guide reads that table row by row and adds the situations where the right answer is not obvious.

Flattened images and outlined artwork

Adobe's FAQ answers the basic question first: you can use Adobe Fonts in any desktop program such as Photoshop "to create images or vector artwork, which you can then use for any purpose." It names the outputs: "a PDF, EPS file, or bitmapped file such as a JPEG or PNG."

Within that, two answers matter for designers who work in vector.

Outlined type can be modified. The FAQ says you can modify or decorate type that has been rasterised or converted to outlines, and "the resulting image may be copyrighted, registered as a trademark, or used in commercial products." That sentence is why a custom wordmark built from an Adobe Fonts typeface and then reshaped is workable. A designer can cut a ligature, extend a stroke, add a swash, and own the resulting artwork.

The boundary is the font software. The same answer continues: "you may not make changes to the font software file or create your own font software from converted outlines." You can draw a custom wordmark. You cannot turn outlines into a new font that you then install or distribute, whether as a font file or as a typeface product.

Outlines carry one cost that the licence does not mention: they are no longer editable text. If the client wants to change "Spring Sale" to "Autumn Sale", an outlined file cannot do that without the font. That is a workflow question, not a licence question, and it leads straight to the next case.

Editable files: where the client's own licence comes in

The line the FAQ draws for clients is this. Your client "does not need a separate font license if you provide them with graphics or documents that contain rasterized or properly embedded font data, such as PDFs, JPEGs, or PNGs." But "if your client needs to edit the design and access the fonts directly, they will require their own license, either through a Creative Cloud subscription or by purchasing a desktop font license."

The practical reading is a two-step test.

1. Can the client use the file without installing or activating the font? If yes (they view it, print it, post it, send it on), no client licence is needed.
2. Does the client need the font active in their application to edit live text? If yes, the client needs a licence of their own.

Neither step depends on how large the client is or how much they paid. A small business that receives an InDesign file and wants to change the headline needs the font; a global brand that receives an outlined PDF does not.

The FAQ lists the two routes to a licence: a Creative Cloud subscription, or buying a desktop licence. For Adobe-owned fonts, it says desktop and extended licences are available from Adobe's resellers. For fonts from other foundries on the service, it says desktop licences "and licenses for self-hosting, use in mobile applications, or other custom uses can be purchased from the font foundry or the foundry's authorized reseller", and that the foundry's name is shown on each family's page on the Adobe Fonts site. So the buying instructions you give a client depend on which foundry made the typeface, and you can find that out in seconds.

What to put in the delivery note

A short, factual note prevents the most common failure, which is a client who opens a file, sees a substitute font and blames you. Something like this works, adapted to your voice:

• The files in /final contain outlined or embedded type and can be used without any font installed.
• The files in /source use [font family, foundry]. To edit the text you will need your own licence, from a Creative Cloud subscription or from the foundry.
• We have not included font files and cannot, under the licence.

We are not suggesting this wording as a legal safeguard. It is a way of telling the client what they have, and it creates a record that you told them.

Print vendors, packaging, and why your printer cannot have the fonts

The FAQ is generous about print output. It says you can use Adobe Fonts "to design merchandise for commercial sale, whether it's a t-shirt for a friend or product packaging for a client," that printed products such as "books, magazines, posters, and other items" are permitted, and that "There are no restrictions on the number of impressions or items you may produce."

It is also direct about the one thing designers often do next: "you are not allowed to package or share the fonts with designers or print bureaus." The packaging answer is firmer still. Adobe Fonts "are not compatible with packaging workflows that involve transferring font files to another user or computer. The Terms of Use don't permit the fonts to be transferred to another user or computer, so they cannot be packaged with the file." If a printer or collaborator needs the fonts, "they must have their own license, either through a Creative Cloud subscription or by purchasing a perpetual desktop license."

So the standard prepress instruction "send us your packaged InDesign folder with fonts" does not work with these fonts. There are three ways around it:

1. Send a print-ready PDF. A PDF with fonts embedded is the normal handoff. The printer needs no font. Our guide to PDF/X-1a versus PDF/X-4 explains which standard keeps embedded fonts and transparency intact.
2. Outline the type for press files. Convert text to outlines in a copy of the file, keeping the live version for yourself.
3. Ask the printer to licence the font. If the printer must edit your layout, they need their own licence, the FAQ says.

Do not assume that a printer's willingness to "just install it" makes it fine. The licence question sits with the font, not with the printer's habits.

Merchandise, and the two things the licence forbids

Merchandise is the most searched use case, and Adobe's FAQ answer is yes with two carve-outs. We find it helps to treat the carve-outs as products rather than as rules.

Product type one: you set the type. You design a shirt with a slogan in an Adobe Fonts typeface and sell it. Allowed. The FAQ covers printed items "for commercial sale", including t-shirts and packaging, with no limit on quantity.

Product type two: the customer sets the type. You build a personalisation tool, a name-on-a-mug product, a custom e-card or a template where customers pick a font and type their own words. The FAQ says "No. The Terms of Use do not permit you to use the fonts in any way where your customers select and apply fonts to their own text as part of the design. This applies to both digital products, such as e-cards, and physical products, such as T-shirts and coffee cups." A custom licence "needs to be purchased directly from the foundry or from an authorized reseller."

Product type three: the product is the letters. The FAQ forbids making "a product that is individual glyphs from the font files, e.g. an alphabet set of each letter to spell out your own phrase. Creating products from individual glyphs is not allowed in any format." So letter stickers, alphabet clipart, monogram packs and cut-out letter sets built from the font's glyphs are out.

The borderline cases are the ones where a design sits between type one and type three. A poster with a single large letter "A" as an illustration is a design that uses a glyph, not a product that is the glyph set. A sheet of 26 letter stickers is a product made of glyphs. The FAQ's own test is whether the thing you are selling is individual glyphs; when it clearly is, the answer is no.

We cover the wider merchandise picture, including fonts with open licences, in free fonts for t-shirts and merch.

Logos and brand marks

The FAQ addresses logos twice, in one answer. You can "copyright or register the logo as a trademark. However, the fonts or typeface designs used in the logo cannot be copyrighted or registered as a trademark, as outlined in the Terms of Use."

Read carefully, this says two things. The logo, as a piece of artwork and a brand identifier, is yours to protect. The typeface inside it is not yours and you cannot claim exclusive rights in the letterforms. That matches how the law treats typefaces in the United States: the Copyright Office says copyright does not protect typeface or "mere variations of typographical ornamentation or lettering" (Circular 33), a rule we explain in can you copyright a logo.

Three design consequences follow.

• A wordmark in an unmodified typeface is a weak asset. Other businesses can set their name in the same font. What distinguishes your client's mark has to come from the arrangement, the modifications, the mark itself, and use over time.
• Modified outlines are the stronger route. The FAQ allows modifying outlined type, and the resulting image may be protected. A custom-drawn change to letters is what moves a logo from "set in a font" to "designed".
• Deliver the logo as outlines. An outlined vector logo needs no font on the client's side, which avoids the editing-licence issue entirely. For logos you may still want a version of the lettering for the client's staff to use in text, which is a separate licensing question for the font.

For logo work with fonts that have fewer limits, see free fonts for logos and our general commercial font licensing guide.

E-books, PDFs and other documents

The FAQ says Adobe Fonts "are licensed for embedding in ebook formats that protect font data, such as EPUB, iBooks, Kindle (MOBI), Adobe's Digital Publishing Suite (DPS), and PDFs." It adds two limits. First, "any ebook authoring workflow that requires users to manually move font files isn't permitted." Second, "as with any electronic document, fonts must be subset and used only for viewing or printing existing content, not for creating new document variations, templates, or dynamic content."

That second limit is important for anyone who builds fillable or dynamic documents. A PDF with fonts embedded for viewing is fine. A PDF form that lets people type into fields using the embedded font, or a document template that generates variations of itself, is the kind of use the FAQ draws a line around. If you build fillable forms, assume the answer is "ask the foundry", and test your assumption against the live FAQ.

Printed publications are covered too: "You may also use the fonts to create printed publications, such as books or magazines," subject to the rule against packaging fonts for designers or print bureaus. And there is no obligation to credit the font: "You are not obligated to include attribution for the fonts used in the documents or products you create."

Video, apps and servers

Some uses are covered, some are not, and the FAQ is clear about which.

The DAM entry is subtle. You may store the designs. You may not store the font files in a way that lets others reach and use them. A studio that keeps a shared asset library should check that the library holds exported artwork, not font files.

If you are building an app, a game or software of any kind, treat the Adobe Fonts licence as the wrong tool and go to the foundry. The same is true for self-hosting on your own server, which the FAQ separately says needs a purchase from the foundry or reseller.

When the subscription ends

Many freelancers ask what happens to delivered work if they stop paying. The FAQ's answer separates two kinds of files.

Files that keep working. "Any file that embeds the font data, such as PDF or image formats, and any text that has been rasterized or outlined will continue to display correctly. These types of files may be reproduced and distributed independent of your subscription status."

Files that stop working. "Documents that reference live, editable fonts, such as an InDesign or Word document, will show a missing fonts warning and use a default font from the program in place of the one from Adobe Fonts. You would need to purchase a new font license and install the fonts on your computer to continue to display and edit these files."

This gives a simple archive policy. At the end of each project, save a copy that can survive the end of your subscription: a PDF with embedded fonts and an outlined vector version for logos. Keep the live files too, with a note of which fonts they need, so you can reopen them with a desktop licence if you ever have to.

The FAQ also notes the difference from the perpetual product: Adobe Font Folio is "a collection of perpetually licensed font files" that you install locally, "not licensed for web use", and it supports server use. Adobe Fonts includes web and desktop use for the library "as long as you have an active Creative Cloud subscription" and does not support server use. The FAQ adds that Font Folio 11.1 and Font Folio Education Essentials stopped being available for purchase after June 1, 2022. If a client's brand fonts come from an older Font Folio purchase, their terms differ from the terms in this guide.

A worked scenario: one project, five deliverables

To show the matrix in use, consider a small business brand project. The inputs: a freelance designer, a client with no Creative Cloud account, and a typeface from Adobe Fonts used in the logo, in a brochure and in social templates. These are illustrative, not a real engagement.

The last row is the one that surprises people, because it feels like a small feature. It is also where the project's cost can jump, which is a reason to tell the client before you pick the typeface rather than after.

Choosing a typeface with the handoff in mind

The earlier you decide what the client will do with the files, the easier the font choice becomes. A few questions to ask at the brief stage.

• Will anyone other than you edit the design in a layout app? If yes, they need a licence, and you should choose a typeface they can obtain.
• Will the typeface appear in a product the client's customers customise? If yes, rule out the standard Adobe Fonts licence.
• Will the typeface appear in an app, a game or a software product? If yes, rule it out for the same reason.
• Is the client likely to want a plain-text fallback, such as an email signature or a Word template? If yes, plan the substitute font in the brand guide. Our guide on brand style guides shows where fallback fonts belong.
• Is the identity likely to need web delivery later? Then check the foundry's web terms before committing, and see font formats and WOFF2 for what delivery involves.

If the answers rule out the standard licence, a typeface with an open licence is sometimes the practical alternative; our guide to commercial font licensing compares the licence families.

Contract language: where the font position belongs

Your contract is where "who needs which licence" is best recorded. Three clauses help, and we expand on each in freelance design contract clauses.

• Deliverables. List file types, and say which contain live fonts.
• Third-party materials. State that fonts and other third-party assets remain subject to their own licences, and that the client is responsible for obtaining a licence if they want to edit live text.
• Source files. Say whether source files are included, and if so which fonts they need. A client who is promised "all source files" and receives an InDesign file with missing fonts has a complaint; one who was told in writing does not.

Ownership of the finished design is a separate matter. Fonts do not move with it. The guide on copyright ownership and work for hire covers who owns the artwork, and the font position stays as the vendor's terms set it.

Quick answers on client work

Can I use Adobe Fonts for a client's logo?

Per Adobe's FAQ, yes: you can use Adobe Fonts for commercial projects including client work, and the logo you create can be copyrighted or registered as a trademark, though the typeface itself cannot be. Deliver the logo as outlines so the client needs no licence to use it.

Does my client need their own Adobe Fonts licence?

Not for a PDF, JPEG, PNG or outlined vector file. They do if they need to edit live text in the design, in which case they need a Creative Cloud subscription or a desktop licence.

Can I send my fonts to my printer?

No. The FAQ says fonts cannot be packaged or shared with designers or print bureaus. Send a print-ready PDF with embedded fonts, or outlined artwork. If the printer must edit the layout, they need their own licence.

Can I sell T-shirts using Adobe Fonts?

Yes. The FAQ allows merchandise for commercial sale, including t-shirts and packaging, with no limit on the number of items. It does not allow products where customers choose the font and type their own text, or products made of individual glyphs.

What happens to my old projects if I cancel Creative Cloud?

Files with embedded font data and anything outlined or rasterised continue to display and can be reproduced and distributed. Live files such as InDesign or Word documents show a missing-fonts warning, and you would need a new font licence to display and edit them with the original fonts.

Can I use Adobe Fonts in an app?

The FAQ says no: the licence does not allow embedding fonts in mobile or desktop applications. You need a licence from the foundry or an authorised reseller.

Do I have to credit Adobe or the foundry?

The FAQ says you are not obligated to include attribution for fonts used in documents or products you create.

Slips that force a re-delivery

• Sending a packaged folder to a printer. The FAQ says fonts cannot be packaged and transferred. Send a PDF.
• Assuming "all fonts are licensed for commercial use" means "all uses". The commercial grant sits inside limits on glyph products, customer-selected type, apps and servers.
• Promising source files without checking what they need. Live files require the font on the recipient's machine.
• Building a font from outlines. The FAQ allows modifying outlined type for artwork, not creating font software from it.
• Letting subscription lapse without saving a durable copy. Embedded PDFs and outlined artwork keep working. Live files do not.
• Treating a system-installed font as an Adobe font. Fonts in the computer's Fonts folder are covered by their own end-user agreements; the FAQ says its answers do not apply to them.
• Ignoring the web section. Website embedding is covered by Adobe's separate web fonts documentation, which we did not read for this guide.

Fonts are one part of what a studio licenses. The software side, including what a free app's terms allow for client work, is collected in the design software hub, starting with is Affinity free for commercial use.

The FAQ we read, and what stayed unread

• Adobe, Font licensing FAQs (Adobe Fonts Help), the page's current address (formerly /fonts/using/font-licensing.html). Quoted from the Internet Archive snapshot of October 17, 2026, retrieved October 22, 2026, because our automated request that day was refused; the live text was re-checked on October 23. The page showed "Last updated on Mar 27, 2026." We read the answers; we did not read the linked Terms of Use or the web fonts section.
• U.S. Copyright Office, Circular 33, Works Not Protected by Copyright, checked October 22, 2026 (typeface and lettering).
• The scenario and checklist tables are our own illustration, not Adobe's.

After the fonts: who may reproduce the logo

Once the logo is delivered, the client's next question is who may reproduce it. Read can you copyright a logo, which separates what the Copyright Office will register from what trademark law can protect. Then, for the rest of your asset stack, the design asset licensing checklist gives the pre-delivery check across fonts, photos, icons and templates.