Free Font Converter — Convert Between WOFF, TTF, OTF, WOFF2
Table of Contents
You downloaded a font as a TTF file but your website needs WOFF2. Or a client sent you an OTF but your web builder only accepts WOFF. Font format compatibility issues are one of the most common friction points in web development and design workflows.
Our free font converter transforms between WOFF, WOFF2, TTF, OTF, and EOT formats instantly. Upload your font file, select the target format, and download the converted file. Everything processes in your browser — your fonts never leave your device and are never stored on any server.
Font Format Differences Explained
There are five font formats you will encounter. Each was created for a specific purpose:
- TTF (TrueType Font): Developed by Apple and Microsoft in the late 1980s. The universal desktop font format. Works on every operating system — Windows, macOS, and Linux. Large file sizes make it inefficient for web use, but it is the starting point for most font conversions.
- OTF (OpenType Font): A successor to TTF, jointly developed by Microsoft and Adobe. Supports advanced typographic features — ligatures, contextual alternates, small caps, and larger character sets. File sizes are similar to TTF. Preferred by designers for print and desktop work.
- WOFF (Web Open Font Format): A compressed wrapper around TTF or OTF data, created specifically for web delivery. Files are 20 to 40 percent smaller than the equivalent TTF. Supported by all modern browsers since 2012. The previous standard for web fonts.
- WOFF2 (Web Open Font Format 2.0): Uses Brotli compression instead of zlib, achieving 30 to 50 percent smaller files than WOFF (and 50 to 70 percent smaller than TTF). Supported by all modern browsers. The current best practice for web fonts.
- EOT (Embedded OpenType): Microsoft's proprietary web font format, created exclusively for Internet Explorer. No longer needed since IE has been retired. Only relevant for legacy support of IE11.
When to Use Which Format
| Use Case | Recommended Format | Why |
|---|---|---|
| Modern website | WOFF2 (primary) + WOFF (fallback) | Smallest file size, fastest loading |
| Desktop app or print | OTF or TTF | Full feature support, universal OS compatibility |
| Email template | System fonts (no custom fonts) | Most email clients do not support custom web fonts |
| Legacy IE support | EOT + WOFF + WOFF2 | EOT for IE, WOFF for older browsers, WOFF2 for modern |
| Mobile app | TTF or OTF | Native mobile frameworks expect desktop font formats |
For 95% of web projects today, you only need WOFF2 with a WOFF fallback. The days of serving four different font formats are over. Modern browser support is universal enough that WOFF2 alone covers nearly all users.
Sell Custom Apparel — We Handle Printing & Free ShippingWeb Performance — Why WOFF2 Matters
Custom fonts are one of the top causes of slow website loading. A single font family with regular, bold, italic, and bold-italic weights can add 400KB+ in TTF format. Convert to WOFF2 and that drops to 120-160KB — a 60% reduction that directly improves page load time.
Font file size matters because:
- Fonts block text rendering. Browsers wait for font files to download before displaying text. Larger files mean longer waiting — especially on mobile networks. Users see a blank space (FOIT — Flash of Invisible Text) or a jarring font swap (FOUT — Flash of Unstyled Text).
- Core Web Vitals impact. Google's Largest Contentful Paint (LCP) metric measures when the main content becomes visible. If your heading uses a custom font that takes 800ms to load, your LCP suffers. WOFF2 cuts that load time significantly.
- Mobile data costs. Not everyone has unlimited data. Serving 400KB of fonts instead of 160KB means users on metered connections pay more to view your page. WOFF2 is a direct cost reduction for your visitors.
Best practice: convert all web fonts to WOFF2, subset them to include only the characters you actually use (Latin characters for English sites), and use the font-display: swap CSS property to show fallback text while fonts load.
Browser Support Table
| Format | Chrome | Firefox | Safari | Edge | IE |
|---|---|---|---|---|---|
| WOFF2 | 36+ | 39+ | 12+ | 14+ | No |
| WOFF | 5+ | 3.6+ | 5.1+ | 12+ | 9+ |
| TTF | 4+ | 3.5+ | 3+ | 12+ | 9+ (partial) |
| OTF | 4+ | 3.5+ | 3+ | 12+ | 9+ (partial) |
| EOT | No | No | No | No | 6+ |
As of 2026, WOFF2 is supported by over 97% of global web users. WOFF covers the remaining fraction. EOT is only relevant for Internet Explorer, which Microsoft officially retired in June 2022.
Convert Your Font Files Now
Free, private, no signup. Convert between WOFF, WOFF2, TTF, OTF, and EOT instantly.
Open Font ConverterFrequently Asked Questions
What is the best font format for websites?
WOFF2 is the best format for modern websites. It offers the smallest file size (30 to 50 percent smaller than TTF), is supported by all modern browsers (Chrome, Firefox, Safari, Edge), and was specifically designed for web delivery. Serve WOFF2 as your primary format with WOFF as a fallback for older browsers.
What is the difference between TTF and OTF?
TTF (TrueType) and OTF (OpenType) are both desktop font formats. OTF supports more advanced typographic features — ligatures, stylistic alternates, and larger character sets. OTF files can also use more efficient curve descriptions, sometimes resulting in smaller file sizes. For most users the difference is negligible. For designers and typographers working with advanced typography, OTF is preferred.
Do I still need EOT font files?
EOT (Embedded OpenType) was created by Microsoft exclusively for Internet Explorer. Since IE has been officially retired and replaced by Edge (which supports WOFF and WOFF2), EOT is no longer needed for new websites. The only reason to generate EOT files is if you must support legacy IE11 users, which is under 0.5 percent of global web traffic as of 2026.

