Screenshot Redaction Best Practices

Start with the edges

Many leaks happen around the edges of a screenshot. Check the browser address bar, tabs, bookmarks, system menu, desktop notifications, and sidebars before looking at the main content.

Use solid boxes for high-risk details

Blur and pixelation can look nicer, but they may leave readable shapes or context. For passwords, tokens, addresses, IDs, documents, and private names, use a solid redaction box.

Redact repeated identifiers everywhere

An account ID, email address, order number, or workspace name may appear in multiple places. Search the screenshot visually and cover every instance, including breadcrumbs, table rows, headers, and footers.

Prefer cropped screenshots when possible

If a smaller crop explains the issue, crop before redacting. Less visible surface area means fewer things to miss. Keep enough context for the viewer to understand the problem, but remove unrelated application chrome.

Review the final file, not the editor

After exporting, open the final image as a normal viewer would. Confirm the redactions are flattened and that no editable layers, source files, or original screenshots are being shared.

Create a disclosure inventory before editing

List what the recipient needs to see and what must be hidden. Typical disclosure categories include names, email addresses, account IDs, tenant names, API keys, URLs with tokens, browser profiles, payment details, customer records, internal hostnames, document titles, and timestamps. This short inventory prevents random box drawing and gives the final reviewer something concrete to verify.

Solid redaction, blur, and pixelation are not equivalent

Use an opaque solid box for secrets, identity, and regulated data. Blur and pixelation can preserve recognizable shapes and may be reversible when the original values come from a small set, such as short codes or interface labels. Blur is better suited to de-emphasizing a face or background when complete secrecy is not required. When in doubt, remove the pixels with an opaque cover or crop.

Example: prepare a support screenshot

1. Crop to the failing interface and the error message.
2. Cover the address bar if it contains an account path, query parameter, or signed link.
3. Hide profile photos, workspace names, customer rows, and browser tabs.
4. Preserve the product version, relevant status, and exact error text when they are safe.
5. Export to a new flattened image.
6. Open the downloaded image at 100% zoom and review each inventory item.

When support needs a real identifier, send it through the provider's approved secure field instead of leaving it in a broadly visible screenshot.

Watch for indirect disclosure

Even after obvious text is covered, layout and context can reveal information. A map marker can disclose location, a unique avatar can identify a user, a notification badge can reveal activity, and a visible clock can establish timing. Reflections in photographed screens and QR codes deserve the same review as readable text.

Do not share the editable project

Some design and annotation formats keep the original image underneath the redaction layer. Export a flattened PNG, JPEG, or WebP copy and share that derivative. Keep the source and editable project private. Renaming an original or placing a rectangle above it does not remove the underlying pixels.

Final review checklist

• The screenshot contains only the context required by the recipient.
• Secrets and identity fields use opaque redaction rather than cosmetic blur.
• Repeated identifiers are covered everywhere they appear.
• Tabs, address bars, bookmarks, notifications, and sidebars were checked.
• The final exported file was reopened outside the editor.
• The filename contains no customer, ticket, or account identifier.
• The original remains in private storage and was not attached accidentally.

Sources and review notes

This guide is informed by the data-minimization principle in NIST SP 800-122 and by common flattened-image publishing workflows. All examples are synthetic. See the ImagePrivacy editorial policy for our review and correction process.

Try the related tool

Open Image Redactor to draw redaction boxes in your browser before sharing screenshots.