Whiteout / Blog

Guides

How to Redact a Screenshot Before Sending It to Support

5 min read

You take a screenshot to explain a bug or a billing question, attach it to a ticket, and move on. Then you realize the corner of that image had a customer's account number or your own API key in it. Here is how to cover sensitive details properly, before the file ever leaves your Mac.

Screenshots are the fastest way to explain a problem, so we fire them off without much thought. The trouble is that a screenshot captures everything on screen, not just the part you meant to show. The browser tab beside the bug. The account number in the sidebar. The home address on the invoice. The API key sitting in your terminal scrollback.

Redacting a screenshot before you send it is a thirty-second habit that saves you from a much longer bad day. Here is how to do it properly on a Mac, starting with the built-in manual methods and ending with how to make it automatic.

First, know what actually leaks

A general-audience guide on redacting support screenshots documents the failure mode plainly: people routinely leak IP addresses, home addresses, and API keys in the images they attach to a ticket, and the usual advice is to reach for a manual tool such as Preview, Snipping Tool, or Snagit to cover it up first (medium.com/@julia-campbell83).

The pattern is always the same. The sensitive detail is not the thing you were screenshotting. It is in the corner, the tab title, the notification banner, or a line of output you were not even looking at. So the real skill is not drawing a black box. It is remembering to look at the whole frame before you hit send.

The one mistake to avoid: blur is not redaction

Blurring or pixelating a piece of text feels like hiding it, but it only transforms the pixels. The underlying pattern of the original characters can still be present in the file, which is why a soft blur is a weaker choice than a hard cover for anything that genuinely matters.

Real redaction means the information is gone, covered by a solid block, then flattened into the image so nothing sits underneath. When it counts, use a solid rectangle, not a blur or a swirl.

Method 1: Preview (built in, honest, free)

  1. Open the screenshot in Preview.
  2. Click the Markup button (the pen-tip icon) to show the editing toolbar.
  3. Click Shapes and choose the rectangle.
  4. Draw it over the sensitive area.
  5. With the rectangle selected, set both the border color and the fill color to solid black. The fill is the part that matters. A hollow outline hides nothing.
  6. Drag the corners so the box fully covers the text, including edges and the ends of numbers.
  7. Export with File then Export, and choose a flat format like PNG so the box is baked into the pixels.

That last step is not optional. If you save in a layered format, someone could move your box aside. Exporting to PNG flattens everything.

Method 2: Quick Look and Photos Markup

You do not always need to open Preview. Select a screenshot in Finder, press the space bar for Quick Look, and click the Markup icon in the top corner for the same shape tools. The Photos app has Markup too, under Edit and then the three-dot menu. Same workflow: solid rectangle, black fill, cover completely, export flat.

Method 3: A dedicated capture tool

If you already capture with a paid tool, use its redaction feature. CleanShot X, for example, is a well-liked capture-and-annotate app that sells for a one-time price with an optional yearly renewal for updates (cleanshot.com/pricing). macshot is a capable free, open-source option that can auto-detect and cover common PII inside its annotation flow (github.com/sw33tLie/macshot). Both are good tools. The catch they share with Preview is that redaction happens at capture time, in a manual step you have to remember every single time.

Where the manual way breaks down

The manual route is fine for the occasional screenshot. It has three real weaknesses at volume. It depends on you noticing the detail in the corner. It depends on you remembering on a rushed day, mid-incident, when you are moving fast. And it is slow: open, draw, export, repeated across a whole support queue. The gap between "I should redact this" and "I actually did" is exactly where the leaks live.

Redact the ones you forget about

Whiteout watches your screenshots folder and covers detected PII with solid black boxes the moment a screenshot lands, before you attach it anywhere. It runs fully on your Mac, with no upload path and no account.

Try Whiteout free for 7 days

$19 one-time after the trial. Fully offline, no account. macOS.

A quick checklist before you hit send

Redacting a screenshot by hand takes about thirty seconds. Forgetting takes one distracted moment. Match the method to how often you share, and you will never get that sinking, week-later feeling again.

Sources

medium.com/@julia-campbell83/how-to-redact-a-screenshot-before-sending-it-to-support (users leak IP addresses, home addresses, API keys; recommends Preview, Snipping Tool, Snagit); github.com/sw33tLie/macshot (free, open-source capture tool with capture-time PII auto-redaction); cleanshot.com/pricing (one-time price with optional yearly renewal).