Find a font by its actual family, use project/workspace sources, embed faces for portable renders, and verify fallback before sharing or exporting.
Where: Video Editor → select a text/shape layer → Inspector → typography/font controls.
Before you start
- Select a text-capable layer. Have a valid font file or an available project/workspace font when using a custom family.
Key ideas
- Font family and font source are related but separate: Choose the intended family, then ensure the project can resolve its source. The picker can use available project/workspace fonts or a supported font source; a family label alone does not guarantee a viewer or render machine has the font.
- The unified picker resolves actual families: Font search and family labels are shared across the project/compositor typography surfaces. Choose the actual family and weight rather than relying on a generic “custom” label.
- Embedding supports portable output: When the font controls offer embedding, embed the selected face for portable project/export use. Confirm that the required file/license supports embedding and that the rendered result uses the intended face.
- Fallback can change layout: If a font fails to load, a fallback can change line breaks, text bounds, alignment, and animation. Inspect the rendered frame rather than trusting only the saved family string.
Steps
- Select the text or shape layer and open its typography controls in the Inspector.
- Search for the family by its displayed family name. Check whether it is available from the project, a workspace font library, or a supported external source.
- Choose the exact family and weight/style needed. If the family is not present, use the available upload/source action and provide a valid font file or configured family source.
- Enable font embedding when the project must render portably on another machine or in a portable export. Use a font that permits embedding.
- Wait for the font to load, then inspect the Viewer at the final output size and verify glyphs, wrapping, line spacing, and alignment.
- Save the project and test the portable/rendered output. If it differs, confirm the selected family actually resolved and inspect fallback/source settings.
Font source checks
- A project font library can include uploaded families and their individual weight/style faces.
- Workspace fonts may be available to projects through the shared font catalog; a family must still resolve to a usable file/source.
- A remote family source can be subject to URL availability and browser/network policy.
- Embed only fonts whose source/license permits embedding.
Portable project checklist
- Confirm each used family and weight resolves.
- Embed custom faces when offered and permitted.
- Reopen or render the project in its delivery environment and compare line breaks and glyph coverage.
- If a missing-glyph fallback occurs, choose a family with the required language/script coverage.
Tips
- For branded work, connect/link the project Brand’s typography guidance as source context, then explicitly choose the actual font face in the text controls.
- Use a representative multilingual string to catch fallback before animating or laying out a long title.
- Keep font source and family choice documented when handing a project to another editor.
Limitations and important notes
- Available families and source actions depend on project/workspace permissions and the current font picker.
- Embedding is subject to font-file licensing and may be unavailable for some sources.
- Fallbacks can vary across browsers, operating systems, and render targets.
Troubleshooting
The font family does not appear in the picker.
Check the project/workspace font library, spelling, and source permissions. Use the supported upload/source action if you have a licensed file.
The font is correct in the editor but changes on another machine.
Confirm the font face is included or embedded when permitted, then test the exported/portable project in its target environment.
Text wraps differently after export.
Check actual family and weight resolution, fallback glyphs, font loading, and the final output dimensions; then compare the rendered result rather than only the editor label.