History of TrueType: How Apple Changed Typography Forever

The Origins of TrueType

Apple began developing TrueType in the late 1980s as a direct response to Adobe's control over the PostScript font market. Adobe had maintained a monopoly on high-quality outline fonts through their proprietary Type 1 format since 1984. The Type 1 specification was kept secret, and Adobe charged significant licensing fees to font foundries and OEMs who wanted access to professional-quality font rendering on their products.

Apple's motivation was to create a royalty-free alternative that would give them control over font rendering on the Macintosh platform without depending on Adobe. The project was initially codenamed "Bass" (later "Royal") within Apple. Engineers on the project understood that for TrueType to succeed, it would need to match or exceed Type 1 quality at screen sizes, where Adobe fonts held a clear advantage thanks to their sophisticated hinting system.

TrueType was publicly announced at the Seybold publishing conference in September 1989 by Apple and Microsoft jointly. Apple CEO John Sculley presented the technology as a way to free the industry from Adobe's pricing control — a bold strategic move that immediately put Adobe on the defensive. The announcement forced Adobe to respond quickly, ultimately leading them to open the previously secret Type 1 specification in March 1990. The mere announcement of TrueType had already achieved a major competitive goal before a single line of final production code shipped to users.

Sampo Kaasila and the Technical Design

Finnish-born engineer Sampo Kaasila was the primary architect of TrueType at Apple. He designed the TrueType rasterizer — the mathematical engine responsible for converting outline font data into the pixel grids that screens display. Kaasila's rasterizer had to produce sharp, readable text at sizes as small as 8 or 9 pixels tall on the low-resolution screens of the late 1980s, a genuinely difficult engineering problem that required both mathematical sophistication and deep understanding of human visual perception.

One of Kaasila's most significant contributions was the design of TrueType's hinting instruction set. TrueType hinting instructions are embedded directly in the font file as a bytecode program executed by the rasterizer. This bytecode interpreter approach was more powerful than PostScript Type 1 hints, which were declarative suggestions rather than explicit instructions. TrueType hinting allowed font designers to precisely control pixel placement at small sizes, snapping specific points to grid positions and controlling how strokes thickened or thinned at different resolutions.

The complexity of TrueType hinting became both its greatest strength and a significant practical limitation. While the system could produce exceptional results when implemented by skilled hinting engineers, creating high-quality TrueType hints required specialized expertise that few type designers possessed. This gap between theoretical capability and practical implementation difficulty would influence font production workflows for the next two decades.

Kaasila later left Apple to work at Type Solutions and subsequently joined Monotype Imaging, where he continued to work on font rendering technology. His contributions to TrueType remain foundational to the font rendering infrastructure used by billions of devices today — an achievement that has largely gone unrecognized outside specialist circles despite its enormous practical impact.

Quadratic vs Cubic Bezier Curves

One of the most significant technical decisions in TrueType's design was the choice to use quadratic Bezier curves rather than the cubic Bezier curves used by PostScript Type 1. This difference has practical implications for font designers, developers, and the tools that process fonts — effects that persist in the font ecosystem to this day.

Quadratic curves were chosen for TrueType primarily for computational efficiency. At the time of development (1987-1989), personal computers had limited processing power, and font rasterization needed to be fast enough to feel responsive on hardware without dedicated graphics processors. Quadratic Bezier curves require fewer floating-point operations to evaluate than cubic curves, making them a practical choice given the hardware constraints.

However, cubic curves can describe more complex shapes with fewer control points, making them the preferred choice for type designers who work by manipulating curve handles. A single cubic Bezier segment can sometimes require two quadratic segments to approximate with equivalent accuracy, which means TrueType fonts occasionally need more outline points to represent the same shapes — resulting in somewhat larger file sizes for complex glyphs.

This is precisely why OpenType, introduced in 1996, supports both outline types within the same container format. Fonts originally designed as TrueType retain their quadratic outlines (.ttf files or OpenType fonts with TrueType outlines), while fonts designed in PostScript tools retain their cubic CFF outlines (.otf files). Variable fonts introduced in OpenType 1.8 (2016) continue to support both outline types, preserving this historical distinction in today's most modern font technology.

Microsoft Licenses TrueType

In 1989, Microsoft licensed TrueType from Apple as part of a broader technology exchange agreement. Microsoft received TrueType technology, while Apple received access to Microsoft's virtual memory technology for use in future Mac operating systems. This deal was strategically important for both companies and represented a rare moment of cooperation between two firms that were increasingly direct competitors in the personal computing market.

Microsoft needed a high-quality font technology for Windows that did not depend on Adobe, which had increasingly strained relations with Microsoft over PostScript licensing terms and the direction of the font technology market. Apple needed Microsoft to adopt TrueType to ensure it became an industry standard rather than a platform-specific curiosity. With Microsoft's endorsement and planned Windows integration, TrueType would instantly gain access to the dominant computing platform, creating a market reality that no font foundry or software company could ignore.

Microsoft engineer Greg Hitchcock led the effort to implement TrueType support in Windows. The implementation work was substantial — integrating a font rasterizer into the Windows graphics subsystem, ensuring compatibility with existing applications, and building the management infrastructure needed for users to install and manage fonts.

Microsoft also invested heavily in creating TrueType versions of core fonts, commissioning the "Core fonts for the Web" project that produced Arial (a Helvetica-inspired design by Monotype), Times New Roman (Monotype's adaptation of the classic Times typeface), Courier New, Verdana (designed by Matthew Carter specifically for screen legibility), Georgia (also by Carter), and other widely-used typefaces that became de facto standards on Windows systems worldwide.

TrueType on Windows 3.1

Windows 3.1, released in April 1992, was the first Windows version to include built-in TrueType support. Previously, Windows relied on bitmap fonts for screen display and PostScript fonts (which required the separately purchased Adobe Type Manager software) for high-quality output. TrueType's inclusion in Windows 3.1 represented a watershed moment for digital typography that transformed the everyday experience of computing for millions of people.

Windows 3.1 shipped with 14 TrueType fonts as part of the base installation, including Arial, Times New Roman, Courier New, Symbol, and Wingdings. For the first time, every Windows user had access to scalable, high-quality fonts without purchasing additional software. Documents could be printed at any size without pixelation, and the same font that appeared on screen would render identically on the printer — a concept called WYSIWYG (What You See Is What You Get) that had previously required expensive proprietary hardware and software.

The impact on font adoption was immediate and dramatic. By 1993, TrueType had become the dominant font format on personal computers, installed on tens of millions of Windows machines worldwide. Type foundries that had previously focused exclusively on Type 1 fonts began producing TrueType versions of their libraries to meet market demand. The rapid expansion of TrueType's installed base was a major blow to Adobe's Type 1 font business, though Adobe responded by releasing its own TrueType versions of popular fonts and accelerating development of what would eventually become OpenType.

TrueType's Lasting Legacy

TrueType's influence extends far beyond its original design goals. The format became the structural foundation for OpenType (announced 1996, first shipped in Windows 2000 and Mac OS X), which added PostScript CFF outline support while retaining TrueType's table-based binary container structure. Every OpenType font — regardless of whether it contains TrueType or CFF outlines — inherits the organizational architecture that Sampo Kaasila and the Apple engineering team designed in the late 1980s.

TrueType's hinting technology influenced display rendering on every major platform. The bytecode interpreter that Kaasila designed became a model for how fonts communicate rendering preferences to operating systems. Modern font rendering engines in Windows (DirectWrite), macOS (CoreText), and Linux (FreeType) all descended conceptually from the rendering philosophy embodied in TrueType's design.

The .ttf file extension remains one of the most widely recognized font formats globally. Today, TrueType outlines are still used in countless popular fonts, including system fonts on Windows, Android, and many Linux distributions. Web font formats WOFF and WOFF2 frequently contain TrueType outlines wrapped in their compressed containers. For a technology developed by a small team in the late 1980s to challenge a proprietary monopoly, TrueType's persistence and continued relevance nearly four decades later is a remarkable achievement in technology standardization.

Related History Pages

Explore more of the history behind the font formats and technologies that shape digital typography today.