I would list the exact font family, style, source and version alongside a reference render. Give collaborators the authorised way to obtain access rather than automatically copying font files into the project package. An editable title needs a reproducible typography setup as well as the project file.
On this page
Our recommendation
I favour a precise font manifest and an authorised acquisition route. Use a rendered fallback when agreed, while keeping editability and licence scope explicit.
Separate rendered output from font software
Adobe Fonts’ current FAQ distinguishes delivered graphics or rendered content from a collaborator’s direct access to the fonts for editing. It says Adobe Fonts cannot be packaged and transferred to another user; collaborators need their own appropriate access. Other fonts have their own licences, so check the actual source rather than applying one service’s terms universally.
Record the title’s family and style precisely, including weight and any variable-font settings relevant to the application. A similar family name can produce different glyphs and line breaks. Keep a short reference showing the intended layout and representative characters.
Test the recipient’s editable result
Ask the collaborator to open the project with the authorised font setup and render a difficult title. Compare wrapping, punctuation, accents, alignment and timing. A missing-font warning is not the only failure; a silent substitution can look plausible while changing the design.
If an editable match cannot be established, agree a rendered or outlined alternative appropriate to the job and retain the editable source separately. Make the trade-off clear. Do not imply that a rendered fallback allows the recipient to edit the original typography.
A useful manifest entry
“Title 03: family X, Semibold, source link Y, version recorded; reference frame at 00:00:14:12; recipient to obtain appropriate access.” The handoff includes the project and reference, with font files only if their actual licence permits that transfer. Test the longest translated title before approving the package.
Before you act
- Record family, style, version and source.
- Check the actual font’s transfer terms.
- Compare a recipient render for silent substitution.
Use the Delivery workbook to apply the guide to your own setup.
Keep exploring
- Subtitle fonts: test the characters and wrapping the audience will see
- Archive an editing project with a readable delivery manifest
Sources and research notes
Research checked on 21 October 2026. Product specifications are manufacturer statements; examples and buying judgements are our analysis. No hands-on product test is implied.
Build on what you just learned
Your next useful step.
Organize, relink and restore with confidence.
Upgrade to Resolve 21 with a project-copy acceptance test
I would upgrade a working editing system only after preserving a recoverable project library and testing a representative project copy.
Read the guide →
Resolve 21 IntelliSearch: budget the analysis before relying on search
I would test IntelliSearch on a representative media subset and keep a conventional folder and logging system alongside it.
Read the guide →