Convert EOT to TTF.
Rescue fonts from legacy EOT files — decoded in-browser.
Drop EOT fonts here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
Old sites and intranets left a trail of EOT files with no desktop counterpart. Most EOTs store the original TTF verbatim behind a header — this unwraps it (XOR-obfuscated ones included) into a font you can install or convert onward.
How it works
- Drop TTF, OTF, WOFF, WOFF2 or EOT files anywhere on the page — or click to browse.
- Pick the output format — the font tables are repackaged losslessly, never re-drawn.
- Convert, then download each font on its own or the whole batch as a ZIP.
Why EOT files still turn up in 2026
Every @font-face kit generated between roughly 2009 and 2015 shipped an .eot next to its .woff and .ttf — so they sit by the thousands in old theme folders, SharePoint sites, agency handover ZIPs and CMS upload directories. The unlucky discovery is the backup where the .eot is the only file that survived: the desktop original was never archived, and the WOFF beside it got lost in a migration. This tool exists for that moment.
Three kinds of EOT, two of them recoverable
Not every EOT is built the same, and the difference decides whether the font can be rescued.
| Variant | How it stores the font | Decodes here? |
|---|---|---|
| Plain | Original TTF verbatim after the header | Yes — byte-exact |
| XOR-obfuscated | First bytes scrambled, rest verbatim | Yes — byte-exact |
| MicroType Express | Proprietary MTX compression (WEFT era) | No — rejected with a clear note |
After the rescue
The unwrapped TTF installs like any desktop font and opens in any editor — and if the point of the exercise is to put the typeface back on the web properly, TTF to WOFF2 turns it into the format every current browser expects. Fonts trapped in the other legacy wrapper of that era travel the same road: WOFF to TTF handles those.
Frequently asked questions
Does every EOT work?
Most do — plain and XOR-obfuscated EOTs decode to the exact original font. The exception is EOTs made with MicroType Express compression (some WEFT-era files): browsers cannot decode MTX, so those are rejected with a clear message. If you have the original TTF, convert from that instead.
Can I install the result?
Yes — the unwrapped file is a regular desktop font. Note that EOTs were often produced under embedding-only licenses, so check whether desktop installation is actually permitted for your font.
Am I allowed to convert this font?
The wrapper changes, the license does not — and direction matters here: a font licensed for web embedding is not automatically licensed for desktop installation or further distribution. Unwrapping a font you own, or one under the OFL or Apache licenses, is fine; for anything else read the terms before installing. Nothing is uploaded either way — the file stays on your device.
Is it private?
Yes. The font is repackaged entirely in your browser — it is never uploaded, and the server does nothing but deliver this page. For licensed fonts that matters twice over: nothing is redistributed to any third party, and no copy lingers on a server afterwards. Want proof? Run one file through, switch your connection off, and run another — it still works.