EraseAILabelHome / Checker vs Content Credentials Verify
Our Checker vs Content Credentials Verify: Which Do You Need?
They answer different questions. Our checker tells you what kinds of metadata a file holds. Content Credentials Verify reads a signed Content Credentials record in detail and checks that it's valid.
Published by Harsh Raj · Last reviewed November 2026
At a glance
| EraseAILabel checker | Content Credentials Verify | |
|---|---|---|
| Main question | What does this file hold? | What does its Content Credentials record say, and is it valid? |
| Location and camera details | Yes, with a local map | Not its purpose |
| Content Credentials | Detects that they're present | Shows the full history and validates the signature |
| AI source tags and prompts | Yes | Only if part of the signed record |
| Where it runs | In your browser, on your device | A website run by the Content Authenticity Initiative |
What our checker does
The checker reads the structure of an image and names each kind of record it finds, such as EXIF, GPS location, XMP, IPTC, Content Credentials, AI source tags, and AI prompts saved in PNG text. It's useful as a quick privacy check before sharing, and as a first step when a platform has labeled a photo. It doesn't validate signatures, and it isn't an AI detector.
What Content Credentials Verify does
Content Credentials Verify is built for one kind of record: the signed C2PA manifest. It shows who signed the record, which tools were used, and what edits are recorded, and it tells you whether the signature holds up. When the question is "can I trust what this record claims?", it's the right tool.
Use them together
- Scan the file with our checker to see everything it holds, including location.
- If it shows Content Credentials, open the file in Content Credentials Verify to read the full record.
- Decide what to do, keeping in mind that a valid record shows what a tool declared, not whether an image is truthful.
What neither can tell you
Neither tool can prove an image is real. A file with no record may simply have lost it when it was re-saved. Neither reads invisible watermarks such as SynthID, which need their own checks. See how watermarks differ from metadata.
A typical workflow
Say a client sends you a product photo exported from Lightroom, and you want to know where it's been. Scan it with our checker first. You might see camera details, a location, XMP data, and Content Credentials. The location tells you something the client may not have meant to share. The Content Credentials tell you there's a signed record to read, so open the file in Content Credentials Verify to see which app signed it, and which edits it lists.
Which to use when
- Before sharing your own photo: our checker, for location and device details.
- When a platform labels your image: our checker first, to see whether a record exists, then Verify to read it.
- When judging someone else's image: Verify, if it has Content Credentials, plus your own judgment about the source.
A tech enthusiast who builds and tests EraseAILabel's tools. How we test
Common questions
Can the EraseAILabel checker validate Content Credentials?
No. It detects that they are present. Use Content Credentials Verify to read and validate the record.
Does a valid Content Credentials record prove an image is real?
No. It shows what the signing tool declared about how the image was made and edited.
Can either tool detect SynthID?
No. Invisible watermarks need their own detection tools, such as the checks Google offers in the Gemini app.
Which should I use first?
Start with our checker to see everything a file holds. If it shows Content Credentials, open the file in Content Credentials Verify to read the full record.
See what your file holds
Read it on your own device. Nothing is uploaded.