MOV Content Provenance
Sign, embed, and verify C2PA manifests in MOV files (.mov)
What Is MOV Provenance?
Apple QuickTime container format used in professional video production. MOV provenance protects production masters and editorial video.
With Encypher, MOV 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 MOV file for free, without authentication.
How C2PA Manifests Are Embedded in MOV Files
- MIME Type
- video/quicktime
- File Extensions
- .mov
- Embedding Method
- JUMBF data stored in a QuickTime uuid atom within the MOV container
- Container Type
- ISO BMFF uuid box (QuickTime)
- 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 MOV files, the manifest is stored using jumbf data stored in a quicktime uuid atom within the mov 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 MOV Provenance
- Professional video production
- Film and television
- Apple ecosystem video
- Video editing workflows
How to Sign MOV Content with Encypher
MOV signing is available at the Enterprise tier through the unified /sign/media API endpoint. Upload your MOV 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.mov" \ -F "title=My MOV Content" \ -F "action=c2pa.created" \ -o signed.mov
Verify MOV Provenance (Free)
Verification is free and requires no authentication. Any third party can verify a signed MOV file to confirm its origin, check for tampering, and read the embedded rights information.