WOFF2 vs WOFF vs TTF vs OTF
For most websites the answer is short: use WOFF2. Here’s what each format is for, and when you might need something else.
The formats at a glance
| Format | Made for | Use it on the web? |
|---|---|---|
| WOFF2 | Websites, with the best compression | Yes, always |
| WOFF | Websites, with older compression | Only for very old browsers |
| TTF | Desktop apps | No, it’s too large |
| OTF | Desktop apps and print | No, it’s too large |
| EOT | Old Internet Explorer | No, it’s obsolete |
| SVG fonts | Early iPhones | No, it’s obsolete |
Why WOFF2 wins
WOFF2 wraps a normal font in Brotli compression, with extra steps designed for font data. It works in all modern browsers, so one file is usually enough. Convert yours with the TTF to WOFF2 Converter or OTF to WOFF2 Converter.
Do I still need a WOFF fallback?
Rarely. Add one only if your analytics show visitors on very old browsers. It costs little, because browsers download only the first format they support:
src: url("brand.woff2") format("woff2"),
url("brand.woff") format("woff");TTF or OTF?
This matters mainly for your source files. TTF uses TrueType outlines, and OTF usually uses PostScript-style outlines. Once converted to WOFF2, both are fine for the web. If you’ve lost a source file for a font you’re licensed to use, the WOFF2 to TTF Converter can restore it.
