C2PA Ecosystem
Cameras, AI tools, and editing software that support the C2PA content provenance standard.
The Coalition for Content Provenance and Authenticity (C2PA) publishes an open standard for embedding cryptographically signed provenance data into media files. Founding members include Adobe, Microsoft, Intel, the BBC, Truepic, Sony, and Arm. NOC builds on this standard to issue permanent, independently verifiable certificates of origin.
NOC Camera
The NOC Camera app brings hardware-backed origin signing to any modern smartphone.
Content captured with the NOC Camera app and certified through NOC Kit carries the same class of hardware-backed provenance metadata as dedicated C2PA cameras. NOC is pursuing formal Level 2 designation through the Content Authenticity Initiative — until granted, the signing approach is technically equivalent but not yet officially listed.
No additional hardware required. Works on most phones released in the last few years.
Cameras with C2PA
These cameras cryptographically sign images at the moment of capture. The signature travels with the file and can be verified by any C2PA-compatible tool — including NOC. Level 2 means the signing key is stored in hardware (a secure enclave or TPM), making it significantly harder to forge.
| Camera | Assurance level | Notes | Status |
|---|---|---|---|
| Leica M11-P | Level 2 (hardware-backed signing) | First camera to ship with C2PA built in at launch (October 2023). Signs images in-camera at capture. | Shipping |
| Nikon Z9 | Level 2 | C2PA added via firmware update. Requires firmware 5.0 or later. | Shipping |
| Nikon Zf | Level 2 | C2PA added via firmware update alongside the Z9. | Shipping |
| Sony A1 | Level 2 | C2PA added via firmware update. Firmware version 2.0 or later required. | Shipping |
| Sony A9 III | Level 2 | Shipped with C2PA support. Sony’s second C2PA-capable body. | Shipping |
| Canon (multiple bodies) | TBD | Canon announced C2PA support across several bodies. As of March 2026, firmware updates have not yet shipped. Announcement confirmed for EOS R1 and R5 Mark II. | Announced |
| Google Pixel 9 / 10 | Level 2 | Native C2PA signing in the Pixel Camera app. Applies to photos taken with the default camera app; third-party camera apps do not sign. Covers both front and rear cameras. | Shipping |
AI tools that embed C2PA
These tools label their output as AI-generated using C2PA manifests. That is a good thing — honest labeling at the source is exactly what the standard is designed to enable. Consumers and platforms that read C2PA can automatically surface this information without relying on watermarks or detection algorithms.
| Tool | Notes |
|---|---|
| OpenAI — DALL-E / ChatGPT image generation | All images generated by DALL-E 3 (via ChatGPT and the API) include a C2PA manifest labeling the content as AI-generated. The manifest identifies OpenAI as the signer and records the generation timestamp. |
| Adobe Firefly | Every Firefly-generated image carries a C2PA manifest with an ‘AI-generated’ assertion and an Adobe content credential. Preserved when the image is used inside Photoshop or Lightroom. |
| Google Imagen (via Gemini / Workspace) | Images generated through Google’s Imagen models include SynthID watermarking plus a C2PA manifest in supported products. |
| Microsoft Designer / Copilot image generation | AI-generated images from Microsoft Designer and Copilot include C2PA content credentials identifying the content as AI-generated. |
Editing tools and C2PA preservation
Running an image through editing software is the most common point at which the C2PA chain breaks. Most tools silently discard any credentials present in the original file. Only a small number currently preserve the chain.
Preserve the chain
| Tool | Notes |
|---|---|
| Adobe Photoshop (2024 or later) | Reads and writes C2PA manifests. When you open a signed image and save it, Photoshop appends its own entry to the ingredient chain. The original camera signature and all prior steps remain visible. |
| Adobe Lightroom (2024 or later) | Preserves the C2PA chain on export. Non-destructive edits in Lightroom are logged as an ingredient step. The original capture credential is retained. |
| Adobe Premiere Pro | Preserves C2PA credentials on video exports when the source clips carry them. |
Strip the chain
The following tools currently strip C2PA credentials on export. A file saved through any of these loses its provenance chain — the resulting file has no manifest, regardless of what was present in the original.
- CapCut
- DaVinci Resolve
- Lightlab
- VSCO
- Snapseed
- Instagram (re-export)
- Most social media download/repost flows
Common questions
If I edit a real photo in Photoshop, does NOC see it as AI?
No. NOC's provenance system is based on creator declaration, not automated detection. When you notarize content, you declare whether it is Camera Captured, AI Generated, or Origin Unknown. A real photograph edited in Photoshop is still Camera Captured — the editing tool does not change the origin.
Photoshop 2024 and later preserves C2PA chains, so the editing history remains transparent. If the credential chain shows Camera → Photoshop → NOC, the certificate will reflect that full history. Reviewers can see exactly which steps the file passed through.
Should edited images be labeled differently?
NOC uses three categories: Camera Captured, AI Generated, and Origin Unknown. An edited human photograph is still Camera Captured.
We do not distinguish between “unedited” and “edited” because virtually all published content is edited — color grading, cropping, and exposure adjustments are standard practice and do not change the origin of the work. For those who want to examine the full edit history, the C2PA ingredient chain records each step.
My camera supports C2PA. Do I still need NOC?
C2PA camera signing and NOC serve different purposes. Camera signing establishes that the image left the camera unaltered. NOC adds a layer on top: an immutable on-chain anchor, a signed manifest, and an invisible watermark that survives compression and re-upload even after platforms strip metadata. Together they provide a complete provenance chain from capture through publication.
I use DaVinci Resolve / CapCut. Will my C2PA chain be broken?
Yes, if those tools are in your workflow. Any tool in the “Strip the chain” list above will discard the C2PA manifest on export. Additionally, the NOC watermark is embedded in the pixel data — editing this can destroy the watermark, and the ability to validate the image.
Verification tools
- Content Credentials Verify — maintained by Adobe and the CAI. Reads C2PA manifests in any compatible file.
- NOC Verify — upload or paste a URL to check for a NOC certificate and invisible watermark.
- CAI public tools — list of C2PA-aware browsers, plugins, and platforms.
NOC and C2PA
NOC uses a hardware-backed signing approach consistent with C2PA standards. NOC is pursuing formal Trust List designation through the Content Authenticity Initiative. Until granted, NOC certificates are technically valid but do not appear on the official CAI Trust List.