You screenshot an error message and post it in a public forum. Helpful strangers see the error — and also your full name in the menu bar, your employer's wiki in the open tabs, and a password reset email popping into the notification corner. Screenshots overshare by default.

The Six Zones to Check Before Sharing

  1. Window title and menu bar — account names, file paths with your username.
  2. Browser tab strip — every open tab's title is readable.
  3. URL bar — internal hostnames, session IDs and tokens in query strings.
  4. Notification corners — message previews love to arrive mid-screenshot.
  5. Taskbar / dock — reveals your tools, chat apps and running software.
  6. The content itself — emails, order numbers, phone numbers, API keys in code.

Crop First, Redact Second

The safest redaction is *absence*: crop the screenshot down to the region that matters. What isn't in the file can't leak — and a tightly-cropped screenshot is also easier for readers to understand. An in-browser crop tool handles this in seconds without installing anything.

For sensitive bits *inside* the needed region, cover them:

  • Solid black (or white) rectangles are the gold standard. Fully opaque, nothing to recover.
  • Avoid mosaic/pixelation and light blur for text. Researchers have repeatedly shown that pixelated text can be reconstructed by trying character combinations against the mosaic pattern. Blur is obfuscation, not redaction.
  • Never rely on annotation layers. Some apps save the "black box" as a removable layer or a semi-transparent highlight — export a *flattened* image and check the result pixel by pixel.

Watch the Metadata Too

A screenshot file itself is usually clean of GPS EXIF (unlike camera photos), but the *filename* can leak ("Screenshot 2026-07-21 at 09.12 – payroll-review.png"). Rename before uploading. If you're sharing a camera photo rather than a screenshot, strip EXIF as well — location data rides along silently.

A Two-Minute Habit

Crop to the essentials → black-box what remains → flatten and re-check the corners → rename the file. All four steps run locally in a browser; the screenshot never needs to touch a third-party server *before* you've sanitized it — which is precisely the moment it's most dangerous. Make the checklist a reflex and screenshots become the safe, fast communication tool they were meant to be.