EOT to SVG Font Converter
FileFlip converts EOT to SVG Font entirely inside your browser, using the font engine compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert an EOT file to SVG Font?#
- Drop your EOT file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to SVG Font and the conversion starts on its own. FileFlip downloads nothing at all, because everything it needs is already built into your browser, then runs the font engine on your own machine.
- Save the SVG Font file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting EOT to SVG Font lose quality?#
No. The glyph outlines are converted between outline models rather than redrawn, so the letterforms in the SVG Font file are the ones in the EOT file. What can change is the hinting and the OpenType tables around them.
Is it safe to convert EOT files online?#
Yes, because nothing is uploaded. FileFlip converts EOT files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What EOT to SVG Font actually does to the file#
Converting EOT to SVG Font runs on the font engine, downloads nothing at all, because everything it needs is already built into your browser, converts the glyph outlines between outline models, keeps hinting and kerning, and drops OpenType features.
| Engine | the font engine |
|---|---|
| Conversion path | One step: EOT → SVG Font |
| Downloaded to your browser | Nothing. Your browser already has everything this conversion needs |
| Quality | Outlines preserved |
| You get back | One file |
| Where it runs | On the page's own thread, so a very large file will make the tab wait |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Hinting | Kept | Carried through into the converted file. |
| Kerning | Kept | Carried through into the converted file. |
| OpenType features | Dropped | The target format has nowhere to put it. |
Worth knowing before you start:
- this conversion runs on the page's own thread, so a large file will freeze the tab while it works
What is an EOT file?#
An EOT file wraps a subsetted, compressed OpenType or TrueType font in a proprietary container that only Internet Explorer's @font-face implementation ever read.
There's no current reason to choose EOT; it only ever mattered for Internet Explorer 6 through 8, both long unsupported.
Convert away from EOT to WOFF2 and TTF for any website still shipping it, since no browser in current use reads EOT at all.
What is an SVG Font file?#
An SVG font file defines each glyph as an SVG path inside a font element, an XML-based approach the SVG 1.1 specification allowed and that SVG 2 has since removed.
There's little current reason to choose SVG fonts for web text; icon font systems built years ago are the main place they still appear.
Convert an SVG font to WOFF2 for anything meant to render as text in a current browser, since SVG font support is largely gone.
EOT to SVG Font questions people ask#
Do any current browsers support EOT fonts?
No. EOT only ever worked in Internet Explorer, and Microsoft Edge, IE's replacement, never implemented support for it. Every browser in current use needs WOFF, WOFF2, TTF or OTF instead.
What was EOT's domain-locking feature for?
EOT could embed a root string listing the domains a font was licensed to appear on, and Internet Explorer would refuse to render the font on any other domain. Font foundries liked that it discouraged casual copying, but no other browser vendor implemented the check, which was part of why EOT never became a cross-browser standard.
Why would I still need to convert a file to EOT today?
Only if a website deliberately still supports Internet Explorer 6 through 8, which is rare given that Microsoft ended support for those browsers years ago. Any current @font-face declaration can drop the EOT source entirely and rely on WOFF2 with a WOFF fallback.
Do browsers still support SVG fonts?
Barely. Chrome removed support in version 38 back in 2014 and Opera followed soon after, while Firefox and Edge never implemented SVG fonts at all. Safari is the one major browser that still renders them, which makes SVG fonts unreliable for any site that needs to work everywhere.