Add your EOT file
Drop one or more .eot files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
EOT to WOFF2
Converting a .eot font to .woff2 repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop EOT files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting Embedded OpenType font to WOFF2 web font
Converting a .eot font to .woff2 repackages the same glyphs and metrics for a different delivery target. Embedded OpenType, extension .eot, was Microsoft's proprietary web-font format for Internet Explorer: a TrueType or OpenType font compressed and optionally bound to specific domains so it could not be reused elsewhere. For a decade it was the only way to serve custom fonts to the web's then-dominant browser.
WOFF2 (.woff2) is the current web-font format: a font's sfnt tables preprocessed and squeezed with Brotli compression so pages download less type data. It is purely a transport wrapper — decompressing a .woff2 reconstructs a working TrueType or OpenType font. For this route the practical draw is the smallest deliverable font format, cutting load time and bandwidth and lossless — full fidelity of the wrapped font is preserved — balanced against operating systems will not install it, so designers juggle separate web and desktop copies of the same font, which is worth knowing before you commit a large batch.
Why convert EOT to WOFF2?
The practical trigger for this conversion is usually a mismatch: with .eot, obsolete: its only consumer, Internet Explorer, has been retired since 2022. Switching to .woff2 buys you the smallest deliverable font format, cutting load time and bandwidth, which is why it is the better fit for serving fonts on production websites as the default @font-face source. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
EOT vs WOFF2 at a glance
| Aspect | Embedded OpenType font (.eot) | WOFF2 web font (.woff2) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | a header wrapping a TrueType font, optionally compressed with the proprietary MicroType Express scheme | brotli compression over the whole font, preceded by a glyf and loca transformation that re-encodes outline data for better compressibility |
| Strongest at | maintaining intranet applications pinned to old Internet Explorer versions | serving fonts on production websites as the default @font-face source |
| Weak spot | obsolete: its only consumer, Internet Explorer, has been retired since 2022 | operating systems will not install it, so designers juggle separate web and desktop copies of the same font |
| Metadata | the wrapper preserves the embedded font's name table and adds header fields for the family name and the domain root strings that governed where the font could be used | all metadata of the wrapped font survives untouched, and the container can additionally carry an optional extended-metadata XML block from the vendor |
Pick WOFF2 as the output
Select .woff2 in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if WOFF2 is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid WOFF2 file. Outputs keep the original filename with the .woff2 extension.
EOT to WOFF2 questions, answered
Will converting EOT to WOFF2 lose quality?
Since eot is container-oriented and woff2 is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .woff2 itself requires.
Is it private to convert EOT files here?
Yes — the .eot file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the WOFF2 file work?
Chrome, Firefox, Safari, and Edge have all supported .woff2 for years — coverage is effectively universal outside long-dead browsers like Internet Explorer, which never adopted it. Because no operating system accepts it for installation, workflows convert to TTF or OTF whenever a font must leave the browser.
Will the WOFF2 file be bigger or smaller than my EOT?
It depends on the content: brotli compression over the whole font, preceded by a glyf and loca transformation that re-encodes outline data for better compressibility. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my EOT file?
In .eot, the wrapper preserves the embedded font's name table and adds header fields for the family name and the domain root strings that governed where the font could be used. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Can I convert WOFF2 back to EOT?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .eot → .woff2 → .eot is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.