ProvenanceGuard
← Go back

← All guides

Screenshots Destroy Provenance: How to Check a Copy Instead

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

The short answer

A screenshot shares zero bytes with the original file, so no embedded metadata, manifest or assertion can survive into it, and its exact hash is meaningless. What can survive is visible: the label strip if it was in frame, and the picture itself, whose perceptual fingerprint can still match the registry if the screenshot kept enough of the image at sufficient size. Check screenshots with recovery, and expect wider distances.

Seal an image free → Recover a reposted image Pricing

Every provenance conversation eventually meets a screenshot, the cockroach of media formats: it survives everything and carries nothing.

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.

What is a screenshot copy? an image captured from a screen rather than copied as a file, carrying none of the original file's bytes or metadata, only a new raster of its visible pixels, at screen resolution and cropping.

Screenshots and provenance: the plain-English version

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.

A visible label does the communicating that metadata cannot. Most people who see an image will never open its properties, and most platforms will never show them a credentials panel. A label in the pixels, naming the content as AI-generated, is read by exactly the audience the disclosure rules exist for, on exactly the surface where they encounter it. ProvenanceGuard's labelled copy carries that strip as part of the image, so the disclosure travels with the pixels instead of depending on a caption that can be separated from them.

Reading the result properly

Labels have their own failure modes, and a serious workflow plans for them. A label placed along an edge can be cropped out; a label rendered too small becomes illegible after a platform resize; a screenshot of the centre of an image may exclude it entirely. That is why the visible label is one layer among several: the survival re-checks specifically test whether the label remains detectable after simulated platform transforms, and the registry fingerprint remains as the fallback when the label is gone.

There is also a tone question. A custody strip that looks like part of the work's presentation, clearly worded and consistently used, reads as professionalism rather than apology. Teams that label every AI asset the same way, from the first post rather than after a complaint, find the label becomes part of their brand's trust signal. The creators who struggle are usually the ones who labelled inconsistently, so that an unlabelled repost looks like concealment next to their labelled originals.

Mistakes that quietly break the record

Pipelines break provenance in boring places: a design tool exporting without metadata, a CDN recompressing on the fly, a social scheduler re-encoding before upload, an archive converting everything to one format. Each is a transform, and each transform is testable. The lineage tool's local transforms and the vault battery's transforms exist precisely so a team can run its own pipeline's steps against a sealed sample and watch which step removes what, instead of discovering it from a published asset that no longer verifies.

Format details decide more provenance outcomes than policy documents do. JPEG carries XMP in application segments that re-encoding discards; PNG carries text chunks that many converters drop silently; EXIF, written by cameras, is routinely stripped by platforms and says little about AI generation in any case. ProvenanceGuard works with JPEG and PNG because their structures are where its inspection, XMP embedding and fingerprinting are defined and tested, and it inspects all three metadata territories, XMP, EXIF and PNG chunks, rather than assuming any one of them is where the truth lives.

When free is enough and when paid depth earns its place

ProvenanceGuard is built around those layers, and its wording is deliberately narrow. The free job inspects one JPEG or PNG, embeds a signed ProvenanceGuard assertion in XMP, produces a visibly labelled copy, registers the SHA-256 and perceptual fingerprints, and gives the asset a public verification page. The assertion is HMAC-signed and labelled accurately everywhere as ProvenanceGuard's own assertion; it is not a C2PA manifest and is never described as one.

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.

Five actions to take

  1. Expect screenshots and design the label to appear inside the likely frame
  2. Run recovery on the screenshot as received, without enlarging or cleaning it
  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 support team verifying a customer's screenshot of a campaign image

The screenshot had no metadata at all, as expected; the labelled strip was in frame, and recovery matched the visible region to the registered asset at the wide end of the threshold, enough to identify which campaign version the customer had seen.

File the pattern, not just the outcome: a dated record, a measured match, and wording that never claimed more than the record holds. Repeated across a catalogue, that pattern is what turns provenance from a feature into a reputation.

FAQ

Why does screenshot matching sometimes fail?

Because a screenshot may be small, cropped, moire-patterned or compressed, pushing the pixel distance past threshold. A failed match means the method could not establish the connection, which is reported honestly rather than forced.

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 →