Novus Convert
Convert files
Font format

TTC converter

A .ttc file is a TrueType Collection: several TrueType or OpenType faces stored behind one collection header, with identical tables allowed to share the same bytes. A family can therefore package regular, bold and related scripts more compactly than separate font files.

Private for supported formats — processed in your browser

Convert supported files

Runs on your device

Drop TTC files here

Batch files can each use a different output. Nothing uploads for local conversions.

Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.

Where TTC comes from

Apple introduced TrueType Collections with QuickDraw GX in the 1990s, and Microsoft adopted the container for Windows' large East Asian font families where sharing common glyph tables saved meaningful disk space. The same sfnt collection structure later gained the name OpenType Collection (.otc) when faces used CFF outlines, while .ttc remained the familiar extension for TrueType-flavoured collections.

How TTC works

  • The file begins with `ttcf`, a version number and an array of offsets to ordinary sfnt face directories.
  • Table offsets are absolute from the start of the collection, which lets two faces point to one cmap, glyf or name table without copying it.
  • Version 2 collections may carry a DSIG signature; safely extracting faces changes offsets and invalidates that signature, so signed collections are rejected rather than silently altered.
  • Each extracted face must rebuild its table offsets, per-table checksums and the head table's global checksum adjustment.
  • A collection may mix TrueType glyf faces and OpenType CFF faces; the standalone extension follows the face's actual outline tables.

When to use TTC

  • Splitting a system font collection into installable individual faces
  • Recovering one family member for a design or document workflow
  • Inspecting which fonts are bundled into a Windows or macOS collection
  • Packaging extracted faces as one ZIP without uploading licensed font data

Strengths and limitations

Strengths

  • Shared tables can save substantial space across related faces
  • Every face retains the mature TrueType/OpenType table model
  • One container keeps a coordinated multilingual family together

Limitations

  • Many web and design tools accept TTF/OTF but not a collection
  • Extraction must rebuild checksums and cannot preserve a collection signature
  • Licensing still applies to every extracted face; a technical conversion grants no new rights

Compatibility

Windows, macOS, FreeType, FontForge and modern Adobe applications read .ttc collections, but browsers do not treat an arbitrary collection as a dependable @font-face source. Novus Convert parses unsigned TTC v1/v2 files locally, verifies every table, reconstructs checksum-correct TTF or OTF faces and packages them in a deterministic ZIP. The original collection never leaves the device.

Each face's name, OS/2, layout, variation and license tables are copied byte-for-byte. Collection-level DSIG signatures are not transferable to standalone faces and therefore cause an explicit refusal rather than being discarded.

Convert TTC to another format