Provenance Erasure
Provenance meta-aggregator / Media and images

C2PA Conformance Program and Explorer

Media and imagesregistryactive
The C2PA Conformance Program is the Coalition for Content Provenance and Authenticity's risk-based governance program that designates generator and validator products as conforming and holds certification authorities to the C2PA Certificate Policy. Administered by the C2PA Conformance Task Force, it opened in June 2025 and is now at version 0.2; its unit is the product on the public Conforming Products List.
Visit C2PA Conformance Program and Explorer ↗The /non rowRun an erasure audit
The C2PA Conformance Program provides assurance that products adhere to the Content Credentials specification, and fulfill a set of security requirements to ensure they are producing and validating C2PA data correctly.

In its own words: https://c2pa.org/conformance/, read 2026-10-29

What it is

Its stated purpose is assurance "that products adhere to the Content Credentials specification, and fulfill a set of security requirements to ensure they are producing and validating C2PA data correctly." The program document says the specification "is limited without a robust governance framework and conformance program." It belongs to a C2PA Governance Framework governed by the Steering Committee; the Conformance Task Force, established in 2024, is co-chaired by Andy Parsons, Yogesh Deshpande and Sherif Hanna. The Content Authenticity Initiative likens the program to the Bluetooth and Wi-Fi programs.

From its /non article, sentences 1, 2, 3

How it works

Applicants sign a legal agreement with the C2PA and provide evidence; the technical evaluation checks that manifests are properly formatted and certificates handled per the Certificate Policy. An accepted product goes on the Conforming Products List, and the generator product, always the signer, is accountable for the assets it generates. Only conforming generator products can receive claim-signing certificates from a Certification Authority on the C2PA Trust List.

From its /non article, sentences 4, 6, 12

Two assurance levels are in operation. Level 2 demands hardware-backed key storage and dynamic security evidence, and Google's Pixel 10 was the first device at the highest level. When the census read the JSON list it held 286 records, 254 generator and 32 validator products, 11 generators at maximum level 2.

From its /non article, sentences 11, 15

What it leaves out

C2PA states the limit itself: Content Credentials "do not provide value judgments about whether a given set of provenance data is 'true'," and "provenance information alone cannot tell you whether the digital content is true, accurate or factual." The core specification "does not support attribution of content to individuals or organizations." Provenance is not always complete: the metadata can be removed and manifests separated, and an ingredient's provenance cannot be verified in the same way as the containing asset's.

From its /non article, sentences 18, 20, 22

On security the sources conflict: the FAQ says faking credentials would require breaking current cryptographic standards, while Wikipedia reports a vulnerability demonstrated in October 2026 that let an image be altered without invalidating its signatures. Adoption is partial: as of 2026 no dedicated camera had achieved compliance, and IPTC Metawatch found 27 C2PA manifests in 6,580 news images in October 2026.

From its /non article, sentences 24, 25

Place in the field

In the archive's reading the program certifies the artifact dimension of provenance, which "verifies that *this file* was created by *this source* at *this time*." Past the artifact the archive finds no reach: "When a 5,000-word article becomes a 200-word AI Overview, C2PA cannot tell you what was lost."

From its /non article, sentences 17, 27

At the name, Google's AI Overview composed the program as its applicants meet it, components and steps, and offered end-to-end tamper evidence for digital media while omitting C2PA's own negative tags. In the Capture Registry's reading, "A reader leaves with tamper evidence and without the caveat that well-formed provenance can be false."

From its /non article, sentences 29, 30

This article is derived from the entity's /non article (EA-NEGONT-02, the knowledge object composed under v0.9): every fact in it is stated there, and each paragraph names the sentences it rests on.

What it carries

What receives provenancea digital asset with its Content Credential (C2PA manifest); the registry's own unit is the product or signer
Relations carriedsigning; creation and edit history (ingredients); trust-list membership
Carriersigned C2PA manifests; the conformance lists as JSON
Expresses · records · testsexpressesrecordstests
Operations testednone
What survivednot tested here: conformance concerns producing and validating C2PA data correctly
Depends onC2PA Steering Committee; C2PA Trust List; C2PA TSA Trust List; the Certificate Policy

op the operator's own statement · 3p a third-party account · obs our observation · rd our reading. Hover a tag for its quote; each opens below with its source.

Entity

Canonical nameC2PA Conformance Program and Explorer
Also known asC2PA Conforming Products List, Content Credentials conformance
Addresshttps://c2pa.org/conformance/
OperatorCoalition for Content Provenance and Authenticity (C2PA), Conformance Task Force
FoundedJune 2025 (the program)
Kindregistry
Unita conforming generator or validator product, or a trust-list entry op
Lifecycleactive — program opened June 2025, now v0.2 op
Count286 records in the conforming-products JSON list (as of 2026-10-29) obs
Data accessConformance Explorer; JSON lists on GitHub
Versions and datesprogram: v0.2; explainer read: 2.4; specification latest: 2.5 (the saved Explainer's version menu); read: 2026-10-29
Observation2026-10-29: read

Relations

Neighbours

Captures: the composition layer's account

The /non row

Evidenceevery field's quote, its source and the hash of the saved copy9
Negative tagswhat it is not3
  • Content Credentials do not judge whether provenance data is 'true'
  • NOT IPTC embedded metadata
  • C2PA does not address human or organizational identity
Sourcesevery source read, with its date and hash3
Not yet checkedwhat remains to read2
  • the C2PA Trust List and TSA Trust List entries (components the program runs, in authority_dependencies)
  • the Content Authenticity Initiative's tools

Cite this record

Lee Sharks, ed. "C2PA Conformance Program and Explorer." Provenance meta-aggregator, Provenance Erasure, compiled 2026-10-29. https://www.provenanceerasure.org/aggregators/c2pa-conformance

Record https://www.provenanceerasure.org/aggregators/c2pa-conformance · entity https://www.provenanceerasure.org/aggregators/c2pa-conformance#entity · the census as data

@misc{pe-c2paconformance2026,
  editor = {Sharks, Lee},
  title = {C2PA Conformance Program and Explorer},
  howpublished = {Provenance meta-aggregator, Provenance Erasure},
  year = {2026},
  note = {Compiled 2026-10-29; every field sourced and dated},
  url = {https://www.provenanceerasure.org/aggregators/c2pa-conformance}
}
Editor: Lee Sharks (ORCID 0009-0000-1599-0703). This page is the provenance meta-aggregator's record of the resource above: its reading and fields are ours, and each field carries its source, its basis and the hash of the copy read. Compiled 2026-10-29. CC BY 4.0.