How to Hide Personal Data in a Screenshot of a Chat or Inbox

You wanted to show one message

You need a colleague or a client to see one line. Confirm what was agreed. Show exactly how the customer phrased it. Pass a complaint on to whoever handles complaints.

So you screenshot the window. And along with the message you meant to show, off goes everything else that was on screen:

• The conversation list down the side — the names of everyone you correspond with.
• The message preview under each name, which is reliably the most interesting fragment of each one.
• Unread counts, quietly showing who you have been ignoring and for how long.
• Other browser tabs, with the subject lines of other emails in them.
• A notification that arrived while you were lining up the shot.
• The search box, still holding whatever you last looked for.

One message — and beside it your entire working day, in other people's names.

Why cropping loses the point

With most documents you could argue for cropping. With a conversation you usually can't, because in a conversation the context is the evidence.

A single message on its own proves nothing. You need to see who wrote it, when, and what it was answering. Crop down to the one line and you have removed exactly the part that made it worth sending — and invited the reply "yes, but what was that in response to?"

Look at what actually has to survive in the picture above. The name at the top, so it is clear whose conversation this is. The date, because the whole question is which day was agreed. The message that confirmed it. And the reply four lines further down, because a confirmation nobody answered is not an agreement. Four small things, scattered down the window — and between them, a note about a different customer's unpaid invoice and somebody's phone number.

That is the shape of the problem: not one block to keep, but a mosaic. No rectangle contains it. If the lines you need happen to sit next to each other, crop them and you are done — genuinely, no tool required. It is when what you need is scattered, and what you must not send is mixed in between, that cropping runs out.

The free way, and where it stops

On Windows 11 (build 24H2 and later) the Snipping Tool can do part of the job:

1. Open the Snipping Tool from the Start menu.
2. Click New and drag across the window. The capture opens in the Snipping Tool, ready to work on.
3. Click Scan Text.
4. Quick Redact — email addresses and phone numbers go immediately.
5. Everything else: select it by hand and choose Redact.

Useful, and in an inbox it earns its keep straight away, because email addresses are everywhere and it removes all of them in one click.

Then it stops, and here the limit is starker than in any other kind of screenshot. A contact list is a list of names, and a name has no pattern. There is nothing in "Elena Rossi" for the software to catch hold of — it is text, exactly like the menu above it. The single most exposing thing on the screen is the one thing automation cannot see.

So you are covering the sidebar by hand: four names, four previews, two unread badges, the search box, and the notification that appeared in the corner. Every time. On a screen that looks different every time.

Hide the window, reveal the thread

The other way round: the capture opens with the whole window hidden, and you brush over the two or three messages the other person actually needs to read.

The sidebar stays hidden because you never went near it. So does the notification, so does the search box, so do the two messages in the middle, the ones about a different customer and somebody's phone number. Not because you remembered them — because forgetting isn't a move that exists. You aren't covering anything; you are revealing four small things and leaving the rest alone.

And a mosaic is exactly what a brush is for. Four scattered spots is four strokes, in any arrangement, without ever asking whether the shape you need is a rectangle.

This is the case where the inversion pays off most, for a simple reason: the ratio. In a chat window almost everything on screen is somebody's private business and almost nothing is what you wanted to show. Covering fifteen things and revealing three is the same job from opposite ends, and only one of those two has a silent failure mode.

And none of it leaves your machine — no cloud, no upload, no account. For a screenshot of somebody else's messages, that is not a small detail.

Can what you hid be recovered?

Fair question, and the answer is easy to check for yourself: blur something and try to undo it with whatever you can find online. No ordinary web tool will bring it back.

What is hidden has been baked into the pixels — there is no layer on top to peel away, and no original hiding inside the file.

Anyone who would genuinely set out to reconstruct an image came for that specifically, and if somebody has targeted you to that degree, a screenshot you forwarded is not your weakest point.

That said, given how far chat screenshots travel, this is the one kind where the frosted glass mode earns its place: hidden areas are replaced with a plain sheet rather than blurred, so nothing left in the file is derived from what was hidden at all.

A quick check before you send

• the conversation list and every preview under it;
• unread badges and status dots;
• the search box, and whatever is still typed in it;
• the notification corner;
• the window title, which often carries the contact's name;
• the messages immediately above and below the ones you meant to show;
• your own profile picture and name in the corner, if that matters here;
• browser tabs, if the chat is in a browser.

Why I built this

This is the case I run into most often myself.

Not because it is hard — because of when it happens. It is always squeezed between other things. Grab the shot, paint over here, strike out there, crop that off, send, back to work. Thirty seconds, in the middle of something else, which is precisely the state in which people miss things. We're not machines, and the fifteenth screenshot of the day does not get the attention the first one did.

What made me actually build something was not the miss itself. It was the minutes afterwards — already sent, hunting for whether it can still be unsent, counting how long it has been there and hoping nobody has opened it yet.

More about why I built BlurSnap →

Related: hiding client names in a screenshot and what Windows can already redact for free.