AVIF Content Provenance
Sign, embed, and verify C2PA manifests in AVIF files (.avif)
What Is AVIF Provenance?
Next-generation image format based on AV1 video codec, offering superior compression and quality. AVIF provenance covers the emerging standard for web images.
With Encypher, AVIF 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 AVIF file for free, without authentication.
How C2PA Manifests Are Embedded in AVIF Files
- MIME Type
- image/avif
- File Extensions
- .avif
- Embedding Method
- JUMBF box in ISO BMFF container (AVIF uses HEIF container)
- Container Type
- JUMBF (ISO BMFF)
- 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 AVIF files, the manifest is stored using jumbf box in iso bmff container (avif uses heif container). The signing process does not alter the image content itself. The manifest is metadata, not a modification of the pixels.
Use Cases for AVIF Provenance
- Next-gen web images
- High-quality web delivery
- Progressive web apps
- Image-heavy platforms
How to Sign AVIF Content with Encypher
AVIF signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your AVIF 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.avif" \ -F "title=My AVIF Content" \ -F "action=c2pa.created" \ -o signed.avif
Verify AVIF Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed AVIF file to confirm its origin, check for tampering, and read the embedded rights information.