WAV Content Provenance
Sign, embed, and verify C2PA manifests in WAV files (.wav)
What Is WAV Provenance?
Uncompressed audio format used in professional music production and broadcasting. WAV provenance protects master recordings and broadcast audio.
With Encypher, WAV 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 WAV file for free, without authentication.
How C2PA Manifests Are Embedded in WAV Files
- MIME Type
- audio/wav
- File Extensions
- .wav
- Embedding Method
- JUMBF data stored in a RIFF chunk within the WAV container
- Container Type
- RIFF chunk
- 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 WAV files, the manifest is stored using jumbf data stored in a riff chunk within the wav 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 WAV Provenance
- Music production
- Broadcast audio
- Podcast masters
- Sound effects libraries
- Forensic audio
How to Sign WAV Content with Encypher
WAV signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your WAV 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.wav" \ -F "title=My WAV Content" \ -F "action=c2pa.created" \ -o signed.wav
Verify WAV Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed WAV file to confirm its origin, check for tampering, and read the embedded rights information.