Keys in plain sight
A live API key on a settings screen, a token in the network tab, or a connection string in a config UI is one screenshot away from being public.
Hide API keys and customer data when you screen share
Blurr.ing detects API keys, secrets, connection strings, tokens and customer records and blurs them before you demo, share your screen or file a bug report.
- 34 secret-detection presets (Premium)
- Runs locally in your browser
- Manifest V3 for Chromium
Quick answer
Blurr.ing uses Blur Text keyword redaction with 34 presets to automatically detect and blur API keys, tokens, secrets, connection strings, and customer PII wherever they appear on a page, before you demo, record, or file a bug. The blurs you draw stay in your browser, and with Premium they re-apply before the page paints, so a hot reload does not flash a live credential.
The risk
Engineers stare at secrets all day, then hit “share screen”
A leaked production key means rotation, an incident review, and working out what was exposed and for how long. Yet keys, tokens, and real customer data sit in plain view in the tools you demo, pair in, and screenshot every day, and scrubbing each screen by hand is the step people skip when they are busy.
A recorded demo or Loom
You scrub through a feature walkthrough and a .env file or a JWT in DevTools is in frame for the whole clip, which then gets forwarded around.
Real PII in the admin panel
Filing a bug against a production admin panel means a table of real customer names, emails, and IDs rides along in the attachment.
How Blurr.ing helps
Blur credentials before they ever leave your screen
Blur Text recognizes common secret formats and blurs them on its own, and you click to blur anything it misses. Set the presets once and they apply to every page you open. The matching runs locally in your browser.
34 secret-aware presets
Match the shapes of API keys, tokens, card numbers, IBANs, SSNs, and crypto wallet addresses out of the box: no rules to write for the common cases.
Runs locally
The regions you draw are applied with CSS and never leave your browser. Blurr.ing reads nothing and uploads nothing, and the screenshots you ask it for are built in your browser too.
Survives hot reloads
With Premium, saved blurs re-apply before the page paints, so a dev-server rebuild or a single-page-app re-render does not flash a live key mid-demo.
Hide whole customer records
Click a row, a card, or a table to blur it instantly, holding Alt and scrolling to grow the selection to exactly the data you need to cover.
Auto-Blur avatars & media
Frost every avatar, image, and ad in an admin panel so a user table full of real people stays anonymous on screen.
Your own patterns
Blur anything containing sk_live, a postgres:// connection string, or an internal ID format. Combine terms with AND, OR, and NOT.
Step by step
Hide credentials before a demo in five steps
Set the presets once and they apply to every session after that.
- 1
Add your secret presets and keywords
Turn on the presets for API keys, tokens, and cards, and add custom patterns like sk_live or a postgres:// string once.
- 2
Open the Blurr.ing toolbar
Press Ctrl + Shift + Y (Cmd + Shift + Y on Mac) or click the Blurr.ing icon on the dashboard, admin panel, or DevTools view you are about to show.
- 3
Let keyword redaction sweep the page
Every matching credential and identifier is frosted wherever it appears, so you never hunt for each one by hand.
- 4
Click-to-blur anything it misses
Click a customer row or a config card the presets do not cover to hide it instantly, and dial the intensity up.
- 5
Demo, record, or file the bug
Screen-share, capture a Loom, or attach a screenshot with production credentials and PII covered.
Keep exploring
More ways to blur before you share
The same blurs work on calls, screenshots and streams.
Screen sharing on calls
Blur salaries, customer data and dashboards before you present on Zoom, Meet or Teams. Share a tab to hide the browser frame, and mask your other tab titles while you are at it.
Clean, redacted screenshots
Redact names, emails and account numbers before you capture a screenshot for docs, tutorials, support tickets or bug reports.
Streaming & recording
Auto-blur images, videos and ads, and hide your own name, email and address before you go live or record a tutorial.
Can Blurr.ing automatically detect and blur API keys and secrets?
Yes. Blur Text ships with 34 presets that match common secret formats (API keys, tokens, card numbers, IBANs, SSNs, and crypto wallet addresses), and you can add your own patterns with AND/OR/NOT logic, such as blurring anything containing sk_live or a postgres:// connection string. Your free saved rule lets you run one keyword rule or preset at no cost; Premium removes the limit.
Is it safe to use on pages that show production credentials?
The blurs you draw are applied locally with CSS and never leave your browser. Blurr.ing reads nothing and uploads nothing on its own: an image appears only when you press the screenshot shortcut, and it is built in your browser. Your keyword rules do sync across your devices when you sign in, while the drawn regions and the blur engine itself stay on your machine.
Will a hot reload flash my keys during a demo?
Not with Premium. Blurr.ing re-applies saved blurs before the page paints, so when your local dev server hot-reloads or a single-page app re-renders, the API keys and secrets stay blurred with no flash of the raw values. On the free plan a full page reload clears drawn blurs.
Can I hide customer records and avatars in an admin panel?
Yes. Click any element (a row, a card, or a whole table) to blur it, holding Alt and scrolling to grow the selection, and turn on Auto-Blur to frost every avatar and image. Combined with keyword redaction for emails and IDs, you can demo an admin panel full of real customer data safely.
