Redact Sensitive Information in Images and Inspect the Export
Cover selected pixels with solid redaction, review the whole image and check the downloaded copy before sharing it.
Content updated:
List the information before covering it
Work on a copy and identify every occurrence of names, addresses, account numbers, signatures and other private details. Inspect the browser title, tabs, filenames, notifications and reflections as well as the obvious document fields.
Treat barcodes and QR codes as separate items. They may encode the printed value, a different identifier or a link. Cover the full symbol and any sensitive text nearby rather than assuming one hides the other. Redaction cannot prevent disclosure from context you leave visible.
Use solid pixel replacement for sensitive text
Blur and pixelation obscure appearance but retain information derived from the original. Do not rely on them for private text, short identifiers or scannable codes. A translucent marker is also unsuitable because the original contributes to the visible result.
In TheImageIs Image Studio, choose Annotate & redact and choose Opaque redaction, which fills a rectangle with solid color. The outlined rectangle is a different annotation and does not cover its interior. Extend the filled region beyond the complete text or symbol, including small edge fragments.
Export a separate raster copy
Apply the redaction and export a PNG copy. The studio renders the edited pixels into a new canvas-based image. This workflow is different from sharing an editable project, an undo history or a PDF with removable drawing annotations.
Keep the source privately and use an unmistakable output name such as order-example-redacted.png. Do not share the source file or a project that retains it. If your input is a PDF, use the dedicated PDF redaction workflow and read its image-only export limitations.
Verify coverage, metadata and context separately
Reopen the downloaded image in a separate viewer and inspect every redacted region at high zoom. Check all surrounding text and the complete frame. A brightness or contrast adjustment can reveal mistakes with translucent covering, but passing that check is not proof that all sensitive information was removed.
A failed text-selection or OCR attempt is also not a security certificate. File-property dialogs show only some metadata fields. Use a metadata inspection tool when hidden metadata matters, and review the actual downloaded copy rather than assuming a filename extension or blank summary proves safety.
Practice with invented information first
Create a screenshot containing a fictional name, address and reference number. Redact only those fields, export it and check whether any identifier is repeated in another place. This teaches placement and review without using a real customer's record.
The ICO's disclosure guidance treats hidden information, output format and checking procedures as parts of the same process. For consequential material, use an accepted review process and an independent reviewer. The tool can cover selected pixels; it cannot decide whether your selection list is complete.
Redact a fictional order screenshot
A guided exercise, not a benchmark. Inspect your own output; results depend on the source and settings.
- Create a non-private practice screenshot with invented customer details and a repeated reference number.
- Open Annotate & redact, select Opaque redaction and cover every full sensitive region with solid rectangles.
- Apply the edit and export a separately named PNG.
- Reopen that exact file and inspect all regions, surrounding context and metadata relevant to your sharing requirements.
No selected identifier should remain visible anywhere in the saved practice image. Visual checks validate coverage; they do not certify every possible hidden field or the completeness of your privacy decisions.
Sources & further reading
Try an idea and review your result before saving your edits.
