What does the content provenance verifier produce?
Check embedded C2PA signatures and original file bindings in your browser. Retain complete manifests, selected trust decisions and unresolved findings.
Select exact original media and explicitly approved local trust anchors. Freeze the scope before authorizing local signature checks. Originals stay in this browser.
What do you need before you start?
- Keep exact original PNG, JPEG or WebP files. Modified or re-encoded copies can change the original binding.
- Select up to 20 files totaling 25,000,000 bytes. Select a responsible reviewer and a review scope.
- Choose no trust anchors, or supply explicitly approved inline CA certificates. Review every unsupported or unresolved result.
What information do you enter?
Select exact original media and explicitly approved local trust anchors. Freeze the scope before authorizing local signature checks. Originals stay in this browser.
- Original PNG, JPEG or WebP media bytes and computed SHA-256 identities.
- Review scope, responsible reviewer, and an explicit local execution authorization.
- Frozen your CA trust anchors, their label, and exact PEM digest.
What you can download
Every result must identify its supplied facts, assumptions and unresolved items.
| Free result | Included downloads |
|---|---|
Enter your information, inspect the on-screen result and keep a browser backup. Editing and direct copies of your entered information stay free. |
These supported outputs are free. No checkout is required. |
Fictional provenance report (PDF). Editable report (DOCX). Complete fictional source pack (ZIP). Requires tailoring. Samples use the finalized output renderer and contain only fictional cryptographic fixtures.
How does the content provenance verifier work?
- 1Select exact originals
Freeze the file names, byte counts, hashes, scope and selected trust policy.
- 2Authorize local verification
Run the pinned SDK inside a bounded browser worker. Inspect each complete result and unresolved finding.
- 3Retain and export
Save local recovery copies. Prepare completed output, review its price, and authorize payment before a finalized export.
Method and sources
Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.
- Content Credentials technical specification, version 2.4Separate signature validation, original asset binding, and trust-anchor decisions. Trust model and manifest validation.Coalition for Content Provenance and Authenticity. Reviewed 2026-10-09.
- C2PA browser SDKThe pinned browser SDK reads and validates embedded manifests from original media bytes. Reading C2PA manifests.Content Authenticity Initiative. Reviewed 2026-10-09.
Common questions
What information does the content provenance verifier need?
Enter original PNG, JPEG or WebP media bytes and computed SHA-256 identities; review scope, responsible reviewer, and an explicit local execution authorization; frozen your CA trust anchors, their label, and exact PEM digest. Keep exact original PNG, JPEG or WebP files. Modified or re-encoded copies can change the original binding.
Who makes the final decision?
A responsible person reviews the result. Signature validation does not prove that a claim or depicted event is true.
Is this tool free?
Yes. The on-screen result and listed downloads are free. No checkout is required. Keep local backups and review the stated method and limits.
Can I use the content provenance verifier for this task?
Check available provenance records without claiming they prove truth. Signature validation does not prove that a claim or depicted event is true.
What still needs review?
Signature validation does not prove that a claim or depicted event is true.
Trust applies only to the selected local CA anchors. Public trust, signer identity, current revocation clearance and legal admissibility remain unestablished.
Remote manifests, resources, OCSP, thumbnails and trust lists are blocked. A missing or incomplete manifest stays unresolved.
A restored record preserves copied observations. It does not repeat verification or restore execution consent or paid access.