Skip to main content
A text layer renders in the font the template asks for. When that font is one you licensed rather than one we ship, upload it here once and every render on the account can reach it.

​
Font management

Gallery is the built-in catalogue, the open-licensed families every account renders from without uploading anything; My fonts is what this account has added. The catalogue belongs to the account rather than to a template, so a font added once reaches every mockup, with nothing to attach per mockup. The same catalogue answers over HTTP: an API key can list, retrieve, add and remove the same entries, and a font uploaded in the browser answers to the API under the same uuid a moment later.
Uploading is on the Pro and Scale plans, and every plan renders from the catalogue. Inside an organization the owner and editors upload and remove fonts, while a viewer renders with the same catalogue without changing it.
The gallery opens on Discover, one row per classification, and View all opens one in full. The search box matches family names as you type and narrows either view. A card stands for a family rather than a file, carrying its name, classification and style count; opening one previews every style in words you type at the size you drag to. The font gallery, grouped by classification, with your own uploads under My fonts.

​
Filter by classification

The tab bar carries the five classifications a font can hold, each with a slug the address takes as cat:
  • sans-serif
  • serif
  • handwriting
  • display
  • monospace
The view is in the address, so ?cat=serif and ?view=my are links you can share or bookmark. Over HTTP the same split is scope: all for both, system for the catalogue, custom for your own.

​
Upload your own font

1

Open My fonts

Switch the source control to My fonts. The header counts your uploads against what the plan allows, and Upload font opens the uploader.The My fonts tab, with the uploader card and the file size limit above it.
2

Add one file

Drop a TTF or OTF file on the card, or choose one from disk. One file per upload, so a family with Regular, Medium and Bold is three uploads and three PostScript names. Fonts carries the size ceiling and how many custom fonts each plan holds.
3

Confirm the licence

Tick the confirmation that you hold the right to use and embed the file. Uploading stays inactive until you do, and the API asks the same as license_confirmed. A public URL works in place of a file.
4

Render with it

The family lands under My fonts, and the response carries the uuid and postscript_name a render asks for. A font you upload is reachable by your account alone.

​
Use a font in a render

A render asks for a font by PostScript name or by uuid, set as font on a text layer override. Leave it out and the layer keeps the typeface the designer chose. A name that is not in your catalogue fails with FONT_NOT_FOUND, and a name that matches more than one font fails with FONT_AMBIGUOUS and hands back the candidates, so the uuid is the safer address. A text layer whose own font is missing renders with a default and warns you rather than failing the job. Text layers covers the override and the warnings, and Fitting and colour covers copy longer than the copy it replaces.

​
Remove a font

Removal works on the family: open it from My fonts, choose Remove font and confirm, and every style under it goes too. A mockup naming the removed font renders with a default font on its next render rather than failing, so a template keeps working while you replace the file. The catalogue is shared, so a removal applies to the whole account. Over HTTP the same removal takes a font’s uuid, one style per call.

​
API reference