Complete Font Format Timeline: 1960s to 2020s
From fixed-size bitmap characters on mainframe terminals to COLRv1 gradient color fonts on modern browsers, this comprehensive timeline traces every major milestone in digital font format history — the technical innovations, the business rivalries, and the open standards that shaped how billions of people read text on screens today.
TL;DR - Key Takeaways
- • Bitmap fonts dominated the 1960s-80s, limited to fixed sizes and low resolution
- • PostScript Type 1 (1984) and TrueType (1991) brought scalable outline technology
- • OpenType (1996) unified TrueType and PostScript in one universal format
- • Web fonts evolved: EOT (1997) → WOFF (2010) → WOFF2 (2014)
- • Variable fonts (2016) and COLRv1 color fonts (2021) represent the latest advances
In this article
Digital font formats have evolved dramatically over six decades, driven by an interplay of technical constraints, business competition, and the evolving needs of designers and readers. Each major format transition reflected a genuine engineering challenge: how to represent typographic shapes efficiently, render them crisply at arbitrary sizes, compress them for network delivery, and encode the full complexity of human writing systems.
This timeline charts the key milestones from the earliest bitmap fonts of the 1960s through the sophisticated variable fonts and color font technologies of the 2020s. Each section provides historical context, technical explanation, and the key people and organizations involved — giving you a complete picture of how the tools typographers and web developers use today came to be.
Understanding this history is not merely academic. The legacy of each format era lives on in modern software — TrueType hinting code still executes in every Windows font rendering stack, PostScript CFF outlines are inside millions of OpenType .otf files, and the design decisions of the 1980s and 1990s continue to shape how fonts are created, licensed, and distributed today.
The Bitmap Era: 1960s-1980s
The earliest digital fonts were bitmap fonts — grids of pixels where each character was defined at a specific size. Each character existed as a rectangular array of on/off values, where a 1 meant the pixel should be filled and a 0 meant it should be empty. This representation was simple, fast to render, and perfectly suited to the raster displays and dot-matrix printers of the era. It was also fundamentally limited: a font defined at 12 points could only display at 12 points without visible degradation.
The concept dates to the 1960s, when mainframe computers used fixed-width bitmap characters for terminal output. Early displays like the IBM 3270 (1971) and DEC VT100 (1978) used character ROM chips containing bitmap glyphs for their character sets. These were not fonts in the typographic sense — they were fixed bitmaps for the ASCII character set, with no variation in weight or style.
The Xerox Alto (1973), the first computer with a graphical user interface, used proportional bitmap fonts for on-screen display — an innovation that directly influenced the Macintosh interface a decade later. Alto fonts were created by Xerox PARC researchers including Charles Simonyi, who later joined Microsoft. Donald Knuth's Metafont system (1979) was among the earliest attempts at programmatically described scalable fonts, using mathematical equations to generate bitmaps at specified resolutions — an important intellectual predecessor to outline font technology.
Apple's original Macintosh (January 1984) shipped with bitmap fonts designed by Susan Kare, a graphic designer with a background in fine arts and no prior experience in digital typography. Kare created the original Mac system fonts — Chicago, Geneva, Monaco, and Cairo — as pixel art, carefully crafting each glyph at the specific sizes that would appear on the Mac's 72 dpi screen. These fonts were notable for their legibility and character at small sizes, and Chicago remained the Mac's system font until 1999.
The fundamental limitation of bitmap fonts — that each size required a separate, hand-crafted bitmap file — was becoming untenable by the mid-1980s. A complete font family might require dozens of separate files for different sizes, weights, and styles. Storage was expensive, and the design labor required to create bitmaps at each needed size was substantial. The industry needed a way to describe font shapes mathematically, so that a single description could be rendered crisply at any size.
Key Bitmap Era Milestones
- 1960s-70s: Fixed-width bitmap characters in terminal ROMs; no concept of a font file
- 1973: Xerox Alto introduces proportional bitmap fonts for GUI display
- 1979: Donald Knuth releases Metafont, the first system for algorithmically described fonts
- 1984: Apple Macintosh ships with Susan Kare's bitmap system fonts (Chicago, Geneva, Monaco)
- 1984: Adobe PostScript and Type 1 begin rendering the bitmap era obsolete for professional printing
The PostScript Revolution: 1984
Adobe's PostScript page description language, released in January 1984, transformed professional typography by representing both text and graphics using mathematical descriptions rather than fixed pixels. PostScript described pages in device-independent terms — a PostScript file could be rendered at any resolution, on any PostScript-capable output device, producing output optimized for that device's capabilities.
PostScript was created by John Warnock and Charles Geschke, who had both worked at Xerox PARC before co-founding Adobe Systems in 1982. Warnock had developed an earlier page description language called Interpress at Xerox, and PostScript was a refined successor influenced by that work. The Apple LaserWriter (March 1985) was the first major product to incorporate a PostScript interpreter, launching the desktop publishing revolution. For the first time, small businesses and design studios could produce typeset-quality output without hiring professional typesetters.
Adobe's Type 1 font format, which accompanied PostScript, used cubic Bézier curves to describe glyph outlines. A single Type 1 font file contained the complete mathematical description of every glyph, with hinting instructions that told the renderer how to adjust curves for optimal rendering at small sizes. The critical business innovation was that Adobe kept the Type 1 specification proprietary and encrypted the hinting data — font foundries had to pay Adobe licensing fees to create Type 1 fonts, and users needed Adobe Type Manager (ATM) software to render them on screen.
By 1989, Adobe's annual revenue had reached $121 million, with font technology licensing representing a substantial and highly profitable portion. Adobe licensed its PostScript interpreter to printer manufacturers and charged foundries for access to the Type 1 development tools. The company effectively controlled the professional digital font market, and this profitable monopoly would soon face a serious challenge from an unexpected direction.
PostScript's Lasting Impact
PostScript remains in use today, particularly in professional printing workflows. The PDF format (introduced by Adobe in 1993) is built on PostScript concepts. OpenType fonts can optionally use PostScript CFF (Compact Font Format) outlines — a direct descendant of Type 1 — giving modern fonts an unbroken technical lineage back to 1984.
TrueType Arrives: 1991
By 1987, Apple was growing increasingly frustrated with its dependence on Adobe for high-quality font technology on the Macintosh. Every Mac sold helped fund Adobe through PostScript licensing fees, and Apple's control over font quality and availability was constrained by Adobe's business decisions. Apple authorized a secret development project to create an alternative outline font technology that would be royalty-free and entirely under Apple's control.
Sampo Kaasila, a Finnish engineer at Apple, was the lead developer of the TrueType rasterizer and format specification. Kaasila's design differed from PostScript in a key technical choice: TrueType used quadratic Bézier curves rather than cubic curves. Quadratic curves require more points to describe complex shapes but are computationally faster to rasterize — an important consideration for the CPUs of the late 1980s. TrueType also included a powerful bytecode hinting system that allowed font designers to write precise pixel-level rendering instructions, potentially enabling better on-screen rendering than Type 1 at small sizes.
TrueType was announced at the Seybold publishing conference in September 1989, causing significant disruption in the font industry. Apple had simultaneously negotiated a licensing deal with Microsoft, trading TrueType technology for Microsoft's virtual memory technology used in System 7. The Apple-Microsoft alliance against Adobe was strategically significant: it guaranteed that TrueType would reach both major personal computer platforms simultaneously, making it impossible for Adobe to marginalize the new format.
TrueType shipped as part of Apple System 7 (May 1991) and Microsoft Windows 3.1 (April 1992). Windows 3.1 bundled several high-quality TrueType fonts including Arial (a Helvetica alternative commissioned by Microsoft from Monotype), Times New Roman, Courier New, Symbol, and Wingdings — giving tens of millions of Windows users access to professional-quality scalable fonts for the first time at no additional cost. This bundling strategy was decisive: TrueType rapidly displaced Type 1 in the consumer and prosumer markets.
OpenType Unites the Industry: 1996
By the mid-1990s, the font market was fragmented between TrueType (dominant on personal computers) and Type 1 (still preferred by professional designers and print houses). Application developers had to support both formats. Font foundries had to maintain two versions of every typeface. The incompatibility created significant friction throughout the industry.
In 1996, Microsoft and Adobe jointly announced OpenType — a grand compromise that would incorporate both technologies in a single specification. OpenType used TrueType's sfnt container format and table structure, and it supported both TrueType quadratic outlines and PostScript CFF (Compact Font Format) cubic outlines within the same container. A font designer could use either outline technology; the OpenType wrapper handled both equally.
Beyond resolving the outline format conflict, OpenType added genuinely new capabilities that neither TrueType nor Type 1 had offered. The GSUB (Glyph Substitution) and GPOS (Glyph Positioning) tables enabled sophisticated typographic features: standard ligatures, discretionary ligatures, small capitals, old-style figures, stylistic alternates, contextual alternates, ordinals, fractions, swashes, and more — all accessible through CSS font-feature-settings today. OpenType also dramatically expanded Unicode coverage, allowing single font files to contain thousands of glyphs spanning multiple scripts and languages.
Apple was initially reluctant to embrace OpenType — the company had invested significantly in its own AAT (Apple Advanced Typography) extension to TrueType, which offered similar features through a different mechanism. Apple eventually supported OpenType while maintaining AAT support, leading to an extended period where fonts needed to encode their advanced features twice (in both GSUB/GPOS and morx/kerx tables) to work optimally on both Mac and Windows. This situation gradually resolved as OpenType became the universal standard and AAT-only features became less common.
OpenType received ISO standardization in 2007 as ISO/IEC 14496-22, which placed it within the MPEG-4 family of standards governing font embedding in multimedia. This formalized its status as an international standard and ensured its long-term stability. As of 2026, OpenType (in its various versions through 1.9) remains the universal desktop font format, with over 99% of professionally produced fonts available in OpenType.
Web Font Formats: 1997-2014
The web's earliest font format was not really a format at all — it was the @font-face rule in the CSS2 specification (1998), which defined the syntax for referencing external font files. However, browser support was minimal and inconsistent. The early web relied on a small set of "web-safe" fonts — Arial, Times New Roman, Georgia, Verdana, Trebuchet MS — that were reliably present on both Windows and Mac systems.
EOT — Embedded OpenType (1997)
Microsoft's proprietary web font format for Internet Explorer, introduced with IE 4.0. EOT applied compression and DRM binding to specific domains, preventing font files from being freely redistributed from a web server. Microsoft submitted EOT to the W3C as a web standard in 2008, but it was rejected by the WebFonts working group in favor of developing WOFF. EOT is now completely obsolete, unsupported in all modern browsers.
SVG Fonts (2001)
The SVG specification included a font description format in which glyph outlines were specified in SVG path notation embedded in an XML document. SVG fonts had several serious disadvantages: they were enormous (essentially uncompressed), lacked hinting, and had no standard way to encode font metadata. They achieved significant support in early WebKit (Safari) but were never adopted by Firefox, IE, or Chrome for web use. SVG fonts are now deprecated and unsupported in all major browsers.
@font-face Revival (2008)
Safari 3.1 (March 2008) re-enabled @font-face support for TrueType and OpenType fonts, a feature that had been in the CSS2 specification but never widely implemented. This sparked the modern web font movement, as designers suddenly had access to custom typography on websites. The technique spread rapidly, though it initially relied on serving raw TTF/OTF files — which raised font licensing concerns since the files were freely downloadable by anyone.
WOFF 1.0 (2010)
The Web Open Font Format was proposed in 2009 by Erik van Blokland (Type Supply), Tal Leming, and Jonathan Kew (Mozilla). WOFF wrapped TrueType or OpenType font data in a container with zlib compression and a standardized metadata block. The format became a W3C Recommendation in December 2012 and quickly achieved universal browser support. WOFF provided ~40% file size reduction and a clear web-specific licensing signal (the metadata identified the font's origin), making it acceptable to type foundries that had been reluctant to license fonts for web use.
WOFF2 (2014)
Google developed WOFF2 as a successor to WOFF 1.0, adding Brotli compression and a font-specific glyph transform preprocessing step. The result was files approximately 25-35% smaller than WOFF 1.0. Chrome 36 (July 2014) was the first browser to support WOFF2. The format became a W3C Recommendation in March 2018 and now has 97%+ global browser support. WOFF2 is the default and recommended format for web font delivery in 2026.
The Web Font Service Revolution
Two services transformed web typography by solving the licensing and hosting problem:
- Typekit (September 2009, now Adobe Fonts): The first major web font hosting service. Typekit negotiated licensing deals with major type foundries and served fonts via JavaScript, allowing designers to use commercial typefaces on the web for the first time through a subscription model.
- Google Fonts (May 2010): A free, open-source web font library that lowered the barrier to web typography dramatically. By hosting fonts on Google's CDN and serving them with simple CSS @import, Google Fonts made professional web typography accessible to every website, regardless of budget. As of 2026, Google Fonts serves hundreds of billions of font requests per day.
Variable Fonts and Beyond: 2016-Present
OpenType 1.8, published in September 2016, introduced font variations — commonly known as variable fonts. The specification was developed jointly by Apple, Google, Microsoft, and Adobe, representing the most significant cooperative effort in font technology since OpenType itself. Variable fonts allow a single font file to contain a continuous design space with multiple variation axes, rather than discrete named instances.
The standard axes defined in OpenType 1.8 include weight (wght), width (wdth), italic (ital), slant (slnt), and optical size (opsz). Font designers can also define custom axes with four-character tags. Registered axes are accessed via familiar CSS properties like font-weight and font-stretch; custom axes use font-variation-settings.
The performance benefits of variable fonts for web use are significant. A type family previously requiring eight separate weight files (Thin through Black) can be replaced by a single variable font file that is often smaller than just two of the static files it replaces. Variable fonts reduce HTTP requests, reduce total download size, enable smooth weight animations, and allow fine-tuned weight selection for precise typographic control. Browser support achieved broad coverage by 2018: Chrome 62 (October 2017), Firefox 62 (September 2018), Safari 11 (September 2017), and Edge 17 (April 2018).
Apple introduced a conceptual precursor to variable fonts in 1991 with TrueType GX Variations, which offered a similar design space concept. GX Variations was available on classic Mac OS but never achieved wide adoption due to limited tool support and the absence of a corresponding web or Windows implementation. The OpenType variable font specification incorporated and refined these concepts in a fully cross-platform, tool-supported implementation.
COLRv1: Color Fonts (2021)
COLRv1 is an expansion of the COLR table for color fonts, introduced in OpenType 1.9 with broad browser support arriving in Chrome 98 (February 2022) and Firefox 107 (November 2022). It enables multi-colored glyphs with gradients, compositing, and geometric transformations — capabilities previously impossible in scalable font technology.
Earlier color font approaches included CBDT/CBLC (bitmap emoji, used by Google), sbix (bitmap emoji, used by Apple), and SVG-in-OTF (supported by Firefox and older Safari). All of these approaches embed raster images or complex SVG documents inside font files, which don't scale as cleanly and require large file sizes for high-resolution displays. COLRv1's vector-based approach produces crisp output at any size and resolution, and COLRv1 fonts are dramatically smaller than bitmap emoji fonts.
The Noto Color Emoji font in COLRv1 format is approximately 1.8 MB, compared to 10+ MB for bitmap equivalents at high resolution. COLRv1 fonts also support the full CSS color model including P3 and other wide-gamut color spaces, enabling colors that bitmap fonts cannot reproduce on modern high-color displays.
The current frontier of font technology includes per-glyph subsetting (serving only the exact characters used on each page, computed at request time using the unicode-range descriptor and progressive font enrichment proposals), and continued improvements to variable font tooling that make the format accessible to independent type designers. The next major OpenType version is expected to formalize features currently in development, including improvements to the variations specification and new table types for advanced script support.
The Complete Timeline Table
The following table summarizes every major font format milestone from the 1960s to the present, providing a single-reference chronology for the entire history covered in this article.
| Year | Format / Event | Key Detail |
|---|---|---|
| 1960s-70s | Bitmap fonts | Fixed-size pixel grids for computer displays and terminals |
| 1973 | Xerox Alto | First GUI computer; proportional bitmap fonts for on-screen display |
| 1979 | Metafont (Knuth) | First algorithmically described fonts; early scalable font concept |
| 1984 | PostScript & Type 1 | Adobe's scalable outline fonts using cubic Bézier curves |
| 1984 | Mac bitmap fonts | Susan Kare designs Chicago, Geneva, Monaco for the original Macintosh |
| 1985 | Apple LaserWriter | First PostScript printer; launches the desktop publishing revolution |
| 1989 | TrueType announced | Apple-Microsoft joint announcement at Seybold conference; breaks Adobe monopoly |
| 1990 | Type 1 spec published | Adobe opens specification under competitive pressure; enables third-party tools |
| 1991 | TrueType ships (Mac) | Mac System 7 includes TrueType; royalty-free scalable fonts for consumers |
| 1991 | TrueType GX | Apple's variable font precursor; never widely adopted |
| 1992 | Windows 3.1 | TrueType reaches the dominant PC platform; Arial, Times New Roman bundled free |
| 1996 | OpenType announced | Microsoft-Adobe joint format unifying TrueType and PostScript in one container |
| 1997 | EOT | Microsoft's proprietary web font format for Internet Explorer; domain-bound DRM |
| 1998 | CSS2 @font-face | First web standard for custom fonts; poorly supported for a decade |
| 2001 | SVG Fonts | Font outlines in SVG XML; huge files, limited browser adoption, now deprecated |
| 2007 | OpenType ISO standard | ISO/IEC 14496-22; formal international standardization of OpenType |
| 2008 | @font-face revival | Safari 3.1 re-enables web font embedding; sparks the web typography renaissance |
| 2009 | Typekit launches | First major web font service; licenses commercial typefaces for web delivery |
| 2010 | Google Fonts | Free open-source web font library; democratizes web typography worldwide |
| 2010 | WOFF proposed | Web Open Font Format with zlib compression; ~40% smaller than TTF/OTF |
| 2012 | WOFF 1.0 W3C Rec | First standardized web font format; achieves universal browser support |
| 2014 | WOFF2 released | Brotli compression + glyph transform; ~30% smaller than WOFF; Chrome 36 first |
| 2016 | Variable fonts (OT 1.8) | Single file with continuous design axes; joint effort by Apple, Google, Microsoft, Adobe |
| 2018 | WOFF2 W3C Rec | Full W3C standardization; WOFF2 becomes the definitive web font format |
| 2021 | COLRv1 (OT 1.9) | Advanced color font technology with gradients, compositing; replaces bitmap emoji |
Work with Any Font Format
Whether you need to convert a legacy Type 1 font or optimize a modern variable font for the web, our converter handles every format in this timeline.
Start Converting NowWritten & Verified by
Sarah Mitchell
Product Designer, Font Specialist
Font Format Timeline FAQs
Common questions about the history and evolution of font formats
