ozDNA / Learn / Content Credentials
What Are Content Credentials? A Practical Guide to C2PA
Content Credentials are tamper-evident provenance records attached to a file, built on the open C2PA standard. A credential records facts such as which tool or device made the content, what edits were made, and whether AI was used. It is signed so that any later change to the file or the record can be detected. C2PA is the technical specification. Content Credentials is the name people see.
C2PA, the CAI and "Content Credentials"
Three names come up together, and they refer to different things:
- C2PA (Coalition for Content Provenance and Authenticity) is the standards body that publishes the technical specification. It was formed in 2021. Its founding members included Adobe, Arm, the BBC, Intel, Microsoft and Truepic.
- The Content Authenticity Initiative (CAI) is an Adobe-led community that promotes adoption and maintains open-source tools for reading and writing C2PA data, at contentauthenticity.org.
- Content Credentials is the public-facing name for a C2PA record, often marked with a small "CR" icon. Adobe Content Credentials are the same thing as produced by Adobe's apps, not a separate format.
So "C2PA vs Content Credentials" isn't a choice between two systems. C2PA is how the record is built and checked, and Content Credentials is what the record is called when it is shown to people.
How Content Credentials work
A Content Credential is a signed bundle of statements, bound to the exact content it describes. In C2PA terms, that bundle is a manifest. Its main parts:
| Part | What it records | What breaks it |
|---|---|---|
| Assertions | Statements about the content: the actions taken (created, edited, cropped), the tool or device, whether a generative AI model was involved, and optional creator information | Changing any assertion after signing |
| Hard binding | A cryptographic hash of the content's bytes, so the manifest belongs to exactly this file | Any change to the content bytes, including re-encoding |
| Claim and signature | The claim gathers the assertions. The signer signs it with a private key backed by an X.509 certificate | Altering the claim, or a certificate that is expired, revoked or untrusted |
| Ingredients | Earlier manifests of the files this one was made from, so the edit history forms a chain | Missing or altered ingredient manifests |
The manifest is usually embedded in the file itself. For a JPEG, it goes in a metadata container inside the file. It can also be stored remotely and referenced by URL. When the file is edited in a C2PA-aware tool, a new manifest is added and the previous one becomes an ingredient, so the history builds up.
Some tools and devices already write credentials. Adobe Firefly attaches them to generated images, OpenAI adds C2PA metadata to images made with its image models, and some cameras, starting with the Leica M11-P, can sign photos at capture.
How to verify C2PA credentials
To verify a Content Credential, open the file in a C2PA validator and read four results: is a manifest present, is the signature valid, is the signer trusted, and does the content still match the hash. Practical options:
- Content Credentials Verify at contentcredentials.org/verify: upload or drop a file and see the manifest and its history.
- The open-source C2PA SDK and command-line tool from the CAI (c2pa-rs), for scripted or bulk checks.
- Platform badges. Some sites show a "CR" icon you can click to inspect a credential. They often show only part of the record, so check the file itself when it matters.
A validator's answer usually falls into one of these cases:
| Result | What it means |
|---|---|
| Valid, trusted signer | The manifest is intact, the content matches, and the signing certificate chains to a trust list the validator uses |
| Valid, unknown source | The signature is cryptographically correct and the content matches, but the signer's certificate is not on the validator's trust list. This is about who signed it, not about tampering |
| Invalid | The content or the manifest changed after signing, or the certificate is bad. Treat the record as broken |
| No credentials found | The file has no manifest, or it was stripped. This proves nothing either way |
What Content Credentials cannot tell you
- Whether the content is true. A credential shows origin and history, not accuracy. A signed photo can still be staged. See provenance vs AI detection.
- Anything once it is stripped. Many social platforms remove embedded metadata on upload, and a screenshot never carries it. The C2PA specification allows "soft bindings", such as watermarks and fingerprints, to find a stripped file's record again, but support varies.
- That the signer's statements are honest. The signature proves who made the statements, not that they are correct. An AI-use assertion is as reliable as the tool that wrote it.
- Anything about files that never had a credential. Most content online today has none.
Trust lists and "unknown source"
Validators decide which signers to trust using trust lists. The C2PA runs a conformance program for products that sign credentials. A signer that has not completed it can produce signatures that are mathematically valid and still be shown as an unknown source by tools that use the official list. When you see "unknown source", ask who signed the file and whether you have another way to check them. Do not assume the file was altered.
Where ozDNA stands. OriginDNA plans to sign to the open C2PA standard. Signing is not live yet. Today the service registers images, records a public timestamp and stores a perceptual fingerprint. ozDNA is not a member of the C2PA conformance program, so its signatures may show as "unknown source" in third-party tools, and it does not claim otherwise. That is why OriginDNA runs its own public verify page and keeps a fingerprint that still matches after metadata is stripped. The verify page currently scans files for a C2PA manifest. Full validation runs in the deep verify app.
FAQ
What are Content Credentials in simple terms?
A signed label inside a file that records how the file was made and changed, such as the device or app, the edits, and whether AI was used. If the file or the label is altered later, a validator can tell.
What is the difference between C2PA and Content Credentials?
C2PA is the open technical standard and the coalition that publishes it. Content Credentials is the public name for a record made to that standard. Adobe Content Credentials are C2PA records produced by Adobe tools.
How do I check if an image has Content Credentials?
Open the original file in a C2PA validator such as Content Credentials Verify, or use the open-source c2patool. Check the file itself rather than a re-uploaded copy, because many platforms strip the credentials on upload.
Why does a validator say "unknown source"?
The signature checks out, but the signer's certificate is not on that validator's trust list. It is a statement about who signed, not evidence that the file was changed. An invalid result is the one that indicates tampering.
Do Content Credentials prove an image is AI-generated?
They record what the creating tool declared. If a generator wrote an AI-use assertion, the credential carries it, signed. A missing credential does not prove the image is human-made, because most files have none and many are stripped.
Has OriginDNA completed the C2PA conformance program?
No. OriginDNA plans to sign to the open C2PA standard, but signing is not live and ozDNA has not completed the C2PA conformance program. It runs its own public verify page instead of relying on a trust-list badge.
Sources
- C2PA technical specifications, Coalition for Content Provenance and Authenticity
- Content Authenticity Initiative and its open-source C2PA SDK
- Content Credentials Verify
Keep reading
- How to Verify an AI Content RecordHashes, signatures and timestamps: what each check proves.
- Content Provenance vs AI DetectionTwo different questions, and why neither proves a claim is true.
Check an image for a C2PA manifest, a content hash and a perceptual fingerprint, all in your browser with no upload.
Open the verify pageAbout OriginDNA