WOFF to EOT Converter
Convert Web Open Font Format to Embedded OpenType. 50 MB file size, unlimited uploads. Fast, secure, and completely private conversion.
Upload Fonts
Drag and drop your font files here or click to browse
Only WOFF files are accepted
Max file size 50 MB.
Disclaimer: This tool is provided as-is for convenience and does not constitute legal advice. Font licenses vary; you are responsible for ensuring you have the rights to upload and convert files and that your intended use is permitted. Converting a font does not grant new rights. Results may be imperfect, and use is at your own risk.
Developer & Verifier
Developed by
Marcus Rodriguez
Lead Developer
Verified by
Sarah Mitchell
Product Designer, Font Specialist
About This Conversion
Everything you need to know about converting between these formats
Web Open Font Format
Web Open Font Format (WOFF) is specifically optimized for web use with built-in compression. It's supported by all modern browsers and is ideal for websites. WOFF files are typically 40% smaller than their TTF/OTF equivalents.
Embedded OpenType
Embedded OpenType (EOT) is a Microsoft format primarily used for older Internet Explorer browsers (IE6-IE8). It includes DRM features but is largely obsolete with modern browsers supporting WOFF/WOFF2.
Why Convert WOFF to EOT?
Supporting Internet Explorer 6-8 browsers
Maintaining compatibility with legacy corporate systems
Working on projects requiring old browser support
Converting historical web font implementations
How to Convert WOFF to EOT
Simple 3-step process that takes less than a minute
Upload Your Font
Select your WOFF font file from your computer or drag and drop it into the converter above.
Convert Instantly
Click the convert button and our tool will process your font file in server RAM only. Files are processed and immediately deleted - never written to disk.
Download Result
Your converted EOT file will be ready immediately. Download it and use it in your project.
WOFF vs EOT: Feature Comparison
Technical comparison between source and target formats
| Feature | WOFF | EOT | Winner |
|---|---|---|---|
| File Size | 75 KB | 82 KB (+9%) | WOFF |
| Browser Support | All modern (IE9+) | IE6-11 only | WOFF |
| Compression | Gzip (efficient) | LZ (poor) | WOFF |
| Modern Browsers | Full support | None | WOFF |
| User Coverage 2024 | 99%+ | <0.01% | WOFF |
| Obsolescence | Current standard | Completely obsolete | WOFF |
| Best For | All modern web | Nothing (obsolete) | WOFF |
Frequently Asked Questions
Common questions about converting WOFF to EOT
1Why would I convert WOFF to EOT?
You almost never should. EOT is only needed for IE6-8 (less than 0.1% of traffic). If you have WOFF files, you already support IE9+. EOT is a legacy fallback format that's obsolete in 2024. Keep WOFF and skip EOT unless analytics show IE8 traffic.
2Will converting WOFF to EOT increase file size?
Maybe. EOT uses different compression (LZ) than WOFF (gzip). Sometimes files are similar size, sometimes EOT is 10-20% larger. Regardless, both are much larger than WOFF2 (which is 25-30% smaller than WOFF).
3Does EOT work better than WOFF in Internet Explorer?
WOFF works in IE9+, which covers 99.9% of remaining IE users. EOT only adds support for IE6-8, which are extinct browsers. Unless your analytics show IE8 traffic, WOFF alone is sufficient for IE compatibility.
4Should I include both WOFF and EOT in @font-face?
Only if you must support IE8 (extremely rare). Modern best practice: WOFF2 (modern browsers) + WOFF (IE9-11). Skip EOT entirely unless you have confirmed IE6-8 users in your analytics. This is vanishingly rare in 2024.
5Can EOT support OpenType features better than WOFF?
No, the opposite. EOT has worse OpenType support than WOFF. Advanced features may not work in IE even with EOT. WOFF fully preserves features, while EOT has limited support, especially in older IE versions.
6Does converting WOFF to EOT lose quality?
No, the conversion is lossless for basic font data. However, EOT may not preserve all OpenType features properly. If you need EOT, convert from TTF instead of WOFF – the conversion path is better tested.
7What's the best @font-face stack with WOFF and EOT?
If you must support IE8: List EOT first (with ?#iefix), then WOFF2, then WOFF. But realistically, skip EOT. Use this instead: WOFF2 (modern browsers) + WOFF (IE9-11). This covers 99.9% of users.
8Is there any modern use case for WOFF to EOT conversion?
Almost none. The only valid scenario: maintaining a legacy corporate intranet locked to Windows XP/IE8 that cannot be upgraded due to ancient internal applications. For any public-facing or modern site, skip EOT completely.
File Size Comparison
See how file sizes change after conversion
| Original (WOFF) | Converted (EOT) | Change | Notes |
|---|---|---|---|
| 75 KB (WOFF) | 82 KB (EOT) | +9% larger | LZ compression less efficient than gzip |
| 140 KB (WOFF) | 158 KB (EOT) | +13% larger | EOT typically larger than WOFF |
| 45 KB (WOFF) | 48 KB (EOT) | +7% larger | Small increase across all sizes |
| 260 KB (WOFF) | 295 KB (EOT) | +13% larger | Consistent size increase |
Performance Metrics
Technical performance indicators for this conversion
- File Size Change:8-13% larger
EOT LZ compression less efficient than WOFF gzip
- Browser Support:IE6-8 only
WOFF works in IE9+; EOT only needed for IE6-8 (<0.01% users)
- Performance Trade-off:Negative
Larger files for virtually no users
- Recommendation:Skip EOT
Use WOFF2 + WOFF; skip EOT unless IE8 confirmed in analytics
- Maintenance Cost:High
Extra format complexity for essentially zero benefit
Implementation Examples
Production-ready code for your converted fonts
WOFF with EOT for IE8
Add EOT fallback to existing WOFF
@font-face {
font-family: 'Web Font';
src: url('fonts/WebFont.eot');
src: url('fonts/WebFont.eot?#iefix') format('embedded-opentype'),
url('fonts/WebFont.woff') format('woff');
font-weight: normal;
font-style: normal;
}Browser Compatibility
Which browsers support EOT fonts
| Browser | Support | Notes |
|---|---|---|
| Chrome | No support | Never supported EOT, use WOFF |
| Firefox | No support | Never supported EOT, use WOFF |
| Safari | No support | Never supported EOT, use WOFF |
| Edge (Chromium) | No support | Use WOFF instead |
| IE | 9+ (WOFF), 6-8 (EOT) | IE9+ supports WOFF; IE6-8 needs EOT |
| Opera | No support | Never supported EOT, use WOFF |
| iOS Safari | No support | Never supported EOT, use WOFF |
| Android Browser | No support | Never supported EOT, use WOFF |
| Chrome Mobile | No support | Never supported EOT, use WOFF |
| Samsung Internet | No support | Never supported EOT, use WOFF |
Troubleshooting Common Issues
Solutions to problems you might encounter
EOT file larger than WOFF
This is common. EOT uses less efficient compression (LZ vs gzip). EOT files are often 10-20% larger than WOFF. Since EOT only supports IE6-11 (obsolete browsers), this inefficiency is one more reason to avoid EOT.
Conversion fails with licensing error
EOT includes Microsoft's DRM/license system. Some converters can't create EOT from WOFF if license flags are incompatible. Check your font license – commercial fonts may prohibit EOT conversion without proper web license.
EOT doesn't work in IE9+
IE9+ supports WOFF natively – use WOFF, not EOT for IE9-11. EOT is only needed for IE6-8 (virtually extinct). If you have WOFF files, you already support IE9+. Skip EOT unless you have confirmed IE6-8 users.
Why would I do this conversion?
You almost never should. WOFF supports IE9+; EOT only adds IE6-8 (under 0.01% of traffic). Converting WOFF to EOT is counterproductive – worse compression for essentially zero users. Keep WOFF and skip EOT entirely.
OpenType features don't work in IE
IE has limited OpenType support. Advanced features fail even with proper EOT files. Basic kerning works; stylistic sets, contextual alternates often don't. This is an IE limitation. Modern browsers with WOFF have full feature support.
When NOT to Use EOT
Scenarios where you should keep WOFF or choose a different format
No IE6-8 traffic
Why not: EOT only for IE6-8 which is <0.01% of usersUse instead: WOFF works in IE9+; skip EOT unless analytics show IE8 usersModern website
Why not: EOT is larger and only works in obsolete browsersUse instead: Use WOFF2 + WOFF; skip EOT completelyPerformance priority
Why not: EOT is 8-13% larger than WOFF with worse compressionUse instead: Keep WOFF; it's smaller and works in modern browsersAny site in 2024
Why not: All IE versions are unsupported by MicrosoftUse instead: Never create EOT; use WOFF2 + WOFF instead
Related Conversions
Other font conversions you might need