Can You Send Font Files to a Client? A Designer’s Handoff Checklist
Delivering the design and transferring font software are different actions. Here is how to hand off a project without leaving the client with missing fonts or unclear permissions.
Oct 17, 2026 · 3 min read
You can send font files to a client only when the applicable license permits that transfer. Delivering a logo, PDF or image is a different action from giving someone the software used to typeset it. A good handoff resolves both the appearance of the finished work and the client’s ability to edit it later.
That distinction is easy to miss when a design application offers a convenient Package button. The button collects dependencies; it does not grant permission to redistribute them. Start with the actual font source and license, not a general assumption that every commercial project works the same way.
Decide what the client needs to do
Ask one practical question: will the client display the finished design, change the wording, or deploy the typeface across a website or application? Those are different deliverables.
For fonts added through Adobe Fonts, Adobe’s FAQ distinguishes finished graphics or properly embedded documents from editable access. A client receiving the former does not need a separate license simply to use that delivered artwork; someone who needs direct font access for editing needs their own license. Adobe also prohibits copying its subscription font files into a project package for transfer.
That is an Adobe Fonts rule, not a universal description of every font purchase. Adobe’s separate packaging guidance notes that terms vary, including provisions for some printer workflows. A desktop font bought from a foundry must be checked against its own agreement.
Create a font record alongside the files
Before delivery, make a short record with these fields:
- Family name, exact styles and source link.
- Which deliverables use each style.
- Who holds the license and who will maintain access.
- Whether the handoff includes editable text or finished artwork.
- The route for future edits and any separately quoted license cost.
Keep the license or purchase record where the project team can find it. “It came with my software” is not a useful instruction for the next designer, a client’s in-house team or a developer maintaining the site two years later.
Agree on the handoff before the final invoice
Consider a small brand project: the client needs a final logo and social images now, but wants to edit presentation slides every month. Deliver the approved static artwork, identify the fonts used in the editable slides, and establish the client’s licensed access before calling the project complete.
If that access is impractical, agree on an alternative font and test the layout. Outlining a display wordmark may preserve its appearance, but converting all document text to shapes can make later edits and accessible text handling harder. It is a delivery choice, not a substitute for a usable design system.
Do not confuse desktop access with every other use
A font that works on a designer’s computer may need a different arrangement for web hosting, apps, servers or customer-editable templates. Confirm the intended deployment with the supplier rather than assuming a desktop purchase covers it. The client’s ownership of the commissioned design and their permission to use the font software also remain separate questions.
This is general workflow information, not legal advice; the specific agreement controls. Le Cadre’s work-made-for-hire guide covers another ownership distinction, while the scope-creep workflow helps price extra handoff requirements. The best final folder contains clear decisions as well as clean files.
How do you handle editable files and font access? Join Le Cadre’s Creative Business community to compare handoff practices.