Articles · Privacy & Trust
Black out the screenshot before you post the bug
Bug reports and Slack threads love screenshots, and screenshots love email addresses in the corner, customer names in a grid, and session tokens in a URL. A CSS overlay or a messy highlighter is not redaction. You need pixels replaced in the file you download.
Why this is worth doing in the browser
People draw a box in a preview app and still attach the original. The DevNestro Screenshot Privacy Redactor writes black, blur, or pixelate into the image. Highlight is for marking, not hiding. There is no automatic face finder in this version — you choose the rectangles. That is slower and more honest.
How to use the tool
Drop a PNG, JPG, or WebP, pick a tool, drag rectangles, and download the flattened PNG. Use Photo Metadata Cleaner for camera photos. Use Screen Recorder when a still frame cannot show the bug.
- Capture the screen, then redact, then attach — never the reverse.
- Cover URLs, names, and numbers even if they look tiny.
- Zoom if the UI is dense; a missed badge is still a leak.
- Download `devnestro-redacted-screenshot.png` and send only that file.
Privacy
The screenshot is processed in your browser and is not uploaded to DevNestro. Automatic detection of emails or faces is not included.
Show the defect, hide the person. Open the Screenshot Privacy Redactor and attach a PNG that cannot be undone with “remove overlay.”