A crop isn't always a clean cut
When you crop a screenshot to hide a name, a balance or a face, you expect the hidden part to be gone. Some screenshot editors have saved the new, smaller image but left the old bytes in the file — so the part you cut out can still be read from the raw file, even though it doesn't show when you open it normally.
This checks your file for that leftover data and tells you plainly whether it's there. If it is, one button gives you a clean copy: the picture you can see, re-encoded fresh, with the leftover run and all metadata dropped.
Share the clean copy, not the original
The clean copy is built by decoding only the visible picture and encoding it again, so there is nothing left over to leak and no camera or location data attached. It's the version that's safe to post or send.
Questions
Does my photo get uploaded?
No. The picture is read, grown and encoded by code running in this browser tab. It is never sent to a server — there is no server to send it to. The only download that ever happens is the optional edge-painter model, which travels one way, from our model file server to you.
How can a cropped image still contain what I cut?
A few editors wrote the smaller image into the file but didn't remove the old bytes after it. Those bytes are ignored when the picture is displayed, but they're still in the file and can be read.
Which screenshots were affected?
Certain phone and desktop screenshot editors from around 2023 had this behaviour. The safest move with any older cropped screenshot you're about to share is to check it here and send the clean copy.
What does the clean copy remove?
Everything except the visible picture: the leftover run after the end marker, any embedded preview, and all EXIF, GPS and camera metadata.