Free C2PA Viewer & Content Credentials Checker
Inspect content provenance, recorded actions, and digital signatures directly in your browser. Your files stay on your device.
Drop a file here
or choose a file
Your media file is inspected locally and is not uploaded for inspection.
What you'll see
Content Credentials
Whether the file carries a C2PA Content Credential, and whether its manifest is bound to this exact file.
Provenance
Recorded actions and ingredient references straight from the manifest — never inferred from file names or heuristics.
Signature
Cryptographic verification state plus signer and issuer information when the credential provides them.
How it works
- 1
Drop a file
Choose an image, video, audio file, or PDF to inspect.
- 2
Inspect locally
The C2PA engine runs in your browser via WebAssembly — nothing is uploaded.
- 3
Read the evidence
See the verification state, provenance timeline, ingredients, and raw manifest data.
Choose your inspection view
C2PA Manifest Viewer
Inspect the manifest store, claim, assertions, ingredients and raw JSON.
Open Manifest Viewer →C2PA Metadata Inspector
Read signer, source disclosure, counts, identifiers and checksum in a structured table.
Inspect metadata →C2PA URL Checker
Inspect remote image, video, audio, or PDF provenance directly from a public URL.
Check a URL →C2PA PDF Checker
Check Content Credentials in PDF files and review signature and validation evidence.
Check a PDF →C2PA Standard
Understand manifests, trust anchors, verification, conformance and versioning.
Read the reference →Core C2PA guides
What C2PA can and cannot tell you
A credential can show
- A signed provenance record bound to the file
- Declared actions such as edits or creations
- Declared use of generative AI, when stated
- Ingredients the producer chose to record
It cannot prove
- That every claim in the manifest is true
- That unrecorded edits never happened
- That a file without credentials is AI-generated
- The overall authenticity of content
Frequently asked questions
What is C2PA?
C2PA (Coalition for Content Provenance and Authenticity) defines an open technical standard for attaching cryptographically signed provenance data to media files. See our guide to C2PA.
What are Content Credentials?
Content Credentials are the user-facing expression of C2PA provenance data: recorded actions, ingredients, and signer information embedded in a file.
Does C2PA prove that a file is authentic?
No. A verified signature proves the manifest is intact and bound to the file. It does not prove every recorded claim is true, and it cannot detect unrecorded edits.
What does it mean when no C2PA data is found?
It only means no C2PA provenance record was detected — many genuine files simply have none. It does not mean the file is fake, edited, or AI-generated. For result boundaries, read How to check C2PA.
Does C2PA Lab upload my files?
No. Inspection runs entirely in your browser using WebAssembly. File contents never leave your device, and analytics records only non-sensitive inspection metadata such as a coarse file class or result status.
Which file types are supported?
JPEG, PNG, WebP, AVIF, HEIC/HEIF, SVG, MP4, MOV, MP3, WAV, and PDF files up to 200 MB are supported after format-specific validation in modern browsers.