ProvenanceGuard
← Go back

← All guides

Image Lineage: Building a Chain of Custody for an Edited AI Image

By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read

The short answer

A lineage chain records an image's stages the way custody records an exhibit: origin upload with its real SHA-256, local transformations executed on the held bytes, declared external steps recorded as declared, and signed assertions linking each stage's hashes. Anyone reading the chain can re-verify the local links and can see exactly which links rest on declaration rather than recomputation.

Seal an image free → Recover a reposted image Pricing

An image with three edits and two platform hops has a biography; lineage is simply refusing to let that biography be retold from memory.

The chain is read through three states, and the discipline is in never blurring them. VERIFIED means ProvenanceGuard holds the step's output bytes and the recomputed hash matches the record, link by link. UNKNOWN means the step was declared rather than executed here, so there are no held bytes to recompute from; it stays unknown forever, however trustworthy the declarant. MISMATCH means bytes are held but the recomputed hash differs from the record, which is reported as a failure with an action, not smoothed over. Those three words, used strictly, are what make a lineage record worth reading.

What is a lineage chain? a hash-linked record of an asset's stages: the origin file, each transformation, and each declared external step, with signed assertions tying every link's before-hash to the previous link's after-hash.

The problem behind image lineage

Lineage extends the record from a single sealing moment to a chain. A lineage record links an asset's stages by content hashes: the origin upload, each transformation executed locally, and each declared external step, with signed assertions tying the links together. Local steps such as stripping metadata or re-encoding as JPEG at quality 82 are executed on the actual held bytes, so their after-hashes are recomputed and checked. Declared steps, like a publish to an external platform, are recorded as declared, with whatever evidence exists attached to them.

Sealing is the moment a record is created. ProvenanceGuard takes the creator and disclosure the uploader declares, the SHA-256 of the original bytes, and the registration time, and signs that assertion with HMAC-SHA256 under the product signing key. The signed assertion is embedded into the file as XMP, producing the sealed copy. Because the signature covers the assertion's contents, altering the creator, the disclosure or the hash inside the file afterwards invalidates the signature, and the verification page shows that plainly.

How ProvenanceGuard handles it

Alongside the sealed copy, sealing produces a visibly labelled copy: the same image with a parchment custody strip in the pixels naming it as AI-generated content whose provenance is registered with ProvenanceGuard. The distinction matters. Embedded assertions are machine-readable and fragile in transport; a visible label is human-readable and survives anything that keeps the strip in frame, including a screenshot. Publishing the labelled copy where the audience actually sees the image, and keeping the sealed copy as the record, uses each layer for what it is good at.

What sealing does not do is just as clearly bounded. It does not certify that a disclosure statement is legally sufficient, it does not turn the assertion into a C2PA manifest, and it does not store the uploaded original: the registry keeps the sealed and labelled copies and the record, so verification and downloads keep working, while the original bytes are not retained. The seal is evidence of a declaration made at a time, about a specific file, and that precision is what makes it useful later.

What survives distribution, and what does not

The registry is the part that survives distribution. At sealing, the asset's SHA-256, its sealed copy's SHA-256, and its perceptual fingerprints are stored against a public exhibit ID. Anyone with that ID, or with the file's hash, can open the public verification page or query the verification API and confirm that this exact file, or a near copy of it, was registered, when, and with what declared creator and disclosure. Verification pages are public by design: a record only a vendor can check would not settle disputes.

Two kinds of fingerprint do two kinds of work. The SHA-256 is exact: change one byte and it changes completely, which makes it perfect for proving a copy is bit-for-bit the registered file and useless for recognising a resized repost. The perceptual fingerprints, computed from the pixels rather than the bytes, are approximate on purpose: they stay close when a copy is resized, re-encoded or lightly edited, and drift as edits accumulate. A good registry stores both and is honest about which kind of match it is reporting.

A routine that survives busy weeks

The registry model also disciplines what a match means. A fingerprint match says this image is the registered image or a close descendant of it; it does not say the person showing it to you owns it, and it does not say the disclosure attached to it was correct. Those judgements stay human. What the registry removes is the argument about identity and timing: which file, registered when, carrying which declaration. Most real disputes shrink considerably once those three facts stop being contestable.

The practical problem is distribution. An image is rarely published once, in one place, in its original form. It is uploaded to platforms that resize and re-encode it, forwarded by partners, saved and reposted by audiences, and archived by people who strip whatever context surrounded it. Each step is normal and usually innocent, yet together they separate the image from anything that said how it was made. Planning for that separation, rather than hoping it will not happen, is the whole discipline this guide is about.

Five actions to take

  1. Start the chain at the origin upload, not at the final export
  2. Add external steps as declared steps at the time they happen
  3. Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint
  4. Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned
  5. Re-check one published asset through the Recovery lookup so you know the stripped-copy path works before you need it

A worked example: A studio delivering an AI campaign image through 4 edit rounds

Its lineage chain held the origin, 4 local transform steps verified link by link, and 1 declared publish step marked UNKNOWN; the client accepted delivery by re-verifying the chain head rather than re-asking how the file had evolved.

The lesson generalises beyond this case. Records made at publication time are cheap, calm and complete; records reconstructed under pressure are expensive, partial and contested. Everything in this guide is in service of moving work from the second category into the first.

FAQ

Is a lineage chain the same as version history in my editor?

No. Editor history lives in the tool and trusts the tool. A lineage chain is hash-linked and signed, its local steps are recomputed from held bytes on every view, and declared steps are visibly downgraded to UNKNOWN rather than presented as verified.

What do Pro and Team cost?

Pro is $29 a month and Team is $79 a month, as shown on the pricing page. Paid depth means per-platform survival re-checks, evidence pack export with EU, California and New York wording, and the bulk hash-verification API.

Are my uploaded originals stored?

No. The registry keeps the sealed and labelled copies derived at sealing time and the registry record, so downloads and verification keep working, while the uploaded original bytes are not retained.

Can anyone verify a record, or only the owner?

Anyone. Verification pages are public by design, the single-hash lookup is a public API, and an exhibit ID or a file hash is enough. A record only its owner could check would not settle a dispute with a stranger.

Seal an image free →