EOT Font File Format: Microsoft's 2007 DRM-Locked Web Font

A Font Wrapper Built to Solve One Company's Licensing Worry

Embedded OpenType was created in 2007 by Microsoft's Internet Explorer team to solve a specific problem font foundries were raising at the time: letting a website embed a real, full font file for display meant anyone could theoretically extract that same file and reuse it as an installable font without ever buying a license for it. Microsoft's answer was a new wrapper format built around exactly that concern, packaging standard OpenType glyph data inside a structure that includes domain locking and a "trusted roots" validation mechanism, restricting the embedded font so it renders correctly on the website it was built for while resisting being lifted out and reinstalled elsewhere as a normal font.

That distinction matters because it's the opposite design philosophy from every other web font format in common use — WOFF, WOFF2, and even the older raw TTF/OTF embedding some early sites used, all treat the embedded font as ordinary font data with no built-in copy restriction. EOT is the one format on this list where digital rights management wasn't an optional add-on; it was the entire reason the format exists in the first place.

Structurally, an EOT file is defined as a single EMBEDDEDFONT structure, and the format went through three distinct defined versions over its lifetime as Microsoft refined the validation and compression details. Underneath that wrapper sits standard TrueType-based OpenType glyph data, meaning the actual letter shapes a designer created are untouched by the format change — EOT never altered how a letter's curves were drawn, only how the finished font file was packaged, locked, and delivered to a browser.

The Compression Scheme and Validation String Hiding Inside the File

An EOT file achieves its file-size reduction through two combined techniques: font subsetting, meaning only the specific characters a given web page actually uses get included rather than the typeface's complete character set, and MicroType Express (MTX), a compression algorithm developed by Agfa specifically for this purpose, built on a variation of LZ77 dictionary-based compression paired with adaptive Huffman entropy coding. This is a meaningfully different, and comparatively simpler, approach than WOFF2 introduced years later, which relies on the general-purpose Brotli algorithm rather than a font-specific compression scheme.

Every EOT file also carries something called a RootString, a unique identifying string the authoring tool sets according to the specific licensing terms under which the font is being embedded, functioning as part of the format's overall validation and security mechanism. Combined with the file's flags field, which includes a specific bit indicating whether the enclosed font data is compressed, this validation apparatus is what let Internet Explorer confirm a given EOT file was authorized for the domain requesting it, rather than simply trusting any font file a page happened to reference.

What Building in Copy Protection Actually Cost the Format

• Gain — genuine licensing assurance for font foundries: the domain-locking and RootString validation gave type foundries a real technical guarantee no other early web font approach offered.
• Lose — adoption by any other browser maker, ever: Firefox, Chrome, Safari, and Opera never implemented EOT support at any point in their history.
• Lose — a path onto Microsoft's own next browser: Edge, Internet Explorer's direct successor, was never given EOT support either, meaning Microsoft's own newer browser can't read a format Microsoft itself invented.
• Lose — W3C standardization: Microsoft submitted EOT to the W3C in 2007 and again as a standalone submission in March 2008, but the W3C ultimately standardized WOFF as its official web font recommendation instead.
• Gain — a working solution for its one intended browser: for the entire span of Internet Explorer 4 through 11, EOT reliably solved the exact embedding problem Microsoft built it for.
• Lose — any forward relevance once IE was retired: unlike WOFF2, which continues active development and use, EOT has no realistic path onto any currently maintained browser engine.

The Exact Dates Behind Why This Format Has No Living Browser Left

Microsoft officially retired the Internet Explorer 11 desktop application on June 15, 2022, ending support on Windows 10's Semi-Annual Channel and Windows 10 IoT builds, and followed that with a Microsoft Edge update on February 14, 2023, that permanently disabled the IE11 desktop app on the affected Windows 10 versions. Since EOT rendered correctly in Internet Explorer versions 4 through 11 and nowhere else, that retirement effectively ended any genuine reason for a public website to serve one.

The one documented exception is Microsoft Edge's built-in "IE mode," a compatibility feature Microsoft has committed to supporting through at least 2029 specifically for organizations still running internal legacy sites and applications never rebuilt for a modern rendering engine. A corporate intranet running in IE mode is, underneath the compatibility shell, still running Trident, the old IE rendering engine, which makes it the only realistic remaining context where an EOT file might still render correctly inside a browser Microsoft actively maintains.

Why the Tool Built to Create These Files Doesn't Exist Anymore Either

Microsoft's own Web Embedding Fonts Tool (WEFT), the utility web authors originally used to generate EOT font objects and link them to a page, saw its final release, version 3.2, on February 25, 2003 — meaning the tool stopped receiving updates nearly two decades before Internet Explorer itself was finally retired. As of 2019, Microsoft no longer offered WEFT for download at all, leaving anyone who genuinely needs to generate a new EOT file today dependent on open-source alternatives like ttf2eot rather than Microsoft's own original software.

This tooling gap is the practical, checkable reason someone hunting for an "official" way to build an EOT file in 2026 comes up empty-handed: the software's own creator abandoned it years before the format's one supported browser was even discontinued, and the format's narrow remaining use case, internal IE-mode legacy systems, is niche enough that no major replacement tool has emerged to fill that specific gap either.

Anyone maintaining one of those legacy IE-mode systems today is, in effect, relying on a font-packaging pipeline nobody has actively maintained in over twenty years, which is worth factoring into any decision about how much longer to keep such a system running rather than migrating it to a modern rendering engine that never needed EOT to begin with.

A DRM-Locked 2007 Wrapper Set Beside the Formats That Replaced It

Direct Answers About Microsoft's Retired Web Font Format

Why did Microsoft build its own font format instead of using one everyone else could adopt?
Font foundries were concerned that embedding real font files on the web would let anyone extract and reuse them without a license, and EOT's domain-locking and RootString validation were built specifically to address that concern.

Can I still download Microsoft's official tool for making EOT files?
No. WEFT's last release was version 3.2 on February 25, 2003, and Microsoft stopped offering it for download entirely by 2019. Open-source tools like ttf2eot are the current alternative.

Does any browser released after Internet Explorer read EOT files?
No. Microsoft never added EOT support to Edge, its own IE successor, and no other browser maker, including Firefox, Chrome, Safari, or Opera, ever implemented it.

Is there any legitimate reason to still generate an EOT file today?
Only for an internal corporate site or application running inside Microsoft Edge's "IE mode," a compatibility feature Microsoft has said will continue through at least 2029 for exactly this kind of legacy system.

What made EOT's compression different from WOFF2's?
EOT relies on MicroType Express, a font-specific LZ77-and-Huffman-based scheme developed by Agfa, while WOFF2 uses the general-purpose Brotli algorithm, a later and generally more effective approach for this purpose.

Does converting an EOT file change how the letters look?
No. The underlying glyph shapes are standard TrueType-based OpenType outlines regardless of the EOT wrapper around them, so converting to another format changes the packaging, not the letterforms themselves.

What exactly does the RootString inside an EOT file do?
It's a unique identifying string an authoring tool sets according to the font's licensing terms, forming part of the format's validation mechanism that let Internet Explorer confirm a font was authorized for the domain requesting it.