Convert TTF to EOT.
EOT files for the old Internet Explorer — created locally.
Drop TTF 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.
EOT (Embedded OpenType) is the web font format Internet Explorer 6–8 understood — a small metadata header in front of the unchanged TTF. If a legacy intranet or an ancient CSS pipeline still demands it, this makes one without your font leaving the machine.
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.
The format that started the web-font war
Microsoft shipped Embedded OpenType with Internet Explorer 4 in 1997 — real web fonts, a decade before anyone else had them. The catch was control: EOTs made with Microsoft’s WEFT tool were bound to specific domains via a "rootstring" and optionally scrambled, a rights-management scheme foundries demanded before they would license fonts for the web at all. No other browser ever implemented it. The standoff lasted until 2009, when WOFF finally gave foundries a wrapper they could tolerate and browsers a format they would actually ship.
Serving EOT to the browsers that want it
IE6–8 parse the src of @font-face greedily and choke on multi-format lists, which is why the classic "bulletproof" syntax exists: declare src: url(font.eot) alone first, then a second src with url(font.eot?#iefix) format("embedded-opentype") ahead of the modern formats — the query-string trick stops old IE from reading past the first URL. Serve the file as application/vnd.ms-fontobject. This tool writes plain, unscrambled EOT: no rootstring, no MicroType compression, maximum compatibility.
For everything that is not old IE
A line of perspective: unless you maintain a legacy intranet, a kiosk fleet or archival reproductions of old sites, no visitor has needed an EOT since roughly 2013. The same TTF converted with TTF to WOFF2 covers every current browser at half the size — do that first, and let this page serve the museum piece.
Frequently asked questions
Do I actually need EOT?
Almost certainly not — EOT only ever mattered for Internet Explorer 6–8, which are long dead outside legacy intranets. For anything current, WOFF2 is the format to serve; this page exists for maintaining old systems.
Is the font changed in any way?
No — a plain EOT is your TTF stored verbatim behind a metadata header (name, weight, embedding flags) read from the font itself. Unwrapping it returns the identical TTF.
Am I allowed to convert this font?
Converting a font never changes its license. Many desktop licenses do not cover web embedding (and vice versa), so check yours before publishing a converted font. Fonts under the OFL or Apache licenses and fonts you made yourself are fine. Your file also never leaves your device — nothing is uploaded anywhere.
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.