Mac privacy / 5 min read
How to keep browser tabs private while screen sharing
Share a single browser tab when the meeting tool offers it. If you need several tabs, prepare a clean window and inspect its tab bar, bookmarks and account menu. With ScreenVeil, move private tabs into another window and select Hide a window. It cannot remove individual tabs from a window you share.
Keep private tabs and bookmarks out of a screen share on Mac. When to share a single tab, and why a second Chrome profile isn't the same as a second browser.
By ScreenVeilUpdated
Is that tab still open?Can you hide “Sharing this tab” in Google Meet?
“Sharing this tab” or “This tab’s content is being shared” is Chrome’s capture indicator. To remove it by ending capture, choose Stop sharing. Keeping other tabs private is a separate task: in Google Meet, choose Present now → A tab and select only the prepared page. Do not widen the share to your entire screen just to get rid of a banner.
A tab share sends the page rather than the surrounding browser window. A window share can include its tab bar, bookmarks and account controls. Check the received picture on another device, especially if your concern is a local banner, a projector or a saved recording rather than the remote presentation.
When Chrome offers Share this tab instead, that button deliberately changes the captured tab. Merely reading another tab is different. Tab-sharing controls depend on the browser, meeting app and version; keep capture indicators enabled and inspect the selected source before switching.
A second profile is useful preparation, not a sharing boundary
Chrome profiles help separate accounts, bookmarks and history. They do not decide which pixels your meeting app sends. A private profile placed in the shared browser window would still be visible, and a whole-app ScreenVeil rule treats every Chrome profile as Chrome.
Keep these two decisions separate: which account should the demo use, and which tab or window should the audience receive? A dedicated demo profile helps with the first. The meeting picker or a specific window exclusion handles the second.
Choose the source before rearranging tabs
Scroll sideways to compare →
| Your presentation | Use this source | What still needs preparation |
|---|---|---|
| One web page | The single tab, where supported | The account, record and links opened inside that tab. |
| Several prepared tabs | A clean browser window | All tab titles, bookmarks, toolbar and account menus in it. |
| Browser plus slides or another app | Privacy Screen | Exclude private windows or whole apps; select Privacy Screen in the meeting. |
| A shared desktop required by the workflow | A display with no private work on it | Every window opened or moved onto that display. ScreenVeil cannot filter it. |
A two-window example for a client demo
Use fictional data for this rehearsal. In Chrome window A, open the demo dashboard and a prepared pricing page. In window B, open a sample inbox. If you only need the dashboard, share its tab directly. If the demo also needs another app, start Privacy Screen, keep window A shared and select window B under Hide a window.
Now follow the transition that is easy to overlook: drag the sample inbox tab from window B into window A. The tab is now inside the shared window. A window exclusion follows the selected window, not the tab as it moves. Undo the move with sharing stopped and decide where new links should open before the real call.
This is a rehearsal scenario, not a claim about a recorded customer incident. Its pass condition is visible: the receiving device shows the prepared work, keeps updating, and never shows the sample inbox while it remains in the excluded window.
Private browsing will not hide a window from a call
Mozilla describes Private Browsing as limiting retained browsing information and tracking; it does not make you anonymous online. That is a different job from choosing what a meeting captures. An Incognito or private window can still be the window you share, so prepare its visible content as carefully as a normal window.
For example, a private window may be signed into a customer account even when the regular window uses a demo account. Check the account menu and the actual record on screen. The private-browsing icon is not evidence that the audience receives a redacted page.
An unexpected link is a reason to pause
Before opening an unprepared link, stop sharing in the meeting app or cover Privacy Screen with ⌘⇧B. Check the destination, account and page locally, then move only the material you intend to show into the public window.
Reopening a private window can create a new window that needs a fresh exclusion. ScreenVeil clears specific-window selections when Privacy Screen stops. Review the list before each session and after creating a new private window; leaving a familiar window title on screen is not enough.