Cropping and Resizing: How Edits Change an Image Fingerprint
By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read
The short answer
Resizing and re-encoding barely disturb a perceptual fingerprint, which is why published copies still match. Cropping removes content the fingerprint described, so distance grows with the crop. Collage, heavy filtering and compositing can push a copy past the recovery threshold, 36 of 192 bits, at which point the honest result is no match, and the remedy is recording the edit as a lineage step rather than pretending the copy is the original.
Editing is not the enemy of provenance; unrecorded editing is. A declared step keeps the chain honest where a silent one breaks 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 edit distance? how far an edited copy's perceptual fingerprint sits from the original's, measured in differing bits: near zero for re-encodes and resizes, growing through crops and filters, and beyond threshold for heavy composites.
Why crops, resizes and fingerprints 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.
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.
How the record is built
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.
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.
Where it meets the real world
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.
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.
Putting it into practice
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.
No single layer does this job alone, and honest tooling says so. Embedded metadata can be stripped. A visible label can be cropped. A fingerprint can drift if an image is edited heavily. A registry entry proves registration, not authorship in a legal sense. Used together, though, the layers cover each other's failures: when the metadata is gone the fingerprint can still find the registry record, and when a copy is too altered to match, the labelled version and the evidence pack still tell the story.
Five actions to take
- Seal heavy crops and composites as their own assets
- Record intermediate edits as lineage steps while you still hold the bytes
- Export an evidence pack while the context is fresh if the asset is regulated, client-facing or likely to be questioned
- Re-check one published asset through the Recovery lookup so you know the stripped-copy path works before you need it
- Seal the final export of the asset, with the creator and disclosure declared in your own accurate words
A worked example: An editor testing her own archive against recovery
Of 20 published derivatives, 17 matched directly; the 3 failures were all cover crops under half the original area, and she sealed those crops as their own exhibits, which is the correct ending for a heavily transformed version.
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
How much cropping is too much?
There is no universal percentage in the product, because distance depends on what the crop removes. The measurement is the answer: run the lookup and read the distance, instead of applying a rule of thumb.
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.
Is ProvenanceGuard's assertion a C2PA manifest?
No. It is ProvenanceGuard's own signed assertion, embedded as XMP and HMAC-signed, and labelled that way everywhere. The inspection detects genuine C2PA markers when a file carries them, but the two records are never conflated.