Does sharing a Chrome tab in Google Meet share the tab's audio?

Yes. Meet asks Chrome for audio when you pick a tab, so the picker's tab audio toggle arrives already switched on and the room hears whatever that page plays. That is why a tab share is the right mode for a video, a demo or anything with a soundtrack. You can untick the toggle before pressing Share if you want the picture only.

Can people see my other tabs or my address bar if I share one tab in Google Meet?

No. A tab share captures the page viewport only. The address bar, the bookmarks bar, the tab strip with every tab title, the downloads bubble or shelf, extension icons and Chrome's own dialogs all sit outside that rectangle and are never transmitted. Switching to another tab does not change what viewers see. They keep watching the tab you selected.

Why do I see an infinite tunnel of screens when I share my screen in Google Meet?

Because the Meet window showing your own presentation preview is sitting on the display you are capturing, so Meet is filming its own output, over and over. It is harmless but it makes the share unreadable. Fix it by presenting a single tab or window instead, or by moving the Meet window to a second monitor before you start.

How do I share computer audio in Google Meet when I am sharing a window?

Generally you cannot. Chrome does not capture audio per window, so a window share is silent no matter what the app is playing. Your two options are to present that content in a Chrome tab instead, which carries its audio automatically, or to share your entire screen and tick the system audio checkbox in the picker before you press Share.

Does a Google Meet tab share stop if I switch to a different tab?

No. The share follows the tab you chose, not the tab you are looking at, so you can read something else while the room keeps seeing the original page. Watch for Chrome's sharing bar, which offers a Share this tab instead button. One accidental click on that swaps the presentation to whatever you are currently viewing.

Should I share a tab, a window, or my entire screen in a Google Meet interview?

Share a tab if the work lives in the browser, because it leaks the least and carries audio. Share a window if you need a desktop app such as an IDE or a terminal. Share your entire screen only when an interviewer explicitly asks for it, since that mode transmits notification toasts, your taskbar and every window you open.

Google Meet: Share a Tab, a Window, or Your Entire Screen?

Present a tab and Meet sends that page's viewport plus that tab's audio, automatically, and nothing else: no address bar, no bookmarks bar, no other tabs, no downloads, no taskbar. Present a window and you send one app with no sound at all, because Chrome does not capture audio per window. Present your entire screen and you send that whole display, notification toasts included, plus the Meet window itself, which is what produces the tunnel-of-mirrors effect. Row by row, below.

The three Present now modes, side by side

Every cell describes what the other participants receive, not what your own monitor shows. The tab column is where those two diverge most.

Behaviour	A tab	A window	Your entire screen
Audio	Included by default. Meet requests tab audio, so the picker's toggle arrives already on.	None. Chrome has no per-window audio capture, so the room hears silence.	Only if you tick the system audio checkbox before pressing Share. It is off until you notice it, and availability varies by platform.
Address bar and bookmarks bar	Never sent. Capture begins at the top edge of the page viewport, below all browser chrome.	Sent in full, bookmark names and current URL included.	Sent in full, along with everything else on that display.
Your other tabs	Not sent. The tab strip is invisible and switching tabs does not change the stream.	Sent. Every tab title is readable and tab switching is fully visible.	Sent, plus any other browser window you open.
Downloads	Not sent. The toolbar download bubble, the older shelf and the downloads page all sit outside the captured tab.	Sent. Filenames appear as they land.	Sent, plus Explorer if you open the folder.
Notification toasts	Not sent. A toast is its own surface, drawn over the browser rather than inside the page.	Not sent, for the same reason.	Sent, sender name and message preview included.
Taskbar, tray, Alt-Tab	Not sent.	Not sent.	Sent, unread badges and the Alt-Tab thumbnail strip included.
Second monitor	Not sent. You can drag the tab across displays without interrupting the share.	Not sent. Capture follows the window.	Not sent. You pick one display and only that one is captured.
Infinite mirror risk	Only if you select the Meet tab itself.	Only if you select the Chrome window holding the meeting.	Yes, whenever the Meet window sits on the captured display.
If you minimise or close it	Closing the tab ends the presentation at once.	Minimising usually freezes viewers on the last frame. Closing ends it.	Nothing to minimise. The display keeps streaming.
An overlay excluded from capture at OS level	Absent from the stream.	Absent from the stream.	Absent from the stream.

The audio difference, in one paragraph

This is the row that decides most real choices. A tab share is the only Meet mode where sound is the default rather than a decision: Meet asks Chrome for the tab's audio when it opens the picker, so the toggle worded along the lines of "Also share tab audio" arrives pre-ticked, and a video clip or a browser audio player reaches the room cleanly, because the sound is taken from the tab rather than through your microphone. A window share has no audio path at all, which catches out anyone presenting a desktop video player. Entire-screen sharing can carry system audio through a separate checkbox, but that checkbox starts off, and being a system-level capture it also carries your notification chimes. Practical rule: if it makes noise and it can live in a tab, put it in a tab.

The infinite mirror, and three ways out of it

Share your entire screen while the Meet window is on that display and Meet captures its own presentation preview, which contains the capture, which contains the preview. You get a receding tunnel, unreadable by about the third repetition. Nothing is broken and nobody is seeing anything private, but you cannot present through it.

Present a tab or a window instead. That removes the cause rather than working around it, since neither mode captures the display Meet lives on.
Move Meet to your second monitor and share the other display. The preview still exists, it is simply outside the captured rectangle.
Minimise the Meet window once the share has started and drive the meeting from the floating controls. Audio and video carry on normally.

Audio has no equivalent loop, because Meet does not play your own presented audio back to you through the meeting. Speakers instead of headphones are still an echo risk, but that is a different problem with a different fix.

What a tab share never transmits

Worth stating precisely, because "just share a tab" gets recommended constantly without anyone drawing the boundary. Participants do not receive:

The address bar, so the URL is not readable, though the page content on it obviously is.
The bookmarks bar, including folder names and the bookmark titles you had forgotten were there.
The tab strip or any other tab, foreground or background, with their titles and favicons.
The downloads bubble or shelf, and any file that finishes downloading mid-call.
Your second monitor, or any pixel of any display outside that tab's viewport.
Extension popups, Chrome permission prompts, save-password bubbles and the Windows file picker, which are browser or OS surfaces rather than page content.
Docked DevTools, attached to the window rather than drawn inside the captured tab.

Two things a tab share does send. First, navigation: type a new URL into the shared tab and the room sees the new page, because the share is bound to the tab, not to the page loaded in it. Second, Chrome's sharing bar carries a button offering to share the tab you are currently looking at instead, and one stray click swaps your presentation to whatever you are reading.

Presenting a tab cleanly, click by click

Open the content first

A tab that does not exist yet is not in the picker, and hunting for it live is exactly when the wrong thing gets shared.

Present now, then Tab

Choosing Tab hands over to Chrome's own picker, which lists tabs by title from every Chrome window you have open, not only the current one.

Check the audio toggle before you press Share

It is pre-ticked for tab shares. Untick it if you would rather stay silent. Changing your mind later means stopping and restarting the presentation.

Confirm with the outline

Chrome draws a border around the tab it is capturing. If it is around a different tab than you expected, restart rather than live with it.

Verify from a second device

Join the same meeting from your phone, mic muted and speaker off, and look at what it actually renders. Your own monitor is the least reliable evidence in the room.

Where the overlay fits, and what it cannot do

The last table row works by a different mechanism from the other nine. Windows lets a window be marked so the compositor strips it out of any capture before an application receives the frame. OfferPilot AI uses that, so its overlay is absent from all three Meet modes, and from Zoom, Teams, OBS and a plain screenshot, while staying visible on your own monitor. It is not blurred or blacked out, the pixels are simply not in the frame that gets encoded. That exclusion is on every plan including the free one, so the phone test above can prove it before you depend on it. In a browser-based coding round the pairing is the point: present the editor tab, which leaks nothing else, and read Code Copilot beside it.

The limits deserve equal billing. Capture exclusion covers screen sharing, screen recording and screenshots. It does nothing about a webcam, a lockdown browser that owns the whole machine, a proctor watching you in person, eye tracking, or a phone propped up as a second camera. Eyes tracking across something off to one side read as exactly that on video, whatever is or is not inside the share.

Where this guide stops being reliable

It describes Chrome on Windows. Meet in Firefox or Safari opens a different picker with different audio options, and system audio capture has never been uniformly available across platforms. If your picker disagrees with this page, trust the picker.
Labels move between releases. The wording on the audio toggle and the position of Present now have both changed more than once, while the behaviour has stayed steadier. Look for a checkbox near the bottom of the picker rather than for a specific string.
Some rounds make the question moot. A proctored assessment in a lockdown browser controls the machine and share-mode nuance does not apply. OfferPilot is the wrong tool there, and it is Windows 10 and 11 only, with no macOS, Linux or mobile build. The free tier exists partly so you find that out at no cost rather than on the day.

For an ordinary Meet interview the takeaway is short. Present a tab when the work is in the browser, present a window when it is a desktop app, keep your entire screen for when an interviewer explicitly asks, and spend a minute checking the result on your phone before it counts.

Google Meet: share a tab, a window, or your entire screen?