What does the Verification section tell me?

It shows one of three badges from the c2pa library: valid with a trusted signer, signature valid but signer not on the trust list, or invalid because the signature or hashes failed. It also reports whether a signature is present and the algorithm used.

Why do some fields say Not specified?

The viewer prints a field only when the manifest contains it. A manifest can leave out a title or a claim generator, and the viewer then shows Not specified rather than guessing a value.

Can this tell me whether an image was made with AI?

Not directly. It does not analyze the pixels. If the creating tool recorded how the image was made, that appears in the assertions, and you can read it there; a file with no manifest says nothing either way.

What are assertions and history in the output?

Assertions are the statements the signer attached to the manifest, such as recorded actions or creation details. History lists the manifest's ingredients, the earlier assets it was built from. Both are shown exactly as stored.

C2PA / Content Credentials Viewer

Inspect the full technical C2PA manifest embedded in an image.

Loading…

About C2PA / Content Credentials Viewer

When a short summary is not enough, this viewer shows what an image's C2PA manifest actually contains. The server reads the active manifest, runs the c2pa library's signature and hash check, and lays out the signing algorithm, issuer name and certificate serial, then the manifest label, format, claim generator and title. Assertions and ingredient history follow as raw JSON. Nothing is inferred or filled in: fields the manifest lacks read Not specified.

Features

Verification block with the c2pa library's validation result and signing algorithm
Issuer name and certificate serial number
Manifest label, format, claim generator and title
Raw assertions and ingredient history shown as JSON
Missing fields shown as Not specified instead of guessed

Limitations

It displays what the file's active manifest says and does not judge whether the picture itself is true or unaltered.
A valid signature from an unrecognized signer proves little about who made the image.
Assertions and history appear as raw JSON, with no plain-language interpretation.
JPG, PNG and WebP files up to 60 MB are accepted, and the upload goes to our server to be read.

How it works

Drop an image that may carry Content Credentials onto the upload area, or browse for it.
Select Inspect manifest.
Read the Verification section: the validation badge, whether a signature is present and which algorithm signed it.
Check the Issuer and Manifest sections for the certificate details, label, format, claim generator and title.
Scroll through the Assertions, History and Technical Details blocks to see the recorded JSON.

Frequently asked questions

: It shows one of three badges from the c2pa library: valid with a trusted signer, signature valid but signer not on the trust list, or invalid because the signature or hashes failed. It also reports whether a signature is present and the algorithm used.
: The viewer prints a field only when the manifest contains it. A manifest can leave out a title or a claim generator, and the viewer then shows Not specified rather than guessing a value.
: Not directly. It does not analyze the pixels. If the creating tool recorded how the image was made, that appears in the assertions, and you can read it there; a file with no manifest says nothing either way.
: Assertions are the statements the signer attached to the manifest, such as recorded actions or creation details. History lists the manifest's ingredients, the earlier assets it was built from. Both are shown exactly as stored.