Download a font family from almost any foundry and you will usually find the same typeface twice, once as a .ttf and once as an .otf. They look interchangeable, and in most apps they behave that way. What sits inside them is where the two flavors part ways.

OpenType takes TrueType’s own sfnt container and lets it hold either TrueType outlines (quadratic curves with hinting instructions) or CFF outlines (cubic curves). It then adds GSUB and GPOS layout tables for ligatures, alternates and kerning.

The extension alone does not settle which outline type a font holds. Microsoft’s OpenType specification identifies it by the sfnt version tag at the start of the file, 0x00010000 for TrueType outlines and OTTO for CFF, and lets fonts with TrueType outlines use either .ttf or .otf.

How Are OpenType and TrueType Related?

YouTube player

A font with TrueType outlines already counts as a valid OpenType font.

The OpenType specification on Microsoft Learn describes the format as an extension of TrueType that keeps the same sfnt container and stays compatible with fonts built to the original spec.

Jelle Bosma of Monotype made the same argument on a W3C font mailing list in October 1997. In his reading, OpenType extends TrueType, and TrueType is not a subset of OpenType.

A High-Logic forum answer draws the line in file terms: a TrueType font is a TrueType-based OpenType font with no DSIG table and no OpenType Layout tables.

People mix up the labels all the time. A plain TrueType font has TrueType outlines and hinting instructions, and nothing from OpenType Layout. An OpenType font in the TrueType flavor has the same outlines plus layout tables and usually gets saved as .ttf, while the CFF flavor keeps cubic outlines in a CFF or CFF2 table and is saved as .otf.

Plenty of ranking guides still call OpenType the better format. Typography.guru’s “OpenType myths” article rejects the idea that it is more reliable, compatible or better supported than TrueType.

A Glyphs forum reply goes further. Every OpenType feature listed in that thread also works in TrueType-based fonts, and the two differ mainly in how outlines are defined and stored.

Where is graphic design headed in 2026?

Explore the newest graphic design statistics: industry growth, creative trends, job outlook, and insights shaping the design world.

Check the Data →

So the useful comparison is about outlines and hinting, and then about which layout tables a given font actually carries.

Where Did TrueType and OpenType Come From?

YouTube player

Apple designed TrueType and shipped it in System 7 in May 1991, Microsoft added it to Windows 3.1 in April 1992, and OpenType arrived later as a Microsoft and Adobe extension of that base (Microsoft Learn, “A brief history of TrueType”).

Apple announced its plan for a system-level font format in 1989. Monotype’s history of the period calls that announcement the first shot of the Font Wars with Adobe.

Licensing talks over Apple’s GX typography technology failed, so Microsoft built its own extension, TrueType Open, in 1994. Adobe joined in 1996 and brought its Type 1 outline technology, which is why the combined format needed a name that did not point back to TrueType (Wikipedia’s OpenType entry, consistent with engineers’ recollections on TypeDrawers).

The dates worth remembering:

  • Apple announced a system-level outline font format in 1989 (Monotype).
  • System 7 shipped with full TrueType support in May 1991 (Microsoft Learn).
  • Windows 3.1, from April 1992, was Microsoft’s first release with TrueType (Microsoft Learn).
  • On 14 September 2016, Microsoft, Adobe, Apple and Google announced OpenType 1.8 and Font Variations at ATypI Warsaw, covering both TrueType and CFF flavors (Monotype, LWN).
  • ISO published Edition 5 of ISO/IEC 14496-22 in July 2026 (ISO).

OpenType also became an international standard, published as ISO/IEC 14496-22, the Open Font Format. The 2007 edition was based on OpenType specification version 1.4 (ISO).

Edition 5 covers the TrueType and CFF outline formats together. It defines the data structures a rendering and text-shaping engine needs (ISO, 2026).

What Actually Differs Between .ttf and .otf Files?

Not much on the outside. A .ttf and an .otf file share the same sfnt wrapper, and the extension is only a hint about which outline data sits inside.

Extension Typical outline data sfnt version tag
.ttf TrueType (glyf, loca) 0x00010000
.otf CFF or CFF2 OTTO (0x4F54544F)
.ttc, .otc Several fonts sharing tables Set per font

Microsoft Learn says fonts with TrueType outlines may use either .ttf or .otf, depending on the creator’s wish for compatibility with older systems. Fonts that contain only CFF data use .otf.

So an .otf file is not proof of CFF outlines. It is rare in practice, but legal.

The outline type also shows up in two tables inside the file. CFF and CFF2 fonts must use maxp version 0.5, which holds only the glyph count, while TrueType fonts use version 1.0 with the full set of instruction limits. In the post table, CFF version 1 fonts are restricted to version 3.0, so glyph names live elsewhere, and versions 1.0, 2.0 and 2.5 apply to TrueType or CFF2 data (Microsoft Learn).

Capacity follows from that same table. Both flavors store the number of glyphs in a uint16 field, which caps a single font at 65,535 glyphs (Microsoft Learn, maxp).

Collections save space by sharing tables between fonts. Microsoft’s example is a set of Japanese fonts that draw their own kana but share identical kanji, and a collection can hold either outline type.

How to Check Which Outline Type a Font File Uses

  1. Open the file in a hex editor and read the first four bytes. In a single-font file, the table directory starts at byte 0.
  2. Match the value. 00 01 00 00 means TrueType outlines, and 4F 54 54 4F (the characters OTTO) means CFF or CFF2.
  3. For a .ttc or .otc file, the collection header gives the offset of each font’s table directory, so read the sfnt version there.
  4. Confirm in a font editor or table viewer. The tables glyf and loca point to TrueType, while CFF or CFF2 point to cubic outlines.
  5. Cross-check the maxp version: 1.0 for TrueType, 0.5 for CFF.

The test only identifies outlines. A TrueType-flavored file can still lack layout tables, and a CFF file can still be poorly hinted.

How Do Quadratic and Cubic Curves Change a Font?

Quadratic curves, defined by three points per segment, are what TrueType outlines use. CFF outlines use cubic curves, which take four.

Apple’s TrueType Reference Manual says a parabolic curve fits in a single quadratic segment, while more complex curves need several connected ones. A quadratic segment cannot form an S-curve, so a stroke that changes direction gets split. A cubic segment can bend that way in one piece.

Microsoft’s CFF2 documentation describes glyph outlines as sequences of cubic (third-order) Bezier curves and straight lines.

Both curve types describe glyphs as vector graphics, so enlarging text never produces blocky edges.

In the glyf table, curves are built from on-curve and off-curve points. When two off-curve points sit next to each other, an on-curve point is implied halfway between them. Positions are stored as offsets from the previous point, and the hinting instructions live with the glyph data.

CFF works differently. Glyphs are written as CharStrings, subroutines let them reuse shared data, and hint operations sit inside the CharString itself. The format has its origins in Adobe’s PostScript language.

That implied midpoint is also why cubic curves cannot simply be dropped into glyf. In a September 2023 thread on the MPEG-OTSPEC mailing list about that idea, one participant pointed out that two off-curve points would become ambiguous: two quadratics, or one cubic.

At text sizes, curve degree is rarely what readers see. A Glyphs forum reply says the formats now differ mainly in how outlines are stored, and a 2010 LuaTeX list post says the real contrast is more likely the hinting engine than the Bezier degree.

TypeType’s foundry notes add that PostScript-flavor contours are the easier ones to edit.

Which Format Renders Better on Screen?

Neither does universally. Rendering depends on the hinting method, the rasterizer and the operating system far more than on the .ttf or .otf extension.

TrueType hinting is a program stored in the font. Instructions such as MIAP and MIRP move points to control values and round them to grid lines (Microsoft’s TrueType hinting tutorial).

CFF turns that around. The font only declares stems and zones, and the rasterizer decides how to fit them. Adobe Typekit’s 2010 write-up summed it up as intelligence in the TrueType font versus intelligence in the CFF rasterizer.

Both approaches solve the same problem, which is deciding which pixels a thin stem covers at small sizes.

Renderer TrueType outlines CFF outlines
Windows GDI ClearType Horizontal anti-aliasing only Grayscale fallback
Windows DirectWrite ClearType, both directions Same ClearType path
macOS Instructions largely ignored Same rendering pipeline
FreeType Bytecode interpreter v40 by default Adobe hinting engine by default

The Windows rows come from Typekit’s 2010 posts and TypeDrawers discussion, the macOS row from TypeType’s foundry write-up. Check current Windows behavior before relying on them.

The FreeType row is documented. Version 2.7, released in September 2016, made the v40 bytecode mode the default for TrueType fonts, and for CFF the project credits Adobe with contributing the hinting engine it now uses by default.

Fonts can also tell the rasterizer which sizes get which treatment. In the OpenType gasp table, Microsoft’s typical values are grayscale only below 9 ppem, gridfitting from 9 to 16, and both above 16.

Experts still disagree about how far CFF’s hinting advantage goes. In an October 2020 MPEG-OTSPEC thread on removing CFF and CFF2 from the Open Font Format standard, one participant argued that CFF hint interpretation is not specified anywhere and that Adobe’s code in FreeType is all that exists.

Terence Dowling, a retired rasterizer implementer, answered that the hinting philosophy has been public since 1990. He added that the same logic would remove TrueType instructions, which major implementations also ignore or interpret in unspecified ways.

Typekit’s own verdict in 2010 had two halves. On aliased displays, TrueType hints and hand-made bitmaps are hard to beat, while CFF fonts need far less hinting data to look good once anti-aliasing is on.

Do TrueType Fonts Support OpenType Features?

YouTube player

Layout features come from a font’s GSUB and GPOS tables, not from its outline format, so a font gets them only if its creator built those tables.

Microsoft’s OpenType Layout chapters split the job in two. GSUB holds glyph substitutions such as ligatures, and GPOS holds positioning data such as kerning.

The tags you will meet first are liga for standard ligatures, smcp for small capitals, onum for oldstyle figures and calt for contextual alternates, all of them GSUB features. Kerning is the odd one out, since kern is a GPOS feature.

The feature registry reserves ss01 to ss20 for stylistic sets and cv01 to cv99 for character variants (Microsoft Learn). A font defines only the ones its designer drew.

HarfBuzz is the shaping engine that applies these lookups in Firefox, LibreOffice and Chromium. It reads TrueType-flavored and CFF-flavored fonts the same way (HarfBuzz user manual).

Older fonts stored kerning pairs in a separate kern table instead of GPOS, and Microsoft’s own chapters disagree on whether CFF fonts may do the same.

The kern chapter says CFF fonts are not supported by the kern table and must use GPOS. The recommendations chapter says the specification allows CFF fonts to keep kerning in a kern table and that many layout engines support it.

That chapter adds that the Windows GDI CFF driver ignores the table when it reports kern pairs through its pair kerning API.

A pure TrueType font has no GPOS at all, so its kerning lives in the kern table. Windows reads only format 0, a sorted list of pairs, and ignores class-based format 2 (Microsoft Learn).

TrueType fonts can also carry Apple Advanced Typography tables in place of OpenType layout tables. HarfBuzz supports those natively and shapes AAT fonts on any platform, so its Core Text integration on macOS and iOS is optional.

Apps differ in how they show you what a font offers. Adobe InDesign lists features the current font lacks in square brackets, such as [Swash], instead of hiding them (Adobe Help). Word has exposed ligatures, number forms and stylistic sets under Font, Advanced since Word 2010 (Microsoft Support). Figma applies OpenType features to every font and greys out the ones a font does not offer (Figma Help).

Test the specific font in the specific app. The extension does not tell you which features will appear.

Where Do OTF and TTF Fonts Work?

Font files prepared for a print production workflow

Windows, macOS and Linux text stacks all load both flavors, so compatibility problems come from what a given app accepts, not from the operating system.

Platform or app Accepted files Catch
Windows Settings .ttf, .otf Not every app supports custom fonts
macOS Font Book .ttf, variable .ttf, .ttc, .otf, OpenType-SVG, OpenType collections Legacy suitcase and Type 1 LWFN not recommended
Canva Brand Kit .otf, .ttf, .woff No WOFF2, files under 15 MB
HarfBuzz-based apps .ttf, .ttc, .otf, either outline flavor Includes Firefox, LibreOffice, Chromium, Pango

Apple’s list of installable formats leaves out WOFF and WOFF2. Installing either desktop flavor works the same way through Font Book, and the walkthrough for installing fonts on a Mac applies to both.

Canva adds a licensing condition to its file rules. Uploaded fonts should be licensed for embedding, and fonts that are not may fail to upload (Canva Help).

Microsoft’s font guide tells Windows users to install .ttf or .otf files, and it warns that some apps ignore custom fonts altogether. If a font installs but does not appear, try a second app before blaming the file.

Which Font Format Works Best on the Web?

Brand site serving its typeface as a webfont

WOFF2 does, whichever outline flavor sits inside it, with WOFF kept only as a fallback for older browsers (Monotype’s 2026 Font Format Guide, updated 29 August 2026).

WOFF2 reaches 97.4% of global browser usage, according to Can I use (StatCounter data for October 2026).

The format is a W3C Recommendation, and the 2018 text says it covers the entirety of the TrueType and OpenType specifications, including variable fonts, color fonts and collections. Its header carries a flavor field holding the sfnt version of the input font, so the file still records whether the outlines are TrueType or CFF.

Compression happens in two steps. A preprocessing pass removes redundant data, then Brotli compresses the result. W3C’s 2018 write-up measured WOFF2 at 27% smaller than WOFF 1.0 for TrueType-outline fonts, and 13.5% smaller for fonts with Type 1 glyphs. The W3C evaluation report from 2014 pointed the same way, with median gains over WOFF 1.0 of 20% to 26% for TrueType and 12% to 13% for CFF.

Adobe Typekit’s 2010 post names smaller files as one of the two main benefits of CFF. Because preprocessing helps TrueType outlines about twice as much as it helps CFF, the size gap narrows once both are WOFF2, so measure your own files before picking a flavor for weight.

List WOFF2 first in the src descriptor and WOFF second, as W3C’s own example does: src: url(example.woff2) format("woff2"), url(example.woff) format("woff");

If you load fonts through Google Fonts, the choice is made for you. Its CSS API serves WOFF2 to browsers that support it and strips hinting data for users whose browsers do not need it (web.dev, Google Fonts team).

Variable Fonts and Outline Type

Variable fonts are not a separate file format. They are an OpenType capability, and the specification allows them in both outline flavors.

Microsoft’s documentation describes CFF2 outlines as taking blend operations controlled by the font variations mechanism, while TrueType outlines draw their variation deltas from the gvar table.

One variable font can replace several static files by covering a continuous range of weights or widths. It is not automatically lighter: Google’s Fonts team warns that each added axis can almost double the file, and Monotype advises comparing against the one or two static cuts a site really uses.

Practice and specification disagree here. One format guide says variable fonts ship on the TrueType outline model, Glyphs’ handbook says they are always exported in the TrueType flavor, and Dalton Maag’s guide says CFF2-based ones lack widespread support.

The reasons show up fast once you test. Windows 10 version 1709 added official variable font support, and Dalton Maag’s compatibility notes cover only TrueType-based fonts. A Mozilla developer replying in the variable font tracking bug called CFF2 problems essentially a Windows limitation, because DirectWrite does not fully support CFF2. Can I use notes that OpenType-CFF2 support needs macOS 10.15 Catalina or later.

The practical read: ship TrueType-flavored variable fonts unless you control the whole rendering path.

Which Should You Use, OTF or TTF?

YouTube player

Use the file the foundry recommends. On desktop either flavor works, and for the web the answer is WOFF2 whatever the outline.

Monotype’s guide says to take the version the font provider recommends when several exist, and to verify it in the apps you need.

Scenario Pick Reason
Office documents, design apps TTF or OTF as supplied Check the app’s accepted file list
Website, one or two styles WOFF2 Compare static and variable sizes
Website, many weights or widths Variable WOFF2 One file replaces several cuts
Variable font on desktop TrueType flavor CFF2 support lags
Legacy browsers WOFF fallback Only where a project requires it

Print workflows follow the same rule. Take the foundry’s recommended file and test it in the layout app.

Choosing OTF because it is the newer format buys nothing, which makes it the obvious pick and the wrong one. Monotype’s capability table lists ligatures, small caps, numeral styles, kerning and variable-font data as supported in both flavors.

Two cases break the rule. An app may accept only some formats, as Canva’s upload rules show, and a format never settles licensing, because a web font license is a separate decision from the file you pick (Monotype).

When Converting Between TTF and OTF Goes Wrong

The conversion is exact in one direction only. Quadratic to cubic is lossless, while cubic to quadratic is an approximation.

FontForge’s documentation explains why. Any quadratic spline can be written as a cubic, but most cubic splines cannot be represented exactly by quadratics.

One browser-based converter’s guide claims the opposite for TTF to OTF, saying it would lose precision, and declines to offer that direction. FontForge’s math notes and Pdftools’ font-conversion write-up treat it as a trivial step, so the sources disagree on the easy direction.

When a conversion does fail, it usually fails in one of a few spots.

  • Curve fidelity suffers because fontTools’ cu2qu splits each cubic into more segments until the error falls under a tolerance, which defaults to 1/1000 of the em square.
  • TrueType instructions are bytecode and CFF carries stem hints, so a converter has to regenerate them (Glyphs ignores manual TrueType hints when autohint is on).
  • A TypeDrawers reply warns that exporting to CFF can bring rounding errors, or bigger files, when points sit at non-integer coordinates.

Renaming does not convert. Monotype notes that changing .ttf to .otf neither converts the outlines nor adds capabilities.

Licensing is the bigger trap. Conversion repackages outline data without transferring rights, and many desktop EULAs forbid exactly that kind of modification (Monotype).

Embedding rights sit in the OS/2 table’s fsType field, as installable, restricted, preview and print, or editable. Current versions of the specification treat those bits as mutually exclusive, and some applications assume the least restrictive permission when several are set (Microsoft Learn). The vendor sets them, so read the font licensing terms instead of inferring rights from the file.

If you need the other flavor, the safest route is to ask the foundry for it. Anyone who owns the sources can export both from Glyphs, RoboFont or FontForge, since all of them build TrueType and CFF fonts. And a file you may legally modify can be wrapped as WOFF2 instead of having its outlines touched.

Convert the wrapper, not the outlines.

OpenType vs TrueType FAQ

Is there any benefit to installing both the OTF and TTF versions of a font?

No. Monotype’s capability table lists ligatures, small caps, kerning and variable-font data as supported in both flavors, so a second copy adds no features.

Keep the version the foundry recommends and test it in your apps.

Why does a font download contain TTF, OTF, WOFF and WOFF2 files?

Each file targets a different job. TTF and OTF are for desktop installation, while WOFF and WOFF2 are compressed wrappers for websites that leave the outlines unchanged (Monotype).

The web files still need a web font license.

How do I install a TTF or OTF font on Windows?

Extract the zip if needed, right-click the .ttf or .otf file and select Install. Choose Install for all users to cover every account on the computer.

Installed fonts then appear under Settings, Personalization, Fonts (Microsoft Support).

Can OpenType fonts contain color or SVG glyphs?

Yes. The specification lets a font store monochrome or color bitmaps, or SVG documents, as alternate glyph descriptions beside TrueType or CFF outlines (Microsoft Learn).

macOS installs OpenType-SVG fonts as .otf files.

What does VF mean in a font file name?

VF marks a variable font. Microsoft recommends appending it to the file name after a delimiter and before the extension.

The extension itself stays the same, since variable fonts use the .ttf, .otf, .ttc and .otc extensions like static ones.

Why do some font files use .ttc or .otc?

Both extensions mark collections, meaning several fonts in one file. Microsoft’s recommendations say a collection should use either .TTC or .OTC, regardless of whether the fonts hold TrueType or CFF outlines. A .TTC extension is still acceptable for CFF collections when compatibility with older software that does not know .OTC matters.

Identical tables can be shared between the fonts, which saves file space.

Auditing Your Font Files by Outline Type

OpenType and TrueType files deserve an audit in order of exposure. Web-served fonts go first, since a licensing gap there is the costliest. Variable fonts come second because of CFF2 rendering failures, and in-house conversions come third, where hinting and curve defects tend to hide.

The order follows cost. A licensing breach carries legal weight, a rendering failure breaks pages for real users, and a soft curve costs only polish.

The recommendation carries one trade-off. A TrueType-flavored variable font renders reliably, but the exported quadratic curves replace the cubic ones the designer drew.

Verified on 6 November 2026, the second priority drops away once Windows text rendering handles CFF2 variable fonts as reliably as TrueType-flavored ones.

Bogdan Sandu
Share
Written by Bogdan Sandu

Bogdan Sandu is a seasoned designer who has been designing websites since 2008. Renowned for his expertise in logo design and visual branding, Bogdan has developed a multitude of logos for various clients. His skills extend to creating posters, vector illustrations, business cards, and brochures. Additionally, Bogdan's UI kits were featured on marketplaces like Visual Hierarchy and UI8. He also wrote in the past years on sites like Design Your Way, WebDesignerDepot, WPDean, Designmodo, Speckyboy, Slider Revolution, and more.