HEIF Sequence Content Provenance
What Is HEIF Sequence Provenance?
HEIF image sequence format for multi-frame content. Provenance covers animated and sequential image content.
With Encypher, HEIF Sequence 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 HEIF Sequence file for free, without authentication.
How C2PA Manifests Are Embedded in HEIF Sequence Files
- MIME Type
- image/heif-sequence
- File Extensions
- .heifs
- Embedding Method
- JUMBF box in ISO BMFF/HEIF sequence 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 HEIF Sequence files, the manifest is stored using jumbf box in iso bmff/heif sequence container. The signing process does not alter the image content itself. The manifest is metadata, not a modification of the pixels.
Use Cases for HEIF Sequence Provenance
- Image sequences
- Animated content
- Multi-frame captures
How to Sign HEIF Sequence Content with Encypher
HEIF Sequence signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your HEIF Sequence 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.heifs" \ -F "title=My HEIF Sequence Content" \ -F "action=c2pa.created" \ -o signed.heifs