Wrap a font locally as EOT for very old Internet Explorer versions (up to IE8) - no upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
EOT (Embedded OpenType) was the @font-face format Internet Explorer required up to version 8, before WOFF became the web standard. Practically nobody needs EOT for real live traffic today - the last IE user is a rare exception - but anyone assembling a complete @font-face fallback chain for a very old corporate intranet, a compatibility-mode test, or a historical project still needs the file.
This tool wraps your font's sfnt bytes unchanged inside an EOT header per the [MS-EOT] specification - family name, style name, version and full name come straight from the font's own name table, PANOSE classification, weight and italic flag from its OS/2 table. No compression and no outline conversion happens: the same glyphs, the same outlines, just a different envelope.
Unlike TTF/OTF/WOFF, the input here is deliberately broad: EOT does not distinguish between TrueType and PostScript outlines, so this tool accepts TTF, OTF, WOFF or WOFF2 and unpacks it back to the plain font locally first, before wrapping it.
| Input formats | TTF, OTF, WOFF, WOFF2 |
|---|---|
| Output format | EOT |
| Batch processing | Yes |
| Processing | Locally in your browser (WebAssembly) |
| File upload | None |
Limitations: EOT is a pure legacy format for Internet Explorer up to version 8; no other current browser reads it. The family/style name in the EOT envelope is taken as-is from the source's name table - if a font is missing OS/2, name or head entirely (practically never the case for a regular font), the tool honestly rejects it. Only convert fonts you own or have a licence for.
No, everything runs locally in the browser - even in airplane mode.
Almost nobody - only very old Internet Explorer versions (up to IE8) still require it, for instance in corporate intranets or compatibility tests.
TTF, OTF, WOFF or WOFF2 - all are first unpacked back to the plain font locally.
Yes. EOT is a pure envelope with no compression; the font bytes stay unchanged.