Guides · Video call platforms and screen sharing

Microsoft Teams: share window vs share screen, and what participants actually see

2026 · ~6 min read · OfferPilot AI

Sharing a window in Microsoft Teams puts exactly one application in the stream: participants see that window cropped to its edges and nothing else, no desktop, no taskbar, no notification banners, and nothing you switch to afterwards. Sharing a screen puts a whole display in the stream, live. Three things catch people out, all of them Teams-specific: the red border follows the shared window rather than your attention, a minimised or covered window can leave viewers on a frozen frame with no warning, and a Windows display set to Duplicate means your spare monitor is already inside the share.

What actually lands in the stream

Two capture models sit under one Share button. A window share is bound to one window and follows it around the desktop. A screen share is bound to one display and sends whatever occupies it. The difference shows up in small behaviours that only matter at the worst moment.

Share a windowShare a screen
What viewers seeOne app, cropped to its edgesThat whole display, live
You alt-tab to your inboxViewers still see the shared appViewers see your inbox
Windows toast notificationAbsent, toasts are separate windowsVisible, sender and message preview
File picker or print dialogOften invisible, separate top-level windowVisible
A second browser windowNot shared. New tabs in it areShared if it is on that display
Taskbar, Start menu, wallpaperNot sharedShared
You minimise the shared thingCan freeze on the last frameKeeps updating
You close the shared thingThe share endsThe share continues
Red border is drawn aroundThat window onlyThe whole display
Your other monitorOut of the stream either way, unless the displays are duplicated

The dialog row varies by app. Some draw dialogs inside their own window, where a window share picks them up. Others hand the job to a separate operating system window, where it does not.

The red border tells you less than you think

Teams draws a red outline around whatever you shared. Share a display and it frames the whole screen, impossible to miss. Share a window and the outline sits on that window's edges only, so it travels with the window, including behind other apps.

The moment you alt-tab to Outlook, the border vanishes with the window and nothing on screen says you are presenting. That causes two mistakes in opposite directions: people who decide the share stopped and start doing private things while participants still watch the shared app, and people who narrate a document nobody can see.

The border is a confirmation cue, not a status indicator, and its absence proves nothing. The signals that do hold are the floating Teams presenter toolbar, which stays on screen whichever app has focus, and the Stop sharing control in the meeting window.

Cover the shared window and viewers can be left on a stale frame

A window share needs that window to keep producing frames. Minimise it and there are none, so the last frame Teams captured stays on everyone's screen. The damage is in what participants do not get: no spinner, no grey overlay, no message saying the presenter's window is minimised. Just a still picture.

A frozen share looks exactly like a share where nothing is happening. That is the whole problem.

Occlusion, dragging another window on top of the shared one rather than minimising it, is the murkier case. Modern Windows window capture can often keep pulling frames from a fully covered window. Older capture paths and some graphics driver combinations cannot, and you get the same held frame. Do not guess.

The 60-second self test

Join your own meeting twice

Start a Teams meeting on your PC, then join it again from your phone. Mute mic and speaker on both so they do not howl.

Share the exact window you will present

Not a similar one: the deck, the editor, the browser window with the right tabs open. The phone now shows what participants get.

Drag another window over it

Pull File Explorer across the shared window and keep moving it. If the phone keeps updating, your machine captures covered windows fine. If it sticks on one frame, nothing may ever sit on top of that window.

Minimise, then restore

Expect the phone to freeze. That is what your audience watches while you spend ten seconds hunting for a file.

Type something and time it

Count how long a typed line takes to reach the phone. That is your real delay, usually a second or two, and it tells you how long to pause before saying "as you can see here".

If the test freezes, keep the shared window unobstructed or share the display instead. It matters most in a live coding round, where a frozen window share leaves the interviewer studying a static screenshot of your editor while you type, which is why the Code Copilot capture flow runs off a hotkey rather than a window switch.

Duplicate displays quietly put your spare monitor in the share

The usual plan is deck on one monitor, share that monitor, notes on the other. It fails outright if Windows is set to Duplicate rather than Extend, because Duplicate is not two desktops. It is one desktop drawn twice. There is no second workspace to hide anything on, so the notes are already on the display you are sharing, and picking the other tile in the Teams picker changes nothing.

You are duplicated if both monitors show the same wallpaper and taskbar icons, or if dragging a window off the edge of one screen does not make it appear on the other.

Press Windows key + P

A panel slides in from the right with four options: PC screen only, Duplicate, Extend, Second screen only.

Choose Extend

The second monitor blanks briefly and returns with an empty desktop carrying none of your open windows. That emptiness is the proof it worked.

Make it stick

Settings, System, Display. Scroll to Multiple displays, open the dropdown beside the arrangement diagram, choose Extend these displays, then click Keep changes before the countdown reverts it.

Share by thumbnail, not by number

Move the notes across, then pick the Teams screen tile whose preview shows the deck. Screen 1 and Screen 2 do not reliably map to left and right.

Set do not disturb by hand

Settings, System, Notifications has a "turn on do not disturb automatically" group with rules for duplicating your display, full-screen apps and games. None of them fire because you started a Teams share, which is exactly the assumption that lands a message preview on a stranger's screen.

Where this advice runs out

A window share is a framing tool, not a privacy guarantee. The edges are fuzzy: a browser extension popup, an app that paints outside its own frame, or an overlay drawn by another program can all reach a stream you assumed was sealed. Teams meetings are recorded routinely too, so a leak is not a moment that passes, it is a file with a transcript beside it.

On our own product, plainly: the OfferPilot AI overlay is excluded from screen capture at the operating system level, so it is absent from a Teams window share, a Teams screen share and a Teams recording alike. That claim is narrow and should stay narrow. It does nothing about your webcam, someone in the room with you, a lockdown browser or a proctoring agent on a monitored assessment, or the fact that reading off a screen looks like reading off a screen. In a supervised exam it is the wrong tool. It runs on Windows 10 and 11 only, and the free tier exists so you can check the capture behaviour in a test Teams call yourself.

Which one to pick

  • Share the window when you will stay inside one app for the whole segment. Fewest ways to embarrass yourself.
  • Share the screen when you will move between apps, drag files or use system dialogs. Clean it first: do not disturb on, mail closed, bookmarks hidden, desktop cleared.
  • Check Win+P after any room presentation, because projectors leave laptops in Duplicate.

Teams signals the share state through a border that hides itself and a stream that freezes silently, so the failure modes are quiet ones. Test them once and they stop surprising you. If your calls are interviews, the Interview Copilot page covers the assistance side and how it stays out of the frame you now control.

Related guides

Test your own share before it matters.

Free tier, no card. Start a Teams call with yourself, share a window, and see exactly what the other side gets.