EOT to WOFF2 Converter
FileFlip converts EOT to WOFF2 entirely inside your browser, using the font engine compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert an EOT file to WOFF2?#
- Drop your EOT file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to WOFF2 and the conversion starts on its own. FileFlip downloads 0.7 MB of WebAssembly the first time and nothing after that, then runs the font engine on your own machine.
- Save the WOFF2 file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting EOT to WOFF2 lose quality?#
No. The EOT to WOFF2 conversion copies the already-encoded streams into the new container without decoding them, so what comes out is bit-for-bit what went in. Only the wrapper changes, which is why it is also fast.
Is it safe to convert EOT files online?#
Yes, because nothing is uploaded. FileFlip converts EOT files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What EOT to WOFF2 actually does to the file#
Converting EOT to WOFF2 runs on the font engine, downloads 0.7 MB of WebAssembly the first time and nothing after that, copies the encoded streams into the new container without re-encoding them, keeps hinting and kerning, and drops OpenType features.
| Engine | the font engine |
|---|---|
| Conversion path | One step: EOT → WOFF2 |
| Downloaded to your browser | 0.7 MB, once, then cached by your browser |
| Quality | Lossless, repackaged rather than re-encoded |
| You get back | One file |
| Where it runs | On the page's own thread, so a very large file will make the tab wait |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Hinting | Kept | Carried through into the converted file. |
| Kerning | Kept | Carried through into the converted file. |
| OpenType features | Dropped | The target format has nowhere to put it. |
Worth knowing before you start:
- this conversion runs on the page's own thread, so a large file will freeze the tab while it works
What is an EOT file?#
An EOT file wraps a subsetted, compressed OpenType or TrueType font in a proprietary container that only Internet Explorer's @font-face implementation ever read.
There's no current reason to choose EOT; it only ever mattered for Internet Explorer 6 through 8, both long unsupported.
Convert away from EOT to WOFF2 and TTF for any website still shipping it, since no browser in current use reads EOT at all.
What is a WOFF2 file?#
A WOFF2 file wraps a TrueType or OpenType font in a Brotli-compressed container built for @font-face delivery on the web, replacing WOFF's older zlib compression.
Serve WOFF2 as the primary font format for any website, since it's the smallest option every current browser supports.
Convert away from WOFF2 only when a font needs to be installed on a desktop or opened by a font editor, since WOFF2 exists purely for web delivery.
EOT to WOFF2 questions people ask#
Do any current browsers support EOT fonts?
No. EOT only ever worked in Internet Explorer, and Microsoft Edge, IE's replacement, never implemented support for it. Every browser in current use needs WOFF, WOFF2, TTF or OTF instead.
Why would I still need to convert a file to EOT today?
Only if a website deliberately still supports Internet Explorer 6 through 8, which is rare given that Microsoft ended support for those browsers years ago. Any current @font-face declaration can drop the EOT source entirely and rely on WOFF2 with a WOFF fallback.
What was EOT's domain-locking feature for?
EOT could embed a root string listing the domains a font was licensed to appear on, and Internet Explorer would refuse to render the font on any other domain. Font foundries liked that it discouraged casual copying, but no other browser vendor implemented the check, which was part of why EOT never became a cross-browser standard.
How much smaller is WOFF2 than WOFF?
WOFF2 typically comes in around 30 percent smaller than the same font packaged as WOFF, because it replaces WOFF's zlib compression with Brotli and adds a font-specific preprocessing step before compressing. The exact saving varies by font, but it's consistent enough that WOFF2 is the default choice for new @font-face declarations.