CometWeb tools
TTF to WOFF2 converter with glyph subsetting
TTF / OTF · conversion and glyph subsetting in your browser, nothing uploaded · WOFF preview
Preview and export run locally. You can generate and download WOFF2 from TTF or OTF; WOFF is currently supported for preview only.
A TTF to WOFF2 converter normally produces a WOFF2 file for browser delivery. This one also subsets the glyphs: it can generate a smaller WOFF2 file from TTF or OTF without uploading it, because conversion and subsetting both run in your browser.
Why are fonts so heavy?
A single weight in TTF can be ~150 KB. A full family with italics often lands in the hundreds of KB.
TTF to WOFF2 conversion with Brotli is usually 30–50% smaller than TTF/OTF.
Subsetting keeps only the glyphs you need, often a fraction of the original.
Read the website quality benchmark to compare font weight, transfer and retest conditions with the rest of the page.
Check characters before subsetting
Use sample text with accented letters, digits, punctuation and currency symbols. Cover every language your site uses. A subset that is too narrow may cause some characters to render in a fallback font.
Common subsets
- latinLatin basic
- ASCII + Western European basics. Enough for English.
- latin-extLatin Extended
- Latin + Central European characters. Typical regional choice.
- cyrillicCyrillic
- When the site serves Cyrillic languages.
- customCustom range
- Your own character set, smallest possible file.
Add a TTF or OTF file, preview it and choose the glyph subset to keep. Conversion runs locally in your browser and lets you download a WOFF2 file containing the selected character range.
Yes, you can convert TTF and OTF locally and download WOFF2. WOFF files can be previewed here, but WOFF export is not supported yet.
A WOFF converter prepares a font for browser delivery. WOFF2 usually reduces transfer size compared with TTF or OTF, but you still need to verify glyph coverage, weights and the @font-face declaration.
Yes. TTF and OTF files are converted locally in the browser and can be downloaded as WOFF2 with the selected glyph subset applied. Check coverage before using the file in production.
Yes for nearly all modern traffic. IE11 needs a WOFF fallback.
Prefer swap or optional. Avoid block (FOIT).
It works, but self-host + subset is usually faster and more private.
They are for different jobs. TTF is the source and desktop format; WOFF2 is the web delivery format, Brotli-compressed and usually 30–50% smaller than the same TTF. Keep the TTF as your master file and serve WOFF2 through @font-face. There is no reason to send a browser a TTF.
Not with this tool: export runs from TTF and OTF, and a WOFF file can only be previewed here. Use the original TTF or OTF if you still have it. WOFF and WOFF2 wrap the same underlying font data, so converting from the source is one step instead of two and keeps the glyph subset under your control.
What else might come in handy
Core Web Vitals in every audit, with priorities, history and before/after comparison.