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
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
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
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
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 receives provenance | a digital asset with its Content Credential (C2PA manifest); the registry's own unit is the product or signer |
| Relations carried | signing; creation and edit history (ingredients); trust-list membership |
| Carrier | signed C2PA manifests; the conformance lists as JSON |
| Expresses · records · tests | expressesrecordstests |
| Operations tested | none |
| What survived | not tested here: conformance concerns producing and validating C2PA data correctly |
| Depends on | C2PA 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.
| Canonical name | C2PA Conformance Program and Explorer |
| Also known as | C2PA Conforming Products List, Content Credentials conformance |
| Address | https://c2pa.org/conformance/ |
| Operator | Coalition for Content Provenance and Authenticity (C2PA), Conformance Task Force |
| Founded | June 2025 (the program) |
| Kind | registry |
| Unit | a conforming generator or validator product, or a trust-list entry op |
| Lifecycle | active — program opened June 2025, now v0.2 op |
| Count | 286 records in the conforming-products JSON list (as of 2026-10-29) obs |
| Data access | Conformance Explorer; JSON lists on GitHub |
| Versions and dates | program: v0.2; explainer read: 2.4; specification latest: 2.5 (the saved Explainer's version menu); read: 2026-10-29 |
| Observation | 2026-10-29: read |
2478cf522501d050…2478cf522501d050…2478cf522501d050…e1872450e1ae7f6a…e1872450e1ae7f6a…e1872450e1ae7f6a…e1872450e1ae7f6a…e2fb3928fbb2ba3d…e1872450e1ae7f6a…2478cf522501d050…e1872450e1ae7f6a…e2fb3928fbb2ba3d…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}
}