What Are C2PA Content Credentials?

The problem C2PA is trying to solve

As generated and edited images became indistinguishable from photographs, the industry response was not to build better detectors — those lose the arms race — but to attach a verifiable history to files at the point of creation. The Coalition for Content Provenance and Authenticity, C2PA, is the standard that came out of that effort, backed by Adobe, Microsoft, the BBC, Sony, Nikon, Leica and others.

The bet is that provenance beats detection: rather than asking whether an image looks generated, you ask what the file says about itself, and whether that claim is cryptographically signed by someone you trust.

What is inside a manifest

A C2PA manifest is a structured record attached to the file, signed with a certificate. A typical one includes:

• Which application created the file, and its version
• Assertions about what was done — captured on a camera, edited, or generated with a model
• Whether generative AI tools were involved, and sometimes which
• Thumbnails of earlier states in the edit chain
• The signing certificate, which identifies the issuing organisation and sometimes the individual

Where it physically lives

The manifest is packaged in a JUMBF box — a container format from the JPEG standards family. In a JPEG that box sits inside an APP11 marker segment; in a PNG it lives in a caBX chunk; other formats have their own designated homes.

This matters for a practical reason: it means content credentials are metadata. They sit alongside the picture rather than inside it, and like all metadata they can be removed by editing the container.

Absence is part of the design

Because the manifest is signed, it cannot be forged or edited without detection. It can, however, be deleted — and the standard's designers were explicit that this is expected.

The consequence is that C2PA does not prove an image is untouched. It provides a verifiable claim when present, and says nothing when absent. In workflows that expect credentials — a newsroom, a stock library — an image arriving without them is itself a signal, which is the closest the system gets to making removal costly.

Reasons people remove them

The debate tends to be framed around bad actors, but the everyday reasons are mundane and mostly about privacy. A manifest can name an individual, an account, a client, or the internal tools a studio uses. Edit history can expose a workflow a business considers proprietary. For a freelancer delivering work, that information travelling with the file is the same category of problem as XMP edit history or an EXIF serial number.

The line worth holding is intent: removing identifying information from your own work is ordinary privacy practice; removing provenance to misrepresent authorship or pass a manipulated image off as unedited is not.

How to check a file

Adobe's Content Credentials verify site accepts an upload and shows any manifest it finds. If you would rather not upload the file, the AI metadata checker on this site detects the presence of a JUMBF box in JPEG and PNG locally in your browser, though it does not validate signatures.