AAC Content Provenance
Sign, embed, and verify C2PA manifests in AAC files (.aac)
What Is AAC Provenance?
Advanced Audio Coding, successor to MP3 with better quality at similar bitrates. AAC provenance covers streaming audio and mobile content.
With Encypher, AAC 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 AAC file for free, without authentication.
How C2PA Manifests Are Embedded in AAC Files
- MIME Type
- audio/aac
- File Extensions
- .aac
- Embedding Method
- JUMBF data stored in an ISO BMFF uuid box (AAC in MP4/M4A container)
- Container Type
- ISO BMFF uuid box
- Verification Pipeline
- c2pa-python (native C2PA library support)
The C2PA manifest contains a JUMBF (JPEG Universal Metadata Box Format) store with COSE-signed claims. For AAC files, the manifest is stored using jumbf data stored in an iso bmff uuid box (aac in mp4/m4a container). The signing process does not alter the audio content itself. The manifest is metadata, not a modification of the audio samples.
Use Cases for AAC Provenance
- Streaming platforms
- Mobile audio
- Broadcasting
- Video soundtracks
How to Sign AAC Content with Encypher
AAC signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your AAC 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.aac" \ -F "title=My AAC Content" \ -F "action=c2pa.created" \ -o signed.aac
Verify AAC Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed AAC file to confirm its origin, check for tampering, and read the embedded rights information.