Invisible Watermark That Survives Screenshots: How It Works
Short answer: A screenshot throws away a file's metadata, but it does not have to throw away an invisible watermark. The mark is not stored in the file's properties: it is written into the pixels themselves, as tiny changes spread across the whole image. Because the same information is repeated over the image, a screenshot, a recompression or a crop can still leave enough of it to read. The mark can still be lost, so detection is never guaranteed.
Last updated: October 9, 2026.
Why a screenshot wipes out most identifiers
A screenshot is a new image built from what the screen displays. File names, EXIF data, PDF properties and any hidden fields in the original file are not copied over. A visible stamp can be cropped or painted out, and if every recipient got the same file it identifies nobody. Whatever identifies the copy has to live in the picture itself.
How an invisible mark lives in the pixels
An invisible watermark changes the image in ways too small to notice: slight shifts in brightness and colour that form a pattern. A forensic watermark makes that pattern unique to each copy, so the pattern works as an identifier.
Two ideas make it robust:
- Spread over the whole image. The information is not placed in one spot. It is distributed across the image, so losing a part of it does not erase it.
- Redundancy. The same information is repeated in several places, so a detector can recover it even when some of the pattern is damaged.
A screenshot, a screen photo or a JPEG recompression changes pixels slightly, but they preserve the overall look of the picture, and that is where a mark of this kind sits.
What a mark of this kind can survive
With Markedfile, a mark is designed to survive:
- Screenshots and recompression.
- Crops down to roughly 230 px of a detailed area. That is an approximate minimum, not a ceiling: smaller or flatter areas can fail.
- Most 90° rotations. A rotation combined with strong, uneven stretching can break it.
- PDFs: a screenshot of roughly a quarter of a page or more can be checked, but only for PDFs marked from now on. A crop of just a barcode or QR code is not detected.
Where it stops working
- Small images and heavy compression. Small images and some heavily compressed ones use a more fragile mark that does not survive screenshots.
- Heavy compression, blur or heavy editing. Detection is heuristic. The more the picture is degraded, the less of the mark is left.
- Unmarked files. If the original was never marked, there is nothing to find.
- No 100% guarantee. No tool should promise it.
How to check a screenshot with Markedfile
- Before sharing, upload the file and create one marked copy per recipient.
- Send each person their own copy.
- If a screenshot turns up, upload it to Detect.
- Read the result. Markedfile reports which recipient's copy it matches. It identifies the copy, not the person who pressed the button, so treat it as evidence to follow up, not as proof of intent.
Files are processed in memory and are not stored. The Free plan covers 5 active files with detection for 6 months.
FAQ
Does an invisible watermark survive a screenshot? It can. The mark lives in the pixels, so a screenshot keeps part of it. Survival depends on the size, detail and quality of what is left, and no tool guarantees 100%.
Can I see the watermark? No. The changes are designed to be imperceptible at normal viewing size.
Does it survive a photo of a screen taken with a phone? Sometimes. A photo of a screen adds more degradation than a screenshot, so results depend on image quality.
How small can the crop be? As a rough minimum, around 230 px of a busy, detailed area. Smaller or flat areas can fail, and small images and some heavily compressed ones use a fragile mark that does not survive screenshots.
Does it work for PDFs? Yes, for PDFs marked from now on. A screenshot of roughly a quarter of a page or more can be checked; a crop of only a barcode or QR code is not detected.
Mark each copy before you share it
Create a free account. You can mark 5 files and see whose copy leaked.