FLAC Content Provenance
Sign, embed, and verify C2PA manifests in FLAC files (.flac)
What Is FLAC Provenance?
Free Lossless Audio Codec for archival-quality audio. FLAC provenance protects lossless music masters and high-fidelity audio archives.
With Encypher, FLAC 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 FLAC file for free, without authentication.
How C2PA Manifests Are Embedded in FLAC Files
- MIME Type
- audio/flac
- File Extensions
- .flac
- Embedding Method
- Custom JUMBF/COSE structural embedding (c2pa-python does not yet natively support FLAC)
- 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 FLAC files, the manifest is stored using custom jumbf/cose structural embedding (c2pa-python does not yet natively support flac). The signing process does not alter the audio content itself. The manifest is metadata, not a modification of the audio samples.
Use Cases for FLAC Provenance
- Lossless music distribution
- Archival audio
- Hi-fi streaming (Tidal, Qobuz)
- Music production masters
How to Sign FLAC Content with Encypher
FLAC signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your FLAC 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.flac" \ -F "title=My FLAC Content" \ -F "action=c2pa.created" \ -o signed.flac
Verify FLAC Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed FLAC file to confirm its origin, check for tampering, and read the embedded rights information.