How to Redact & Blur Sensitive Information in Screenshots
Why translucent markers fail at redaction, the difference between Gaussian blur and pixelation, and how to obscure credentials and personal data safely.
Screenshots are the universal language of technical support, bug reports, documentation, and social media. They are also the easiest way to leak something you did not mean to. An API key. A customer’s email. A credit card number. A proprietary URL. The common redaction methods, scribbling with a marker or drawing a box, often leave the text fully recoverable.
Knowing how to redact properly is not a neat trick. It is a security practice, and the tools matter as much as the technique. This is why common methods fail, what actually works, and how to do it without sending your unredacted screenshot to a server.
Why Markers and Boxes Fail
The default markup tools in iOS, Android, macOS Preview, and Windows Snipping Tool are built for annotating, not redacting. Their brushes use anti-aliasing and partial opacity to look natural, which means the pixels under the stroke keep subtle contrast differences. Import the “redacted” image into Photoshop or GIMP, crank exposure, brightness, and contrast, and the underlying text ghosts back into view.
A solid color block is only safe if the image is flattened. In a PDF or layered PSD, the block is a layer that can be deleted, revealing the text beneath.
True redaction is destructive. The edit has to scramble the pixels themselves, and the export has to be flat.
Gaussian Blur vs. Pixelation
Two techniques actually destroy the data, and they serve different purposes.
Gaussian blur recalculates each pixel as a weighted average of its neighbors, blending everything into a soft, unreadable smear. For security, the radius needs to be strong. 10 to 20 pixels minimum depending on resolution. A light blur is a trap. Neural networks like DeblurGAN have been trained to reverse-engineer lightly blurred text by learning font shapes, so if the letter structure is vaguely visible, it can be guessed. Blur suits faces, license plates, and background clutter where you want a clean aesthetic.
Mosaic pixelation divides the region into large square blocks, 16x16 or 24x24 pixels, and fills each with the average color of its contents. The block size must be substantially larger than the font height and stroke width. Small blocks are vulnerable. Tools like Depix reconstruct pixelated text by matching block patterns against known character sequences. Chunky blocks destroy the character geometry entirely. Pixelation suits API keys, passwords, card numbers, and wallet addresses, where the obvious redaction block is itself desirable.
The Server-Side Trap
Even a correct redaction fails if the tool uploads the image first. Sending an unredacted screenshot, plaintext API key included, to a cloud processor means the original exists on their server. In temp storage, logs, or training datasets. Free tools monetize uploads, sometimes OCR-ing content for ad profiles. For anyone under HIPAA, SOC 2, or GDPR, routing internal documents through an unapproved third party is a compliance violation in itself.
Never hand your unredacted secrets to a server to draw a box over them.
Redacting Locally
In-browser processing with WebAssembly keeps the whole operation on your device. The image loads into browser memory, the blur or pixelation algorithms run on your CPU, and the flat, redacted file saves back to your drive. No network request carries the image, so there is nothing to intercept, store, or harvest. Real-time application of effects. Offline capability once loaded. No DLP violations from uploading internal assets to shadow-IT services.
The Step-by-Step
The Blur & Pixelate tool walks through it. Load the screenshot, choose blur for a smooth look or pixelate for a hard redaction block, draw rectangles over each sensitive area, and push the intensity until the text is completely smooth or the blocks are large enough to destroy the letter forms. Use the hold-to-view-original toggle to confirm nothing is left exposed. A trailing digit of an API key or half a password can still be useful to an attacker. Then export the flat image.
Redaction Failures in the Wild
The consequences of weak redaction are documented enough to be predictable.
A support screenshot with a customer’s session token, redacted with a highlighter-style brush, gets reposted to a public forum. A compliance document with black bars drawn in a PDF editor ships as the layered source file, and the recipient deletes the bars. A developer shares a debugging screenshot with a password blurred at low intensity, and the text is reconstructed within minutes.
Each of these followed the same pattern. The redaction looked adequate at a glance and was not. The fix is not a better marker. It is a tool that performs a destructive edit on the pixels and exports a flat file, so there is no layer to remove and no ghost to recover. The mechanical difference between annotating and redacting.
When Blur Is and Isn’t Enough
Context decides the right tool.
Blur is the right choice when the goal is aesthetic. Faces in a street photo, license plates in the background, a bystander in a product shot. A soft, unobtrusive mask keeps the image usable.
Pixelation is the right choice when the goal is absolute removal. Credentials, card numbers, and strings that must not survive reconstruction. The chunky blocks signal intentional redaction.
The failure mode is mixing them up. A lightly blurred API key is a reconstruction risk. A heavily pixelated face in a marketing photo looks broken. Decide by asking what the worst case is if the region is recovered. A leaked credential means pixelate hard. A privacy courtesy means blur cleanly.
Verifying the Redaction
Verification is not optional. After applying the blur or pixelation, zoom in on the region and check that no letterforms survive, then search the exported file for the redacted string if it was text. The tools that show a hold-to-view-original toggle make this fast. Confirm the intended region is covered. Confirm nothing adjacent leaked. Only then send the screenshot anywhere. A redaction that is not verified is a redaction that might not have happened.
Screenshots go out constantly in support, dev, and documentation work. Redact them like the data matters, because it does, and the tool that keeps the unredacted original on your machine is the only one that gets that right.
Heavy blur or chunky pixelation on a flat export, applied locally, means the data is gone and the original never traveled anywhere.