How to hide part of a screenshot on iPhone (without blur)

The most common way people hide information in screenshots is blur. It’s the default option in most photo editors, and it looks like it’s doing the job.

The problem is that it’s not.

Why blur isn’t safe for sensitive information

Gaussian blur — the kind almost every app applies — can be partially reversed. Not easily, and not by everyone, but with the right tools and enough pixels, there’s enough information left in a blurred image to reconstruct what was underneath. Security researchers have demonstrated this repeatedly.

For genuinely sensitive information — passwords, API keys, credit card numbers, social security numbers — blur is not a safe redaction method. It gives the impression of redaction without providing the protection.

Beyond the security risk, blur looks rough in professional contexts. A pixelated smear over an email address or internal URL signals that you threw something together quickly. It’s fine for a personal note; it’s not what you want in client-facing materials, documentation, or a product update.

What actually works: solid coverage

The right approach is covering the sensitive area with a solid, opaque block. No pixels from the original image show through. Nothing to reverse. The information is gone.

This is what document management tools and legal redaction software use. A flat rectangle over the sensitive area, saved to a new image. The original isn’t modified — you just never export it.

What to cover

The things most commonly missed before sharing screenshots:

• Email addresses — visible in inboxes, settings screens, account pages
• Names — in thread lists, user profiles, admin panels, anywhere real users appear
• Internal URLs — address bars on internal tools, staging environments, admin dashboards
• Account or payment details — balances, card numbers, order IDs
• Auth tokens or API keys — sometimes visible in settings, logs, or developer tools
• Notification content — message previews in the status bar at the top of the screenshot
• Anything identifying someone who didn’t consent to being in the screenshot

The status bar is the one people forget. If you have a text message preview or email notification showing when you take the screenshot, it’s in the image.

Crop as an alternative

If the sensitive information is at the edge of the screenshot — in the status bar, the URL bar, a corner — cropping is often cleaner than redacting. A tighter crop removes the information entirely rather than covering it, and the result looks like you intended the frame.

Use crop when the sensitive area is peripheral. Use solid redaction when it’s in the middle of something you need to keep visible.

Before you send

A quick checklist before sharing any screenshot externally:

1. Status bar: any notification content showing?
2. URL bar: any internal URL or auth token?
3. Usernames or emails: visible in thread headers, account settings, user lists?
4. Payment or account info: balances, card details, order numbers?
5. Anything identifying someone without their consent?

For internal screenshots — sending to a teammate about a bug you both know about — you can be looser. For anything going to a client, public forum, or external support thread, run through the list.

The general rule

If you’d hesitate to say something out loud to the person receiving the screenshot, cover it. A solid block takes five seconds. An accidental data exposure takes much longer to deal with.