WOFF2 (.woff2) is the current web-font format: a font's sfnt tables preprocessed and squeezed with Brotli compression so pages download less type data. It is purely a transport wrapper — decompressing a .woff2 reconstructs a working TrueType or OpenType font.
Private for supported formats — processed in your browser
Convert supported files
Runs on your device
+
Drop WOFF2 files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.
Google's font-compression research fed into the W3C effort that produced WOFF2, and the specification reached Recommendation status in 2018. It succeeded the zlib-based WOFF 1.0 by delivering roughly thirty percent smaller files, and Google Fonts switching to it made it the dominant delivery format within a few years.
How WOFF2 works
Brotli compression over the whole font, preceded by a glyf and loca transformation that re-encodes outline data for better compressibility.
Averages around 30% smaller than WOFF 1.0 on the same font, with larger wins on CJK fonts.
Cannot be installed as a system font — it must be unpacked to TTF or OTF first.
Passes payload tables through intact, so variable fonts and color-font tables survive completely.
When to use WOFF2
Serving fonts on production websites as the default @font-face source
Shrinking variable fonts for web delivery
Delivering icon fonts efficiently
Meeting page-weight performance budgets
Strengths and limitations
Strengths
The smallest deliverable font format, cutting load time and bandwidth
Lossless — full fidelity of the wrapped font is preserved
Supported by every browser that matters today
Limitations
Operating systems will not install it, so designers juggle separate web and desktop copies of the same font
Encoding is computationally heavier than WOFF, though that cost is paid once at build time
Compatibility
Chrome, Firefox, Safari, and Edge have all supported .woff2 for years — coverage is effectively universal outside long-dead browsers like Internet Explorer, which never adopted it. Because no operating system accepts it for installation, workflows convert to TTF or OTF whenever a font must leave the browser.
All metadata of the wrapped font survives untouched, and the container can additionally carry an optional extended-metadata XML block from the vendor.