Skip to content
BlurFirst

How to Blur GitHub During Screen Sharing (Hide API Keys, Env Vars & Private Repos)

5 min read

Pair-programming or doing a code walkthrough on a call? Here's how to hide API keys, tokens, .env values and private repository names on GitHub before you share your screen.

Code walkthroughs and pair-programming sessions put a lot of secrets one scroll away: tokens in a .env file, an Authorization header in a code sample, the names of private repositories in your sidebar. The reliable fix is to blur those specific elements in the page before you share — not to scramble to close files mid-call.

What's risky to show on GitHub during a screen share

  • Secrets in files — API keys, tokens, passwords and connection strings in .env, config files, or example code.
  • Secrets in the UI — values shown on Actions logs, repository Settings → Secrets (names are visible), and environment variables in deployment views.
  • Private repo and org names — your repository list, the org switcher, and breadcrumbs reveal projects and clients you may be under NDA about.
  • Personal and account details — your email in commit metadata, notifications, and the account menu.

How to blur GitHub specifically

  1. 1

    Open the repo or file you'll present

    Get to the exact view you're going to share before the call starts.

  2. 2

    Element-blur the secrets

    With BlurFirst active, click the line containing a token, the .env value, or the secret name to blur just that element — the surrounding code stays readable.

  3. 3

    Box-blur the sidebar and lists

    Drag a box over the repository list, the org switcher, or the notifications bell so private project names never show.

  4. 4

    Keep the panic shortcut ready

    If a notification or a new file with secrets appears, press Ctrl/⌘ ⇧ H to blur the whole page instantly.

What native tools won't hide

Sharing a single browser window keeps your terminal and other apps out of frame — do that. But within the GitHub tab itself, neither Zoom, Meet nor Teams can hide a single line of a diff or one entry in your repo list. That selective, in-page hiding is exactly what an element-level blur does, and because it's painted into the page it appears in the shared feed and any recording.

Save a reusable blur profile for GitHub

If you present from GitHub often, set up the blurs once and let them persist. With BlurFirst Pro you can turn on per-site auto-apply for github.com, so your saved blurs (the sidebar, the notifications area) re-apply automatically each time you open it — even after the page re-renders. You blur the secret-specific lines per session, and the structural stuff is always covered.

Frequently asked questions

Can I blur a single line of code without hiding the whole file?

Yes. Element blur targets one element — a line, a cell, a sidebar item — so you can frost the line holding a token while the rest of the file stays perfectly readable for your walkthrough.

Does blurring a secret on screen make it safe?

It prevents the secret from being seen during the call or in a recording. But if a real secret was ever committed or exposed, rotate it — blurring the presentation doesn't undo prior exposure.

Will the blur survive scrolling and GitHub's dynamic loading?

Region and element blurs anchor to the content and re-apply when the page re-renders, which GitHub does as you navigate. For absolute certainty on a specific element, element blur is the most stable choice.

Blur it before you share it.

Hide any field, region or message on a page before your next call. Nothing you blur leaves your browser.

Add to Chrome

Keep reading