Local C2PA verification

Verify Content Credentials without uploading your files

Inspect C2PA manifests, signatures, declared actions and certificate-chain status in Chrome, then open or export the technical report.

Verification evaluates provenance and integrity evidence. It does not decide whether content is true, false or AI-generated.

How it works

From media to an explainable result

ProvSeal keeps the headline status connected to the evidence behind it.

01Choose

Select a local file or start a page scan.

02Parse

Read the available C2PA manifest and assertions.

03Validate

Check integrity, signature and certificate chain.

04Explain

Show the result with report details and limits.

Four outcomes

Read the badge, then read the context

A status summarizes validation; it is not a verdict about the subject of the media.

TrustedValid and recognized

The credential validates and its certificate chain is recognized by the active trust policy.

Signed but untrustedValid signature, limited trust

Signed evidence exists, but public trust is not established in the active context.

InvalidValidation failed

C2PA evidence exists, but integrity, signature or another validation check failed.

No credentialsNo C2PA evidence found

This means provenance is unknown to the verifier, not that the content is fake.

Inside the report

Evidence you can inspect

Move from a simple badge to the technical layers needed for editorial, compliance or security review.

Manifest and actions

  • Claim and assertion data
  • Declared edits and processing actions
  • Ingredients and provenance relationships

Integrity and signer context

  • Asset-to-manifest validation
  • Signature result
  • Certificate chain and trust status
Responsible interpretation

Evidence is not truth detection

A valid Content Credential can document origin and declared history; it cannot guarantee that every claim inside the media is factual. Missing credentials are equally not proof of deception.