Check a Screenshot Before Sharing It
AI-assisted article. Reviewed by Codebuff automated editorial review on 2026-11-08. Examples are illustrative, not real user data.
A screenshot is the fastest way to show an error, and one of the easiest ways to publish something you did not intend to. The conspicuous part, the error message, is rarely the problem. What leaks usually sits at the edges: a file path with a customer name, a sidebar of open conversations, a notification that arrived mid-capture. A fixed check takes under a minute.
What do the edges of a screenshot reveal?
Start with the frame rather than the centre. Window titles carry project and repository names, tab strips list unrelated work, and taskbars show the applications you keep open. On a wide screen the crop often includes a second monitor's worth of context that has nothing to do with the bug.
Crop before you annotate. Drawing an arrow on the interesting line and then cropping means the arrow moves, but cropping first also removes anything that would otherwise have needed redaction.
Treat blur as decoration, not protection
A Gaussian blur is reversible enough to be a risk when the underlying text is high contrast and the original resolution is preserved, and a mosaic that is coarse enough to be safe often makes the document unreadable anyway. Solid boxes and cropped regions have no such ambiguity.
If a value must stay visible as a shape, replace it with typed placeholder text instead of covering it. The reader still learns that a token was there, and the pixels that carried the real value never leave your machine.
# Replace, do not cover
Authorization: Bearer <redacted>
DATABASE_URL=postgres://app:<redacted>@db.example.test:5432/app
Check what arrived while you were capturing
Notifications appear after the moment you decided the screen was clean. Look at the captured image, not at the screen you remember. The same applies to tooltips, autocomplete lists and hover cards, which can display a full email address for a person whose name you already hid.
Close chat and mail before the capture when the screenshot is going somewhere public, and take a second capture after the first one if anything moved.
Prefer text when text will do
A screenshot of a log cannot be searched, copied or quoted, and it forces the next person to retype the line they need. Pasting the text, with the sensitive parts replaced, is more useful and easier to review. Keep the screenshot for layout problems where the appearance is the bug.
Text also survives differently: a paste can expire or be deleted, while an image attached to a ticket tends to stay. That is a reason to be stricter with the image, not more relaxed with the text.
Look at the metadata before you upload
Image files can carry the account name of the person who captured them and the software used. Many chat tools strip this, many do not. If you are publishing the image on a page rather than dropping it into a private thread, check the file you are about to share, not the one you took.
Finally, open the image at full size once. Thumbnails hide exactly the small text that matters, and the check is only useful if it is done on the version that will be read.
Sources and editorial review
Prepared with AI assistance and checked against the screenshot and plain-text sharing pages at the reviewed revision: the advice to crop, to replace rather than blur, and to prefer searchable text. No image tooling was run and no claim is made about a specific blur implementation.