XConvert
Downloads
Pricing

Convert WOFF2 to TTF Online

Turn a WOFF2 web font into a TTF font file in seconds—upload your WOFF2, convert to TTF, then download.

Input (WOFF2)
🅰
Choose a WOFF2 font file to convert
Output (TTF)
🅰
Output will appear here after conversion

How to Convert WOFF2 to TTF Online

  1. Upload Your WOFF2 File: Drag and drop a .woff2 file onto the page or click "+ Add Files" to pick one from disk. Parsing and Brotli decompression happen locally in your browser via opentype.js — the file never leaves your session, and batch uploads of an entire font family are supported.
  2. Confirm TTF as the Output: The output is already locked to TTF for this tool. WOFF2 is a Brotli-compressed sfnt wrapper, so decoding restores the underlying TrueType (or CFF/OpenType) tables without any re-encoding of glyph outlines, hinting, or layout data.
  3. Convert and Download: Click Convert. Each font is written as a standalone .ttf file with the original name table preserved, so it appears with the correct family and style in your OS font picker. Files queue in the page for batch download.
  4. Install on Your System (Optional): On Windows 11, double-click the .ttf and choose Install, or drop it into C:\Windows\Fonts. On macOS Sonoma, double-click and click Install Font in Font Book. On Linux, drop the file into ~/.local/share/fonts and run fc-cache -f. The same .ttf works on all three.

Why Convert WOFF2 to TTF?

WOFF2 (Web Open Font Format 2.0) became a W3C Recommendation on 1 March 2018 and is the modern default for web font delivery — Brotli compression combined with table-level transforms makes WOFF2 files typically 20–30% smaller than WOFF 1.0 (median ~24% for TTF-flavored fonts) and ~40–60% smaller than the uncompressed TTF master they wrap. The trade-off is that desktop operating systems, design apps, font managers, and PDF embedders do not accept .woff2. Converting back to TTF unwraps the Brotli layer and gives you the underlying TrueType data — installable, editable, and embeddable everywhere a standard font is accepted.

  • Install a web font into a desktop app — Windows 11, macOS Sonoma's Font Book, and Linux's fontconfig accept .ttf but reject .woff2. Designers picking up a brand typeface from a site's @font-face CSS need TTF to use it in Figma desktop, Adobe Illustrator, InDesign, Sketch, or Microsoft Word.
  • Match website type in print and PDF — Adobe InDesign, Affinity Publisher, and QuarkXPress embed TTF/OTF outlines into PDF/X output for offset and digital print. A .woff2 cannot be embedded; converting first keeps the printed brochure visually identical to the live site.
  • Edit, hint, or subset the font — FontForge, Glyphs, Birdfont, and FontLab open TTF directly. WOFF2's table transforms are not editor-friendly; even tools that read it usually round-trip through TTF/OTF for editing.
  • Convert onward to another web format — If you need to ship WOFF 1.0 for older clients or build an EOT file for a legacy intranet, TTF is the canonical intermediate. Most encoders take TTF or OTF as input, not WOFF2.
  • Archive an uncompressed master — Brands that rotate typefaces every few years benefit from keeping a TTF master alongside the deployed WOFF2. Text editors and font inspectors read TTF natively, the format has been stable since 1991, and any future re-encoding starts from the master rather than a Brotli-transformed copy.
  • Embed in a slide deck or e-book — PowerPoint's "Embed fonts in file" option, Keynote's font collection, and EPUB 3 font embedding all require TTF or OTF and reject WOFF2 at import time.

A note on file size: removing Brotli typically grows a .woff2 3–5× when it expands to .ttf (a 30 KB WOFF2 may become 100–150 KB TTF). You are decompressing, not transcoding — the size increase is the whole point. For web delivery you would keep using WOFF2; TTF is for the desktop side of the workflow.

WOFF2 vs TTF — Format Comparison

Property WOFF2 TTF
Year standardised W3C Recommendation, 1 March 2018 Apple, 1991 (later co-developed with Microsoft)
Container vs format Wrapper around sfnt (TTF/OTF) tables with Brotli compression and glyf/loca transforms Native sfnt outline format
Compression Brotli (whole-font), with table-level pre-processing None at file level
Typical size vs TTF ~40–60% smaller than uncompressed TTF Baseline
Typical size vs WOFF 1.0 typically 20–30% smaller (median ~24% for TTF-flavored fonts) n/a
Browser support Chrome 36+, Firefox 39+, Safari 12+, Edge 14+ — ~96% global support Limited — works in older IE, modern browsers prefer WOFF/WOFF2
Desktop install Not supported by Windows, macOS, or Linux installers Native install on every desktop OS
Reconstructed-byte equivalence Renders identically, but the W3C spec allows reconstructed tables to differ byte-wise from the source TTF Original — no reconstruction step
Best for @font-face delivery over HTTP/2 and HTTP/3 Desktop apps, print, PDF embedding, font editing

WOFF2 and TTF carry the same glyph data and render pixel-for-pixel the same; what changes is the outer envelope, the compression scheme, and which apps accept the file.

Font Format Quick Guide — When to Use Each

Format Compression Primary use Notes
TTF None Desktop install, print, PDF embed, font editing Universal support across Windows, macOS, Linux since the 1990s
OTF None Desktop and print, with PostScript (CFF) outlines and richer typographic features Preferred when the font uses advanced OpenType layout features
WOFF zlib Web @font-face delivery for older browsers (IE 9+, Android 4+) Roughly 40–50% smaller than TTF; standardised 2012
WOFF2 Brotli + table transforms Modern web delivery (Chrome 36+, Firefox 39+, Safari 12+) Typically 20–30% smaller than WOFF (median ~24%); the current best practice for the web
EOT LZ-style Legacy Internet Explorer 4–8 only Effectively obsolete; only ship if you still support IE ≤ 8

If your goal is web delivery, you would convert TTF → WOFF2. If your goal is desktop use, you convert WOFF2 → TTF (this tool).

Frequently Asked Questions

Does converting WOFF2 to TTF lose any glyph quality or hinting?

No. WOFF2 is a Brotli-compressed container around the same sfnt tables that live inside a TTF or OTF. Decoding restores the glyph outlines, instructions (hinting), cmap, GPOS/GSUB, kern, and name tables exactly as the foundry encoded them — the resulting TTF renders pixel-for-pixel the same as the original master. The W3C WOFF2 spec does note that decoders may produce a TTF whose glyf table is structured slightly differently byte-wise from the absolute original (the transform allows multiple valid reconstructions), but rendering, metrics, and feature behaviour are identical.

Why is the TTF so much larger than the WOFF2 I uploaded?

Because WOFF2 uses Brotli plus table-level pre-processing and TTF is uncompressed. A 30 KB WOFF2 commonly expands to 100–150 KB as TTF — that is the compression layer being removed, not data being added. The same glyph and hinting tables are present in both files. If keeping size down matters for delivery, stay on WOFF2 for the web and only convert to TTF when you need the desktop file.

Will the converted TTF install on Windows 11 and macOS Sonoma?

Yes. After downloading, double-click the .ttf on Windows 11 and click Install (or right-click and choose Install for all users), or drop it into C:\Windows\Fonts. On macOS Sonoma, double-click to open in Font Book and click Install Font, or drag into the Font Book window. Linux distributions accept TTF in ~/.local/share/fonts followed by fc-cache -f. The same .ttf works on all three operating systems.

Can I legally convert a WOFF2 I downloaded from a website?

Format conversion does not change the font's licence. A typeface bought under a web-only licence (priced on monthly pageviews) generally does not grant desktop or app-embedding rights, and converting WOFF2 to TTF for installation may violate that EULA. A desktop licence already entitles you to the TTF and the foundry will usually ship one directly. Self-hosted webfonts whose licence allows desktop use (Google Fonts, SIL Open Font Licence releases, fonts you commissioned) can be converted freely. Adobe Fonts and Monotype, for example, explicitly disallow extracting webfonts for desktop use — when in doubt, check the licence file or contact the foundry.

Does the converter handle CFF (PostScript-flavour) WOFF2 files too?

Yes. WOFF2 can wrap either TrueType (glyf) outlines or PostScript (CFF/CFF2) outlines. If the source is CFF-flavour, the natural output is OTF rather than TTF — we provide a dedicated WOFF2-to-OTF tool for that case. If you pick the wrong tool, the converter detects the outline type and warns you. The file extension on disk is independent of the outline flavour, so picking the right tool by checking what the foundry shipped (TTF master vs OTF master) is the cleanest path.

Will OpenType features like ligatures, small caps, and variable axes survive?

Yes. Ligatures (liga, dlig), small caps (smcp), stylistic sets, kerning, and language-specific substitutions all live in the GSUB/GPOS tables, which are preserved verbatim during decompression. Variable-font axes (fvar, gvar for TrueType or CFF2 for PostScript) are also preserved — a Roboto Flex or Inter variable font round-trips cleanly from WOFF2 back to a fully-functional variable TTF.

What about colour fonts (COLR/CPAL, SVG-in-OpenType)?

Preserved. Colour-font tables (COLR, CPAL, sbix, CBDT/CBLC, SVG ) are pass-through data inside the sfnt structure that WOFF2 wraps. Apple Color Emoji, Microsoft's Segoe UI Emoji, and SVG-in-OpenType colour fonts all round-trip cleanly. Whether your destination app renders those colour tables is a separate question — Adobe Illustrator added COLRv1 support in 2022, and Word for Microsoft 365 renders Microsoft's emoji palette.

Is anything uploaded to your servers?

No. The conversion runs entirely in your browser via opentype.js — your font file is Brotli-decoded, the sfnt tables are reconstructed, and the download blob is generated client-side. There is no upload, no account, no watermark, no Pro tier hiding behind a paywall.

How many files can I convert at once?

Drop several WOFF2 files onto the page and they queue in the browser. Practical batch size is bounded by your machine's RAM rather than any server cap — most users comfortably process a 20-font family in a single pass. There is no per-file size limit beyond what your browser can hold in memory; Brotli decoding is the most memory-hungry step, so very large display fonts (50 MB+ WOFF2 with extensive glyph coverage) benefit from converting one at a time.

Related Generate tools
Font Face Css GeneratorFont Subsetter
Related Convert tools
Convert Woff2 To OtfConvert Woff2 To WoffConvert Woff2 To EotConvert Otf To TtfConvert Woff To TtfConvert Eot To Ttf

Image Tools

Image CompressorCompress JPEGCompress PNGCompress GIFCompress WebPImage ConverterJPG ConverterImage Resizer

Video Tools

Video CompressorCompress MP4MP4 to GIFVideo to GIFVideo ConverterMP4 ConverterVideo Cutter

Audio Tools

Audio CompressorCompress MP3Compress WAVAudio ConverterMP3 ConverterFLAC to MP3Audio Cutter

Document Tools

Compress PDFMerge Images to PDFSplit PDFPDF to JPGUnzip FilesRAR Extractor
© 2026 XConvert.com. All Rights Reserved.
About UsPrivacy PolicyTerms of ServiceContactHelp Us Grow