Every other page on this site starts from an image that already exists, as a permanent file, and asks how to cover what's sensitive inside it before you send it somewhere. This page starts one step earlier, with an image that was never supposed to become a permanent file at all. Disappearing messages, vanish-mode chats, and view-once photos are built around a promise: the sender shows you something once, on their terms, and then it's gone. The moment you screenshot or screen-record it, you've already broken that promise, independent of anything you do to the resulting file afterward.
That makes this a different kind of problem from anything else here. Every technique page on this site assumes the person capturing the image and the person it's about are either the same person, or someone who's agreed to be in the frame. A disappearing message flips that: the sender actively chose a feature designed to prevent the exact thing you're doing, and on several platforms their app tells them when you do it anyway. Redacting what you captured is still worth doing if you're going to keep it — it protects whoever you eventually show the saved copy to. It just doesn't touch the first, separate question, which is whether keeping a copy was something you should have done at all.
How It Works
1
Open
Drop your image in or paste from clipboard.
2
Pick Mode
Black Box, Blur, or Pixelate.
3
Select Areas
Rectangle, oval, or freehand lasso — then hide what you selected.
4
Download
Hit Download PNG. Done.
SquooshNeed to shrink your image after editing? Squoosh is a free browser-based image compressor with no upload required.
Visit Squoosh →
Guide
One sentence carries this page: covering what's sensitive in a saved copy protects whoever eventually sees that copy, but it does nothing about the separate fact that you turned something the sender meant to disappear into a file that doesn't.
Why this image started differently from every other one on this site
Everywhere else on this site, the image you're editing already exists as an ordinary file before you open it, and the only question is how to cover what's inside it. A disappearing message, a vanish-mode chat, or a view-once photo is built around the opposite default: the platform tries to make sure no ordinary file is ever created from it. The sender picked that feature on purpose, usually because they wanted to show you something without it becoming a thing that sits on your device, gets forwarded, or turns up again later. A screenshot or screen recording is the act that converts their one-time show into exactly the kind of permanent file they chose that feature to avoid. That conversion already happened by the time you open an editor; redacting only decides what the resulting file looks like from that point forward.
What capturing it actually sets off
Specific behavior varies by app and changes over time, so check the current behavior of whichever app you're using rather than assuming either way — but the general pattern reported across several popular platforms is consistent enough to describe. Apps like Snapchat, and Instagram's vanish mode and disappearing direct-message photos and videos, are widely reported to send the other person a notification when a screenshot or screen recording of that content is detected; Instagram's own help documentation for vanish mode states that you'll receive a notification if someone screenshots or screen-records a message in that mode. Other platforms handle it differently: WhatsApp's View Once media has been reported to block the screenshot attempt itself, showing a blank or black result instead of letting the capture through and notifying anyone afterward. The common thread is that these features are usually built to make captures visible to someone, in one way or another, rather than treating them as invisible by default. Don't assume silence means no one was told; the notification you'd see, if there is one, lands on the sender's device, not yours.
Redacting answers a different question than capturing does
These are genuinely two separate decisions, and it's worth keeping them that way instead of letting a good answer to one stand in for the other. The first decision is whether to capture and keep the content at all, which is a question about the sender's expressed intent and whatever trust is involved in the conversation — redaction has nothing to say about it one way or the other. The second decision, and the only one this editor can help with, is what to do with the file once it exists: who else might see it, and whether anything inside the frame identifies a third person or some other sensitive detail that has nothing to do with why the message was sent as disappearing in the first place. A careful cover on the second question is a real improvement. It isn't a substitute for having answered the first one honestly, and it doesn't make the capture retroactively consistent with what the sender asked for when they chose a feature built to prevent it.
If you decide to keep it, that decision has its own obligations
There are legitimate reasons people keep a screenshot of something that was supposed to disappear: documenting a threat, a boundary violation, or harassment is the clearest one, and it's reasonable to prioritize your own safety or a necessary record over a feature's design intent in that situation. Even then, the honest version of that choice usually involves being direct about it rather than quiet about it — many of these platforms' own notification systems will tell the sender regardless of what you do next, so treating the capture as secret when the app itself may not be keeping it secret tends to create a worse version of the conversation than simply being upfront would have. If your reason for keeping the image doesn't rise to that level — curiosity, convenience, wanting a copy "just in case" — that's worth sitting with honestly before you redact anything, since no amount of careful covering changes what the capture itself represents to the person who sent it.
A practical ordering
Decide whether you're keeping this before you touch the editor at all, and be able to say why in one sentence; if you can't, that's usually itself the answer. If a platform blocks the capture outright rather than notifying anyone, treat that as a deliberate boundary rather than a bug to route around with a second device photographing the screen, which produces a worse file through reflections and moire while still working against the sender's original intent. If you do keep a copy, redact anything inside the frame that identifies a third person or exposes a detail unrelated to your reason for keeping it, using Black Box for anything you need fully gone rather than Blur or Pixelate, which are built to preserve the coarse shape of what they cover. Store the finished file somewhere you control rather than somewhere it could recirculate casually, and if the situation calls for it, tell the sender you kept it rather than relying on their app to do that telling for you.
What this editor does and does not do here
No knowledge of where the image came from. There's no network code anywhere in the editor — no fetch, XMLHttpRequest or WebSocket call — so it has no way to know whether the file you dropped in started as a disappearing message, an ordinary photo, or anything else, and no way to tell whether a notification already fired on someone else's device before you ever opened this tab.
Regions only, applied destructively. Three modes, Black Box, Blur and Pixelate, across three shapes, painted directly onto the canvas; there's no detection of faces or text and no whole-image operation of any kind.
No crop, resize, or rotate. The canvas is created at the source image's exact pixel dimensions, so the frame you load is the frame you export.
One file at a time, with no memory between them. Loading a new image resets the undo history immediately with no prompt, so download one finished file before moving to the next.
Nothing leaves the browser. There's no upload step and no storage of any kind; the image exists only in this tab until you download it or close the page.
Your clipboard still holds the original. If you pasted the capture in with Ctrl+V, there's no clipboard-write code in the editor, so pasting again anywhere else sends the unredacted version, not your covered export.
Common mistakes and misconceptions
"Disappearing messages are private, so no one will know I kept one." On several widely used platforms, the app itself tells the sender when a screenshot or screen recording is detected. Whether or not you redact what you captured, that notification, if the platform sends one, already happened at the moment of capture.
"Screen recording instead of screenshotting gets around the notification." Not reliably. At least one platform's own help documentation describes screenshots and screen recordings of vanish-mode content the same way for notification purposes, and people who've tested this report the same result. Treat it as unverified rather than as a known trick.
"Once I've covered the sensitive part, I've handled the situation responsibly." Covering a detail inside the frame handles what a later viewer of your saved copy can see. It doesn't address whether making that saved copy was the right call in the first place, which is a separate question redaction can't answer for you.
"If the platform blocked my screenshot, there's nothing I can do, so photographing the screen with another phone is a harmless workaround." It produces a file, but a lower-quality one, through a problem this site covers separately — reflections and the display's own pixel grid interfering with the camera's. It also still works against the reason the platform blocked the capture in the first place.