TTF vs OTF: which font format should you use?

You've made or downloaded a font and the file is either .ttf or .otf. Does it matter which? For most uses, no — they render identically and every modern OS and design tool accepts both. But there are a handful of specific cases where one beats the other, and knowing the difference saves you from picking the wrong format and finding out the hard way.

This is the practical comparison. No marketing, no oversimplification.

The 30-second answer

• TTF (TrueType) — older, simpler, slightly larger files, uses quadratic Bézier curves. Best for: most use cases, web fonts, anything you want maximum compatibility with.
• OTF (OpenType) — newer, more capable, slightly smaller files for complex fonts, uses cubic Bézier curves. Best for: fonts with advanced typography (ligatures, alternates, stylistic sets) and professional design work.

For a handwriting font you made yourself, TTF is almost always the right choice. The advanced features OTF supports are rarely used in handwriting fonts, and TTF's compatibility is better in edge cases (older apps, Cricut software, some embedded systems).

The rest of this guide is the why.

Where TTF and OTF came from

TTF (TrueType) was developed by Apple in the late 1980s as a competitor to Adobe's Type 1 PostScript fonts. It was designed to be a single, scalable format that worked on screen and on paper.

OTF (OpenType) was developed jointly by Microsoft and Adobe in the mid-1990s. It's technically a superset of TTF — an OTF file can use either TrueType curve data or PostScript curve data internally, plus a bunch of extra typographic features.

Today both formats are part of the same OpenType specification. You'll sometimes hear "all OTF is OpenType, and all TTF is OpenType" — that's technically true. The distinction is really about what's inside the file.

The curve difference

The technical heart of the difference: how each format represents the shape of a letter.

TTF uses quadratic Béziers

Quadratic Bézier curves have one control point between each pair of anchor points. They're simpler mathematically. To represent a complex curve, TTF often needs more anchor points.

OTF uses cubic Béziers

Cubic Bézier curves have two control points between each pair of anchors. They're more expressive. The same complex curve can be drawn with fewer anchor points, which can make the file smaller for very complex glyphs.

Does this actually matter?

Visually, no. Both can represent the same shapes to a precision well beyond what any display can show. The difference is internal — how the font file is structured.

For most fonts, including handwriting fonts, the rendered output is identical. The file size difference is in the kilobytes, not megabytes.

OpenType features

The bigger practical difference is what each format supports for typographic features.

OTF was designed from the start to support a rich set of OpenType features:

• Ligatures — special combined forms for letter pairs like fi, fl, Th. Common in serif and script fonts.
• Contextual alternates — different glyphs for the same letter depending on what's next to it. Used heavily in script fonts to fake the look of natural handwriting variation.
• Stylistic sets — alternative versions of the whole alphabet (e.g., a more rounded variant, a more angular variant) that you can toggle on per text element.
• Small caps, swashes, oldstyle figures — typographic niceties that serious typefaces ship.
• Fractions, scientific notation, ordinals — automatic substitution of 1/2 into a proper fraction glyph, H2O into H₂O, etc.

TTF can support these features (OpenType features are technically format-agnostic), but support in practice is more uneven. Many tools assume TTF doesn't have them and skip the relevant lookup tables.

If you're making a handwriting font and you want it to automatically swap between three slightly different versions of e depending on what's around them, OTF is the right format and you'll need a font editor that exports OpenType features (Glyphs, FontLab, or FontForge). The font maker on this site outputs basic TTF without contextual alternates — fine for most purposes, not for advanced typography.

File size

A handwriting font with 73 characters and no advanced features will be roughly the same size in either format — usually 30-100KB. The difference is single-digit kilobytes either way.

For complex fonts with thousands of glyphs and extensive OpenType features (think professional foundry releases), OTF can be smaller because cubic Béziers represent complex curves more efficiently. But this matters at scale, not for typical use.

Compatibility

Here's where TTF still has a clear edge.

Modern OSes and apps

macOS, Windows 10+, iOS, Android, every modern browser, Office, Adobe CC, Affinity, Canva — all support TTF and OTF equally. Pick either.

Older or specialised software

• Cricut Design Space prefers TTF. Some users report OTF works fine, others have problems. If you're making a font for crafting use, TTF is the safer choice.
• Silhouette Studio also leans toward TTF.
• Older versions of Office (pre-2010) had spotty OTF support.
• Embedded systems, e-readers, and game engines often only support TTF.
• Some print drivers for non-PostScript printers handle TTF better than OTF.

If you have any chance of your font being used in one of those environments, ship it as TTF.

Web

WOFF and WOFF2 are the standard for web fonts (much smaller than either TTF or OTF), but if you're serving a raw font file, both TTF and OTF work in every modern browser. No difference.

When OTF wins

To be fair to OTF, there are real reasons to choose it:

1. Advanced typography. Ligatures, contextual alternates, stylistic sets, small caps — if your font uses these and you want them to work reliably, OTF is the format the typography community expects.
2. Working with type designers and foundries. Professional font work is almost always OTF (sometimes ".otf with PostScript curves", which is the more advanced sub-variant). If you're collaborating with a type designer, expect OTF.
3. Selling on font marketplaces. Some marketplaces prefer or require OTF. Check your destination's preferences.
4. Pixel-perfect display at small sizes on Windows. OTF with PostScript curves is generally considered to render slightly better at small sizes on Windows, particularly in environments without good hinting.

For a handwriting font being used personally, none of those usually apply.

Other formats you might see

• WOFF and WOFF2 — web-optimised wrappers around TTF or OTF. Smaller download size. Used for @font-face in CSS. You won't install these like fonts; they're for serving to browsers.
• EOT (Embedded OpenType) — old Microsoft web format. Effectively dead. Don't use unless you're supporting IE8, which you shouldn't be.
• SVG fonts — old web format. Also dead. Don't use.
• Variable fonts — newer feature inside the OpenType spec. One file contains an axis of weights, widths, or styles. Saves bandwidth on the web. Most handwriting fonts don't use this — variable axes are uncommon outside professional foundry releases.

If you're given a .zip of a font with TTF, OTF, WOFF, and WOFF2 versions inside, that's a complete package designed to cover every install scenario. Install the TTF or OTF on your computer; use the WOFF2 (or WOFF as fallback) on a website.

Converting between formats

You can convert TTF to OTF and vice versa using a font editor. Free options:

• FontForge (free, open source, ugly UI but does the job).
• Online converters like CloudConvert, OnlineFontConverter — fine for casual use.
• Glyphs Mini or FontLab (paid, professional).

A conversion preserves the visible glyphs but drops or rebuilds the OpenType features depending on the tool. If your font relies on ligatures or alternates, test after converting.

What format does the font maker on this site output?

The font maker on this site outputs .ttf. Three reasons:

1. Maximum compatibility. Cricut, Silhouette, older Office, e-readers, every OS and design tool — TTF works everywhere.
2. Simpler implementation. Without contextual alternates or stylistic sets in the source data, TTF's structure maps more cleanly onto a handwriting font.
3. Smaller files for the typical case. A 73-glyph handwriting font is meaningfully smaller as TTF than as a feature-rich OTF.

If you specifically need OTF (because you're submitting to a foundry, or your destination tool requires it), open the .ttf in FontForge and export as .otf. Five minutes, no loss of visible quality.

Quick reference

Question	Answer
Which is older?	TTF (1980s). OTF was built on top of it in the 1990s.
Which renders better?	Visually identical for almost all fonts.
Which has smaller files?	OTF, marginally, for complex fonts. TTF for simple ones.
Which is more compatible?	TTF. OTF works everywhere modern, but TTF works everywhere full stop.
Which supports advanced typography?	Both can, but OTF is the format the typography community uses for it.
Which should I pick for my handwriting font?	TTF.
Which does the font maker output?	TTF.

Now go make a font

If you haven't made yours yet, open the font maker and grab a .ttf in five minutes. Then install it on macOS, Windows, iOS, or Android, and start using it in Word, Docs, and Canva.