Verified local conversion

WOFF2 to EOT

Converting a .woff2 font to .eot 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

Convert supported files

Runs on your device

Drop WOFF2 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 WOFF2 web font to Embedded OpenType font

Converting a .woff2 font to .eot repackages the same glyphs and metrics for a different delivery target. 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.

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. For this route the practical draw is solved web typography for IE4 through IE8 years before any open alternative existed and domain-binding reassured foundries wary of font piracy — balanced against obsolete: its only consumer, Internet Explorer, has been retired since 2022, which is worth knowing before you commit a large batch.

Why convert WOFF2 to EOT?

The practical trigger for this conversion is usually a mismatch: with .woff2, operating systems will not install it, so designers juggle separate web and desktop copies of the same font. Switching to .eot buys you solved web typography for IE4 through IE8 years before any open alternative existed, which is why it is the better fit for maintaining intranet applications pinned to old Internet Explorer versions. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.

WOFF2 vs EOT at a glance

AspectWOFF2 web font (.woff2)Embedded OpenType font (.eot)
Format typeContainer — quality depends on the codecs and settings insideContainer — quality depends on the codecs and settings inside
How it stores databrotli compression over the whole font, preceded by a glyf and loca transformation that re-encodes outline data for better compressibilitya header wrapping a TrueType font, optionally compressed with the proprietary MicroType Express scheme
Strongest atserving fonts on production websites as the default @font-face sourcemaintaining intranet applications pinned to old Internet Explorer versions
Weak spotoperating systems will not install it, so designers juggle separate web and desktop copies of the same fontobsolete: its only consumer, Internet Explorer, has been retired since 2022
Metadataall metadata of the wrapped font survives untouched, and the container can additionally carry an optional extended-metadata XML block from the vendorthe 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
01

Add your WOFF2 file

Drop one or more .woff2 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.

02

Pick EOT as the output

Select .eot in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if EOT is selectable, the route is real and validated.

03

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.

04

Verify and download

Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid EOT file. Outputs keep the original filename with the .eot extension.

WOFF2 to EOT questions, answered

Will converting WOFF2 to EOT lose quality?

Since woff2 is container-oriented and eot is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .eot itself requires.

Is it private to convert WOFF2 files here?

Yes — the .woff2 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 EOT file work?

Internet Explorer 4 through 11 was the entire market for .eot; Edge, Chrome, Firefox, and Safari never supported it. With IE fully retired, the format is dead weight in font stacks, and its practical relevance is limited to unwrapping legacy files to recover the font inside.

Will the EOT file be bigger or smaller than my WOFF2?

It depends on the content: a header wrapping a TrueType font, optionally compressed with the proprietary MicroType Express scheme. Convert one representative file first and compare before batch-processing a large set.

What happens to the metadata in my WOFF2 file?

In .woff2, all metadata of the wrapped font survives untouched, and the container can additionally carry an optional extended-metadata XML block from the vendor. 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 EOT back to WOFF2?

Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .woff2 → .eot → .woff2 is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.