Glossary
Screenshot laundering: a new image with no history
Screenshot laundering is the practice of displaying an AI-generated or edited image and capturing it as a screenshot so that the new file carries none of the original’s C2PA manifest, IPTC fields, saved prompts or hash, defeating every metadata-based check while keeping the picture recognisable.

without-records.pngPNG file · controlled example
- Signature + IHDR
- iTXt XML:com.adobe.xmp
- tEXt parameters
- tEXt prompt / workflow
- tEXt invokeai_metadata
- eXIf
- caBX C2PA manifest
- IDAT pixels
- IEND
No record in this copy
Screenshots and re-exports often drop records.
A clean copy is not proof of a human author, so the report says what is missing and asks for the original.
Check an image →Why it works
A screenshot is rendered by the operating system from the screen buffer. The resulting PNG or JPEG is written by the screenshot tool with its own minimal metadata and a fresh hash; nothing from the displayed file is copied. Vendors acknowledge this directly: OpenAI and Black Forest Labs both state that screenshots remove their metadata. Scaling and colour management also alter the pixels slightly.
What still survives
The picture’s appearance survives, which is what perceptual hashing and invisible watermarks rely on. isGenAI’s difference-hash fingerprint can match a screenshot to a known original within a small distance when the crop is close. Vendors state that SynthID and similar watermarks are designed to survive screenshots, checkable with the vendor’s own tool. Visible watermarks survive unless cropped out.
How to counter it
Ask for the original file and compare it with the screenshot using the image pixel compare tool. Record the platform label or credential icon seen on the original post. Check the screenshot anyway: the fingerprint match is the one route back to file evidence, and the report will be honest about finding nothing else.
Laundering also happens by accident. Many people share AI images by screenshotting them on a phone because it is the fastest route, with no intent to hide anything. The effect on the evidence is the same, so the remedy, asking for the original, is too.
How to use this term when checking a file
- Upload the original file to the AI image detector or the tool named on the page.
- Find the finding that uses this term under “How we checked” and read the source field it names.
- Weigh it by kind: a signed record, a declared field, a saved prompt and a matching copy are different strengths of evidence.
- Remember that absence of a record is not evidence of a human author.
Frequently asked questions
Does a screenshot keep any AI metadata?
No. The screenshot tool writes a new file; the displayed file’s records are not copied.
Can isGenAI detect a screenshotted AI image?
Only through a perceptual match to a known original in its records. Otherwise it reports no evidence found.
Do invisible watermarks survive screenshots?
Vendors state theirs are designed to; verify with the vendor’s detector. isGenAI does not read watermarks.
How do I prove a screenshot came from a specific original?
Compare the two with the image pixel compare tool and the fingerprint match, and keep the source post reference.
Sources
Definitions follow the published standards linked above; the isGenAI behaviour described is the deployed checker as of October 2026.