TTF to WOFF2 Converter
Compress a TTF into a WOFF2 you can serve via @font-face. 100% private — runs entirely on your device.
Drop your TTF file here
Converts to .woff2 — stays on your device
Why convert TTF to WOFF2?
- Self-hosting a custom font on your website without pulling from Google Fonts.
- Cutting font payload weight for Core Web Vitals and Lighthouse scores.
- Bundling a licensed commercial font into a web app you control.
- Preparing a client's brand font for delivery in a Webflow, WordPress, or Shopify theme.
- Replacing a heavy TTF in a Next.js or SvelteKit project with a ~30% smaller WOFF2.
- Generating web-ready assets from a font you designed in Glyphs or FontLab.
How our converter works
Your TTF is compressed in-browser using Google's official wawoff2 WebAssembly library — the same encoder Google Fonts uses to produce WOFF2 assets. The resulting WOFF2 contains your font's glyph data reorganized for Brotli compression, typically coming out around 30% smaller than the source TTF.
TTF vs WOFF2 — what's the difference?
| Feature | TTF | WOFF2 |
|---|---|---|
| Size | Uncompressed baseline | ~30% smaller |
| Use | Desktop, design tools, OS install | Web browsers via @font-face |
| Installable | Yes — double-click to install | No — browser-only |
| Compression | None | Brotli + glyph transforms |
| Legacy support | Universal since 1991 | Chrome 36+, Firefox 39+, Safari 12+ |
Frequently asked questions
Why use WOFF2 instead of serving the TTF directly?
WOFF2 is roughly 30% smaller than gzipped TTF and 50% smaller than uncompressed TTF, which meaningfully reduces Largest Contentful Paint on font-heavy pages. It's also the only font format browsers are guaranteed to treat as a web font rather than attempting to install it.
Do I still need to provide a WOFF fallback?
Not in 2026. WOFF2 is supported by 97%+ of browsers worldwide. Only users on IE11 or pre-2018 Safari need WOFF1, and those browsers have other compatibility issues that make font fallback the least of your concerns.
Is the conversion lossless?
Yes. WOFF2 is a compression container — the glyph outlines, hinting, kerning, and OpenType features all survive byte-for-byte. Decompressing the WOFF2 back to TTF produces the original file.
Can I convert a commercial font without violating the license?
Read the EULA. Many commercial font licenses (Monotype, Linotype, Adobe retail) prohibit web use entirely unless you purchase a separate web license. Converting to WOFF2 is a technical operation — licensing is a legal one.
How do I use the WOFF2 on my site?
@font-face { font-family: 'MyFont'; src: url('myfont.woff2') format('woff2'); } — then use font-family: 'MyFont' in your CSS. Set font-display: swap to avoid invisible text during load.
Should I subset the font before converting?
For maximum size savings, yes. Tools like fonttools pyftsubset or glyphhanger strip unused glyphs before WOFF2 compression, often cutting file size by another 50–80%. This converter doesn't subset — it compresses the whole font as-is.
About the TTF format
TTF (TrueType Font) was introduced by Apple in 1991 and co-developed with Microsoft. It remains the dominant installable font format on every desktop operating system — its glyphs are described as quadratic Bézier curves in the 'glyf' table, and the SFNT container format it uses is the same one that later underpinned OpenType (OTF) and the web font formats WOFF and WOFF2. Converting TTF to WOFF2 is the standard step for publishing a custom font to the web: same glyph data, Brotli-compressed, ~30% smaller, browser-optimized.