Hide a phone number or email in a screenshot

Chat bodies get the bar. Chat headers often do not, and that is how the number leaks. The same goes for an email in a profile chip, a quoted reply, or a notification that slid in while you captured. You covered the bubble you meant to share and left the contact string sitting in the chrome.

A phone number is 10 to 12 digits. That is not enough entropy to hide behind a polite smear. This page is the covering technique for numbers and addresses wherever they print in a still. It is not a WhatsApp-only walkthrough, not a Gmail inbox checklist, not an OTP-sharing warning, and not a SIM-swap write-up. Those jobs have their own guides.

How to hide a phone number or email in a screenshot

Open larger image in a new tab

1. Capture the frame, then look top to bottom before you paint: header, profile strip, body, quotes, footer, toasts.
2. Paint an opaque rectangle over every instance. Not a highlighter. Not a light Gaussian. Include the plus sign, the country code, spaces, and separators.
3. Cover the email the same way. Cover the local part, and cover the domain when the domain identifies a person at a small company.
4. Zoom until you cannot guess a digit from the edge. What you should see is a dead rectangle, not a grey ghost of the numbering plan.
5. In BlurThis, pick Black bar and Box, drag each repeat, then tap Download PNG.

Open larger image in a new tab

Start with the header, not the bubble

Most people bar the message they meant to share and leave the name and number sitting in the chrome. Call screens, SMS threads, Slack DMs, Teams chats, and help-desk tickets all reprint the contact at the top. Cover that strip even if the body is already clean.

Emails get the same treatment. alex@ plus a company domain of forty people is already a name. Inbox lists show many addresses at once. One bar on the message body is not a redaction of the page.

App-specific checklists still matter when the UI is unique. WhatsApp headers and OTP banners have their own traps. Gmail list views reprint subjects you did not mean to share. Here the rule is simpler: wherever a phone or mail string appears, including chrome, it gets a bar.

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 overlays that brightness can lift are a known fail on some devices. A light Gaussian is a research fail. Paint a bar. BlurThis includes that mode because blur looks tidy and still leaks OTPs. The longer comparison is blur versus black bar.

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 phone” footers
• QR codes and barcodes that encode the same digits
• Notifications that landed mid-capture
• Lock-screen previews in a photo of a desk
• Calendar invites and PDF ticket footers
• Account chips on a success modal
• Maps pins and ride-share receipts next to a first name

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 a leaked number matters more than the joke

SIM-swap and account-recovery 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. Fuller ticket habits: redact a customer support screenshot.

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.

Troubleshooting

• I barred the bubble and they still have the number. Check the header, the quote, and the notification. Partial cover fails when chrome repeats the string.
• Three digits still show at the edge. Enlarge the bar. People recognise a numbering plan from a city code and a shape.
• The domain is unique. Cover it. A local-part bar next to @tinyfirm.co is a name.
• The file name is the leak. alex-phone.png undoes a perfect bar. Rename the export.
• A toast arrived mid-snip. Recapture with banners dismissed, or bar the toast after the fact. See notifications in screenshots.

Recap

Search the image 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. Phone numbers are short. That is why they are easy to type and easy to leak. Bar them like you mean it, starting at the top of the frame.