EOT Converter
FileFlip converts EOT files into 4 other formats entirely inside your browser, using the font engine compiled to WebAssembly. The EOT file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. There is no file-size limit and no account to create.
How do I convert an EOT file?#
- Drop your EOT file onto the converter at the top of this page, or click it to pick one from your computer.
- Choose the format you want out of it. FileFlip downloads the engine that conversion needs, once, and your browser caches it.
- Conversion starts the moment you pick the format, and the result is yours to download. The work happens in this tab, so nothing is uploaded and nothing is queued.
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 happens to a EOT file#
FileFlip converts EOT into 4 formats with the font engine, all of it inside the browser tab. Each conversion below names the engine it uses, what it downloads, and exactly what that conversion keeps or drops.
| Category | Fonts |
|---|---|
| File extension | .eot |
| FileFlip support | Read and written |
| Conversions available | 4 |
| Engines | the font engine |
| Downloaded to your browser | 0.7 MB on the first conversion, then cached |
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.
The EOT file format reference covers the specification, the programs that open one, and what each conversion keeps or drops.
EOT 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.
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.
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.