← Back
Team Delegation, Outsourcing, Remote Editors & Production Pipelines

An editor's project uses fonts installed locally, while the graphics workstation substitutes different fonts and changes title dimensions during render.

Problem

An editor's project uses fonts installed locally, while the graphics workstation substitutes different fonts and changes title dimensions during render.

Solution

Root Cause / Diagnostic:
Typography rendering depends on local operating system font libraries. When a project opens on a machine missing the specific font weight or PostScript name, the NLE silently substitutes a default font, breaking formatting and line wraps.

Actionable Fix:
1. Package Font Assets with Project Handoffs: Create an Assets/Fonts folder within every project archive containing open-source or licensed font installer packages.
2. Standardize on Universal Web or Adobe Fonts: Restrict channel branding and titling to Adobe Fonts or widely available Google Fonts pre-installed across all team machines.
3. Convert Final Titles to Motion Graphics Templates (MOGRTs) or Baked Video: Render locked titles to ProRes 4444 with alpha to ensure typographical integrity during final render.

Pro Tip:
Before final export, render all approved title cards and text lower-thirds to ProRes 4444 with alpha; this insulates the render pipeline from workstation font library mismatches.