Google Cloud Console, Firebase configs, GCP API keys, Google Meet screen sharing - the entire Google ecosystem is a minefield of exposed credentials. StreamBlur protects them all.
Protects GCP Console, Firebase, Cloud Shell, and every Google service in Chrome.
Add StreamBlur to Chrome. It immediately starts scanning Google Cloud pages for secrets.
Navigate Cloud Console, Firebase, Cloud Shell - API keys and service account credentials get blurred automatically.
Present on Meet, stream, or screenshot. Your GCP credentials are already masked.
From Cloud Console to Firebase to Google Meet - StreamBlur covers the entire Google ecosystem.
Navigate the GCP Console during demos, tutorials, or team meetings. API keys, service account credentials, and project secrets stay blurred.
Managing Firebase projects on screen? Config objects with API keys, database URLs, and messaging sender IDs are automatically masked.
Sharing your screen on Meet with clients or colleagues? StreamBlur protects every tab you switch to - no more "hold on, let me close that."
Using Cloud Shell in the browser? Terminal output containing credentials, gcloud auth tokens, and environment variables are all protected.
The APIs & Services credentials page is one of the most dangerous pages to show on screen. StreamBlur masks every key and secret on it.
Demoing deployments? Environment variables, connection strings, and secrets in deployment configs are masked across all compute services.
Real examples of secrets found across GCP, Firebase, and Google Cloud tools
const firebaseConfig = {
apiKey: ,
authDomain: "myapp.firebaseapp.com",
projectId: "myapp-12345",
storageBucket: "myapp.appspot.com",
messagingSenderId: ,
appId:
};APIs & Services → Credentials
API Key 1 (Browser):
API Key 2 (Server):
OAuth Client Secret:
$ gcloud auth print-access-token
$ cat service-account.json
{
"private_key": ,
"client_email": "sa@proj.iam",
"project_id": "my-project"
}StreamBlur detects 50+ secret patterns including GCP API keys, Firebase configs, OAuth tokens, and service account credentials.
StreamBlur protects every Google service where credentials appear in the browser
APIs & Services, IAM, Compute Engine, Cloud Storage, BigQuery - every console page where API keys, service accounts, and connection strings appear.
Project settings, Cloud Messaging keys, Realtime Database URLs, Authentication config - the Firebase dashboard fully protected.
Browser-based terminal and IDE. Environment variables, gcloud auth tokens, and file contents in the cloud editor are all masked.
When you share your screen on Meet, every tab is protected. Switch between Cloud Console, code, and docs without worrying about exposed keys.
Yes! StreamBlur recognizes Google Cloud API keys (AIzaSy...), OAuth client secrets (GOCSPX-...), service account private keys, and Firebase configuration values. These patterns are built into the core detection engine.
Absolutely. StreamBlur operates at the browser level, so when you share your screen (or a specific tab) on Google Meet, the secrets are already blurred in the browser itself. Meet participants see the blurred version. This works for both "share entire screen" and "share a tab."
Yes. Cloud Shell runs in the browser, and StreamBlur scans its rendered content. Output from commands like gcloud auth print-access-token or cat on credential files will have secrets masked.
StreamBlur detects API keys and sensitive values within Firebase config objects displayed in the browser - whether in the Firebase Console's project settings page, in code files viewed on GitHub, or in Codespaces. The apiKey, messagingSenderId, and appId fields get masked.
No - they solve different problems. Secret Manager secures secrets in your infrastructure. StreamBlur prevents those secrets from being visible on your screen when you share it. Use Secret Manager for production security; use StreamBlur for screen sharing safety.
StreamBlur focuses on actual secrets - API keys, tokens, passwords, and credentials. Project IDs, region names, and other non-sensitive identifiers remain visible so you can still present and teach effectively.
More questions? Check our full FAQ.
Join cloud engineers who present, demo, and stream GCP - without leaking credentials.
Free tier includes full protection. No credit card required.