Processed in your browser · never sent to our servers

Blur text in a screenshot (passwords, account numbers, keys)

Cover a password, API key, IBAN, OTP, or card number. Use a black bar, not a smear. Download a PNG. Editing stays in this tab on your device.

Loading editor…

How to hide sensitive text in three steps

1
Add the screenshot or photo
Choose the file from your phone or computer, or paste it. It opens in this tab. Nothing is sent to BlurThis.
2
Select black bar (not blur)
Short secrets survive a smear. Use Black bar for passwords, keys, IBANs, card digits, and OTPs. Box for a rectangle; Draw for an irregular shape.
3
Drag over the secret, then download
Drag across the text with a little padding. Download the PNG and share that copy, not the original.

Why blur fails on short secrets

A six-digit code or IBAN is a small alphabet in a known font. A moderate blur can leave digit stems and bowl shapes that still read at full zoom. Pixelate can leave a readable mosaic at the same strength. A black bar is a flat slab with no glyph edges left to guess. Crop is even better when the secret sits in a corner you do not need for the story.

Research on reconstructing soft covers is why BlurThis pushes opaque bars for passwords and keys. Start with blur vs black bar if you want the decision tree without a full how-to dump.

What usually needs covering

Passwords and recovery codes
API keys, tokens, and .env lines
IBANs, account numbers, balances
Card PAN, expiry, CVV
OTPs from SMS or WhatsApp
Phone numbers and emails next to the secret

Find text can suggest a box. It will miss odd fonts, tiny captions, and the second line that repeats the amount. After one pass, zoom in and hunt for leftovers. Open the downloaded file at full size before you send it. Sharing the original by mistake is a common fail.

Banking snips, bug reports, and OTP traps

Banking screenshots: cover the balance, full account or IBAN, and any banner that echoed the amount. Card shots need PAN, expiry, and CVV, not just the last four if the rest of the number is visible. Walkthrough: hide a credit card in a screenshot.

Bug reports: cover the token and the nearby query string or header dump. A redacted body with a live key in the URL still fails. Guide: hide an API key before a bug report. OTPs: the safer habit is not to screenshot them at all. If one already exists, bar it before share. See do not screenshot an OTP.

Phone and email chrome often sits beside the secret: hide phone number and email in a screenshot. General ticket chrome belongs on blur a screenshot.

Hiding passwords and account numbers: common questions

Is this free, and does the file get uploaded?

Yes. No account, no watermark, no sign-in. Editing runs in this tab on your device. No. Your file stays in this browser tab. We never get a copy. Processing delay does not prove an upload; a wait while the file opens is still on your device.

Blur or black bar on digits and passwords?

Black bar. A short high-contrast string can still be guessed from a light blur or pixelate. Why a bar beats a smear.

Does Find text catch every secret?

No. It is a suggestion. After you apply one, zoom in and look for the rest: CVV, routing number, recovery code on the next line.

Banking or bug-report screenshots?

Cover the balance, full account or IBAN, and any banner that repeated the amount. For keys in a bug report, cover the token and nearby query string too. Cover a banking screenshot.