Hide a phone number or email in a screenshot
Cover a phone number or email before you send a screenshot. Black bar is safer than a light blur.

A phone number is 10–12 digits. That is not enough entropy to hide behind a soft smear.
Cover the digits, the country code, and the formatted spaces. Cover the email, including the domain if the domain identifies a person at a small company. Then look up: chat headers repeat the number. Then look down: quoted replies repeat it again. Then look at the contact card peeking from a notification.
How do I hide a phone number in a screenshot?
Paint an opaque rectangle over every instance, not a highlighter and not a light Gaussian. Zoom until you cannot guess a digit from the edge. Include the + and the country code. Include spaces and dashes. People recognize their own numbering plan from three visible digits and a city.
Emails get the same treatment. alex@ plus a company domain of forty people is already a name. Cover the local part and, when the domain is identifying, cover that too. Inbox lists show many addresses at once. One bar on the message body is not a redaction of the page.
Why not blur the number?
Short strings are the easy case for recovering mosaiced or blurred text. A polite smear over ten digits is theater. Yellow Markup on iPhone is a known fail: brightness can lift the overlay. A light Gaussian is a research fail. Paint a bar. BlurThis includes that mode because blur looks tidy and still leaks OTPs.
If you already blurred and the file is gone, do not “fix it” by uploading the original to an unblur site. Capture a new screenshot if you still have the chat, and bar it properly. If you do not have the original, assume the number is public to whoever received the smear.
Where numbers hide besides the bubble
- Chat headers and profile strips
- Quoted replies and forwarded banners
- Signature blocks and “sent from my iPhone”
- QR codes and barcodes that encode the same digits
- Notifications that landed mid-capture
- Lock-screen previews in a photo of a desk
QR codes are easy to forget. A mosaic over the human-readable number that leaves the code intact still hands over the digits. Bar the code or crop it. Same for “share contact” cards that render a vCard-looking block.
Why does a leaked number matter more than the joke?
SIM-swap and WhatsApp hijack write-ups keep repeating the same ingredients: a phone number, a texted code, a rushed relative. A screenshot is not the whole crime. It is a way to hand someone the number they did not have. That is why we wrote a phone number in a screenshot and SIM-swap scams as a separate piece. This page is the covering technique. That page is why the covering is not optional.
Never photograph the SMS or in-app verification code. If someone asks you to “read the six digits,” stop. A screenshot of that code is the whole attack. Don’t screenshot the WhatsApp code.
Support tickets and school threads
Customer support will ask for a screenshot of the error. They need the modal, not your login email in the corner. HR will ask for a payroll glitch. They need the error code, not the national ID in the sidebar. Students screenshot a login page that still shows a classmate’s address in an autocomplete row. Cover the row.
You can tell people you redacted “contact info” without listing which tool you used. What they receive should be a PNG with dead pixels in those rectangles. If they need to call the person, they already have another channel. The screenshot is not the address book.
Calendar invites and PDF tickets print emails in footers. A screenshot of a “success” modal still includes the account chip. Cover the chip. Maps pins and ride-share receipts print phone numbers next to a first name. Cover both if either identifies someone who did not agree to be in the PNG.
A last pass before send
Search the image with your eyes the way you would search a document: header, footer, sidebar, quotes, toasts. Check the file name. Check that you attached the export. Check that Recents is not also in the share sheet selection. Phone numbers are short. That is why they are easy to type and easy to leak. Bar them like you mean it.
