Redact screenshots before sharing: a practical checklist

Reviewed 14 October 2026.

A screenshot can expose more than the field you meant to capture. Customer names may appear in a table, an email address in a profile menu, and an access token in a URL. A notification can arrive after you prepare the screen. Review the whole image, then review the document that contains it.

Redaction removes information from the copy you intend to share. Drawing something that looks opaque over a screenshot is not enough if the recipient can remove the shape or recover an original image. This guide gives a practical review method for screenshot instructions and support documents, including what to hide and how to check the final deliverable.

Prepare a safer capture

Use clearly labeled sample records or a suitable demonstration environment where possible. Close unrelated tabs and windows, dismiss notifications, and show only the application area needed for the instruction. Avoid displaying secrets just to demonstrate which field accepts them. Explain where authorized values come from in the written step.

Decide who will receive the guide. An internal technician and an external customer may need different detail. Information appropriate for one client may be inappropriate for another. If a screenshot is crowded with confidential records, a new capture using sample data is often clearer and easier to review than covering most of the page.

What to hide in screenshots

Emails and identities: account menus, avatars, names, email addresses, phone numbers and message recipients.
Customer data: contact lists, ticket bodies, invoice details, account numbers, addresses and records belonging to another client.
Credentials and access: passwords displayed by a reveal control, API keys, recovery codes, one-time codes and sign-in QR codes.
URL secrets: access tokens, signed-link parameters, invitation codes and reset links in an address bar or on the page.
Notifications: email previews, chat popups, calendar reminders and system alerts that overlap the intended application.
Environment details: private hostnames, network paths, internal addresses and tenant identifiers when the audience does not need them.
Repeated content: search suggestions, validation messages, previews, breadcrumbs and recent-record lists that echo a value entered elsewhere.

Not every identifier is a secret, but it should have a reason to be in the deliverable. Preserve useful labels and neutral context so the reader can still locate the control. Replace a sensitive value in the instruction with a placeholder and a source rule, such as ?use the approved client identifier from the ticket.?

Blur versus black-out

Blur and pixelation obscure an image by transforming its pixels. They can retain clues such as character length, edges, colors and layout. Weak effects, short predictable strings and removable editing layers can allow recovery or inference. This does not mean every blurred image can be perfectly reconstructed; it means blur is an unreliable choice when the underlying text must not be recoverable.

The UK Information Commissioner's Office warns that simple blur or pixelation may be reversible. It recommends fully obscuring image information and exporting to a format without layers or edit history. See its guidance on securely disclosing documents, image redaction section (published July 2025, checked 2026-10).

For secrets and private text, prefer an opaque solid fill that replaces the sensitive pixels in the exported image. Black is an easy convention, but the critical properties are complete opacity and actual pixel replacement. A translucent highlighter, CSS overlay, annotation layer or Word rectangle can leave the original content underneath.

How to black out an image safely

Work on the intended capture. Open the image in an editor that can apply an opaque fill to its pixels. Keep any necessary original in an appropriately restricted location.
Cover the whole value. Include a margin around the text and check for repeated values elsewhere. Do not leave the first or last characters visible when they are sensitive.
Export a flattened copy. Use a fresh PNG or JPEG containing the edited pixels. Verify the output rather than sharing an editable project with hidden layers.
Reopen the exported image. Zoom in and confirm the region is fully covered. Check that the image still shows the control and context the reader needs.
Replace the image in the guide. Remove the original asset from the deliverable, then inspect the resulting document or archive.

Flattening an image does not sanitize accompanying text, comments, filenames or other embedded files. It also does not remove an original from previous exports or backups. Inspect what you are actually sending. Avoid relying on cropping inside a document editor when it may preserve the full source image; use a reviewed replacement image.

Review the document around the screenshot

Check step titles, descriptions, captions, hyperlinks, alternative text and filenames. A recorder may capture a visible label containing a customer name. A manually written caption may repeat an email that you removed from the picture. Replace these occurrences with neutral examples while keeping the instructions understandable.

For Word files, inspect comments, tracked changes and embedded images in addition to the visible pages. For an HTML or Markdown bundle, check every included image and text file. Verify that hyperlinks do not contain credentials or signed parameters. For a PDF, review visible pages and selectable text; an image redaction step alone is not a general PDF sanitization method.

If a live token or credential was already shared, editing a later screenshot does not invalidate it. Use your organization's established secret-rotation or incident process. Do not assume deleting your own copy removes copies recipients have already downloaded.

What Ownsteps does, and what still needs review

Ownsteps does not read what you type into fields, skips password fields and blacks out input boxes in screenshots. A page can display that text elsewhere, such as a preview or search suggestion, and that content can still appear in screenshots or step text. Review both before sharing. Input masking does not amount to complete redaction of every private element on a page.

The redaction tool blacks out any area and changes the image itself. Use it on the regions your review identifies, then inspect the exported result. Edit any private step title or note separately. Retake or replace screenshots that are unsuitable, and check replacements again rather than assuming a previous redaction carries over.

Before-sharing checklist

The audience and destination are appropriate for the document.
Every image has been inspected, including corners, menus, URLs and popups.
Sensitive values are removed from pixels, not hidden under a removable shape.
Step text, captions, links and filenames do not repeat removed information.
The delivered file or bundle contains the reviewed images and no unintended originals.
The final file has been reopened and checked; another reviewer checks sensitive handoffs where appropriate.

Once the images are ready, the free screenshot guide maker can assemble them into a numbered Word or printable PDF guide. It does not redact images; do that first. See the Word handoff guide for document checks, or the free SOP template for the surrounding procedure.