How to Blur Google Docs During Screen Sharing (Hide Contract Terms, Salaries & Comment Threads)
Presenting a contract, offer letter or draft from Google Docs? Here's how to hide client names, dollar figures, comment threads and suggestion authors before you share your screen — and why Docs' constant re-rendering means you should use region blurs.
The safest way to present a Google Doc without leaking sensitive text is to blur it directly in the page with a browser extension before you share your screen, so the blur becomes part of what the capture sees. Because Docs re-renders constantly as you type, scroll and accept suggestions, use region (box) blurs that stay anchored to a screen area — and keep the panic hotkey (Ctrl/⌘ ⇧ H) ready for anything that pops into frame.
This works because BlurFirst paints the blur into the web page as real pixels rather than laying an overlay over your monitor. That means it survives Zoom, Google Meet, Microsoft Teams, Loom, OBS and even a screenshot of the shared feed — and nothing you blur ever leaves your browser.
What's risky to show in a Google Doc
A single legal or HR document can carry more than you intend to disclose on a call. The usual offenders:
- Client and counterparty names — the parties named in an MSA, NDA or SOW, often right in the first paragraph and the signature block.
- Contract terms and figures — fees, hourly rates, effective dates, liability caps, discounts and payment schedules that you may be negotiating differently with someone else.
- Salary numbers in offer letters — base, bonus, equity grants and sign-on amounts that should never be visible while you screen-share the template with a colleague.
- Comment threads — the right-hand comment column shows reviewer names, timestamps and blunt internal notes ("push back on this clause") written for your team, not the audience.
- Suggestion-mode author names — in Suggesting mode every tracked edit is tagged with the author's name and a colored avatar, quietly revealing who worked on the draft.
- The shared-with avatars — the collaborator photos and initials at the top-right expose exactly who has access to the file.
- The document title in the browser tab — the tab shows the file name, e.g.
Acme MSA v3 — FINAL, which alone can leak a deal.
How to blur a Google Doc before you present
Set up your blurs on the exact document before the call starts. Press Ctrl/⌘ ⇧ Y to open the BlurFirst control bar and work through the doc:
- 1
Open the document in your browser
Navigate to the doc on docs.google.com and scroll to the section you'll actually walk through, so you know what needs covering.
- 2
Box-blur the margins
Drag a box over the right-hand comment column and another over the shared-with avatars at the top-right. Anchored region blurs stay put as you scroll, so comments never flash into view.
- 3
Element- or region-blur the sensitive lines
Click a single element to hide it, or drag a box over a salary figure, a fee, or a party name. Because Docs re-flows text, a box pinned over the paragraph band is the most stable choice for a value you'll keep on screen.
- 4
Share a single tab, and keep panic ready
Present just the Docs tab (not the whole window), so the browser tab strip and its file name aren't captured. If the wrong section scrolls up or a comment popover appears, press Ctrl/⌘ ⇧ H to blur the entire page instantly.
Why Google's sharing settings don't protect a live share
Sharing permissions — Viewer, Commenter, Editor, link access — control who can open the file. During a screen share, the person opening the file is *you*, so the audience simply sees everything you can see. Restricting access does nothing about the salary figure on screen or the comment thread in the margin. In-page blurring works at the presentation layer: it controls what the viewer of your screen sees, independent of who has document access.
Save a reusable blur profile for Google Docs
If you demo from Docs often — reviewing contract templates or offer letters on repeat calls — set the structural blurs once. BlurFirst Pro's per-site profiles re-apply your saved boxes (the comment column, the share avatars) automatically each time you open a doc, and they persist between sessions. The profile stores only a CSS selector for the region, never the text inside it. You then add the document-specific blurs per session.