Skip to content

FreeNo account, up to 25 MB

C2PA Content Credentials Checker

Check whether an image carries C2PA Content Credentials, the provenance standard behind DALL·E, Adobe Firefly and a growing list of cameras.

  • Deleted right after analysis
  • Original never modified
  • No sign-up
Drop an image here
or click to browse (up to 25 MB)
FormatsJPEGPNGWebPHEICTIFFGIF

Your original file is never modified. Every action produces a new image.

What are C2PA Content Credentials?

C2PA (Coalition for Content Provenance and Authenticity) is an open standard for recording where an image comes from. Adobe sells it to the public as Content Credentials, and the two names describe the same thing.

Tools that support it embed a manifest inside the file, stored as a JUMBF block. That manifest declares three things: the capture device or generator, the editing steps applied, and whether generative AI had a hand in it.

What does this C2PA checker show?

Pixvisor scans the file at the byte level for C2PA containers (JUMBF / caBX boxes) and C2PA-related XMP tags. It reads the rest of the metadata at the same time: IPTC digitalSourceType, generation parameters and software tags.

If credentials are there, you see which signals turned up and what the surrounding metadata declares about where the image came from.

Does it verify the C2PA signature?

No. This is a presence check, not a cryptographic verification. Pixvisor does not validate the manifest’s signature chain. For that, use an official C2PA verifier.

A missing manifest proves nothing either. Social platforms and screenshots strip metadata as a matter of course.

To see everything else a file holds, open the EXIF viewer. For broader AI fingerprints, try the AI image checker.

Which files can carry Content Credentials?

A manifest lives nowhere near EXIF or XMP. It has its own home, which is why most metadata viewers walk straight past it.

  • In a JPEG, it sits in the APP11 segment.
  • In a PNG, it sits in a chunk named caBX.

Both are packaged as JUMBF, a container format for embedding structured boxes inside an image. Those are the two places this checker reads at the byte level, which is how it finds a manifest that never shows up in a normal EXIF listing.

So a manifest travels less well than people expect. Copying EXIF from one file to another leaves it behind. Converting to a format the tool does not support drops it.

A screenshot removes it outright, because a screenshot is a new image with no relationship to the original file.

What a manifest proves, and what it does not

A valid manifest proves two things: the holder of a particular key signed a particular state of this file, and the pixels have not changed since. That is genuinely useful, and narrower than most people read it as.

It says nothing about whether the photograph is honest. A camera will happily sign a staged scene, a misleading crop, or a picture of a screen showing another image.

The reverse error is more common still. No manifest proves nothing at all. Most images online carry none, because most software never writes one.

Reading that absence as evidence of AI, or of a fake, gets the logic backwards. We explain both halves in what C2PA is.

Frequently asked questions

What are Content Credentials?
Content Credentials are the consumer-facing name of C2PA, an open provenance standard. Tools that support it embed a signed manifest in the file describing how the image was created and edited, including whether generative AI was involved.
Which tools add C2PA metadata?
A growing list: OpenAI's DALL·E images, Adobe Photoshop and Firefly, some Leica cameras, and other editors and generators joining the C2PA coalition. Many images on the web still carry none at all.
Does this checker verify the C2PA signature?
No. It detects whether C2PA / Content Credentials data is present and shows what it declares. It does not cryptographically validate the signature chain; for that, use an official verifier such as the Content Credentials Verify site.
Can C2PA data be removed?
Yes. C2PA lives in the metadata layer, so stripping metadata removes it, which is exactly why provenance can never be assumed just because it's absent. You can remove it from your own images with the remove EXIF tool.