Blur a screenshot online

What leaked in a snip I took for this page

I captured a dummy support ticket with Win + Shift + S. The ticket body was clean. The leftover frame had an unread badge, a calendar toast, and a second customer email in a Gmail peek. Cropping the toast was enough. The email sat in the middle of the window I needed to keep, so I barred it.

That split is the job on this page: throw away chrome you do not need, then paint over secrets that sit inside the rectangle you must send. Crop vs black bar walks through when each move is enough.

What usually needs covering in a screenshot

The thing you meant to share is rarely the only thing in the frame. A screenshot captures whatever the window had open at that moment, and the parts that leak tend to be the parts you stopped noticing months ago.

• Email addresses in a sidebar, an inbox list, or a quoted reply below the message you actually care about.
• One-time codes and verification numbers, which are short enough to guess back from a light blur.
• Account numbers, card digits, invoice totals, and salary columns in a spreadsheet.
• Tokens and keys sitting in the browser address bar or a terminal scrollback.
• Real names and profile photos of people who are not part of the conversation you are forwarding.
• Notification banners that slid in mid-capture, plus taskbar and menu-bar badges around the edge of the crop.

Online does not have to mean uploaded

Most free screenshot redactors work the same way: you send the image to a server, a worker blurs it, and a link comes back. That is fine for a meme and wrong for a payslip. The original, the one that still has the secret in it, is the copy that travelled.

A browser can do the whole job locally. It decodes the image, draws it onto a canvas, lets you paint over regions, and hands you the result as a download without a single network request carrying your pixels. That is what this page does. If you want proof rather than a promise, the Network panel in DevTools will show you.

Pick the right cover for what you are hiding

Blur and a black bar are not interchangeable. Blur keeps the original pixels and smears them, so the information is still in the file in a degraded form. For a face in a crowd that is enough. For a six-digit code it is not, because there are only so many candidates and the shape of the digits survives.

A black bar replaces the pixels with flat colour. Nothing is left to recover. Use it for every short string that would matter if someone guessed it correctly, and use blur for the softer cases where you only need “not identifiable at a glance.” Passwords, API keys, and account numbers have their own walkthrough on the sensitive text tool.

Cropping is the third option and often the best one. If the secret sits in a corner, cut the corner off rather than painting over it. There is nothing to reverse in pixels that are no longer in the file.

Capture first, then redact

Your operating system takes the screenshot; it does not clean it. On Windows, Win + Shift + S gets you the snip, and Snipping Tool will crop and annotate but has no reliable blur brush. On Mac, Preview Markup can place a filled shape. On a phone, Photos Markup works if you use an opaque shape rather than the highlighter.

Whatever you capture with, finish the redaction before the file leaves your device, and attach the export rather than the original that is still sitting at the top of your recents.

Platform walkthroughs: Windows, Mac, iPhone, Android, and Snipping Tool.

Check the export before you send it

Open the downloaded PNG at full size and look at it properly. A box that covered the text in a small preview can leave a character sticking out at full resolution, and a blur that looked heavy on a phone screen can read clearly on a monitor.

Then check that you are attaching the right file. Sending the original by accident, because it is the newest item in the folder, is a more common failure than a weak blur.

For other kinds of files, the how to blur hub covers photos, faces, backgrounds, and video.