What can people see when you share your screen?

The sharing mode decides everything

Viewers see exactly what your sharing mode captures, nothing more and nothing less: an entire-screen share shows everything on that monitor, a window share shows one application, and a tab share shows the inside of one browser tab. Every major meeting app offers some subset of those three modes, under slightly different names.

• Google Meet calls the feature Present now and offers all three modes directly: your entire screen, a window, or a tab.
• Zoom shares entire screens and application windows from its desktop client, which has no single-tab option. The Zoom web app, running inside your browser, adds the tab choice through the browser's own share picker.
• Microsoft Teams shares a screen or a window from the desktop app, plus special modes such as PowerPoint Live. Teams in the browser hands the choice to Chrome or Edge, which bring the tab option with them; Microsoft supports sharing from Teams on the web only in those two browsers.

The rest of this article walks the three modes from widest to narrowest, then answers the questions people actually type into a search box five minutes before a call.

An entire-screen share shows everything on that monitor

Sharing your entire screen transmits everything that appears on the shared monitor, live, exactly as you see it. That includes more than most presenters have in mind:

• Every window on that screen, including the ones parked behind the window you are presenting.
• Every notification. Mail previews, calendar reminders, and chat toasts complete with the sender's name and the first line of the message. Microsoft's own documentation describes screen sharing as showing your entire screen including notifications and other activity, and tells presenters to enable Do not Disturb so others cannot see them. That advice applies just as much in Zoom and Meet.
• Your cursor. Every hover, every tooltip it triggers, every second of hesitation over the Delete button.
• The taskbar or dock, with the icon of everything currently running.
• Your whole browser. The tab strip with every tab's title and favicon, the bookmarks bar, and the address bar together with anything you type into it.
• Autofill. Click into a form field and the dropdown of saved emails, names and addresses renders on the shared screen like everything else.

One genuine boundary exists in this mode: on a multi-monitor setup you pick which screen to share, and only that screen is captured. Keeping notes, chat and everything personal on the other monitor is a real privacy line, not a trick.

Entire-screen sharing is the right tool when a demo hops between applications. As a default, it is the most exposed choice there is.

A window share shows one app, with caveats

When you share a window, viewers see the contents of that single application window, title bar included, and none of your other windows, your desktop or your taskbar. The catch is that everything inside the window still counts as content.

That catch matters most when the window is a browser. A shared Chrome window includes the tab strip with every open tab's title and favicon, the bookmarks bar with every folder name, the address bar with its typed URLs, and the profile chip with your name on it. A window share of a browser is far closer to an entire-screen share than most people expect. If what you are presenting lives on a web page, share the tab instead and the whole problem disappears.

Notifications are the honest gray area. Whether a toast that pops over the shared window reaches viewers depends on the operating system and on how the meeting app captures the window. Modern window capture on Windows and macOS generally grabs the window's own surface, so an overlapping toast is usually not transmitted; some Linux setups instead capture the region of screen the window occupies, and overlays behave inconsistently across platforms. And sound travels regardless of pixels: Zoom's Share sound and Teams' Include sound both send every sound your computer plays, notification dings included. The only setting that behaves the same everywhere is Do Not Disturb, so treat toasts as unsafe in every mode and pause them before you share.

A tab share is the narrowest mode

A tab share transmits only what renders inside one browser tab, so viewers see the page itself and nothing around it: no address bar, no autocomplete dropdowns, no bookmarks, no tab strip, no other windows, and no notification toasts. It is the narrowest capture the meeting apps offer, which is exactly why it is the safest default for anything that lives in a browser.

Meet offers it directly as A tab, and presenting a Chrome tab shares that tab's audio by default, which makes it the one mode where playing a video for the room just works. In the Zoom web app and in Teams on the web, the browser's share picker offers the same tab choice, and Chrome adds an Also share tab audio toggle.

Two things still reach viewers in a tab share. The first is the page content itself, all of it. The second is navigation: the share follows the tab, not the page it happened to be on, so if you navigate that tab to your inbox, everyone comes along. What you cannot do is leak a second tab by accident: in Meet, moving the share to another tab takes an explicit click on Share this tab instead.

The full walkthrough for turning this mode on in each app is in Share a tab, not a window.

Can people see my passwords?

Typed passwords render as dots on a screen share, the same as they do on your own display, so viewers cannot read the characters as you type them. The leaks happen around the dots:

• The autofill dropdown. Click a login field and the browser can pop a list of saved usernames and email addresses. On entire-screen shares that list is fully readable, and on window shares it may be.
• The reveal toggle. The eye icon next to a password field prints the password in plaintext for you and for everyone watching.
• Password managers. Their overlays list account names and emails right next to the field.
• The wrong field. Pasting a password into a search box or a chat message renders it in plaintext, and it sits in your clipboard waiting for exactly that mistake.
• The URL. Reset links, session tokens and API keys ride along in query strings, and the address bar shows them in screen and window modes.

The safe pattern is boring: sign in to everything before the meeting starts, or pause sharing for the ten seconds it takes to type. A tab share removes the browser-chrome vectors entirely, the address bar and its suggestions included, but a reveal toggle is part of the page and stays visible in every mode.

Can people see my other tabs?

Only in the modes that show the browser frame: an entire-screen share and a browser window share both expose the tab strip, where every tab's title and favicon are readable, and a tab share exposes none of it.

Tab titles gossip more than the pages behind them. A strip that reads like a diary, from an ATS tab titled with a candidate's name to a thread called Re: offer letter, tells the room a story you never opened. Favicons do the same work at sixteen pixels: a recognizable logo is enough for everyone to know exactly where else you are signed in.

When you genuinely need window or screen mode with a crowded browser, Tab Privacy in Blurr.ing masks every tab title and favicon behind one of 17 neutral disguise styles while you present, then puts everything back. The free plan includes three activations; Premium keeps it always available.

The mirror question, whether people can see what you do in other apps while you share a tab, has a clean answer: no. The capture is bound to the tab. Apps you open, windows you drag and anything on a second monitor never enter the feed, and neither does the rest of the browser.

The practical fix stack

Three habits cover nearly every leak on this page: share a tab instead of a screen, silence notifications at the source, and blur whatever must stay visible.

1. Share a tab whenever the demo lives in the browser. One decision removes the browser chrome, the desktop, the taskbar and the toasts all at once. The per-app steps are in the tab-sharing guide.
2. Turn on Do Not Disturb at the OS level (Focus on macOS, Do not disturb on Windows), and pause notifications inside the chatty apps themselves. Do it before you join, not after the first toast.
3. Blur the sensitive parts of the page itself. Sharing modes control what surrounds the page; they do nothing about the salaries, customer emails and API keys inside it. With Blurr.ing you draw a box over a region, click an element (hold Alt and scroll to grow the selection), or select a run of text, and it stays frosted while you present. Manual blurs are free, unlimited and need no account. A free blur clears when the page refreshes; Premium ($5 a month, $29 a year, or $39 once) saves your blurs and restores them before the page first paints, so nothing sensitive flashes even for a frame.

Know the limit: a browser extension works inside web pages, so Blurr.ing cannot hide OS notifications, desktop applications, or anything else outside the browser page. That is what the first two habits are for. For the full pre-meeting routine, run the screen-share privacy checklist.