What is C2PA and why it matters for AI content
C2PA is the open technical standard for Content Provenance and Authenticity. It lets creators, platforms and tools attach a tamper-evident manifest—known publicly as Content Credentials—to images, videos, audio and documents. The manifest records the file’s origin, the tools used to create or edit it, and the sequence of changes. That history is cryptographically signed and embedded in the file so recipients can verify it has not been altered since it was signed. C2PA does not by itself detect AI-generated content; it proves what the signers claim about the file’s history, so viewers can decide whether to trust it.
What a C2PA manifest contains
A Content Credentials manifest is a JSON object stored in the file. It must include the file’s unique identifier, the date and time it was signed, and the public key or certificate of the signer. It can also carry a chain of actions: who captured the original, which AI model generated or modified it, what prompts or edits were applied, and by whom. Each edit can be a separate entry, so the manifest builds a step-by-step audit trail. Optional fields include the software or service used, the geographic location of capture, and a human-readable label. The manifest itself does not contain the content; it only describes the content’s lineage and binds that description to the file with a digital signature.
How a C2PA manifest is signed and verified
Signing happens when a creator, a camera, an editing tool or a platform writes the manifest and then signs it with a private key. The signature is stored alongside the manifest. When someone opens the file, a viewer or validator can use the public key to check that the manifest has not been tampered with and that it belongs to the file. If the file is changed after signing, the signature will no longer match and the validator will flag it. Platforms can strip the manifest when they re-encode or resize content; that is why many providers combine C2PA manifests with an invisible watermark embedded in the pixels or audio, so the provenance can still be detected even if the manifest is removed.
What C2PA proves and what it does not
C2PA proves that the manifest was created by the stated signer at the stated time and that the file has not been altered since it was signed. It proves the chain of edits described in the manifest, provided each step was signed by a trusted party. It does not prove the truth of the claims inside the manifest; if a signer falsely states that a human took a photo, the manifest will still verify, because the signature only confirms authorship of the manifest, not the accuracy of its contents. It does not detect AI-generated content unless the manifest explicitly states that an AI system was used. It does not prevent editing; it only makes editing detectable if the manifest is preserved.
C2PA and the EU AI Act Article 50 marking duty
The EU AI Act Article 50 requires providers of generative AI systems to mark synthetic audio, image, video and text output in a machine-readable format so it can be detected as artificially generated or manipulated. Marking solutions must be effective, interoperable, robust and reliable as far as technically feasible. C2PA manifests, combined with invisible watermarks, are one way to meet that duty because they can carry machine-readable labels and bind them to the file. The Code of Practice on Transparency of AI-Generated Content, finalised on 10 June 2026, also endorses a multi-layered approach that uses metadata and watermarks, and signatories can rely on it to demonstrate compliance. Content generated and published before 2 August 2026 does not need to be labelled retroactively.
Practical steps to use C2PA for provenance
Start by capturing or exporting the file with a tool that supports C2PA. Cameras, editing suites and generative AI platforms increasingly offer built-in signing. If your tool does not, use a certification service that appends a manifest and an invisible watermark. Always sign at the earliest point—ideally at capture or generation—so the chain is complete. When sharing, keep the file in a format that preserves the manifest, such as JPEG, PNG, MP4 or PDF; avoid formats or processes that strip metadata. For public validation, link to a viewer that reads Content Credentials, or embed a badge that viewers can click to see the manifest. For AI-generated content, ensure the manifest explicitly states the use of AI and includes the model name or service provider.
Common misconceptions about C2PA
A frequent misunderstanding is that C2PA is a watermark. A watermark is embedded in the content itself, whereas a C2PA manifest is metadata attached to the file. The two are complementary: the manifest provides the audit trail, and the watermark survives if the manifest is stripped. Another misconception is that C2PA is mandatory by law. It is not; it is a voluntary standard. However, the EU AI Act’s marking duty can be fulfilled using C2PA, and the Code of Practice recommends it. Some also assume that a missing manifest means the content is inauthentic. In reality, many legitimate files lack manifests because they were created before C2PA existed or by tools that do not yet support it.
Frequently asked questions
Does C2PA work with all file types?
C2PA manifests can be embedded in common formats such as JPEG, PNG, MP4, PDF and some audio files. Support depends on the tool or platform creating the file and the viewer used to check it.
Can a C2PA manifest be faked?
The manifest itself can be edited, but the cryptographic signature will no longer match the file if it is altered. A validator will detect the mismatch and flag the file as tampered.
Is C2PA the same as a digital watermark?
No. C2PA is a manifest that records provenance and is signed. A digital watermark is embedded directly in the content. Many implementations use both together so provenance survives even if metadata is stripped.
How do I check if a file has a C2PA manifest?
Use a C2PA-compatible viewer or validator. Many are available online; some platforms display a Content Credentials badge on signed files. A public validator such as laitelier.com/validator can confirm the manifest and its signature.
Do I need C2PA to comply with the EU AI Act?
No. The EU AI Act does not mandate C2PA, but it requires machine-readable marking of AI-generated content. C2PA manifests, especially when combined with watermarks, are a practical way to meet that requirement.