Brand systems

One brand voice, several scripts, identical typography.

Custom fonts are where multi-market campaigns most often drift off-brand: a missing weight here, a substituted Arabic face there. Handling licensing, uploads and fallbacks deliberately keeps every market consistent.

  • Licensed brand faces
  • Arabic and Latin pairing
  • Verified before export
  • No credit card required · Full per-size control
Brand typography
1080×1080
One approved creative
Adapted formats
1:1 square
4:5 portrait
9:16 story
Before uploading

Licensing and file preparation.

Getting these two right removes most of the typography problems that surface later in the campaign.

Check the licence scope

Desktop, web, app and broadcast licences cover different uses, and some foundries require a separate permission for uploading fonts into a production tool. Confirm the scope before the campaign, not during it.

Prepare the right files

OTF, TTF or WOFF2, one file per weight and style you actually use. Keep the foundry originals; files re-exported from a design application often lose kerning and OpenType features.

Account for missing weights

If a weight is absent the renderer fakes it. Faux bold thickens strokes unevenly and faux italic simply slants the letterforms — visible immediately next to a real weight.

Define the fallback

Choose a fallback with comparable x-height and width so a missing glyph does not re-wrap the headline. Leaving this to the system default is how markets end up with different line breaks.

Multi-script

Pairing Arabic and Latin without losing the brand.

Arabic and Latin typefaces rarely align at the same point size. Consistency here is optical, not numeric.

Match apparent size

Arabic text usually needs a slightly larger size than the Latin face beside it to read at the same visual weight.

Increase line height

Ascenders, descenders and diacritics need more vertical room. Latin line-height values applied to Arabic look cramped.

Verify glyph coverage

Confirm the Arabic face covers the numerals, diacritics and punctuation the copy uses before the campaign is localized.

Keep weights parallel

Map each Latin weight to its closest Arabic counterpart so the same hierarchy reads across markets.

Watch shaping

Arabic letterforms connect contextually. A face without proper shaping support produces disconnected, incorrect text.

Test the real copy

Test with the actual localized strings, not placeholder text — real copy exposes length and wrapping differences immediately.

Sequence

A repeatable font setup for every market.

  1. 1

    Confirm licensing

    Verify the brand's licence covers the intended use in every market before uploading anything.

  2. 2

    Upload complete families

    Every weight and style the brand actually uses, per script, stored in the Brand Kit for that brand.

  3. 3

    Assign roles

    Map headline, subhead, body and disclaimer to specific faces and weights, for both Latin and Arabic.

  4. 4

    Set fallbacks

    Choose a deliberate fallback per script so a missing glyph never silently changes the layout.

  5. 5

    Render and verify

    Preview real localized copy at real ratios, then check one export before running the full set.

Pre-export checks

Rendering and export verification.

  • Every weight referenced by the layout is actually uploaded
  • No faux bold or faux italic in any output
  • Diacritics and descenders are not clipped
  • Arabic text shapes and connects correctly
  • Numerals render in the intended style per market
  • Line breaks match the approved copy in each language
  • One export compared against the on-screen preview
  • Fonts confirmed loaded before the full export runs
Where this fits

Typography inside the wider workflow.

Fonts belong in the brand system rather than in individual campaign files — see building a reusable Brand Kit for how to structure that. For direction-aware layout beyond typography, read RTL ad production for Arabic campaigns. The production workflow shows where font rules are applied, and the per-size QC checklist covers the final render inspection before delivery.

Questions

Frequently asked questions

Do I need a specific licence to use a brand font in ad production?
Usually yes. Desktop, web and app licences cover different uses, and some foundries treat uploading a font to a production tool as a separate permission. Check the licence text or ask the foundry before uploading.
Which font file formats should I upload?
OTF, TTF and WOFF2 are the common choices. Upload one file per weight and style you actually use, and keep the original files rather than re-exported copies from a design file.
What happens if a weight is missing?
The renderer synthesises it — faux bold or faux italic — which distorts letterforms and looks subtly wrong next to the correctly weighted version. Upload the real weight instead of relying on synthesis.
How should fallback fonts be chosen?
Pick a fallback with similar x-height and width so a missing glyph does not change line breaks. Define the fallback deliberately rather than letting the system default decide.
How do you pair an Arabic typeface with a Latin one?
Match optical weight and apparent size rather than point size. Arabic typefaces usually need a slightly larger size and more line height than the Latin face they sit beside.
Why does exported text look different from the on-screen preview?
Almost always because a font was not fully loaded when the export ran, or a weight fell back. Confirm every weight is present, then compare one exported file against the preview before running the full set.
Keep reading
All resources

Ready to automate your creative production?

Start with one approved creative, produce every required size, and keep full control over each output before export.

No credit card required · Full per-size control