Convert WOFF to OTF Online

How to Convert WOFF to OTF Online

1. Upload Your WOFF File: Drag and drop or click "Add Files" to select one or more .woff files from your device. Batch upload is supported — drop a whole @font-face stack and convert each in one pass. Parsing runs entirely in your browser via a lazy-loaded build of opentype.js; nothing leaves your machine.
2. Confirm Output Format (OTF): OTF is preset as the target since you landed on this route. The converter unwraps the WOFF container, decompresses each zlib-compressed sfnt table, and writes a clean OpenType file with the OTTO (CFF) or 0x00010000 (TrueType-flavored) sfnt header preserved from the source.
3. Optional — Convert More Files: Add additional WOFFs to the queue, or switch to a sibling route (WOFF to TTF, WOFF to WOFF2) if you need a different desktop or web target instead.
4. Convert and Download: Click "Convert" and grab each .otf file individually. No sign-up, no watermark, no upload to any server — the file you download is generated in your browser session.

Why Convert WOFF to OTF?

WOFF is a transport wrapper, not a font format in its own right. The W3C published WOFF 1.0 as a Recommendation on December 13, 2012 specifically so designers could ship existing TrueType (sfnt 0x00010000) or CFF/OpenType (sfnt 'OTTO') tables over HTTP with zlib compression — typically 40-50% smaller than the raw sfnt for TTF-flavored fonts, and a smaller gain for CFF-flavored fonts since CFF is already compact. When you need the font on the desktop, in a print layout, or inside a design tool, you have to unwrap the WOFF back to a flat OpenType file. Typical reasons to do that:

• Install a webfont on macOS or Windows for desktop design work — Adobe Illustrator, Affinity Designer, Figma desktop, Sketch, and InDesign read .otf from /Library/Fonts (macOS) or C:\Windows\Fonts (Windows). They don't read .woff directly. Convert the WOFF you downloaded from a brand's CDN, then double-click the OTF and macOS Font Book or Windows Font Viewer installs it.
• Hand a font to a print vendor — Print shops and prepress workflows want OTF or TTF; many RIP softwares simply skip WOFF files in a packaged InDesign or Illustrator folder.
• Match the font you see on a website — If a brand ships its logotype as WOFF via @font-face and you're rebuilding the marketing site or a printed brochure, converting the same WOFF to OTF guarantees metric and glyph parity (the underlying glyf or CFF table is identical — only the container changes).
• Embed in a PDF or office document — Microsoft Word, PowerPoint, and Apple Keynote embed .otf and .ttf cleanly; WOFF is not part of the embeddable font list, and fsType permissions are read from the OS/2 table, which survives the unwrap intact.
• Repackage for an icon font workflow — Tools like FontForge, Glyphs 3, and IcoMoon consume OTF, edit hinting or rename glyphs, and re-export. The first step of every such pipeline when you only have a WOFF is to unwrap it.
• Archive a deprecated webfont — Foundries sometimes pull editions off the web. If you have an old WOFF licensed for your project, converting to OTF keeps a stable, openable copy on disk.

Need a different format? See WOFF to TTF for TrueType installs, WOFF to WOFF2 to upgrade an old WOFF to WOFF2's Brotli compression, or OTF to WOFF for the reverse direction.

WOFF vs OTF — Format Comparison

What's Inside the File — Container vs Outlines

The headline implication: converting WOFF to OTF is lossless for the font itself. The only data that doesn't survive is the WOFF-specific metadata wrapper around the font (which is just descriptive XML/key-value, not glyph data).

Frequently Asked Questions

Will my OpenType features (ligatures, kerning, alternates) survive the WOFF to OTF conversion?

Yes. The OpenType layout tables — GSUB (substitutions including ligatures and stylistic alternates), GPOS (kerning and mark positioning), GDEF (glyph definitions), and BASE/JSTF — are stored inside the WOFF container as ordinary sfnt tables, just zlib-compressed. Unwrapping decompresses them back to their raw form. The resulting OTF behaves identically to the OTF the foundry originally compiled before they wrapped it for the web.

Will my output be .otf or .ttf? They both came out before.

It depends on the outline format inside your WOFF. If the source font uses CFF/CFF2 (PostScript outlines, common for Adobe and contemporary type-foundry releases), the sfnt header is OTTO and the right extension is .otf. If it uses TrueType outlines (glyf table, sfnt header 0x00010000), the technically-correct extension is .ttf even though "OTF" colloquially covers both. This converter writes .otf for the file extension since that's what you asked for, but if your design tool complains about the format, try the WOFF to TTF route — it's the same unwrap, different extension label.

Can I legally install a webfont I extracted from a website?

Only if the license allows it. Most commercial webfont licenses (Adobe Fonts, Monotype, MyFonts) restrict the WOFF to browser use on a specific domain. Self-hosted open-source fonts (SIL Open Font License — fonts from Google Fonts, Fontsource, Font Squirrel) are explicitly licensed for desktop use too. Check the foundry's EULA before installing a webfont you pulled from someone else's CSS. xconvert does the technical conversion; you're responsible for the licensing.

Why is my OTF noticeably larger than the WOFF was?

Because WOFF 1.0 applies zlib compression to every font table, the resulting WOFF is typically 40-50% smaller than the raw TrueType-flavored sfnt. CFF-flavored fonts (already-compact PostScript outlines) shrink less under WOFF, but you should still expect the OTF to be 20-40% larger than the WOFF it came from. The OTF you download is a faithful, uncompressed copy of the OpenType data — that's by design, because operating systems can't read zlib-wrapped tables.

How is this different from WOFF2 to OTF?

WOFF2 swaps zlib for Brotli compression plus a glyph-data preprocessor, so WOFF2 files are typically 20–30% smaller than equivalent WOFF 1.0 files (median ~24% for TTF-flavored fonts). The unwrap is the same idea — decompress the tables, write a flat sfnt — but the algorithm and the parser are different. If you have a WOFF2, use WOFF2 to OTF instead; this page only accepts WOFF 1.0.

Does the converter work offline?

Once the page has loaded, yes. opentype.js is lazy-loaded into the page and runs entirely in your browser. After the initial page load you can disconnect and continue converting — your files never go to a server.

Will the converter strip the font's vendor name, copyright, or license string?

No. Those live in the name table (name IDs 0, 7, 8, 9, 10, 13, 14, 16, 17), which is preserved during the unwrap. Open the resulting OTF in macOS Font Book or use a tool like ttx to dump the name table — you'll see the same copyright, designer, vendor URL, and license URL strings that the foundry shipped.

My WOFF has variable-font axes. Will those work after conversion?

Yes, with caveats. OpenType Font Variations are defined by the fvar, avar, gvar (for TrueType outlines), HVAR, MVAR, and STAT tables — all standard OpenType tables that ride inside the WOFF container unchanged. The resulting OTF is a valid variable font and modern apps (Illustrator 24+, Photoshop 22+, Figma, recent InDesign) honor the axes. Older apps that predate variable-font support will fall back to the default instance.

Can I rename the font or change the family during conversion?

Not from this page — xconvert is purely a container-level converter. To rename the family or rebuild the name table, open the resulting OTF in FontForge or Glyphs and edit the name fields, then re-export. Renaming is a licensed activity in most foundry EULAs, so confirm you have rights before redistributing a renamed font.