What is EOT? The Embedded OpenType Web Font Format Explained

How EOT Works

EOT stands for Embedded OpenType, and it is best understood not as a new outline technology but as a wrapper. An EOT file takes an ordinary OpenType or TrueType font and packages it inside a compact binary container designed for one job: delivering a font over the web so that a browser can render text in it without the font being installed on the machine. The glyph outlines inside are the same quadratic or cubic curves a desktop font would carry; what EOT adds is a header and, usually, compression around them.

The header is where most of EOT's distinctive behaviour lives. It records the font's family name, style flags, and a rootstring field that lists the web domains the font is licensed to appear on. A browser reading the file is expected to compare the page's address against that list and refuse to use the font if it does not match. This was Microsoft's attempt at a lightweight digital rights mechanism, meant to reassure type foundries that letting a font travel to a browser did not mean giving it away for desktop use.

To keep transfers small, EOT files are normally compressed with Microsoft's MicroType Express (also called MTX), a font-aware compression scheme, and they can be subset so that only the glyphs a page actually needs are shipped. Subsetting matters most for large character sets: a page using only Latin text need not download thousands of unused CJK glyphs. The combination of subsetting and compression is what made EOT practical on the slow connections of the era it was built for.

Because the decoding logic, the DRM check, and the MTX decompressor all had to be present in the browser, EOT support was in practice tied to Internet Explorer. No other browser implemented the format, so a page relying on EOT would show its custom typeface in IE and fall back to a system font everywhere else. That single-vendor dependence is central to understanding both its brief usefulness and its obsolescence.

History and Standardization

EOT was created by Microsoft and introduced with Internet Explorer 4 in the late 1990s, long before other browsers had any way to load a custom font. For years it was effectively the only route to real web typography, which gave designers who targeted IE a capability their competitors could not match, at the cost of only working in one browser.

Microsoft submitted EOT to the W3C as a proposed standard, and it was published as a W3C member submission describing the format and its compression. It was never adopted as a broad web standard, however, because the wider browser community objected to building a proprietary, DRM-oriented format into the open platform. The other vendors preferred to serve raw .ttf and .otf files and, soon after, a purpose-built open wrapper.

That open wrapper became WOFF, which took EOT's good idea (compressing and packaging a font for web delivery) and dropped the parts the community rejected (the IE-only decoder and the domain-locking DRM). Once WOFF gained support across every major browser and Internet Explorer itself was retired, EOT lost its last reason to exist. It is now firmly a legacy format, encountered mainly in old @font-face stacks kept for compatibility with browsers that no longer ship.

EOT Compared to WOFF and Raw Fonts

Against WOFF and WOFF2, EOT loses on every axis that matters today. WOFF is an open standard supported by all browsers, compresses at least as well, and carries no domain-locking machinery; WOFF2 compresses considerably better still. EOT's only historical advantage was existing years earlier, which is no advantage once the browsers that needed it are gone. There is no modern reason to author new EOT files.

Against serving a raw TrueType or OpenType file, EOT once offered smaller transfers through MTX compression and subsetting, plus its licensing check. But raw fonts have the decisive benefit of working in every browser, and modern tooling can subset a .ttf or .otf just as easily before wrapping it as WOFF2. The compression gap that once justified EOT has been closed and then some by newer formats.

The one place EOT still appears is in bulletproof @font-face rules written years ago, which listed an .eot source first specifically to feed old Internet Explorer while other formats served everyone else. Maintaining a modern site, you can almost always delete the EOT source entirely: keeping it adds bytes and complexity to support browsers that are no longer in use. Converting or re-wrapping an existing EOT to WOFF2 is the sensible migration path.