Local Provenance Inspection & Binary Markers
Adobe CAI & Content Credentials Marker Detector
Quickly scan image file containers for embedded Adobe CAI and C2PA Content Credentials markers. Triage whether photos carry provenance envelopes directly in your browser — private and client-side with zero server uploads.
Drag and drop an image to check markers
Reads container structure directly in browser memory. Supports JPEG, PNG, and WebP up to 20 MB.
Binary Envelope Architecture
How C2PA Markers Are Embedded in Media Files
Standard image formats enclose Content Credentials within dedicated binary marker segments:
APP11 Segment (0xFFEB)
Standard JPEG files store C2PA envelopes inside APP11 application marker segments without interfering with standard photo viewers.
caBX Ancillary Chunk
PNG containers house provenance data in a specialized 'caBX' chunk, safe from standard graphics rasterization pipelines.
JUMBF FourCC Box
WebP files embed a RIFF chunk containing the Universal Media Box (JUMBF) data superbox holding signed provenance manifests.
Embedded Manifest Pointer
Points to either an embedded manifest store or provides an external URI reference to cloud-hosted provenance ledgers.
The 3-Tier Authenticity Verification Hierarchy
Understanding where container marker detection fits in the broader forensic workflow:
Binary Envelope Scan
Scans container bytes in under 15ms. Tells you immediately whether C2PA credentials exist or were stripped by web compression.
Cryptographic Binding
Unpacks the manifest, checks X.509 certificates, and hashes pixel arrays to ensure no pixel was altered since signing.
Multi-Modal AI Scan
When markers are stripped by social media, neural vision models inspect micro-textures, lighting physics, and compression artifacts.
Marker detection is only the first step
| Verification Step | This Tool (Marker Triage) | Full C2PA Validator |
|---|---|---|
| Find supported embedded marker | Yes | Yes |
| Parse manifest assertions (Origin, Edits) | No | Yes |
| Validate digital signature & pixel hash binding | No | Yes |
| Evaluate certificate authority trust chain | No | Yes (against trust policy) |
| Determine if real-world event is factual | No | No |
Frequently Asked Questions
What is an Adobe CAI / C2PA container marker?
A C2PA container marker is a standardized binary header identifier (such as the 0xFFEB APP11 segment in JPEG or the caBX chunk in PNG) indicating that an image carries embedded Content Authenticity Initiative (CAI) provenance metadata. It acts as an envelope flag signaling to parsers that verifiable credentials exist within the file.
Why is a marker check faster than full cryptographic validation?
Full cryptographic validation requires unpacking the complete JUMBF superbox, reading binary assertions, parsing X.509 certificate chains, and recalculating SHA-256 hashes across raw uncompressed pixel bitmaps. In contrast, this marker checker scans only initial file bytes in milliseconds to confirm whether a provenance envelope exists.
Does a detected marker guarantee the image is authentic?
No. Finding a marker indicates only that a provenance package is present. It does not verify whether the cryptographic signature is valid, whether the signing certificate is trusted, or whether the image depicts genuine real-world events. A complete cryptographic audit is needed to verify signer identity.
Why do most genuine photos lack C2PA markers?
Currently, only a few specialized cameras (such as the Leica M11-P and select Sony Alpha models) include in-camera hardware signing chips. Furthermore, social platforms (X/Twitter, Instagram, WhatsApp) automatically strip all container markers during upload compression.