How to blur or redact sensitive info in a screenshot, the safe way

A screenshot is a copy of everything on the screen, including the parts you did not think about: the email subject in another tab, an API key in the terminal scrollback, a customer's name in a sidebar. Redacting before sharing is a two-minute habit, but only if you use the right kind of redaction, because the intuitive choice, a soft blur over the secret, is the weakest one.

The three moves, and when each is right

Crop when the sensitive part sits at the edge of the frame. It is the cleanest option because the pixels are removed entirely, and on this site the crop step happens before upload, so the trimmed region never leaves your machine.

Cover with a solid shape when the secret sits inside the area you need to keep. An opaque rectangle destroys the information underneath it. There is nothing to reconstruct.

Blur the whole image when the content should be unreadable but the shape should survive, like a dashboard used as a background illustration. That is a different job from hiding one field, and it is the job the blur tool here is built for.

Why a light blur is not a redaction

Blur and pixelation do not delete information, they smear it. Enough of the original survives that reconstruction is sometimes possible, and this is not theoretical: researchers and hobbyists have repeatedly recovered text and numbers from pixelated screenshots, because text drawn in a known font at a known size gives an attacker a small search space. Tools built for exactly this job have been public for years.

The rule that follows is simple. For a password, a token, a name, an address, anything that is text, use an opaque bar at 100 percent opacity, not a blur, not a highlighter at 80 percent, and not a swirl effect, which is famously reversible. Blur is for making things illegible at a glance, not for defeating someone motivated.

The markup tool you already have

• iPhone and iPad: take the screenshot, tap the preview thumbnail, and you are in Markup. Pick the shape tool, draw a rectangle, set its fill to solid black, and drag it over the secret. Filled shapes here are fully opaque.

• Android: open the screenshot in Google Photos and hit Edit, then Markup. The pen at full width, drawn over the field a few times, gets to full coverage. Some manufacturer editors, like Samsung's, include proper shapes.

• macOS: open the capture in Preview, then Tools and Annotate. Draw a rectangle and set the fill color to black. Preview's shapes are opaque by default.

• Windows: after Win+Shift+S, open the capture in Snipping Tool from the notification. The pen at a wide setting covers a field in a couple of strokes.

One habit worth adding: after saving, zoom in on the covered area once. The mistake people actually make is not a weak tool, it is a bar that missed two characters at the end of the token.

What actually leaks in screenshots: a checklist

The secrets people redact are rarely the ones that leak. The leaks come from the frame around the content, the parts your eyes have learned to skip. Before sharing, scan the edges for these:

• The taskbar and dock: pinned apps, a company chat icon with an unread count, the clock proving you took this at 2 a.m.

• Browser chrome: your profile avatar and name, bookmark names, the titles of every other open tab, autocomplete text sitting in the address bar.

• Notification popups: the classic. A message preview slides in during the capture and ships a stranger's words with your screenshot.

• Terminal prompts: username, hostname, and working directory, in every single frame of scrollback.

• Sidebars in work tools: channel lists, customer names, and calendar entries along the edge of the app you actually meant to show.

The cheapest fix is to capture tight in the first place, a region shortcut around exactly the content, so the frame never enters the file. The shortcut reference lists the region capture for every platform.

Flatten before you share

Redaction fails in a second, sneakier way: annotation layers. Some editors store your shapes as objects on top of the image rather than baked into it, and formats like PDF keep those layers separate, which is how redacted documents keep ending up in the news. Screenshots exported as PNG or JPEG are flattened by definition, so the fix is simply to share the exported image, not the editor's project file, and not a PDF with a rectangle drawn on it.

Pixels are not the only leak

A screenshot's metadata is thin, usually just dimensions and a timestamp. A camera photo is a different story: it can carry the GPS coordinates of where it was taken, the device model, and the exact capture time in its EXIF block, all invisible in the image itself. If what you are redacting is a photo rather than a screen grab, read the EXIF guide before sharing, because a blacked-out street sign does not help if the file still says where you were standing.

Match the effort to the audience

Redaction has a threat model, and it changes with where the image goes. A screenshot for an internal ticket, seen by colleagues who already have access to the system shown, mostly needs notification popups and unrelated customer data cleaned up. A screenshot going into a public forum post, a tweet, or a blog deserves the full pass: edges checked, identifiers covered with solid bars, and a zoom-in on every covered area before posting, because the public version is permanent the moment someone else saves it.

If you share screenshots often, make the tight-capture-then-check routine a habit rather than a decision. Habits survive busy days; decisions do not. Ten seconds per screenshot is the entire cost, and one prevented leak pays for years of it.

Then share the safe version

Once the image is clean, share the redacted export the same way as any screenshot: paste it on the home page, crop if the framing needs it, and send the link. For anything sensitive, the 7-day expiry on anonymous uploads works in your favor, and the share page's delete button ends the link the moment the conversation is over, as covered in the delete guide.