Guide
Start with the asymmetry that makes this worth its own page: a technique failure is a partial disclosure, an omission is a total one. If a blur is too weak, an opponent has to work to pull something back out of it, and what they get is degraded. If a region was never covered, there is nothing to pull — it is published, in full, at the resolution of the original, and it will still be there years later in whatever copy the image ended up in. The two failures are not in the same class, and yet essentially all of the effort and all of the advice goes to the first one.
The reason is that covering is a satisfying task and searching is not. Covering has a visible result: a black rectangle appears where the account number was. Searching for what you have not yet thought of produces nothing to look at, has no natural end, and feels finished long before it is. So people do the part with the feedback and skip the part without it.
Why frames get missed
Three things work against you, and none of them are carelessness.
You did not compose the frame. A screenshot is composed by the operating system and whatever was open at the time. A photograph of a document is composed around the document, with the rest of the desk arriving as a side effect. In both cases most of the pixels are there by accident, and accidental content is exactly the content you have no mental inventory of. When you go to share it, you are not reviewing a picture you built; you are reviewing a capture of a moment, and the moment included things you were not thinking about.
Attention follows intent. You opened the image for a reason — to show the error, the amount, the damage, the listing — and that reason directs where you look. Everything else is peripheral in the literal sense. This is why the same person who would never post their home address will happily post a screenshot with a mail app open in the background: they were not looking at the background, they were looking at the thing they meant to show.
Finding one thing feels like finishing. Once you have identified something to cover, a switch flips from searching to doing. You draw the box, you feel the task complete, and the second thing in the frame never gets found. The effect is strongest when the first thing is obvious, which is the usual case — a face, a card number, a name at the top of a letter.
None of that is fixed by trying harder or by being the kind of person who is careful. It is fixed by not relying on noticing.
The sweep
The whole idea is a route you walk every time, in the same order, whether or not you expect to find anything in each stop. Six passes, roughly thirty to sixty seconds on a screenshot.
- Look at it at full size first, somewhere you can zoom. Before you open any editor, view the file at one hundred percent or larger in whatever image viewer you already have. This pass is only about reading — you are finding out what is actually in the file, at the resolution a recipient will have. Small text that is illegible on a scaled-down view is fully legible to anyone who zooms, and the file does not know the difference.
- Sweep the edges before the middle. Start with the outermost band of the image and work inward: the top strip, the bottom strip, then the two sides, then the centre. The middle is where the thing you meant to show lives, and if you start there you will not leave. The edges are where the operating system, the browser and the room put everything you did not choose.
- Run the category list. Six families, below. The list matters more than the order within it, because each family is a different kind of thing and you will not think of a family you are not prompted with.
- Cover what you found, then sweep again with the boxes on. The second pass is the one that pays. With the obvious item now a black rectangle, it stops absorbing your attention and the rest of the frame becomes visible in a way it genuinely was not before. Most second finds come from this pass.
- Ask the stranger question. Not "is there anything secret here" — almost always no — but "what could someone who does not know me work out from this, if they cared?" Those have different answers. The first asks about secrets, the second asks about identification, location, employment, schedule and association, which is what most images actually leak.
- Re-check at full size before you export. Same as step one, on the edited image. This catches boxes that landed short and regions you covered in the scaled view without seeing exactly where the edge fell.
The six families
1. Window and system chrome. Everything the application and the operating system drew around your content. Browser tab titles, which name documents and customers with no prompting. The address bar, which can carry account identifiers, search terms and query strings. Bookmark bars. The window title and any visible file path, which often contains a person or a client or a case name. The application sidebar: workspace names, channel lists, folder names, other people in the list. Notification banners that arrived mid-capture. The clock, the date, the battery, the network name. The taskbar or dock, which says which applications you run and often how many unread items each has. Your own avatar and account initials in the corner. This family is the biggest single source of misses because it is not content, so it does not read as information.
2. Reflective and secondary surfaces. In photographs: glasses, monitors, television screens, glossy table tops, framed pictures, windows at night, mirrors, a phone in someone hand, polished metal. A reflection is usually low resolution and low contrast, which makes it easy to dismiss, but a reflected screen showing a messaging app or a document is a real capture of that content, and the frame that includes it is the only place it exists. The same applies to a second display visible behind the subject.
3. Paper and objects in the background. Envelopes and mail, which carry a name and address. Shipping labels and delivery boxes. Prescription and medication labels. A wall calendar, which is a schedule. A whiteboard. Book spines and course materials, which carry a surprising amount about occupation and affiliation. Keys. A lanyard. A sticky note near a monitor, which is the joke that keeps being true.
4. People, beyond faces. Faces get remembered; the rest does not. Name tags and conference badges. Uniforms and employer logos. Tattoos and distinctive jewellery. A cast or a visible medical device. A school uniform on a child, which locates the child. Hands holding a document. And in group photos, the people at the edges who were not the point of the picture and whose presence in that place at that time may matter to them even if it does not to you.
5. Metadata rendered into the image. Not file metadata — the timestamps and identifiers that applications print on screen. Message timestamps and read receipts, which establish a schedule. Presence indicators. Member and participant counts, which can identify a small group precisely. Document footers reading last modified by, with a name. Version strings, internal reference numbers, seat and desk numbers, licence identifiers. Any of these can be the most identifying thing in a frame while looking like furniture.
6. The container itself. Sometimes the disclosure is not in the frame but is the frame: which application this is, which portal, which private community, which internal tool. A screenshot that reveals you hold an account somewhere can matter more than anything visible inside it, particularly for health, legal, financial, employment or membership contexts. This is the one family where the answer is often not a black box but a decision to describe the thing in words instead of showing it. Redacting background detail that can doxx you works through the physical-room version of this problem in depth; the same reasoning applies to the software room you are standing in when you take a screenshot.
Reduce the search area before you search it
The sweep gets easier the less there is to sweep, and the cheapest move available is to capture less in the first place. A region-limited capture — dragging a selection around just the panel you need, rather than grabbing the whole screen and covering the rest — removes an entire class of risk, because content that was never captured cannot be missed, cannot be covered badly, and cannot be recovered from the file. That is a stronger guarantee than any redaction, and it costs a second.
The same logic applies after the fact, with one important limit: trimming the outside of an image removes what is outside and nothing else. It is genuinely useful when the sensitive material is at the edges, which for screenshots it very often is. It does nothing at all when the sensitive material sits next to the thing you are trying to show, which for photographs of documents it very often does. So use it to shrink the problem, not to solve it, and run the sweep over whatever survives.
And when a frame is dense with things that need covering, consider whether the image is the right way to send this at all. Three covered regions is a sign the capture is too wide. Six is usually a sign that a sentence of text, or a fresh screenshot of just the relevant panel, would carry the same information with none of the risk.
What the editor on this page shows you, and what it does not
Everything in this section is how the tool above actually behaves, read from its own code, and it matters for the sweep specifically because it changes what you can see while you work.
The view is scaled down; the file is not. When an image loads, the canvas is set to the image true pixel dimensions, and every edit is applied at that resolution. What you see is that canvas fitted to the width of the panel, so a wide screenshot is displayed at a fraction of its real size. Small text may be unreadable to you on screen and perfectly readable in the exported file. This is why the inspection pass belongs in a viewer where you can zoom, and the drawing belongs here. Do not use how legible something looks in the editor as evidence that it is safe.
Tall images scroll, and the export is the whole canvas. The editing panel is height-limited with its own scrollbar. Load a long capture — a full-page screenshot, a long thread, a receipt — and you can cover the part you were thinking about and press Download while the lower part of the image has never once been on your screen. Nothing warns you. Scroll the image from top to bottom before exporting, every time, and watch for elements that repeat down its length, because each repetition is a separate region needing its own box.
Your pointer precision is coarser than the preview suggests. Because the canvas works in real image pixels while being displayed scaled, one pixel of mouse movement can cover several image pixels. A box that looks flush with the edge of a character on screen can land short in the file. Overshoot deliberately: extend past the text on both sides and into the line spacing above and below.
Very small drags are discarded without telling you. A rectangle under about four image pixels in either direction, or an oval under six, is thrown away rather than applied, and the only feedback is the dashed outline vanishing. Three points are required for a lasso. If you tapped a tiny box over something and moved on, check that it is actually there.
Adding coverage is free right up until you export. Covering is painted onto the working canvas, Undo steps back through saved snapshots, and Clear redraws from the original image the page is still holding. Download writes out whatever the canvas currently shows as a freshly encoded PNG, and you can press it more than once in a session. So there is no cost to covering something you are not sure about and no cost to a second sweep — the only expensive discovery is the one you make after the file has been sent. How much of a field to leave showing once you have found it is a separate decision, covered in partial redaction: how much can you leave visible.
All of this happens on the device the image is already on. The page reads the file in your browser, draws it into a canvas and hands the result back as a download; nothing about the picture reaches this site, and there is no account or history for it to sit in. The working copy exists only while the tab is open.
Common mistakes and misconceptions
"I looked at it." Looking is intent-driven and stops when it feels done. A sweep is a route. The entire value of the procedure is that it continues past the point where you stopped noticing, and it takes under a minute.
Judging legibility from a scaled-down view. If you cannot read it in a fitted preview, that is a fact about your screen, not about the file. Anyone who receives the image can zoom.
Sweeping the content and skipping the chrome. Tabs, titles, sidebars, paths, clocks and notification banners are not the subject of the screenshot, which is exactly why they are invisible to the person taking it and obvious to everyone else.
Assuming a low-resolution or small image is self-protecting. Resolution is what it is in the file. A phone screenshot is not low resolution, and scaling an image down after the fact is not a redaction technique — it degrades everything except the part you wanted to remove, which often survives well enough to read.
Sweeping once, before you start editing. The first pass is run with your attention fixed on the obvious item. Run it again after that item is covered; that is where the second find comes from.
Applying the sweep to your own captures but not to received ones. An image someone forwarded to you gets less scrutiny than one you took, because it arrives already framed as a finished thing. It has had exactly as much review as its sender gave it, which may be none, and if you are the one about to publish it, their sweep is not a substitute for yours.
Trusting that a miss can be fixed quietly later. Replacing a released image with a better-covered version does not retract the first one, and a file that has already been forwarded, cached or downloaded is out of reach. The sweep is cheap precisely because it happens before that becomes true.