Screenshots reveal more than you think
The dangerous part of a screenshot is rarely the middle — it's the edge. That's where the things you didn't mean to share sit:
- Name and address in the header of an invoice or app
- IBAN, balance, and transactions in banking screenshots
- Other open chats in the messenger overview
- Push notifications at the top of the screen
- Browser tabs and bookmarks with telling titles
- Autocomplete in the address bar
The best protection is therefore not redacting afterward, but: not capturing it in the first place.
Rule 1: cropping beats bars
What isn't in the image can't leak. Instead of painting over a sensitive area afterward (and risking that the bar doesn't cover or stays movable), crop the screenshot tightly so only the necessary section remains. The crop tool does this browser-local in seconds — the screenshot never leaves your computer. As a bonus, the image also gets smaller and clearer.
Rule 2: paint over what remains, opaquely
Sensitive spots in the middle of the image (an IBAN in the line above the error message) can't be cropped away. Paint over these opaquely — a full, opaque marker or filled rectangle, no semi-transparent color. Then save as a new file so the fill is burned firmly into the pixel image and doesn't stay a removable object. Why light pixelation isn't enough here is covered in Redacting faces and license plates.
Rule 3: mind the notification bar
Phone screenshots show the status bar at the top — and there, at the wrong moment, message previews pop up ("Mom: Are you …"). If you share screenshots regularly, briefly enable Focus / Do Not Disturb or hide notification previews. Alternatively, just cut off the status bar when cropping.
The special case: a photographed screen
Sometimes you photograph a screen with your phone instead of taking a real screenshot. Then the metadata note applies additionally: such photos carry GPS coordinates. So before sharing with strangers, check the metadata here too. A real screenshot (key combination or swipe gesture) is anyway the cleaner, sharper, and more data-thrifty choice — more on that in Optimizing screenshots.
The 30-second routine before sending
- Crop tightly — only the necessary section remains.
- Check the edges — header, notifications, other chats, tabs gone?
- Paint over interior data opaquely and save as a new file.
- Look at the finished image once before it goes out.
Frequently asked questions
What is most often shared accidentally in screenshots?
At the edge of the intended crop: names and addresses in headers, IBAN and balance in banking apps, other open chats in the overview, notifications at the top, browser tabs with telling titles, and autocompletions in address bars.
Is a black bar over the IBAN enough?
Only if it's opaque and saved firmly into the image. A semi-transparent marker the digits show through is unsafe. Safest is not to capture the sensitive area at all — crop tightly instead of painting over afterward.
Do screenshots contain metadata?
PNG screenshots contain hardly any classic EXIF data, but sometimes software notes; they usually reveal no location. Still, for screenshots you pass on, a quick look is worth it — especially because screens photographed with a phone very much do carry GPS data.
How do I redact a screenshot fastest and safely?
First, crop tightly so only the necessary area remains. Second, paint over any remaining sensitive spots with an opaque marker or filled rectangle. Third, save as a new file so the bars are burned in. Cropping first prevents most mishaps.
Sources
Apple — Markup and screenshots · NCSC — Staying secure online.