ProvenanceGuard
← Go back

← All guides

How to Recover an Image's Provenance After It Has Been Reposted

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

The short answer

Upload the reposted copy to the Recovery Registry lookup. It fingerprints the copy with aHash, dHash and pHash, searches the registry within the stated threshold, 36 of 192 bits combined, and on a match returns the exhibit, the declared creator and disclosure, and the registration time. No metadata, filename or watermark in the copy is needed, because the match is made on pixels.

Seal an image free → Recover a reposted image Pricing

Recovery is the feature you want on the worst day: the image is already out there, renamed twice, and someone is asking whose it is and what was declared about it.

Recovery exists for the copy that comes back to you with nothing attached: no metadata, a new filename, dimensions changed by two platform hops. The Recovery Registry lookup fingerprints the uploaded copy perceptually, using aHash, dHash and pHash together, and searches the registry for a record within the stated threshold: a combined distance of at most 36 differing bits out of 192 compared, or 12 out of 64 for older records that carry only the legacy average hash. A match returns the original exhibit, its creator and disclosure declarations, and its registration time.

What is provenance recovery? reconnecting a travelled copy of an image, stripped of metadata and renamed, to its registry record by perceptual fingerprint similarity, returning the original exhibit, declarations and registration time.

Why recovering reposted images matters

The honesty of the method is in its stated limits. This is fingerprint-only soft binding: ProvenanceGuard embeds no invisible watermark, so recovery can only find images that were registered before they travelled, and only while their pixels stay within threshold of the original. Heavy cropping, collage, or aggressive filtering can push a copy beyond matching, and the lookup then says so rather than forcing a nearest guess. A tool that always found something would be manufacturing provenance, which is the opposite of the point.

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.

How the record is built

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.

Where it meets the real world

Checking a copy is the mirror image of sealing one. On an asset's verification page, uploading a candidate copy runs the same byte inspection on it and compares it against the record: its SHA-256 against the original and sealed hashes, whether a ProvenanceGuard assertion is present and its signature valid, and the perceptual distance between the copy and the registered fingerprint, with a match at a Hamming distance of ten or under on the average hash, or an exact hash match. The result states which of those held and which did not, separately, instead of collapsing them into one vague verdict.

For libraries rather than single files, bulk verification is a paid API feature: submit up to a hundred SHA-256 hashes in one call and get back, per hash, whether it is registered, its exhibit ID, its public verification URL and its registration time. That shape suits the questions teams actually ask at scale: whether everything in a delivered campaign folder was sealed, whether a partner's asset library overlaps the registry, or whether a month of published images all carry records. Single lookups stay free and public through the verification page and the single-hash API.

Putting it into practice

Provenance is the record of where a piece of content came from and what has happened to it since: who or what created it, when it was registered, and which copies descend from the original. For an AI-generated image that record matters because the file itself is easy to copy, rename, crop and re-upload, and none of those actions leaves a reliable trace inside a filename. A provenance record kept outside the file, in a registry keyed to the file's fingerprints, survives exactly the handling that erases the signals embedded in the file.

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. Run recovery on the copy as found, before cleaning it up or resizing it
  2. Save the match distance and exhibit ID with whatever action follows
  3. File the exhibit's verification URL beside the asset wherever your team keeps campaign or client records
  4. Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint
  5. Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned

A worked example: A creator whose AI artwork appeared on a print-on-demand store

The store's image was a resized JPEG with no metadata; her recovery lookup matched it at 18 bits of combined distance to a record registered 5 months earlier, and that dated record anchored her takedown request.

Notice what made the difference: not a better argument, but a record created before it was needed, carrying dates and hashes a stranger could check. That is the whole pattern this guide recommends, applied at the scale of one team and one deadline.

FAQ

Does recovery work on images I never sealed?

No. Recovery searches the registry, so it can only find images that were registered before they travelled. That limit is stated in the method; sealing at publication is what makes future recovery possible.

What does the free tier actually do?

The complete job on an asset: byte-level inspection, a signed assertion embedded as XMP, a visibly labelled copy, SHA-256 and perceptual fingerprints registered, and a public verification page. Paid plans add survival re-checks, evidence packs and bulk verification.

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.

Seal an image free →