Protect browser-visible secrets
Before sharing, open the console, repository page, or browser-based editor. Use Smart Auto Blur Pro API key masks and custom rules for the secret formats your team uses.
Hide API keys during screen sharing and coding streams
Use local masks and manual blur to protect visible tokens, .env secrets, and AWS or GitHub keys in browser dashboards.
Add to Chrome — Free
Contact supportCompatible with your browser • Free install in 2 clicks • No signup required
Cover the fields that patterns miss
Select an exact DOM element or draw a manual overlay for custom token fields and browser-visible .env text. The Chrome extension cannot protect a native terminal or desktop editor; use the macOS app’s manual overlays for those windows.
Preview before streaming
Scroll through the debugging path and verify each value is obscured. Pattern matching is local but cannot guarantee every secret format is found. If an actual credential is exposed, rotate it through its provider.
- Local API key masks
- Custom token patterns
- Manual element selection
- Browser-based coding walkthroughs
How to prepare before sharing
When setting up Hide API keys during screen sharing and coding streams (Hide API Keys on Coding Streams | Screen Privacy Blur), Screen Privacy Blur runs 100% locally in your Chromium browser so private records, credentials, and financial balances remain hidden or replaced with realistic demo data before any frame is shared.
- Open the browser tab or desktop context you plan to present.
- Place blur overlays over the private fields that can appear during the walkthrough.
- Review the visible area, then start the call or recording.
Compare protection modes for this workflow
| Capability | Manual Blur (Free) | Smart Auto-Blur (Pro) | Auto-Replace Data (Pro) |
|---|---|---|---|
| How it targets data | Click exact DOM element or draw freeform region | Local regex & pattern masks (emails, phones, keys, cards, SSNs) | Local pattern masks + custom CRM/dashboard rules |
| How your screen looks on calls | Customizable frosted glass overlay | Automatic frosted glass over detected PII | Clean, natural UI with realistic synthetic demo data |
| Best for | Quick internal calls & ad-hoc sections | Live debugging, coding streams & support calls | Client sales demos, Loom tutorials & Stripe/CRM walkthroughs |
| Role presets | Per-website saved layouts | Dev / Streamer & PII mask profiles | SaaS Sales Demo, FinTech / Stripe & Dev / Streamer scenarios |
| Data privacy | 100% local in browser | 100% local in browser | 100% local in browser (never alters backend DB) |
Related resources
Hide balances and customer PII in financial dashboards
Blur account balances
Blur sensitive data in Microsoft Teams screen sharing
Works with Teams tab & window sharing
Hide API keys and PII in OBS Studio & live streams
Built for OBS Window & Display Capture
Screen sharing without exposing sensitive data
Protect demos
ANSWERS BEFORE YOU INSTALL
Frequently asked questions
Can the Chrome extension hide secrets in my native terminal or code editor?
It protects browser-visible text, including web editors and dashboards. It cannot inspect a native terminal or desktop editor. Use the macOS app’s manual overlays for those windows, and custom Pro patterns for browser-visible secret formats that built-in masks do not cover.
How do Manual Blur, Smart Auto-Blur, and Auto-Replace work for Hide API keys during screen sharing and coding streams?
For Hide API keys during screen sharing and coding streams (Developers & API keys), Manual Blur is free forever and lets you click exact DOM elements or draw custom frosted-glass regions (Local API key masks, Custom token patterns, Manual element selection, Browser-based coding walkthroughs). Smart Auto-Blur Pro masks detected emails, phones, and API keys locally, while Auto-Replace Pro swaps sensitive text with realistic demo data.
Does any page data leave my browser during Developers & API keys sessions?
No. When using Screen Privacy Blur for Hide API keys during screen sharing and coding streams, all pattern matching and DOM replacement run 100% locally inside the Manifest V3 Chrome extension. Open Chrome DevTools → Network while toggling Developers & API keys protection to verify zero page content is uploaded.
Can I save my Developers & API keys layout for future calls and recordings?
Yes. Once you configure Hide API keys during screen sharing and coding streams rules (Local API key masks, Custom token patterns, Manual element selection, Browser-based coding walkthroughs) on a domain, Screen Privacy Blur saves that layout locally so your protection is ready automatically before your next Zoom, Google Meet, Microsoft Teams, Loom, or OBS session.