Coding tutorials. Pair programming. Conference demos. Tech interviews. Every time you share your screen, your secrets are at risk. StreamBlur fixes that.
Detects 50+ secret formats. Zero configuration.
Recording a YouTube tutorial or course? StreamBlur ensures you can show real code without accidentally including your actual API keys in the video.
Screen sharing with colleagues via VS Code Live Share, Tuple, or Zoom? Keep your personal credentials private while collaborating.
Live coding at a meetup or conference? Present with confidence knowing that if you accidentally open the wrong file, you're protected.
Showing portfolio projects or doing live coding in interviews? Don't let interviewers see production credentials from your side projects.
Streaming on Twitch or YouTube? Stream Mode keeps your secrets blurred while you code in front of your audience.
Walking a client through their setup? Debugging with a colleague over Zoom? Share your screen without revealing your own credentials.
Real examples of secrets that get automatically blurred
# Database
DATABASE_URL=
REDIS_URL=
# API Keys
OPENAI_API_KEY=
STRIPE_SECRET_KEY=
# App Config (visible)
NODE_ENV=development
PORT=3000const config = {
firebase: {
apiKey: ,
projectId: "myapp-12345"
},
stripe: {
publishableKey: "pk_live_...",
secretKey:
}
};$ heroku config
=== myapp Config Vars
DATABASE_URL:
GITHUB_TOKEN:
SECRET_KEY:
APP_NAME: myapp-productionStreamBlur uses pattern recognition to identify secrets. Non-sensitive values like port numbers and app names remain visible.
Add StreamBlur to Chrome. Takes 10 seconds, no configuration required.
StreamBlur runs quietly in the background. No changes to your workflow.
When you share your screen, secrets are automatically blurred.
StreamBlur protects browser-based dev tools where secrets often appear
AWS Console, GCP Console, Azure Portal, DigitalOcean, Vercel, Netlify - wherever you manage your infrastructure.
Stripe Dashboard, Twilio Console, SendGrid, OpenAI Playground - showing docs without showing your keys.
Settings pages, personal access tokens, webhook configurations, secrets management.
MongoDB Atlas, PlanetScale, Supabase, Firebase Console - connection strings and admin keys protected.
IDE extensions only protect your editor. StreamBlur protects everywhere secrets appear in Chrome.
We launched recently and are building our reputation one review at a time. Try StreamBlur and share your experience.
Leave a Review on Chrome Web StoreEngineering teams doing demos, training, or remote pair programming can deploy StreamBlur across the organization.
StreamBlur is a Chrome extension, so it protects browser-based content. For VS Code, we recommend using its built-in settings to exclude sensitive patterns from the workspace. For terminal, consider using tools like direnv with .envrc files. We're exploring broader coverage for future versions.
Yes! Pro users can define custom regex patterns for proprietary credentials. This is especially useful for internal tokens, legacy systems, or custom authentication schemes your team uses.
No. All detection and blurring happens locally in your browser. Your credentials never leave your machine. We couldn't see them even if we wanted to. See our privacy architecture page for technical details.
Nope. StreamBlur uses efficient CSS-based blur filters and lightweight pattern matching. Performance impact is negligible - we're talking single-digit milliseconds of processing per page load.
Yes. Toggle Stream Mode off (keyboard shortcut: Alt+Shift+S), show what you need, then toggle it back on. The blur can also be clicked to temporarily reveal content (while not in Stream Mode).
Our patterns are designed to minimize false positives while catching real secrets. If something is incorrectly blurred, you can add it to an allowlist. If we're missing a secret format, let us know and we'll add it.
More questions? Check our full FAQ or open an issue on GitHub.
Join thousands of developers who share their screen without sharing their credentials.
Free tier includes full protection. No credit card required.