HEIC Sequence Content Provenance
Sign, embed, and verify C2PA manifests in HEIC Sequence files (.heics)
What Is HEIC Sequence Provenance?
HEIC image sequence format for burst photos and animations. Provenance covers multi-frame image sequences from Apple devices.
With Encypher, HEIC 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 HEIC Sequence file for free, without authentication.
How C2PA Manifests Are Embedded in HEIC Sequence Files
- MIME Type
- image/heic-sequence
- File Extensions
- .heics
- 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 HEIC 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 HEIC Sequence Provenance
- Burst photography
- Live photos
- Image sequences
- Animated captures
How to Sign HEIC Sequence Content with Encypher
HEIC Sequence signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your HEIC 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.heics" \ -F "title=My HEIC Sequence Content" \ -F "action=c2pa.created" \ -o signed.heics
Verify HEIC Sequence Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed HEIC Sequence file to confirm its origin, check for tampering, and read the embedded rights information.