What can other people see when I share my screen in Whereby?

It depends entirely on which tab of Chrome's share picker you choose. Entire Screen sends one whole display, including notification toasts, your taskbar and anything you open on it. Window sends a single application and nothing behind or around it. Chrome Tab sends one page's viewport, with no address bar, no bookmarks bar and no other tabs.

Does Chrome's Stop sharing bar appear in my screen share?

No. Chrome draws that bar, and the coloured border around the captured surface, as its own on-screen indicators and keeps them out of the frames it hands to the meeting. You see them, the far end does not. That is deliberate, so a capture can never run without you being told. Confirm it once from a second device if it matters.

Can I share computer audio in a browser-based Whereby or RingCentral call?

Only from two of the three tabs. Chrome Tab offers a share tab audio tick box, which carries whatever that page plays. Entire Screen on Windows offers a system audio tick box that starts switched off. The Window tab has no audio option at all, so a shared desktop application is silent no matter how loud it is.

Why does the Whereby share dialog look different from Zoom's?

Because it is not Whereby's dialog. Browser-based meeting tools call the getDisplayMedia API and Chrome, not the website, draws the chooser and owns the decision. The site can hint which tab opens first and whether an audio tick box appears, but it sees nothing of your screen until you have picked a surface and pressed Share.

How do I make sure I share the right monitor in Chrome's picker?

Chrome's Entire Screen tab identifies displays by live thumbnail and a generic number rather than by monitor name, and its ordering need not match Windows'. Open Settings, System, Display and press Identify to learn which physical screen is which, tidy the one you intend to send, then match it by picture in the picker.

If I share one Chrome tab, can people see my other tabs?

No. A tab capture starts at the top edge of the page viewport, so the tab strip, the address bar, the bookmarks bar and the downloads bubble all sit outside it. Switching tabs yourself does not change what viewers receive. Watch the sharing bar, though, because its Share this tab instead button swaps the stream in one click.

Whereby Screen Share: What Others Can See in Each Picker Tab

Whereby, RingCentral in the browser and every other tool that runs a call inside a tab do not draw their own share dialog. They call one browser API and Chrome takes over, with a picker that has exactly three tabs. Entire Screen sends one whole display, notification toasts and taskbar included. Window sends a single application, with no audio at all. Chrome Tab sends one page's viewport and nothing around it. The one thing you never send is the Stop sharing bar Chrome pins to your own screen.

Why a browser meeting hands the decision to Chrome

A native client such as the Zoom or Teams desktop app holds an operating-system capture permission and can enumerate your windows itself, which is why it can build a chooser with its own extras. A page running in a tab cannot do any of that. It has one entry point, navigator.mediaDevices.getDisplayMedia(), and the rule attached to it is that the browser presents the choice and the site receives nothing until you have made it. Whereby's own interface ends at the Share screen button. Everything from that click until the stream starts belongs to Chrome.

Three consequences worth knowing. The site never sees a list of your open windows, so no meeting platform can report what you had open and chose not to share. It cannot preselect anything for you, which is why the Share button stays greyed out until you click a thumbnail yourself. And it cannot dismiss or restyle the picker to rush you past it.

What a site can do is pass hints, which explains why your picker sometimes differs from a colleague's on the same Chrome build. A site can ask which tab opens first with displaySurface, hide the system audio tick box with systemAudio, turn on the Share this tab instead button with surfaceSwitching, and keep its own meeting tab out of the tab list with selfBrowserSurface. That last one is why the Whereby or RingCentral tab is often missing from the list, and why the classic infinite mirror is harder to trigger from Chrome Tab than from Entire Screen.

The three tabs, and what each one transmits

Every cell describes what the far end receives, not what your own monitor shows.

Behaviour	Entire Screen	Window	Chrome Tab
What is captured	One display in full, plus whatever moves onto it.	One top-level window, cropped to its own edges.	One tab's page viewport, from the top of the page down.
How you pick it	By live thumbnail and a generic number. No monitor names.	By thumbnail plus the window's title text.	By favicon and tab title in a list.
Audio offered	A system audio tick box on Windows, off until you tick it.	None. There is no per-window audio capture.	A share tab audio tick box, carrying that page's sound.
Toasts, taskbar, tray	Sent, sender names and unread badges included.	Not sent. They are separate surfaces.	Not sent.
Address bar, bookmarks, other tabs	Sent whenever Chrome is on that display.	Sent in full if the window you picked is Chrome.	Never sent. Capture starts below all browser chrome.
Something covering it	Whatever is on top is what goes out.	Generally still captured while occluded. Minimising usually freezes the last frame.	Unaffected. A background tab keeps streaming.
Your other monitor	Not sent. You choose one display, not all of them.	Not sent, and dragging the window between displays does not break the share.	Not sent.
Ends when	You press Stop sharing, or the call ends.	You close the window, or press Stop sharing.	You close the tab, or press Stop sharing.
An overlay excluded from capture at OS level	Absent from the stream.	Absent from the stream.	Absent from the stream.

Three details the table cannot hold. The mouse pointer rides along with an Entire Screen or a Window share, so a cursor circling a line of code is part of the picture, while a Chrome Tab capture is normally pointer-free and viewers see the page move without seeing you move it. Chrome's own dialogs behave the same way: a permission bubble, a print preview or the native Save file box are browser furniture, not page content, so they land in a screen share and stay out of a tab share. And whichever surface you pick, Whereby and RingCentral put it into the room as a WebRTC video tile that participants can expand or pin, encoded at whatever the connection will carry. Nine-point text in a wide IDE can arrive soft even though your own display looks crisp, so raise the font before you share rather than after someone asks.

The Stop sharing bar is for you, not for them

Once capture starts, Chrome adds its own furniture: a coloured border around the captured tab or window, and a small bar carrying a Stop sharing button, joined by a Share this tab instead button when the site has asked for surface switching. Those are Chrome's indicators, drawn as Chrome's own surfaces, and Chrome keeps them out of the frames it encodes for the meeting. You sit looking at a bar that says you are sharing, while the interviewer looking at that same display sees only the desktop underneath it. The picker never reaches the stream either, for the simpler reason that capture does not begin until after you press Share.

Two practical notes. The bar floats above your content and can cover the bottom of the window you are demonstrating, which is your problem and not theirs. And Share this tab instead is one click that silently swaps what the room is watching, so treat it the way you would treat any button next to a live microphone.

The gaps against a native desktop client

If you have only ever shared from the Zoom or Teams desktop app, the browser picker will feel stripped back, because it is.

No filtering and no region select. The Window tab is a flat grid of every top-level window you have open: no search box, no grouping by application, and no equivalent of the desktop clients' portion-of-screen, whiteboard, second-camera or computer-sound-only modes. Twenty open windows means scrolling twenty live thumbnails, all readable on your own screen while you hunt.
Audio is bolted to the surface type. You do not choose sound separately from picture. Tab audio exists only under Chrome Tab, system audio only under Entire Screen and only on Windows, and window shares are silent, full stop. A desktop client will mix computer audio into any share type. In the browser the rule is simpler: if it makes noise and it can live in a tab, put it in a tab.
Monitors are chosen by picture, not by name. Chrome shows a thumbnail and a generic number for each display, never the model, and its ordering need not match Windows'. This is the most common route to sharing the wrong screen in a browser call.
No pause. The picker has no pause control. Stopping means walking back through it from the beginning, which the whole room watches you do.

What to do in the ninety seconds before you press Share

Decide the surface, then run Identify

Pick the surface before the grid is open and everyone is waiting. On a multi-monitor setup, Settings, System, Display, Identify puts a large number on each physical screen, so you can match Chrome's thumbnail by picture rather than trusting the numbering to agree.

Tidy the surface you are sending, not the one you are on

For Entire Screen, quieten notifications and close chat windows on that display. For a window share, only that window matters.

Read the audio tick box

It is the only chance you get. Changing your mind later means stopping the share and reopening the picker in front of everyone.

Verify from a second device

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

Where the overlay fits, and what it will not do

The last table row works by a different mechanism from the rest. Windows lets a window be marked so the compositor removes it from any capture before an application receives a single frame. OfferPilot AI uses that, so its overlay is absent from all three picker modes, and from Zoom, Teams, OBS and a plain screenshot, while staying visible on your own monitor. Because the exclusion happens below Chrome, which picker tab you used makes no difference, and no browser extension is involved, so nothing of it shows in your tab list. It is on every plan, the free one included, which is the point of the phone test above: prove it before you rely on it. In a browser-based coding round, share the editor tab 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 takes over the machine, a proctor watching you in the room, eye tracking, or a phone propped up as a second camera. Eyes travelling repeatedly to one side read as exactly that on video, whatever is or is not inside the share. It is also Windows 10 and 11 only, so on a Mac it is the wrong tool and no amount of picker knowledge changes that. The free tier exists partly so you find that out today rather than five minutes before a call.

Where this page stops being reliable

It describes Chrome on Windows. Firefox draws a different chooser that names windows in text rather than showing thumbnails, which is genuinely better for picking, and its audio support is narrower. Recent Safari hands off to the macOS system picker. If your dialog disagrees with this page, trust your dialog.
RingCentral ships a desktop build as well as a browser one, and a desktop app is free to draw its own chooser with extras a web page cannot have. If your picker offers options this page does not mention, you are almost certainly not in the browser version.
Labels move between Chrome releases more often than behaviour does. Look for a tick box near the bottom of the picker rather than one exact string, and confirm the indicator behaviour once from a second device.

The short version for a browser-based interview: the picker is Chrome's, its three tabs are three different privacy trade-offs, and the only one that sends nothing but the work itself is Chrome Tab.

Whereby screen share: what others can actually see