TTF Converter

How to Convert TTF to Any Font Format

1. Upload Your TTF Files: Click "Choose font file" or drag and drop .ttf files from your device. Batch is supported — drop in a whole family (Regular, Bold, Italic, Bold Italic, plus weights like Light and Medium) and convert them all in one pass.
2. Pick an Output Format: Use the "To format" dropdown to choose your target — WOFF2, WOFF, OTF, or EOT. WOFF2 is preselected because it is the smallest web format. There are no compression sliders or codec settings: font conversion is defined by each format's spec, so the output bytes are deterministic for a given input.
3. Review the File List (Optional): Remove any font you don't want, add more files, or reorder them for download convenience. Each glyph, kerning pair, and OpenType feature carries through unchanged — there is nothing else to tune.
4. Convert and Download: Click "Convert" and grab each file individually or as a ZIP for batch jobs. The conversion runs entirely in your browser via opentype.js — your font file never leaves your device, so it is instant and private. No sign-up, no watermark.

Popular TTF Conversions

• TTF to WOFF2 — the smallest web font; Brotli-compressed for the fastest @font-face loads
• TTF to WOFF — the widely supported web font, used as a fallback for very old browsers
• TTF to OTF — re-flavor into the OpenType container for design apps that prefer it
• TTF to EOT — Embedded OpenType, needed only for Internet Explorer 6–11 intranets

Going the other way, WOFF to TTF and OTF to TTF turn web or OpenType files back into an installable desktop TrueType font.

Why Convert a TTF File?

TTF (TrueType Font) is the format Apple developed in the late 1980s and shipped in 1991, with Microsoft adopting it shortly after — it stores glyph outlines as quadratic Bézier curves inside an sfnt table structure. It is the universal desktop font: what you install in Windows, macOS, and Linux for use in Word, Photoshop, and the operating system's own menus. That ubiquity is exactly why most font downloads arrive as TTF, and why you rarely need to leave it for local design work.

The trouble starts when a TTF has to do a job it was not built for. The most common reasons to convert:

• Embedding a font on a website (WOFF2 / WOFF) — A raw TTF has no compression and is not the documented @font-face path. Wrapping the same glyph data in WOFF (zlib) or WOFF2 (Brotli) shrinks the download substantially and matches what src: ... format("woff2") expects in CSS. WOFF2 is the default for new sites; WOFF is the fallback tier for the small slice of legacy traffic.
• Moving into the OpenType superset (OTF) — OTF and TTF are both sfnt-based, but OTF can carry CFF (PostScript) outlines and is the container some foundries and design tools prefer to distribute. Re-flavoring TTF to OTF keeps the font installable on the desktop while matching that workflow.
• Legacy Internet Explorer support (EOT) — Embedded OpenType is the only web font IE 6–8 understood, and IE 9–11 still accept it. It is dead weight on a modern site, but corporate intranets and kiosks locked to old IE sometimes still require an EOT tier in the src chain.
• Self-hosting instead of a font CDN — Converting and hosting your own WOFF2 under your origin removes a third-party DNS lookup and the privacy footprint, and lets you set a long, immutable Cache-Control header — which matters more since browser cache partitioning rolled out in 2020.

Font Format Comparison

WOFF2 lands roughly 24% smaller than WOFF for TrueType-flavored fonts (median 23.94% on the Google Fonts corpus, per the W3C WOFF 2.0 Evaluation Report), which is why current guidance is to ship WOFF2 first and add WOFF only as a fallback.

Which format() Keyword and Media Type Each Target Needs

The font/* media types come from RFC 8081, which registered the font top-level type in 2017 (it also defines font/sfnt and font/collection for .ttc collections). Browsers do not strictly enforce the header for @font-face, but serving the registered type is what CDN, cache, and compression rules key off — and Brotli-compressing an already-Brotli-compressed WOFF2 at the server is wasted work.

Frequently Asked Questions

What is the best format to convert a TTF to for a website?

WOFF2. It wraps the same glyph data in Brotli compression, is a W3C Recommendation, and has ~96% global browser support per caniuse — every browser shipped since 2017 except Internet Explorer and Opera Mini. Declare it first in your CSS and add a WOFF tier only if your analytics still show legacy-browser traffic: src: url("font.woff2") format("woff2"), url("font.woff") format("woff"). The browser picks the first format it understands. For desktop use in design apps, keep the TTF or convert to OTF instead — neither web format installs as a system font.

Will converting a TTF lose any quality, glyphs, or kerning?

No. Every common target here — WOFF, WOFF2, OTF, EOT — preserves the full sfnt table set: the glyf outlines, cmap character map, hmtx/kern spacing, and the OpenType GSUB/GPOS feature tables (ligatures, small caps, kerning). WOFF and WOFF2 are lossless wrappers — the compression is reversed on decode, so the font renders byte-for-byte identical to the source. Variable-font axes (fvar, gvar, STAT) carry through intact as well.

Can I install a converted WOFF or WOFF2 as a system font?

No, and that is by design. The WOFF specifications require decoded font data to stay scoped to the document that loaded it — it cannot be installed system-wide. That is what lets foundries license fonts for web use without users redistributing the underlying outlines. If you need a desktop install, keep the original TTF, or convert a web font back with WOFF to TTF.

What is the difference between TTF and OTF, and should I convert between them?

Both are sfnt-based and both install on the desktop, so for most users they are interchangeable. The technical difference is the outline type: TTF uses quadratic Bézier curves, while OTF usually carries CFF (PostScript) cubic outlines and tends to expose richer OpenType typographic features. Convert TTF to OTF only when a specific design app or foundry workflow expects the OpenType container — there is no rendering benefit on the web, where you should ship WOFF2 regardless of the desktop flavor.

Do I still need WOFF or EOT, or can I ship WOFF2 alone?

For most modern sites, WOFF2 alone is enough — it covers ~96% of global traffic. Add a WOFF fallback only if your audience includes Internet Explorer or other pre-2017 browsers (some enterprise intranets and public-sector kiosks). EOT is needed only for Internet Explorer 6–11 specifically; if you have no IE traffic, skip both extra tiers and serve one WOFF2 file per weight and style.

Does the converter upload my font to a server?

No. TTF conversion here runs entirely in your browser using opentype.js — your font file never leaves your device, there is no account requirement, no watermark, and no file-count cap. In our testing, a 168 KB Roboto Regular TTF converted to a ~53 KB WOFF2 and an ~85 KB WOFF, with both rendering identically to the source in side-by-side checks. Because each format's compression is fully defined by its spec, the output is the same byte-for-byte as any spec-compliant tool would produce.

Should I convert every weight and style, or just the regular?

Convert every weight and style you actually use in CSS. Each @font-face block targets one font-weight/font-style combination, and the browser does not synthesize real bold or italic from the regular cut (synthetic versions look noticeably worse). A typical body family needs at least Regular 400, Italic 400, Bold 700, and Bold Italic 700 — four files. A variable font collapses that back to a single file at the cost of a slightly larger initial download.

My converted WOFF2 is still large — how do I shrink it further?

Subset it. This converter re-wraps the whole font, so a WOFF2 built from a full Unicode TTF still carries every glyph the family ships with — Cyrillic, Greek, Vietnamese, and in some families CJK ranges you will never render on an English-language site. Subsetting strips the glyphs you don't use before compression, and it is a separate step from format conversion: pyftsubset (part of the fonttools package) and glyphhanger are the usual tools, and font services do the same thing behind the scenes when they hand you unicode-range-split files. Convert first, subset second, then pair the result with font-display: swap and a <link rel="preload"> for the one or two cuts that render above the fold.