EOT

EOT — Embedded OpenType

EOT (Embedded OpenType) is the legacy web font format created by Microsoft for Internet Explorer. It is a TrueType or OpenType font wrapped in a Microsoft-specific container with a lightweight digital-rights wrapper that satisfied font foundries before web licensing was common. EOT only ever shipped in one browser engine — Internet Explorer 4 through 11 — so its relevance ended when IE retired in 2022. Today EOT exists mainly to keep legacy enterprise intranets running.

History

Microsoft introduced EOT with Internet Explorer 4 in 1997, almost a decade before the open web caught up. The W3C submitted EOT for standardisation in 2008, but Mozilla, Apple, and Opera refused to implement it, preferring the open WOFF specification that arrived in 2010. EOT remained an IE-only quirk for its entire life. When Microsoft shipped Edge in 2015 and discontinued IE11 in 2022, EOT effectively retired. The format is still important for two reasons: large enterprise environments often run pinned IE-mode browsers inside Edge for legacy intranet apps, and a handful of PDF and ePub readers use EOT-style embedded fonts internally. The format also leaks into a few unexpected places — some Windows administration tools, internal Microsoft Office font installers, and a handful of font-management utilities still emit EOT files when exporting cross-format bundles. That long tail of producers keeps the format alive in archival workflows long after the last EOT-consuming browser shipped.

When to use EOT

Convert EOT to other formats

Convert other formats to EOT

Frequently asked questions

Is EOT still needed in 2026?

Almost never on the public web. The last browser to support EOT was Internet Explorer 11, which Microsoft retired in 2022. EOT is only relevant for internal corporate environments that still run IE-mode inside Edge for legacy applications.

Can I convert EOT to WOFF2?

Yes. Our converter unwraps the EOT container, extracts the underlying TrueType data, and re-wraps it in a Brotli-compressed WOFF2 envelope. Glyph outlines and hinting transfer cleanly.

Why did EOT lose to WOFF?

EOT was a Microsoft-only specification that other browser vendors refused to implement. WOFF was designed as an open standard with multi-vendor agreement from day one, so foundries and browser vendors backed WOFF and let EOT die with IE. The lesson — that proprietary web formats lose to open ones — became a defining pattern of the standards era.