EOT Converter

How to Convert an EOT Font

1. Choose Your EOT File: Click "Choose a EOT font file to convert" (or drag one in). The converter accepts a single .eot file — the legacy Embedded OpenType web font you pulled out of an old site's /fonts folder or a stylesheet's @font-face rule.
2. Pick the Output Format: Use the "To format" dropdown to pick TTF, OTF, WOFF, or WOFF2. WOFF2 is selected by default — it's the right target for any modern website. Choose TTF or OTF if you want to install the font on your desktop.
3. Convert in Your Browser: Click "Convert". A lazy-loaded build of opentype.js parses the EOT glyph data and re-writes it into the format you chose. Nothing is uploaded — the conversion runs entirely in your browser tab.
4. Download the Result: When the output appears, click the "Download" button to save the new font. No sign-up, no watermark, and the file never leaves your device.

Popular EOT Conversions

• EOT to WOFF2 — the modern web standard; smallest files, the only format you need for current browsers
• EOT to WOFF — the broad-compatibility web fallback for older Chrome, Firefox, and Safari builds
• EOT to TTF — a desktop-installable TrueType outline you can open in any OS or design app
• EOT to OTF — an OpenType desktop font, useful when the glyphs carry OpenType layout features

Why Convert an EOT File?

EOT (Embedded OpenType) is a web-font format Microsoft created for Internet Explorer — it first shipped with IE4 in 1997 as a "compact form of the OpenType font format" with light compression and subsetting so a page could embed a typeface. Microsoft submitted it to the W3C as a Member Submission in March 2008, but the W3C declined to standardize it (partly over its DRM-style obfuscation) and instead backed WOFF, which Mozilla, Opera, and Microsoft jointly submitted in 2010.

That history is why almost everyone who lands here is converting away from EOT. The format is effectively dead on the open web:

• No modern browser reads it. Per caniuse, EOT is supported only by Internet Explorer 6 through 11 — global support sits at roughly 0.26%. Chrome, Firefox, Safari, Edge, and every mobile browser ignore it.
• Its only browser retired in 2022. Microsoft retired the Internet Explorer 11 desktop app on June 15, 2022. With IE gone, there is no shipping browser that needs an EOT file.
• You inherited a legacy asset. Most conversions start with an old @font-face stack that listed an .eot first for IE. To reuse that typeface today you re-derive a usable outline: WOFF2/WOFF for the web, or TTF/OTF to install on a machine and edit.

EOT itself is a wrapper around TrueType/OpenType outline data, so converting it out is lossless for the glyph shapes — you're unpacking the embedded font back into a standard container, not re-rendering it.

EOT vs. Its Common Targets

Frequently Asked Questions

Is the EOT format still needed in 2026?

For the live web, no. EOT existed solely to embed fonts in Internet Explorer, and Microsoft retired the IE11 desktop app on June 15, 2022. Every current browser uses WOFF2 (with WOFF as a fallback) instead. The only situation where an EOT might still matter is a frozen legacy intranet that's pinned to old IE — and even there, that environment is winding down. If you're building or refreshing a site today, convert your EOT to WOFF2 and drop the EOT entirely.

What should I convert my EOT file to?

It depends on where the font is going. For a website, choose WOFF2 — it has the smallest files and is supported by every modern browser; add a WOFF copy if you still need to serve older browser versions. For installing the font on your computer or editing it in a design or font app, choose TTF or OTF, which are the standard desktop outline formats.

Will converting EOT to WOFF2 lose any quality?

No. EOT is a wrapper around the same TrueType/OpenType outline data used by every other format here, so converting it out re-packages the existing glyph outlines rather than re-rendering them. Vector font outlines are resolution-independent, so they scale cleanly at any size after conversion. The only thing that can be lost is metadata or hinting in unusual files, not the letterforms themselves.

Can I install an EOT font on my computer?

Not directly — Windows, macOS, and Linux font managers don't install .eot files, because EOT was built for web embedding, not desktop use. Convert the EOT to TTF or OTF first, and then the resulting file installs and opens like any normal desktop font.

Does my EOT file get uploaded to a server?

No. This converter runs entirely in your browser using opentype.js — your font file is read and rewritten locally on your own device and is never uploaded to xconvert or anywhere else. In our testing, a typical webfont EOT (tens to a few hundred kilobytes) converts to WOFF2 in well under a second with no network request, which you can confirm in your browser's network tab.

Is EOT a subset or the full font?

It can be either. EOT files were often subsetted at build time to embed only the glyphs a page actually used, which kept the download small. If your source EOT was subsetted, the converted TTF, OTF, or WOFF2 will contain only those same glyphs — not the original full character set. To get a complete font back, you need the original unsubsetted TTF/OTF source rather than the embedded EOT.