Upload WOFF2 files and pick an output format — TTF is selected by default. Batch supported, free up to 400 MB per file.
For the most common job, use the dedicated WOFF2 to WOFF converter.
.woff2 file onto the page or click "Choose font file". You can drop several WOFF2 files at once — each is queued and converted in turn.WOFF2 (Web Open Font Format 2.0) is a W3C Recommendation — first published in March 2018 and revised to a second edition in August 2024 — and it is the current best practice for shipping fonts to the web. It isn't a new typeface format: WOFF2 is a thin wrapper around the same SFNT outline data found in TrueType and OpenType fonts, compressed with Brotli plus a font-aware preprocessing step. That compression makes a WOFF2 roughly 30% smaller than the same font as WOFF 1.0, which is why nearly every site built since 2018 serves WOFF2 first. It's supported in about 96% of browsers in use today (Chrome 36+, Firefox 39+, Safari 12+, Edge 14+), with Internet Explorer the main holdout.
The catch is that WOFF2 is a web-delivery format, not a desktop one. Drop a .woff2 into your system Fonts folder and Windows and macOS will refuse to install it — the OS font installers only accept TTF and OTF. That mismatch is the single most common reason people convert:
.woff2 served by a website and want to use it in Photoshop, Word, Figma, or InDesign. Converting WOFF2 to TTF (or OTF) produces a file your operating system's font installer accepts.@font-face rule..woff2 sometimes need the uncompressed TTF/OTF to run their own subsetting and re-export a leaner web bundle.| Format | Standard / Origin | Compression | Primary use | Installs on desktop |
|---|---|---|---|---|
| WOFF2 | W3C (2018, rev. 2024) | Brotli (~30% smaller than WOFF) | Web font delivery | No |
| WOFF | W3C (2012) | zlib/Flate | Web fonts, older-browser fallback | No |
| TTF | Apple / Microsoft (TrueType, 1991) | None (uncompressed) | Desktop fonts, broad app support | Yes |
| OTF | Adobe / Microsoft (OpenType, 1996) | None (uncompressed) | Desktop fonts, advanced typography | Yes |
| EOT | Microsoft (1997) | Optional MTX | Legacy Internet Explorer web fonts | No |
| Font data | Survives? | What actually happens |
|---|---|---|
Glyph outlines (glyf or CFF ) |
Yes | WOFF2's transform is reversed on decode, so the vector shapes are functionally identical to the original |
Character map (cmap) |
Yes | Every codepoint-to-glyph mapping is preserved |
Metrics and kerning (hmtx, kern, GPOS) |
Yes | Spacing and kerning pairs come through unchanged |
OpenType features (GSUB — ligatures, small caps, stylistic sets) |
Yes | Layout tables are carried, which is why OTF is the better target when they matter |
Variable-font axes (fvar, gvar, STAT) |
Yes | A variable WOFF2 unwraps to a variable TTF or OTF |
TrueType hinting (prep, fpgm, cvt , glyph instructions) |
Yes | Hinting instructions are part of the font data the wrapper carries |
Color and emoji tables (COLR/CPAL, sbix, CBDT) |
Yes, where present | WOFF2 wraps whatever tables the source font contained |
Digital signature (DSIG) |
No | The WOFF2 spec requires encoders to strip DSIG before compressing, because repacking invalidates any signature over the original bytes |
| WOFF2 extended metadata block | No | The optional XML metadata block is a WOFF/WOFF2 container feature with no slot in a bare TTF or OTF |
| File size | Grows substantially | Brotli compression is undone, so expect the TTF to be several times the size of the WOFF2 |
A decoded WOFF2 is functionally identical to the source font but is not guaranteed to be a byte-for-byte match: the W3C WOFF 2.0 specification notes that encoding variations mean different decoders may produce output that differs in bytes while retaining the exact functionality of the input font.
WOFF2 is meant to be loaded by a web browser through a CSS @font-face rule, not opened directly. Browsers (Chrome, Firefox, Safari, Edge) decode it transparently to render web pages, but double-clicking a .woff2 on your desktop won't preview or install it the way a TTF or OTF would, because the OS font installers don't accept the web format. To preview, install, or edit the font yourself, convert it to TTF or OTF first.
You can't install a .woff2 directly — Windows Font Viewer and macOS Font Book only accept TTF and OTF. Convert the file to WOFF2 to TTF first, then install the resulting .ttf: on Windows, right-click it and choose "Install", or drop it into C:\Windows\Fonts; on macOS, double-click it and click "Install Font", or copy it into ~/Library/Fonts. After that the typeface shows up in your application font menus.
The glyph outlines are preserved exactly. WOFF2 stores the same SFNT (TrueType/OpenType) outline data as a TTF, just compressed with Brotli, so converting to TTF decompresses and rewraps that data without re-rendering any glyphs — the vector shapes are byte-for-byte equivalent. What can change is metadata and OpenType layout tables: a font that was originally OpenType (with ligatures and stylistic sets) is best converted to OTF rather than TTF to keep those features intact.
It depends on the target. WOFF2 only wraps whatever was inside the original font, so if the source was an OpenType font with ligatures, kerning pairs, or stylistic sets, convert to WOFF2 to OTF to carry those layout tables through. Converting to plain TTF keeps the outlines and basic metrics but is more likely to flatten advanced OpenType typography, so pick OTF when those features matter.
Those targets are for browser fallbacks, not desktop installation. WOFF (2012) is decoded by slightly older browsers that predate WOFF2 support, and EOT was Internet Explorer's proprietary web-font format for IE 6–11. If you're still supporting very old browsers, you'd list a WOFF2 file first and a WOFF (or EOT) second in your @font-face rule so each browser picks the newest format it understands.
No. This font conversion runs entirely in your browser using JavaScript — the .woff2 file is read and decompressed. There's no account and no watermark, which makes it a good fit for licensed or proprietary fonts you'd rather not send to a third-party server.
In our testing, a typical regular-weight Latin text font that is around 150–200 KB as an uncompressed TTF lands near 50–70 KB as WOFF2 — roughly a 60–70% reduction — because WOFF2's Brotli compression and glyph preprocessing pack the outline data far tighter than the unwrapped TTF. That difference is exactly why the web serves WOFF2 and why converting back to TTF produces a noticeably larger file.
Technically it is trivial; legally it depends entirely on the licence, and this is the question worth stopping on. A large share of commercial webfonts are licensed for web embedding only — the licence grants a site the right to serve the font to its visitors, not to install it, redistribute it, or use it for print and design work. The WOFF specifications reinforce that boundary at the technical level too: decoded font data must not be made available to other applications or documents on the user's system, which is precisely why a browser will happily render a .woff2 while your operating system refuses to install one. Open-licence families are the clear exception — anything under the SIL Open Font License or Apache 2.0, which covers most of Google Fonts, can be converted and installed freely. When in doubt, read the font's licence file or the foundry's EULA before converting, and for open families prefer downloading the original TTF or OTF from the source rather than unwrapping a served WOFF2.