AVI Content Provenance
Sign, embed, and verify C2PA manifests in AVI files (.avi)
What Is AVI Provenance?
Microsoft Audio Video Interleave format. AVI provenance covers legacy video content and Windows ecosystem video.
With Encypher, AVI 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 AVI file for free, without authentication.
How C2PA Manifests Are Embedded in AVI Files
- MIME Type
- video/x-msvideo
- File Extensions
- .avi
- Embedding Method
- JUMBF data stored in a RIFF chunk within the AVI 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 AVI files, the manifest is stored using jumbf data stored in a riff chunk within the avi container. The signing process does not alter the video content itself. The manifest is metadata, not a modification of the video frames.
Use Cases for AVI Provenance
- Legacy video archives
- Windows ecosystem
- Surveillance footage
- Industrial video
How to Sign AVI Content with Encypher
AVI signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your AVI 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.avi" \ -F "title=My AVI Content" \ -F "action=c2pa.created" \ -o signed.avi
Verify AVI Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed AVI file to confirm its origin, check for tampering, and read the embedded rights information.