WOFF Converter

How to Convert WOFF to Any Format

1. Add Your WOFF File: Drag and drop your .woff font or click "+ Add Files". You can queue several fonts at once and each one is converted separately, then downloaded individually.
2. Pick an Output Format: Choose your target from the format dropdown — TTF, OTF, WOFF2, or EOT. Picking TTF or OTF extracts the outlines so the font can be installed on a desktop; picking WOFF2 re-compresses it for the web.
3. Convert: Click Convert. The conversion runs entirely in your browser via opentype.js — your font is parsed, decompressed, and re-serialized locally, so the file is never uploaded to a server.
4. Download: Grab the converted font. No sign-up, no watermark, and because everything happens on your device, the file data never leaves your browser.

Popular WOFF Conversions

• WOFF to TTF — unwrap the font so you can install it on Windows, macOS, or Linux as a desktop font
• WOFF to OTF — extract to OpenType when you need PostScript outlines or advanced typographic features for print and design tools
• WOFF to WOFF2 — re-compress with Brotli for a smaller web font and faster page loads
• WOFF to EOT — produce an Embedded OpenType file for very old Internet Explorer fallbacks

Why Convert a WOFF File?

WOFF (Web Open Font Format) is a W3C Recommendation first published on December 13, 2012, created by Jonathan Kew, Tal Leming, and Erik van Blokland. It is not a new outline format — the W3C spec describes it as "a container format or 'wrapper' for font data in already-existing formats." A WOFF file takes an ordinary TrueType (TTF) or OpenType (OTF) font, compresses its tables with zlib, and optionally bolts on a block of XML metadata for licensing and vendor information. The whole point is web delivery: a WOFF loads through a CSS @font-face rule and is typically 40-50% smaller than the raw TTF or OTF it wraps.

That web-first design is exactly why people convert it. A WOFF works beautifully inside a browser but is awkward everywhere else:

• Installing it as a desktop font — Windows, macOS, and Linux font managers, plus apps like Word, Photoshop, and Illustrator, expect TTF or OTF, not WOFF. Converting to TTF or OTF unwraps the original outlines so you can double-click and install.
• Smaller, faster web fonts — If you already self-host WOFF, converting to WOFF2 swaps zlib compression for Brotli, shaving roughly another 25% off the file size on average (the W3C WOFF 2.0 Evaluation Report measured a median of about 24% on the Google Fonts corpus).
• Editing or hinting — Type-design tools such as FontForge or Glyphs work with TTF/OTF sources, so extracting back to one of those is the first step before any glyph edits.
• Legacy fallbacks — A handful of intranet apps still target Internet Explorer, whose older versions only accept Microsoft's EOT format, so an EOT export is occasionally still needed for those edge cases.

Because WOFF is just a compressed wrapper, converting it back to the TTF or OTF it was built from is a near-lossless operation — the glyph outlines and hinting are restored intact.

WOFF Compared to Common Font Formats

Frequently Asked Questions

Can I install a WOFF file as a desktop font?

Not directly. WOFF is a web-delivery format — operating-system font managers and design apps like Word, Photoshop, and Illustrator don't recognize it. To install the font on your computer, convert it to TTF or OTF first using WOFF to TTF or WOFF to OTF, then double-click the resulting file to install it the normal way.

Does converting WOFF to TTF lose any quality?

No. WOFF doesn't change the font's outlines — it just compresses the TTF or OTF data with zlib and adds optional metadata. Converting back to TTF or OTF decompresses that same data and re-serializes it, so the glyph shapes and hinting are restored byte-faithfully. There is no re-rendering or resampling step that could degrade the font.

What's the difference between WOFF and WOFF2?

Both are W3C web font wrappers around the same TTF/OTF data; the difference is the compression. WOFF 1.0 (2012) uses zlib, while WOFF2 (2018) uses Google's Brotli algorithm, which the W3C WOFF 2.0 Evaluation Report measured as roughly 24% smaller on average. WOFF2 is supported by about 96% of browsers (Chrome 36+, Firefox 39+, Safari 12+, Edge 14+), so it's the recommended self-hosting format today, with WOFF 1.0 kept only as a fallback for very old browsers.

Should I convert my WOFF to WOFF2 for my website?

Usually yes, if your audience is on modern browsers. WOFF to WOFF2 re-compresses the font with Brotli for a smaller download and faster first paint. The only reason to keep the original WOFF is to serve a fallback to browsers predating Chrome 36 / Firefox 39 / Safari 12, which now make up only a few percent of traffic. Many sites ship both in the @font-face src list, letting each browser pick the format it supports.

Will the font's license metadata survive the conversion?

It depends on the target. WOFF can embed an XML metadata block with license and vendor details. Converting to TTF or OTF extracts the outline tables but does not carry over that separate WOFF metadata wrapper — though any licensing information stored inside the font's own name table is preserved. Always keep your original license; converting a font does not grant you any rights you didn't already have.

Does my font get uploaded to a server when I convert it?

No. This converter runs entirely in your browser using opentype.js: the WOFF is parsed, decompressed, and re-written into the target format locally, and the download is generated on your device. The font data never leaves your browser, so there's no upload, no account, and no waiting in a server queue. In our testing, a typical 30-50 KB web font converts in well under a second once the page has loaded.