C2PA provenance guide

What happens to Content Credentials after image editing?

Editing does not automatically preserve a Content Credential. A C2PA-aware editor can validate the source as a parent ingredient, record the edit, and sign a new credential for the output. A non-aware workflow may not update or retain the embedded manifest. Validation shows provenance integrity; it does not prove the image’s claims are true.

Standards and product sources checked August 11, 2026.

Open the image editor

Start with the distinction

Content Credentials are not ordinary metadata

Ordinary metadata

EXIF, IPTC, and XMP fields can describe an asset. A Content Credential can include these formats as assertions, but adds a signed claim and a cryptographic binding to the content.

Content Credentials

A C2PA Manifest records provenance assertions, a content binding, and a claim signature. That structure makes alteration detectable; it does not turn every assertion into a statement of truth.

Embedded manifests can become separated from an asset. C2PA also defines durable credentials that use soft bindings to help rediscover associated provenance. File metadata and the recoverable provenance model are therefore related, but not interchangeable.

Preservation-positive workflow

What a C2PA-aware editing workflow records

An aware editor first validates the source credential, opens the source as an ingredient, records the actions applied to the asset, and signs a new credential bound to the edited output. The new signature belongs to the derivative; it is not a reuse of the source asset’s binding.

1. Validate the source

Check the source asset and record the validation status available when it becomes an ingredient.

2. Record the edit

Describe the material actions in the new manifest rather than silently treating the derivative as the original.

3. Sign the output

Create a new claim and signature bound to the derivative asset that the workflow actually exports.

Parent and derivative

Parent ingredients connect derived assets

C2PA defines a derived asset as one made by modifying an existing asset. In the derivative’s ingredient assertion, a parentOf relationship says the current asset derives from that ingredient. The actions assertion records that the parent was opened and what the workflow did next.

Ingredient provenance can be included and its earlier validation can be recorded. A consumer may still lack the ingredient data needed to verify every hard binding in the complete chain.

Interpretation boundary

What validation does—and does not—prove

Validation can show

  • • Whether the claim and signature satisfy the validator’s checks.
  • • Whether the active manifest remains bound to the asset.
  • • Which signer and recorded actions supplied provenance signals.

Validation cannot establish alone

  • • Whether the image’s real-world claims are true or factual.
  • • Whether every ingredient in a provenance tree is available.
  • • Whether an absent credential means the asset is deceptive.

Review before export

Six-step Content Credentials preservation checklist

  1. 1Keep the original asset and its Content Credential unchanged.
  2. 2Use an editor that explicitly documents C2PA-aware validation and signing.
  3. 3Validate the source before editing and record it as the parent ingredient.
  4. 4Record the material edit actions in the new asset’s provenance.
  5. 5Sign a new Content Credential that is bound to the edited output.
  6. 6Validate the derivative independently and retain the source with it.

Product compatibility boundary

Peelaway’s current documented C2PA boundary

Peelaway’s current public contracts do not document reading, validating, preserving, emitting, or signing C2PA Content Credentials. Do not infer that an edited output retains a provenance chain. Keep the original and independently validate and re-sign derivatives when provenance matters.

This is a documentation boundary, not a product conformance test. It does not establish whether a particular input or output contains a credential, and it does not claim that Peelaway strips credentials.

Source ledger

Sources checked August 11, 2026

Standards sources define provenance and validation. Peelaway’s machine-readable public contracts establish only the product-specific documentation boundary above. Inspect the current sources before designing a provenance-sensitive workflow.

Open the image editor