Skip to content

What is C2PA?

C2PA is the open standard behind Content Credentials: a signed record, inside the file, of where a photo comes from. Here is what it contains, how to check it, and what it does not prove.

C2PA in short

C2PA stands for Coalition for Content Provenance and Authenticity. It was founded in 2021 by Adobe, Arm, BBC, Intel, Microsoft and Truepic, and is hosted by the Linux Foundation. It publishes an open technical specification that anyone can implement.

"Content Credentials" is the public name for what the standard produces: a C2PA manifest attached to a photo, a video or a document. Camera makers, editing software, media and platforms use it to show where a file comes from.

What a C2PA manifest contains

The manifest travels with the file: for a JPEG photo, inside the file itself. It is signed with an X.509 certificate and holds:

  • the claim generator: the tool that produced or changed the file;
  • assertions: what happened to the file, for example captured by a camera, cropped or exported, and the files it was made from;
  • a hash of the content, which binds the manifest to these exact pixels;
  • the signature, which ties all of the above to the signer's certificate.

Tamper-evident, not tamper-proof

C2PA does not stop anyone from editing a photo. It makes the change visible: if the pixels change outside a signed edit, the hash no longer matches and a validator reports the manifest as invalid.

An edit made with a C2PA-aware tool adds a new manifest that points to the previous one. The history stays readable: anyone can see that the photo was edited, and how.

How to verify a C2PA photo

Three ways, from the quickest to the most thorough:

  • Content Credentials Verify, the free web page of the Content Authenticity Initiative: drop a file, read its manifest and who signed it.
  • c2patool, the open-source command line tool of the same initiative: it prints the manifest as JSON and checks the signature, in a script or a CI job.
  • For a tryVidimus proof: its public verification page, or the open-source tryVidimus verifier, which also checks the eIDAS time stamp without our servers.

Conformance and the trust list

The C2PA runs a conformance program. A generator product that passes it can get a signing certificate from a certification authority on the C2PA trust list. A validator can then tell a signature from a conformant product apart from a signature anyone could make with their own certificate.

tryVidimus Proof Capture is a C2PA conformant Generator Product: the program issued its Notice of Conformant Status on 19 October 2026, at assurance level 1, for JPEG photos.

What C2PA does not tell you

C2PA is a strong base, but three things are outside its scope:

  • Whether the scene is true. A manifest says which tool made the file, not that what it shows is honest.
  • A date you can rely on, on its own. The date in a manifest is written by the signing tool; only a time stamp from a time stamp authority certifies it.
  • Anything once the manifest is gone. Many apps and platforms strip metadata when a photo is uploaded or sent. A photo without Content Credentials is not proven fake: it simply carries no proof.

From a C2PA photo to a proof

tryVidimus adds what C2PA leaves out. The photo is taken live, through a capture link in your colors, with no gallery import. Each photo is fingerprinted and C2PA signed, and each proof gets an eIDAS qualified time stamp from Certigna, a French qualified trust service provider. In the EU, that date is presumed accurate until proven otherwise.

Anyone can check the result on a public page, without an account, or offline with the open-source verifier.

Add C2PA-signed photos to your app.

Create an account and seal your first proof in test mode, for free. In production, €5 is offered, then €1 per sealed proof. No subscription.

Create an account