TTF Content Provenance
Sign, embed, and verify C2PA manifests in TTF files (.ttf)
What Is TTF Provenance?
TrueType Font format widely used in operating systems and applications. TTF provenance protects font assets across platforms.
With Encypher, TTF files carry their own cryptographic proof of origin. A C2PA manifest is embedded directly into the file, recording who created it, when, and whether it has been modified. Anyone can verify a signed TTF file for free, without authentication.
How C2PA Manifests Are Embedded in TTF Files
- MIME Type
- font/ttf
- File Extensions
- .ttf
- Embedding Method
- Custom JUMBF/COSE structural embedding in TrueType font tables
- Container Type
- Custom JUMBF/COSE
- Verification Pipeline
- Custom JUMBF/COSE structural verification (Encypher implementation)
The C2PA manifest contains a JUMBF (JPEG Universal Metadata Box Format) store with COSE-signed claims. For TTF files, the manifest is stored using custom jumbf/cose structural embedding in truetype font tables. The signing process does not alter the font content itself. The manifest is metadata, not a modification of the content.
Use Cases for TTF Provenance
- System fonts
- Web fonts
- Application fonts
- Font distribution
How to Sign TTF Content with Encypher
TTF signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your TTF file, and the API returns a signed copy with an embedded C2PA manifest.
curl -X POST https://api.encypher.com/api/v1/sign/media \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "file=@example.ttf" \ -F "title=My TTF Content" \ -F "action=c2pa.created" \ -o signed.ttf
Verify TTF Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed TTF file to confirm its origin, check for tampering, and read the embedded rights information.