Open the extension and choose the local file workflow.
Step-by-step tutorial
How to verify Content Credentials in an image
Check whether a JPG or PNG contains C2PA evidence, whether the image still matches its signed manifest and how its certificate chain is evaluated.
Use the original file when possible. Screenshots, downloads and social platforms may remove or change embedded credentials.
Verify locally
Four steps from image to report
The normal workflow takes less than a minute, while the full report supports deeper review.
Choose a supported JPG or PNG file.
Note the status and any validation warning.
Open the manifest, signature and certificate details.
Interpret the result
Four statuses, four different next steps
The most useful response depends on the exact validation outcome.
Confirm the recognized signer and inspect actions relevant to your use case.
The signature can be valid even when the chain is not recognized publicly.
Review failed checks before drawing a conclusion about alteration.
Look for another source or supporting evidence; do not label the image fake.
Troubleshooting
When the expected credential is missing
Distribution workflows often change or strip embedded provenance data.
Check the file path
- Download the original asset again
- Avoid screenshots and clipboard copies
- Compare the source and published versions
Check delivery behavior
- Review CMS or DAM transformations
- Look for recompression or format conversion
- Test whether the platform preserves credentials
Interpretation boundary
A credential can document provenance, not reality itself
Verification can show signed origin and declared edits. It cannot independently prove that a depicted scene occurred, that all declarations are accurate or that unsigned content is deceptive.