Can I just delete the post if I notice the leak too late?

You can delete your copy, but you cannot delete the internet's. A public post gets scraped, archived, quote-posted and screenshotted by other people within minutes. By the time you spot the stray detail, it may already sit in an archive or someone else's reply. Deleting removes your version, not the copies. The only reliable move is to clean the image before it ever goes up.

What do people most commonly forget to redact in a public post?

The corners. The point of the screenshot is in the middle, so attention goes there, while the edges quietly carry your username and handle, a notification preview, the other browser tabs you had open, the bookmarks bar, and sometimes a balance or order total. Follower counts and location hints in a weather widget or timestamp leak the same way, unnoticed because they were never the point.

Is cropping enough for a public post?

Sometimes, when the sensitive thing sits at the very edge and you remove it entirely. Cropping is great for trimming the frame down to just the point. But anything in the middle, a row in a list or a name next to the thing you are showing, cannot be cropped without cutting the context. For that, scrub it in place, then crop the frame tight around what is left.

How do I redact without uploading the screenshot to some website first?

Capture and clean on your own Mac in one pass, then post the result. With ScrubShot you press the shortcut, drag the Scrub tool over anything that is not the point to pixelate it into the image, crop the frame tight, then save or copy and post that. Nothing is sent to a server, so the only version that ever exists publicly is the cleaned one.

← Resources

Redact screenshots before posting them publicly

Short answer: clean the image before it goes up, because a public post is a different category from a chat message. The second a screenshot lands on X, Reddit, a forum or a blog, it can be scraped, archived, quote-posted and reverse-image-searched, all outside your control. Deleting the post later removes your copy, not the internet's. The safe workflow is one pass on your own Mac: scrub everything that is not the point, crop the frame tight, then post the cleaned version. Here is why public is its own risk, what tends to leak, and the loop that stops it.

A public post is not the same as a chat message

Posting a screenshot to a public timeline feels like the same gesture as pasting one into a group chat, but the audience and the lifespan are nothing alike. Chat has its own habits, which is why doing it before you paste into Slack or Teams is worth treating as a separate discipline. A public post goes further. It is open to everyone, not a known room of colleagues, and it gets handled by machines as much as by people.

Within minutes a public image can be scraped by an archive, quote-posted with your screenshot baked in, saved by anyone who saw it, and run through a reverse-image search that ties it to whatever else is online. Issue trackers carry a similar permanence on public repos, which is the subject of secure screenshot sharing for Jira, GitHub and Linear, but a social post adds reach: it is built to spread, and the more it spreads the less you can ever pull it back.

Deleting removes your copy, not the internet's

The instinct when you spot a stray detail is to delete the post and breathe out. It feels like an undo. It is not. Deleting takes down the one copy you control and leaves every copy you do not: the archive snapshot, the quote-post that embedded your image, the reply someone screenshotted, the search engine that already cached the page.

That is the core difference with public. In a chat you are at least dealing with a finite, known set of people. Once an image is out on the open web, the number of places it might live is unbounded and unknowable. So the only point you genuinely control is before you press post. Clean the image first and there is nothing for the archives to keep.

What leaks in a "look at this" post

The typical public screenshot is a "look at this" post: an app you want to show off, a funny reply, a bug, a chart. Your eye is on the middle of the frame, which is exactly why the edges get you. The leak is almost never the thing you meant to share. It is grouped by where it hides:

Where it hides	What tends to leak	The fix
Corner of the OS	A notification preview sliding in, the clock and date, a battery or location hint, the menu bar showing what else is running.	Scrub the notification and any corner widget, or crop the frame so the OS chrome is not in shot at all.
Browser chrome	Other open tabs and their titles, the bookmarks bar, an autofilled address, a saved-password prompt.	Scrub the tab strip and bookmarks bar, or capture and crop to just the page content below the chrome.
The app itself	Your username and handle in the corner, a balance or order total, a follower count you did not mean to share, another person's name in a sidebar.	Scrub each one in place so the surrounding context survives but the number or name does not.
Notifications	A message preview, a sender's name, a verification code or one-time passcode that happened to arrive while you captured.	Scrub the whole banner. A code is live until it expires, so treat it as urgent and do not post the raw shot.

The trap that makes all of these worse is zoom. A detail that is an unreadable smudge in your timeline is perfectly legible the moment someone taps the image and pins it open. You cannot rely on small to mean safe. If a value is in the frame, assume it can be read, and decide on purpose whether it should be.

The workflow: scrub, crop, post the clean version

The whole thing works because the cleaning happens in the same pass as the capture, before anything is posted. With ScrubShot the loop is short enough that you do it every time instead of meaning to:

Press the shortcut. ScrubShot captures the screen you are looking at.
Drag the Scrub tool over everything that is not the point: the handle, the balance, the notification, the open tabs.
Tap the image open in your head, or actually zoom in, and scrub anything that becomes readable up close.
Crop the frame tight around the thing you are showing, which removes whole regions of chrome in one move.
Use the Marker to circle the point or Text to label it, then save or copy and post that cleaned version.

The Scrub tool pixelates straight into the image, so a scrubbed area cannot be lifted off or sharpened back by anyone who saves your post or runs it through a tool. The blocks are random samples of the region's colors rather than averages, so there is nothing for a depixelation attempt to reconstruct. There is Undo if you over-scrub before you post. None of it touches the network, and that matters most here: a tool that uploads your screenshot to redact it would send the unredacted original to a server first, which is the opposite of what you want before going public. The reasoning behind keeping the whole loop on-device is laid out in the guide to redacting screenshots without uploading them.

The cleaned image is the only version that should ever exist publicly. Not the original sitting in a folder, not a half-redacted draft, just the one you posted on purpose. Make that the default and the question stops being "did I catch everything before I deleted it" and becomes "is this frame ready", which is a question you get to answer calmly, before anyone is watching.

FAQ

Can I just delete the post if I notice the leak too late?: You can delete your copy, but you cannot delete the internet's. A public post gets scraped, archived, quote-posted and screenshotted by other people within minutes. By the time you spot the stray detail, it may already sit in an archive or someone else's reply. Deleting removes your version, not the copies. The only reliable move is to clean the image before it ever goes up.
What do people most commonly forget to redact in a public post?: The corners. The point of the screenshot is in the middle, so attention goes there, while the edges quietly carry your username and handle, a notification preview, the other browser tabs you had open, the bookmarks bar, and sometimes a balance or order total. Follower counts and location hints in a weather widget or timestamp leak the same way, unnoticed because they were never the point.
Is cropping enough for a public post?: Sometimes, when the sensitive thing sits at the very edge and you remove it entirely. Cropping is great for trimming the frame down to just the point. But anything in the middle, a row in a list or a name next to the thing you are showing, cannot be cropped without cutting the context. For that, scrub it in place, then crop the frame tight around what is left.
How do I redact without uploading the screenshot to some website first?: Capture and clean on your own Mac in one pass, then post the result. With ScrubShot you press the shortcut, drag the Scrub tool over anything that is not the point to pixelate it into the image, crop the frame tight, then save or copy and post that. Nothing is sent to a server, so the only version that ever exists publicly is the cleaned one.

Try it

ScrubShot is a Mac app built for exactly this: press the shortcut, scrub everything that is not the point straight into the image, crop the frame tight, then save or copy and post the cleaned version. It is the only copy that ever leaves your Mac. There is a free 7-day trial with no card required. After that it is $30 once.

Try ScrubShot free →