Skip to main content
POST
/
fonts
Upload new font
curl --request POST \
  --url https://api.nexrender.com/api/v2/fonts \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --form familyName=null \
  --form font='@example-file'
{
  "id": "<string>",
  "familyName": "<string>",
  "fileName": "<string>",
  "createdAt": "2023-11-07T05:31:56Z"
}
After Effects needs fonts installed on the rendering system. If a font referenced in your template isn’t available, it will silently substitute a fallback - causing layout shifts, incorrect spacing, or broken text styling. Upload fonts once to your team account and Nexrender installs them on the render worker before After Effects starts.

​
Supported Formats

Only .ttf (TrueType Font) files are currently supported.

​
Upload a Font

Fonts are uploaded as multipart/form-data. The font field carries the file, and the optional familyName field lets you override the family name that Nexrender auto-detects from the font metadata. 
curl -X POST https://api.nexrender.com/api/v2/fonts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "font=@/path/to/Montserrat-SemiBold.ttf"
To override the auto-detected family name, include the familyName field: 
curl -X POST https://api.nexrender.com/api/v2/fonts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "font=@/path/to/CustomFont.ttf" \
  -F "familyName=My Brand Font"

​
Upload Fields

FieldTypeRequiredDescription
fontfileYesThe .ttf font file to upload
familyNamestringNoOverride for the font family name (auto-detected from file metadata if not provided)

​
Using Fonts in a Job

Reference uploaded fonts by their fileName in the fonts array of any job payload. Nexrender installs them on the render worker before rendering begins. 
{
  "template": {
    "id": "YOUR_TEMPLATE_ID",
    "composition": "main"
  },
  "fonts": [
    "Montserrat-SemiBold.ttf",
    "Roboto-Bold.ttf"
  ],
  "assets": []
}

​
Missing Fonts Warning

When you create a job, if any font listed in the fonts array hasn’t been uploaded to your team account, the API flags them in the missingFonts field of the response. The job is still created, but rendering may produce incorrect results. 
{
  "id": "01JTRDF7HCR8QAHYW8GPCP4S9Y",
  "status": "queued",
  "outputUrl": "https://nx1-outputs-eu.nexrender.com/.../job.mp4",
  "missingFonts": ["Roboto-Bold.ttf"]
}
Always resolve missing fonts before submitting production jobs.

​
Best Practices

  • Name font files clearly - OpenSans-Bold.ttf rather than font1.ttf
  • Keep naming consistent between your After Effects project and the uploaded file
  • Use preview mode to catch font issues cheaply before running full renders
  • Treat .ttf files as versioned assets - store them in source control alongside your templates

Authorizations

​
Authorization
string
header
required

Bearer token authentication using API tokens for team-based access control.

You can generate your own API token at: https://app.nexrender.com/settings/api-tokens

Body

multipart/form-data
​
familyName
string

Optional font family name override (auto-detected if not provided)

​
font
file

Font file to upload (supports TTF only)

Response

Font successfully uploaded and processed

Font file metadata for team-shared typography resources used in After Effects rendering

​
id
string

Unique font identifier

​
familyName
string

Font family name (e.g., "Arial", "Helvetica Neue") extracted from font metadata (or custom)

​
fileName
string

Original font file name as uploaded (supports TTF only). This is the file name referenced in pushed jobs.

​
createdAt
string<date-time>

ISO timestamp when the font was uploaded and processed