Inspect Provenance.
Verify The Record.
Upload media to inspect its file fingerprint, search for embedded C2PA / JUMBF markers, review Content Credentials data, and run full cryptographic verification through a configured C2PA backend or the official Verify service.
Drop Media.
Check Credentials.
Load an image, video, audio file, or PDF. The page performs a local metadata preflight and can submit the asset to your secure C2PA verification service.
Credential
Status.
Upload a file to begin Content Credentials inspection.
No report loaded.
Provenance Is Context.
Not A Truth Detector.
Content Credentials can show where media came from, which tools handled it, and whether signed provenance data validates. They do not automatically prove that every visible or audible claim is true.
Manifest
A Content Credential can contain signed claims, assertions, ingredients, actions, timestamps, and creator information.
Hard Binding
Cryptographic bindings help determine whether the active manifest still matches the asset bytes being checked.
Trust
A valid signature and a trusted signer are related but separate questions. Trust depends on the verifier’s trust policy and lists.
No Credential
An absent credential does not prove media is fake. Metadata may never have existed or may have been removed during export or sharing.
Inspect The Record.
Keep The Context.
Use local preflight for fast inspection, then confirm important files with a current C2PA SDK or the official Content Credentials Verify service.