Redact a screenshot
A screenshot is the most casually shared file there is. It goes into a ticket, a group chat, a support thread, a bug report — and it is almost entirely text, which is exactly what a screenshot is worst at hiding.
This opens with the text already covered, so what you paste is the part you meant to show.
Works today, in your browser. Photos open in the editor and Word documents are checked for hidden data; either way the file is read on your device and never uploaded.
What leaks in a screenshot
Not the thing you cropped for. The rest of the window: a notification sliding in, the browser tab beside the one you meant, an email address in a sidebar, a token in a terminal’s scrollback, a customer’s name in a list behind the dialog.
- Email addresses and phone numbers in headers, sidebars and signatures
- API keys, bearer tokens and session identifiers in a terminal or a dev console
- Customer names and account numbers in a list behind the thing you meant to show
- Notification banners that arrived in the half-second before the capture
- The file path in a title bar, which often contains a person’s name
Solid boxes, not blur
Screenshots are the worst case for a blurred redaction: crisp, high-contrast text in a standard font at a known size is the easiest kind to recover. Everything here defaults to a solid fill for that reason.
If you switch to a blur anyway, the editor tells you what you are trading. It does not stop you — it is your screenshot — but it will not let you do it unknowingly.
Before you attach it to a ticket
Check what the automatic pass found and what it did not. Recognition is good on screen text and still misses things: a name in a stylised font, text in an image inside the screenshot, numbers in a chart’s axis labels.
Anything it missed, drag a box over. It takes a second and it is the difference between a redaction and an apology.
How to do it
- 1Drop the screenshot inText is read and covered automatically.
- 2Reveal what the ticket needsClick an area to show just that one.
- 3Save and attachSolid boxes, and no metadata on the copy.
Questions
Yes. Phone screenshots are PNGs like any other, and the text in them reads well because it is crisp. The editor works on a phone too, down to small screens.
That is the normal way to use it. Switch categories on and off, or click individual areas — the error message you are reporting stays legible while the account details beside it do not.
Cropping genuinely removes what is outside the crop, so it is a real defence — unlike a black rectangle pasted on top in some tools. It does nothing about what is inside the part you kept, which is what this is for.
Related
- Blur the text in an imageFind the words in a photo or screenshot and cover them. Card numbers and addresses get a solid box, because bl…
- Check a document before you upload it to ChatGPTSee what a file really carries before you paste it into an AI chatbot: author names, comments, edit history an…
- Blur part of an imageDrag a box over any part of a picture and cover it with a blur, a pixelation or a solid block. No account, no …
We report no issues found, never “safe”. Absence of detections is not proof of absence, and detection is best-effort.