Add your WOFF file
Drop one or more .woff 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.
WOFF to EOT
Converting a .woff 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
Runs on your deviceConvert supported files
Drop WOFF 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 WOFF web font to Embedded OpenType font
Converting a .woff font to .eot repackages the same glyphs and metrics for a different delivery target. WOFF, extension .woff, wraps an OpenType or TrueType font in zlib compression plus a small header and an optional metadata block, creating a format websites could legally and efficiently serve. It was the format that ended the web's font drought and made @font-face mainstream.
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 WOFF to EOT?
The practical trigger for this conversion is usually a mismatch: with .woff, superseded by WOFF2's stronger compression. 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.
WOFF vs EOT at a glance
| Aspect | WOFF web font (.woff) | Embedded OpenType font (.eot) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | each sfnt table is individually zlib-compressed, so the structure mirrors the original font table for table | a header wrapping a TrueType font, optionally compressed with the proprietary MicroType Express scheme |
| Strongest at | web-font serving for audiences on older browsers such as IE9 and early Android | maintaining intranet applications pinned to old Internet Explorer versions |
| Weak spot | superseded by WOFF2's stronger compression | obsolete: its only consumer, Internet Explorer, has been retired since 2022 |
| Metadata | beyond the wrapped font's own name table, the extended metadata block stores vendor, credits, description, and license information as XML | 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 |
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.
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 EOT file. Outputs keep the original filename with the .eot extension.
WOFF to EOT questions, answered
Will converting WOFF to EOT lose quality?
Since woff 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 WOFF files here?
Yes — the .woff 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 WOFF?
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 WOFF file?
In .woff, beyond the wrapped font's own name table, the extended metadata block stores vendor, credits, description, and license information as XML. 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 WOFF?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .woff → .eot → .woff is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.