What Is a TTF Font? TrueType's Real History Explained

Where TrueType Actually Came From and Why Apple Built It At All

TrueType shipped with Apple's Macintosh System 7 in May 1991, developed primarily by engineer Sampo Kaasila under the project names Bass and later Royal. Apple built it as a direct competitor to Adobe's PostScript Type 1 fonts, which at the time required Apple to pay licensing fees to Adobe for the screen-rendering technology needed to display PostScript fonts clearly on a monitor. The first typefaces released in the new TrueType format were Times Roman, Helvetica, and Courier, replacing the older fixed-size bitmap fonts that earlier Macintosh System versions had relied on for on-screen text. Microsoft licensed and co-developed the format for Windows starting in the early 1990s, and by 1994 Microsoft was extending it into what eventually became OpenType.

That rivalry with PostScript is the reason TTF exists as a distinct outline system rather than everyone simply adopting Adobe's math: Apple needed a font technology it could render on-screen without paying per-font licensing costs, and TrueType's scalable outline system, designed to be interpreted directly by an operating system rather than a separate rendering engine, solved that problem. A TTF file sitting on a computer today is a direct technical descendant of that specific 1991 cost dispute between Apple and Adobe.

What's Physically Stored Inside a TTF File's Glyph Table

Every letter shape in a TTF file lives inside a table named glyf, describing each outline using quadratic Bézier curves, meaning one control point steers each individual curve segment rather than the two control points a cubic curve uses. Sitting alongside glyf are several supporting tables that make TrueType's rendering system work: loca stores the byte offset of every individual glyph within the larger glyf table, cvt holds shared reference values used across multiple glyphs' hinting instructions, and fpgm and prep store actual executable hinting instructions, small programs that adjust how curves render at specific pixel sizes so letters stay crisp rather than blurry on lower-resolution screens.

A structural detail most explainers skip entirely: the glyf table supports composite glyphs, meaning a single character's outline can be defined not as its own independent set of points, but as a reference to one or more other glyphs already in the font, combined with a positioning offset. An accented letter like "é" is frequently stored this way, as a composite referencing the base glyph for "e" plus a separate accent glyph placed at a specific offset above it, rather than as one fully independent outline. This saves space in the font file, since the accent shape only needs to be stored once and gets reused across every accented letter that needs it, but it means any tool reading raw glyph data has to resolve those composite references correctly before it has a complete, usable outline for that character.

What TTF Offers Over Its Rivals, and Where It Genuinely Falls Short

• Gain — the deepest pixel-level hinting control available: TrueType instructions can specify exactly how individual glyphs render down to specific pixels, which historically outperformed PostScript-style hinting at small sizes on low-resolution displays.
• Gain — near-universal native installation: every major desktop operating system has recognized TTF as an installable font format since the early 1990s, with no conversion step required.
• Lose — no OpenType layout features by default: a plain TTF file has no standard mechanism for ligatures, small caps, or contextual alternates unless GSUB/GPOS tables are specifically added, which technically turns it into an OpenType-flavored file.
• Risk — laborious, expert-level hinting work: building genuinely good pixel-level TrueType hints for a full character set is a specialized skill that historically took type foundries far longer than the lighter hinting model CFF-flavored OTF fonts use.
• Gain — composite glyphs keep file size down: reusing base glyph shapes for accented characters avoids duplicating outline data across every accented variant in a large character set.
• Lose — an older, less scalable kerning system: TTF's original 'kern' table stores kerning as explicit letter-pair values, which becomes unwieldy for fonts covering large multilingual character sets, compared to the class-based approach OpenType's GPOS table allows.

Which Systems Read TTF Natively, Documented by Version

Windows has installed TTF files through its native font manager since Windows 3.1 in 1992, and macOS has supported TrueType since its introduction on classic Mac OS in 1991, carried forward through every version to today's macOS. Linux desktop environments read TTF through the freetype rendering library, which has shipped as a standard component of nearly every major distribution for decades. Professional design applications including Photoshop, Illustrator, InDesign, and every major word processor read TTF without any conversion step, and it remains the single most broadly compatible font format across operating systems released at any point in the last three decades.

The compatibility gaps that do exist involve highly specialized software rather than mainstream operating systems: certain embroidery machine design programs, older CAD packages, and some engraving or vinyl-cutting software expect plain TTF-style glyf outline data specifically, and can reject or partially misread an OpenType file carrying CFF outlines instead, since that outline math is structurally different even though both files might carry the same .otf or .ttf-style extension conventions in casual use. This is the reverse compatibility direction of the concern most people expect, since TTF is usually assumed to be the more universally accepted format, and largely is, except in this specific narrow category of older specialized hardware-driving software.

Why One Specific Kind of Glyph Inside a TTF Can Break an Extraction Tool

A specific, real problem reported around font-editing and glyph-extraction tools involves a composite glyph, most often an accented letter, extracting as a blank shape, a misplaced accent, or two disconnected pieces instead of one complete character. The technical cause traces directly back to the composite structure described earlier: the tool read the top-level composite glyph record, which is really just an instruction saying "place this other glyph here, then place this other glyph there," without following those references through to actually assemble the two component outlines into one final path. A properly built font tool has to resolve every composite reference recursively before treating any letter as a single, complete shape, and tools built quickly without handling this case correctly are a documented, recurring source of exactly this failure.

A second, unrelated and separately documented complaint on Adobe's own community forums involves a TTF-flavored font and a CFF-flavored OTF version of the same typeface installed on different computers, causing a shared document to silently substitute one for the other depending on which machine opens it, with no obvious error message explaining why. The fix reported to resolve this consistently is standardizing which specific flavor of a font gets installed across an entire team or shared project folder, rather than letting whichever version happened to be available get installed ad hoc on each machine.

TTF Set Beside the Rival Format It Was Built to Compete With

Straight Answers About What a TTF File Actually Contains

Who actually invented TrueType, and why?
Apple, released in 1991 with System 7, built primarily to avoid paying Adobe's PostScript screen-rendering licensing fees while still delivering smooth on-screen text.

What's a composite glyph, and why does it matter?
It's a glyph, commonly an accented letter, built by referencing and positioning other existing glyphs rather than storing its own independent outline. Tools that don't resolve these references properly can extract broken or misplaced shapes.

Does TTF support fancy ligatures and alternate characters like OTF does?
Not by default. A plain TTF file has no built-in mechanism for those OpenType layout features unless GSUB or GPOS tables are specifically added to it.

Why did my TTF font substitute for an OTF version of the same typeface?
Some foundries release both a TrueType and a CFF-flavored version under similar names, and different computers may have installed whichever one was available first, causing silent substitution when a shared document opens elsewhere.

Is TTF still relevant compared to newer font formats?
Yes, for desktop installation and everyday document use. Web delivery today favors WOFF2 instead, since it's specifically compressed for that purpose, but TTF remains the standard for installing a font directly on a computer.