Tool
Content Credentials checker
Content Credentials are the consumer name for C2PA provenance, and the term most people meet in an Adobe app or on a file someone sent them. This checker reports whether a supported credential container is present, so you can decide before you publish.
How to use it
- 1Add the exported image you received or created.
- 2Check the report for a Content Credentials or C2PA indicator.
- 3If you want it gone, clean the image to rebuild the container.
- 4Scan again to verify, then download.
Credentials you can and cannot see
Some files embed full credentials, others carry a soft binding or a link. MetaRase reports supported embedded indicators; it does not resolve remote credential records or validate signatures cryptographically.
Why it matters for publishing
A signed file can trigger a provenance label on social platforms. Knowing whether the mark exists before you post helps you avoid surprises, and lets you keep the signed original if you need it.
What a credential can contain
The record is structured, and its fields depend on the tool that wrote it.
- The application used and its version.
- A history of edits or generative actions.
- A statement about whether AI was involved.
- A claim signer for verification, where a certificate was used.
Where credentials live by format
The container is format-specific.
| Format | Credential location | Notes |
|---|---|---|
| JPEG | APP11 (C2PA/JUMBF) | Common for Adobe and editor exports. |
| PNG | caBX chunk | Used by many publishing tools. |
| WebP | C2PA chunk | Compact and widely supported. |
| AVIF / HEIC | ISO-BMFF C2PA box | Newer formats and phone captures. |
Removing or just checking
You can check the file without removing anything. Cleaning clears the embedded credential container along with other supported metadata. For JPEG, PNG and WebP, lossless mode strips it while keeping the compressed image data unchanged; rebuilding re-encodes the image and may change pixel values. Either way, the exported file is scanned again for supported indicators. For a format-level view of where the container sits, the C2PA checker page works from the standard's own terminology.
Frequently asked questions
Does every Content Credentials file look the same?
No. Credentials vary by tool and version, and some are only partially embedded. MetaRase flags supported container indicators it can detect.
Will removing credentials break the image?
No. Lossless mode keeps the compressed image data unchanged for JPEG, PNG and WebP; rebuilding re-encodes the image into the output format you choose. Either way the result is a normal image file.
Can I prove an image was AI-generated later?
If you remove the credentials, that embedded proof is gone. Keep an original copy if you need the provenance record.
Is checking private?
Yes. The scan runs locally in your browser and the file is not uploaded.
Do credentials prove an image is authentic?
They record claims about a file's history. Whether that is sufficient for your purpose depends on the signer and the platform.
Can I check a video or PDF?
MetaRase focuses on the image formats it can decode in the browser, mainly JPEG, PNG, WebP, and AVIF.
Sources
Inspect, clean, and verify in your browser
Your image bytes never leave your device. MetaRase rebuilds the image locally, then scans the output again before you download it.
Open the cleanerRelated pages
Results describe supported embedded indicators only and cannot guarantee how a platform will classify an image.