Skip to main content

​
Overview

Using custom fonts in Nexrender Cloud allows you to maintain brand consistency and typography control. However, incorrect font handling is a common source of layout issues and rendering bugs. This guide outlines best practices for referencing and managing fonts inside your render job payloads.

​
Use the Exact PostScript Font Name

The value for Source Text.font must match the internal PostScript name of the font — not the .ttf or .otf filename.

​
Incorrect

"value": "Montserrat-SemiBold.ttf"

​
Correct

"value": "Montserrat-SemiBold"

​
How to find the correct name:

  • macOS: Open the font in Font Book → “Full Name”
  • Windows: Right-click font → Properties → Details
  • CLI (optional): 
    ttx -t name YourFont.ttf
Font FileCorrect Source Text.font Value
Roboto-Bold.ttf"Roboto-Bold"
This_Is_The_Future_Italic.ttf"This Is The Future Italic"
Montserrat-SemiBold.ttf"Montserrat-SemiBold"

​
Preload Fonts in the fonts Array

All fonts must be explicitly preloaded in your render job payload: 
"fonts": [
  "Montserrat-SemiBold.ttf",
  "Roboto-Bold.ttf"
]

​
Why this matters:

  • Fonts not listed in fonts won’t be loaded during rendering
  • Fallback to system defaults is silent but incorrect
  • Text may shift, break, or lose styling

​
Use Preview Mode to Test Fonts

"preview": true
Preview renders are faster and cheaper — ideal for catching:
  • Font name mismatches
  • Layout shifts
  • Rendering errors from missing or misapplied fonts

​
Version-Control Your Fonts

Treat fonts like code assets:
  • Store .ttf/.otf files in Git or cloud buckets
  • Bundle fonts with template archives or CI pipelines
  • Never use non-versioned URLs (e.g. latest.ttf)

​
Prefer Google Fonts (When Possible)

Google Fonts are:
  • Open-source
  • License-safe
  • Render-friendly across OSes and pipelines
If branding allows, use them to reduce friction and ensure stability.

​
Summary of Do’s and Don’ts

DoDon’t
Use exact internal PostScript font namesUse .ttf or .otf filenames as override value
Include every font in the fonts arrayAssume AE or OS fallback will match your design
Validate using preview: true rendersWait for production jobs to catch font errors
Keep fonts versioned and committedLoad from changing external CDN links
Stick to known-good, portable fontsRely on obscure or platform-specific fonts
💡 Pro tip: Assign the font manually in AE first, then inspect the font dropdown. Use that exact value in "Source Text.font".
⌘I