Guide · Screenshot privacy
How to redact sensitive information in a web screenshot
A useful screenshot should explain the problem without exposing the account, customer, or internal system behind it. Use this short review method before you send one.
1. Capture the relevant context
Keep the page state that helps another person understand the task: the visible control, error message, selected tab, or part of the address. Do not crop away the context before you know what needs to be protected.
2. Look beyond the obvious field
Check passwords, tokens, names, phone numbers, emails, customer records, order details, internal URLs, browser notifications, and any data in the address bar. PrivacyShot can flag common patterns, but a human review is still necessary.
3. Prefer an opaque cover for secrets
Blur and mosaic can be useful for reducing visual detail, but an opaque rectangle is the safer choice for passwords, access tokens, identity numbers, and other high-sensitivity values. Cover the whole value, not just the middle characters.
4. Review the final image
- Read the screenshot at 100% zoom
- Check the address bar and page title
- Confirm the cover does not leave a readable edge
- Remove unnecessary personal or internal context
Share the minimum necessary. If the screenshot is only needed to explain a button or layout, do not include a real customer record just because it was on screen.
When one screenshot becomes a workflow
PrivacyShot is designed for a single web screenshot. If you are documenting a repeatable process across several pages, use StepWise to capture the workflow and edit the resulting guide.
Make redaction part of the capture step
Download PrivacyShot and review sensitive areas before the image leaves your browser.
Download free