Convert WOFF2 to WOFF.
Repack WOFF2 as WOFF for legacy browsers — output grows.
Drop WOFF2 fonts here
or browse your files
Paste with ⌘V · or drop files anywhere on the page
Files never leave your device. Everything runs in your browser, nothing touches a server — tools you've used even work offline.
Going from WOFF2 back to WOFF trades size for reach: zlib compresses less than Brotli, so expect the output to be 25–40% larger — same font, older wrapper. Useful when a legacy browser or an old toolchain insists on WOFF.
How it works
- Drop TTF, OTF, WOFF, WOFF2 or EOT files anywhere on the page — or click to browse.
- Pick the output format — the font tables are repackaged losslessly, never re-drawn.
- Convert, then download each font on its own or the whole batch as a ZIP.
The short list that still wants WOFF
Downgrading only makes sense when something in the chain cannot read WOFF2 — and that list is short, specific and shrinking.
| Environment | Why it needs WOFF |
|---|---|
| Internet Explorer 9–11 | WOFF2 support never shipped |
| Android 4.x stock browser & webviews | Frozen before Brotli existed |
| Old smart-TV & e-reader browsers | Engines forked around 2013–2015 |
| Strict CMS / email-builder allowlists | Upload validation predates WOFF2 |
Budget for the growth
Expect the output to land 25–40% above the WOFF2 you started with — zlib simply cannot match Brotli on font tables. A 70 KB WOFF2 typically becomes a 90–100 KB WOFF. If both files end up on the same site, serve them as a pair in @font-face with the WOFF2 listed first, so only the browsers that truly need the bigger file ever download it. Upgrading in the other direction is WOFF to WOFF2.
Frequently asked questions
Why is the converted file bigger than my WOFF2?
Because WOFF uses zlib and WOFF2 uses Brotli, and Brotli simply compresses better. The font inside is identical — the older wrapper just costs 25–40% more bytes. That is the honest price of legacy compatibility.
Who actually needs WOFF today?
Browsers that predate 2016 — IE9–11, old Android stock browsers, some embedded webviews — and the occasional tool or CMS that validates uploads against a WOFF-only allowlist.
Am I allowed to convert this font?
Converting a font never changes its license. Many desktop licenses do not cover web embedding (and vice versa), so check yours before publishing a converted font. Fonts under the OFL or Apache licenses and fonts you made yourself are fine. Your file also never leaves your device — nothing is uploaded anywhere.
Is it private?
Yes. The font is repackaged entirely in your browser — it is never uploaded, and the server does nothing but deliver this page. For licensed fonts that matters twice over: nothing is redistributed to any third party, and no copy lingers on a server afterwards. Want proof? Run one file through, switch your connection off, and run another — it still works.