You're ready to export and FontCreator offers several formats. This is the short version: pick by what you're doing, not by theory. Each option below links to the full how-to when you need the detail.

Quick answer

TTF — a safe default for desktop

For ordinary desktop use, TTF with TrueType outlines is often the safest default — it's the most broadly compatible choice and works for most variable-font workflows too. It's the right starting point when you're unsure, but it isn't the answer to every job: ship WOFF2 for the web, a color font for multi-color designs, and OTF (CFF) when you deliberately want PostScript outlines (all below).

OTF (CFF) — when you want PostScript outlines

Choose OTF with CFF (PostScript) outlines when you deliberately want cubic Bézier curves — for example, to keep the exact curve math you drew in a cubic workflow. The trade-offs between quadratic (TrueType) and cubic (PostScript) curves are explained in TrueType vs PostScript: TTF, OTF & Curve Formats.

WOFF2 — for the web

For a website, export WOFF2: it's a compressed web wrapper that loads fast and is supported by all modern browsers. WOFF2 is for web delivery, not for installing the font as a normal desktop font — for desktop use, export TTF or OTF instead. Only add a WOFF version if you still need to support very old browsers. Before you ship, consider trimming the character set so the file stays small — see Optimizing Webfonts by Reducing Character Sets.

Variable font — one file, many styles

Export a variable font when you want a single file that interpolates across axes such as weight or width, instead of shipping many static styles. FontCreator can build either flavour — TrueType-based (glyf/gvar outlines) or PostScript-based (CFF2 outlines) — so choose TrueType for the broadest compatibility, or CFF2 when you specifically want PostScript outlines and your target software supports it. Start with How to Make a Variable Font.

Color font — for multi-color designs

For color, FontCreator exports COLR/CPAL (compact, widely supported) and/or SVG color fonts. Which to use, and how to build them, is covered in Create OpenType Color Fonts.

Note — the extension doesn't tell the whole story. A .ttf or .otf file name doesn't fully reveal what's inside (which outline format, which tables). If that distinction matters to you, read TrueType versus OpenType Fonts.

Then set it up properly

Once you've picked a format, the full set of export controls — outline format, components, hinting, color options, web and variable targets, file names and folders — is walked through in Export a Font: TTF, OTF, WOFF & WOFF2. Run a quick Test & Validate pass before you release.

Frequently asked questions

Should I just export TTF? For most desktop uses, yes — TTF is the most compatible choice and works for most variable-font workflows too. Reach for OTF/CFF only when you specifically want PostScript (cubic) outlines, and WOFF2 for the web.

Is a variable font better than separate styles? It's better when users benefit from adjusting axes or when one file is easier to ship than many; otherwise static styles are simpler. See How to Make a Variable Font.

Can one font be both color and variable? Color and variable are separate concerns and support varies by application — decide based on where the font will be used, and test in your target apps.

Does the .ttf vs .otf extension decide the format? No. The extension is only a hint about what's inside; see TrueType versus OpenType Fonts.

What to read next

• Export a Font: TTF, OTF, WOFF & WOFF2 — every export setting, explained.
• TrueType vs PostScript: TTF, OTF & Curve Formats — the quadratic vs cubic deep dive.
• TrueType versus OpenType Fonts — terminology, myth-free.
• Test & Validate a Font Before Release — the pre-release checklist.