Convert WOFF2 to EOT Online

How to Convert WOFF2 to EOT Online

1. Upload Your WOFF2 File: Drag and drop your .woff2 file or click "Add Files" to select one from your device. Batch upload is supported — convert a whole family (regular, bold, italic, bold-italic) in one pass. Files are parsed by opentype.js inside your browser; nothing is sent to a server.
2. Confirm Output Format: The output is locked to EOT (Embedded OpenType). The converter decompresses WOFF2's Brotli-packed sfnt payload back to raw TrueType/OpenType tables, then re-wraps that sfnt in the IE-specific EOT header with size, version, and embedding-permission fields.
3. Review Font Metadata (Optional): Before you click convert, check that the family name and weight class look right in your file manager — those values get copied verbatim into the EOT header and into the CSS @font-face font-family you'll declare later. Rename the source file if you want a different font-family string.
4. Convert and Download: Click "Convert". You get a .eot for each input, ready to drop into @font-face { src: url('font.eot') format('embedded-opentype'); }. No sign-up, no watermark, no server upload.

Why Convert WOFF2 to EOT?

WOFF2 is the modern web-font workhorse — Brotli-compressed, typically 20–30% smaller than WOFF 1.0 (median ~24% for TTF-flavored fonts), and supported by every current browser. EOT is the opposite: a Microsoft format from 1997, submitted to W3C in 2008, rejected in favor of WOFF, and only ever recognized by Internet Explorer 6 through 11. IE11 retired on June 15, 2022, which means the audience that actually needs EOT today is narrow but real. Common reasons to go the "wrong direction" from WOFF2 back to EOT:

• Legacy intranet apps stuck on IE mode — Many enterprises still run line-of-business apps inside Microsoft Edge's IE mode, which is contractually supported through at least 2029. Edge's IE mode renders pages using the MSHTML engine and prefers EOT in @font-face for compatibility with the original IE rendering path.
• Government and regulated portals — Procurement specs in healthcare, finance, and public-sector deployments sometimes still list IE 11 as a supported browser, and validation suites flag missing format('embedded-opentype') fallbacks. Shipping an EOT alongside WOFF2 keeps the audit green.
• Bulletproof @font-face stacks — The historical "bulletproof" fallback chain (eot → eot?#iefix for IE 8, then woff2, woff, ttf, svg) still appears in design-system style guides and Sass mixins. If you only have a WOFF2 master, you need to back-fill the EOT slot.
• Kiosk and POS terminals — Self-checkout, ticketing, and digital-signage systems imaged years ago on Windows Embedded / Windows 10 LTSC still ship IE 11 as the default browser (IE 11 desktop app support on LTSC is not affected by the 2022 retirement). Custom-branded fonts on those screens need an EOT.
• Compliance with vendor brand kits — Some font foundries license a "full web bundle" that includes EOT, and downstream brand teams expect every format in the zip even when EOT files won't actually be served.
• Round-tripping a legacy font you've lost — If the only copy of a custom font you have is a WOFF2 served from a CDN, decompressing it back to sfnt and wrapping it as EOT can rebuild the file that an old IE-only app expects.

If your audience is purely modern browsers, don't ship EOT — a WOFF2 + WOFF fallback covers more than 99% of users today and keeps your CSS shorter.

WOFF2 vs EOT — Format Comparison

Where EOT Still Fits — @font-face Quick Reference

The eot?#iefix query-string suffix is the well-known workaround for IE 6–8's broken handling of the ? in src — without it, those browsers append the entire CSS stylesheet to the EOT request and the font fails to load.

Frequently Asked Questions

Why would I ever convert a modern WOFF2 back to EOT?

Three real cases: you maintain an intranet app running in Edge's IE mode and your audit requires an EOT fallback; you only have the WOFF2 distribution of a custom font and need to rebuild an EOT for a legacy kiosk image; or a brand-asset bundle spec lists .eot as a deliverable and you don't want to ship an incomplete kit. For brand-new public websites in 2026, you almost certainly don't need EOT.

Does EOT preserve all the glyphs and OpenType features in my WOFF2?

It preserves whatever was inside the WOFF2's sfnt payload — outlines, kerning, GSUB/GPOS feature tables, and naming records all survive the round-trip. WOFF2 stores the same TrueType/OpenType tables as the source, just Brotli-compressed and reordered for streaming; converting to EOT decompresses those tables and re-wraps them in the EOT header. Color fonts (COLR/CPAL, sbix, SVG ) technically survive but won't render in IE 6–11 anyway.

Will the EOT work in Internet Explorer 8 specifically?

Modern converters output "EOT Lite" — the same sfnt payload, no MTX compression, no URL binding — which IE 8 reads correctly when you include the ?#iefix query suffix in your CSS src. IE 8's well-known bug appends the rest of the CSS file to the EOT URL if there's no ? to stop it; the #iefix fragment is the historical workaround.

Is EOT smaller than the original WOFF2?

No, almost always larger. WOFF2's Brotli compression typically shrinks the sfnt payload by 50% or more compared to raw TTF/OTF. EOT only adds a thin header on top of the uncompressed sfnt (the MTX-compressed variant is mostly unused outside Microsoft's own tooling). Expect your .eot output to be roughly 2x the size of the WOFF2 you converted from.

Do I need to license the font again for EOT?

You need whatever your foundry's license specifies for web embedding — the format doesn't change the licensing terms, only the byte layout. Many foundries grant a single "web font" right that covers WOFF, WOFF2, and EOT together; some require a separate "embedded for IE/legacy" rider. Check your EULA before shipping an EOT on a public domain.

Does the conversion work fully offline / locally?

Yes. The page lazy-loads opentype.js and a small EOT writer into your browser, parses the WOFF2 in JavaScript using a Brotli decoder, and emits the EOT bytes directly. There's no upload step and no server-side processing — useful if your source font is unreleased, NDA-restricted, or a paid commercial license you can't legally upload to third-party servers.

What's the difference between EOT and "EOT Lite"?

Original EOT (2008 W3C submission) included two features that made it controversial: optional MTX compression (a Monotype-patented algorithm) and URL binding (the font would only decode on a specific domain). EOT Lite drops both — it's a plain sfnt wrapped in an EOT header with no compression and no URL lock. Every realistic modern converter, including this one, produces EOT Lite, which is what IE 6–11 reads without complaint.

Will I need to ship a separate EOT file per font weight?

Yes. Like WOFF, WOFF2, and TTF, each weight and style is its own file — regular, bold, italic, and bold-italic are four distinct EOTs. Batch-upload the four WOFF2s and you'll get four EOTs back, then point each at the right @font-face block with matching font-weight and font-style declarations.

Should I prefer EOT or WOFF for IE support?

WOFF, every time. IE 9, 10, and 11 all natively load WOFF 1.0 via format('woff'), no EOT required. EOT is only needed if you must also support IE 6, 7, or 8 — and IE 8's global share dropped below 0.1% years before IE 11 itself retired. If your "legacy" target is just IE 11, ship a WOFF and skip the EOT step entirely.