Privacy before sharing
Redact a support screenshot before sending it: inspect the edges
Review a dashboard error screenshot area by area, cover sensitive details and verify the downloaded image.
When a dashboard throws an error, the red message draws your eye. The material you should not send may be at the edge of the screenshot: an account email in the top corner, a query parameter in the address bar, a customer name in the sidebar, or a QR code that opens a page. Review the whole frame before sharing it.
Make a list before drawing boxes
Open Screenshot Redaction and load the original PNG, JPG or WebP. Scan from top left to bottom right. Mark names, email addresses, phone numbers, IP addresses, access tokens, order identifiers, QR codes and any URL parameters. Chat avatars and notification previews can identify people too.
Optional OCR and QR detection can point you toward items you missed, but either can miss low-contrast text, a partly obscured code, handwriting or an internal identifier with no standard pattern. Treat automatic findings as prompts for review, not as a certificate that the image is safe.
Cover sensitive content with an opaque block
Choose the cover method and draw beyond the edges of the information, not just over its middle. Cover an entire email address or token. Even the beginning of a token may reveal a system or account; inspect text printed beside a QR code as well as the code itself. If a label beside the value contains a person's name, cover that separately.
Blur and mosaic can soften visual detail, but a solid cover is easier to inspect for passwords, tokens and full personal details. Zoom in when drawing small rectangles. Do not judge coverage only from a thumbnail; a larger block over a whole panel is often more reliable than a collection of tiny patches.
Inspect the exported image
Choose the output format, examine the export preview, and download the new file. Open the download in an image viewer and inspect the covered edges at 100% or higher. Then scan every corner, the address bar, sidebars and pop-ups once more. Store the original and redacted versions separately, and attach only the redacted one.
The goal is not “three black boxes.” It is a screenshot that still explains the bug without exposing an account, customer record or usable access detail. If a secret was already sent, follow your team's incident process; sending a new redacted image does not undo the earlier disclosure.