Only Meet's tab sharing mode hides the address bar, and Docognito turns that shared tab into a document. Choosing a window or your entire screen sends the browser frame too, address bar included, no matter what the page underneath looks like. Pick tab sharing before you present, and the disguise handles the page itself.
The three modes behind Present now
Google Meet's Present now button offers three choices: a tab, a window, or your entire screen. A tab share sends only the content of one Chrome tab, rendered as a video stream. A window share sends the full application window that tab lives inside, title bar and address bar included. An entire screen share sends everything on the chosen display, every window, every app, all at once.
The three sound similar and behave nothing alike once a browser is involved, because a tab is the only one of the three that Chrome renders without the frame around it.
Most people default to whichever mode Meet remembers from the last call, which is often a window or an entire screen simply because that was convenient once and nobody revisited the choice afterward. Reconsidering it before a call that might touch anything sensitive costs one extra click in the Present now menu.
Why tab sharing crops the frame
Chrome's tab capture API works at the level of the page itself. It hands Meet the rendered content of the tab, the same pixels a reader sees inside the page, and stops there. The address bar, the tab strip and the bookmarks bar are part of Chrome's own window, not part of any tab, so tab capture never touches them.
Window and screen capture work differently. Both use the operating system's own screen recording, which takes a picture of whatever occupies that space on the monitor, browser chrome and all. There is no equivalent narrowing available once you step up from a tab to a window.
| Sharing mode | Address bar visible | Other tabs visible |
|---|---|---|
| A tab | No | No |
| A window | Yes | No |
| Entire screen | Yes | Yes, any open window |
The first row is the one worth remembering: tab sharing is the only mode built to leave the address bar out of the stream.
What a window or screen share sends
Choosing a window sends the whole browser, including the tab strip along its top. Anyone watching can read every tab title, not only the one you meant to present, and the address bar for whichever tab is active shows for the entire share.
An entire screen share removes even that boundary. Switching between applications during a call, checking a message, opening a file, all of it streams live to everyone watching, because the capture is of the monitor rather than of any one piece of software running on it.
A second monitor is not covered unless you choose it directly
Sharing your entire screen only sends the display you selected when the share started. Opening a document or a message on a second monitor mid call keeps that content private, right up until you switch the share to that display too.
What a tab share leaves for your own screen to show
Tab capture is narrow enough to leave Meet's own interface out of the stream entirely. The participant grid, the in-call chat panel and the reaction icons all live inside the Meet application itself, not inside the tab you present, so a tab share never sends any of that to the call. The same narrowness cuts the other way, too. Anyone glancing at your own screen while you present, rather than watching the stream, can still see all of it sitting around the edges of the shared window.
Tab audio follows the same boundary as the video, through a control rather than something fully automatic. Google's own Meet support page describes a share tab audio control that is already switched on the moment you pick a tab to present, so the presented tab's sound reaches the call without you touching anything further, while a notification sound from a different tab stays off the call because that control only ever carries the one tab you chose.
Swapping tabs without ending the share
Meet lets you change which tab, window or screen is being sent without fully ending the share and reconnecting everyone on the call. That control matters here for one reason only: it removes any excuse to leave extra tabs within reach during a presentation. Switch deliberately to the tab you mean to show, through that control, rather than clicking across to a different tab and trusting that nobody noticed the change happen.
The same rule applies in reverse once you are done. Stop presenting through Meet's own control rather than simply closing the tab, since a share left running by accident keeps sending whatever loads next in that window.
Setting up before you open Present now
Turn Docognito on first
Toggle the disguise on before you join the call, not after Present now is already open.
Choose a tab, not a window
When the Present now menu appears, pick Chrome Tab and select the disguised tab specifically.
Confirm the border before you speak
Meet marks the shared tab with its own on-screen indicator once sharing starts, so check it before continuing.
Where the disguise and the sharing mode meet
Tab sharing and the disguise solve two separate problems that happen to line up. Tab sharing keeps the browser's own frame, including the address bar, which still reads claude.ai or chatgpt.com, out of anyone's view. The disguise changes what sits inside that frame, so the page itself does not read as a chat interface either. Neither one substitutes for the other: choose the wrong sharing mode and the disguised tab still arrives at the address bar visible in a window share.
Tab sharing is the mode that keeps the disguise covered
Choose Chrome Tab from Present now, not a window and not your entire screen, and turn Docognito on before you open that menu. That combination is the only one of the three that keeps both the address bar and the page content out of what a colleague sees. Any other mode sends the browser frame along with it, disguise or not.