Fonts

Headless renders have no system fonts, so every non-generic font a program or overlay uses must come from the hosted catalog: self-hosted woff2 files on assets.vos.so, latin subset, one file per weight. This page is generated from the same catalog module the product reads, so it is always current.

Using a catalog family

• In a program config, declare each family and weight you use so the engine registers and awaits the faces before first render:

"fonts": [{ "family": "Playfair Display", "weight": 700,
            "url": "https://assets.vos.so/fonts/playfair-display/700.woff2" }]

• On a take's text overlays, set family to a catalog family name; the render loads it from the CDN, and unknown names fall back to the preset font on the fleet.
• As a machine manifest, GET vos.so/api/fonts returns families, hosted weight steps and file URLs.

Weights snap to the hosted steps; canvas cannot synthesize weights, so a weight the catalog does not host renders as its nearest neighbor. vos check warns on undeclared families.

The catalog

Related

• doc.json for where overlay text options live.
• 3D typefaces for the extruded-text faces.