What to hide in a screenshot before you share it
API keys in a terminal, customer emails in a ticket, OTPs in a notification: a checklist of what leaks in screenshots, and how to clean them in seconds.
Updated · 2 min read
Do it now: free, in your browser, nothing uploaded.
Open Blur screenshotThe usual suspects
- Secrets: API keys, tokens, passwords, private keys, .env files and session cookies in dev tools.
- Personal data: customer names, emails, phone numbers and addresses in tickets, CRMs and dashboards.
- Money: card numbers, bank details, invoices and balances.
- Around the edges: browser tabs, bookmarks, notifications (OTPs!), the address bar and other open windows.
- Chats: names, phone numbers and profile photos of people who didn't agree to be shared.
Clean a screenshot in seconds
- Copy the screenshot and press Ctrl+V on Blur screenshot.
- Keys, tokens, emails and numbers are highlighted automatically.
- Accept, draw boxes over anything else, and download.
Rotate any secret that appeared in a screenshot you already shared. Hiding it later doesn't undo the leak.
Crop before you cover
The safest pixel is the one you don't share. Crop to the part that matters, then cover what's left. For short text like keys and numbers, use solid boxes rather than blur.
Questions
Which API keys are detected?
AWS, GitHub, Stripe, Google and Slack keys, JWTs, private keys, password assignments and long random-looking tokens.