A Windows application can ask the operating system to keep its own window out of anything that captures the screen. It is one function call, SetWindowDisplayAffinity, with the flag WDA_EXCLUDEFROMCAPTURE. The desktop compositor keeps drawing that window on your physical monitor but leaves it out of the frames it hands to capture, so the window is missing from Zoom, Teams, Meet, OBS and a plain screenshot simultaneously. Two things follow that people usually get wrong: an app can only do this to its own windows, and it hides nothing from a camera.
The one function that does the work
Every top-level window on Windows carries a property called display affinity. The default is WDA_NONE, meaning treat me like everything else. An application can change its own window to WDA_EXCLUDEFROMCAPTURE, which has been available since Windows 10 version 2004, build 19041. Both Windows 10 and Windows 11 support it. On older builds the call falls back to the earlier behaviour described further down.
The important restriction is who is allowed to make the call. Display affinity is set by the process that owns the window. You cannot point a utility at Chrome, Notepad or a PDF reader and switch it on for them. There is no Windows setting for it, no registry key that reliably does it, and nothing in Zoom's or Teams' options that hides a chosen window from your own share. That is why searching the operating system's settings for a way to keep a window off a screen share turns up nothing. The switch exists, but it sits on the other side of the fence, inside the application, and a developer has to have decided to use it.
You have probably met the result without knowing the mechanism: a messaging client with a screen security option whose window drops out of screenshots, or a credential prompt that refuses to photograph. Software handling secrets reaches for this, because the cheapest way to stop a password landing in someone's support recording is to make the window uncapturable in the first place.
Where the pixels actually get removed
Since Windows Vista, no application draws directly onto your monitor. Each top-level window renders into its own off-screen buffer, and the Desktop Window Manager composites those buffers into the image you see. Capture reads that composited output rather than the glass, which is the design decision that makes exclusion possible and also defines its boundary.
When a window is marked as excluded, DWM includes it in the composition sent to your display hardware and omits it from the composition offered to capture. The removal therefore happens upstream of every application that could receive a frame. Zoom never gets the window and then filters it out. Zoom is handed an image that never contained it. This explains behaviour that otherwise looks like magic: one flag knocks a window out of a dozen unrelated programs at once, and no setting inside any of those programs can undo it, because none of them are making the decision.
| Capture path | How it gets its pixels | Does an excluded window appear? |
|---|---|---|
| Zoom, Teams or Webex sharing an entire screen | Windows display capture of one monitor. | No. Viewers see the desktop behind it. |
| Sharing a single window, pointed at the excluded window itself | Per-window capture of that window's surface. | No. The source comes back empty or black. |
| Google Meet, or any browser-based share | Chrome or Edge calls the same Windows capture APIs behind getDisplayMedia. |
No. The browser inherits the exclusion. |
| Local or cloud meeting recording | Encodes the stream that was already being shared. | No. A file cannot contain what the stream never carried. |
| OBS, in display, window or game capture mode | The same three Windows capture routes. | No, in all three modes. |
| Print Screen, Windows key with Shift and S, Snipping Tool, Xbox Game Bar | Same composition path, one frame instead of many. | No. |
| Remote control tools such as Quick Assist or TeamViewer | Usually the same capture APIs, though some use their own display driver or session. | Usually no. This is the one row worth testing rather than assuming. |
| A phone camera, a webcam pointed at the monitor, a capture card in the video cable | Photographs the light leaving the panel, or taps the signal after composition. | Yes. Fully visible. |
| Software on your machine listing running processes and windows | Not a capture path at all. | Yes. The window and its process still exist. |
Absent, blanked, or black for a completely different reason
Three outcomes look similar in a recording and mean different things. Telling them apart is genuinely useful.
- The window is simply not there. That is
WDA_EXCLUDEFROMCAPTURE. The capture frame shows whatever sits behind the window, so nothing in the image suggests a window was ever in that spot. - A black rectangle in the exact shape and position of a window. That is the older
WDA_MONITORflag, which blanks the window's pixels in capture instead of removing the window. It protects the content, but it advertises itself, because the viewer sees a hole that moves when you drag it. - A black rectangle where a video was playing. A different mechanism entirely. Protected playback is enforced in the media pipeline rather than by a window flag, which is why a streaming service goes black in a screenshot on a machine where nothing else does.
Absence is unremarkable. A moving black hole is close to the most conspicuous artefact you can put on a screen share, so people who report that their hidden window is obvious are nearly always looking at the older flag or at protected video.
Verify it on your own machine in three minutes
Do not take any vendor's word for this, ours included. The test is short, it produces a file you can open, and it is worth re-running after a Windows feature update.
Take a full screenshot from the keyboard
Press Windows key and Print Screen together. Windows writes a PNG into your Pictures folder under Screenshots. Open it. If the window you expected to be hidden is not in that image, exclusion is working on the capture path.
Record ten seconds and play the file back
Windows key with Alt and R starts an Xbox Game Bar recording. A live preview proves nothing, since the preview is drawn on your own machine. The saved MP4 is the artefact that matters, so watch it rather than the window showing it.
Start a meeting with only yourself in it
Open Zoom, Teams or Meet, start a meeting alone, share your entire screen, then join the same meeting from your phone as a second participant. What arrives on the phone is exactly what a viewer receives, with none of the guesswork.
This is the mechanism OfferPilot AI uses for its overlay on Windows 10 and 11, which is why the answer panel stays readable on your own monitor while being absent from Zoom, Teams, Meet, OBS and screenshots. The same applies to the selection rectangle you drag after Ctrl+Alt+S in Code Copilot, because it belongs to the same excluded surface. Capture exclusion is on every plan, including the free tier, so the three tests above can be run before you pay for anything.
What capture exclusion cannot do
This is the part most explanations leave out, and it decides whether the mechanism is any use to you. Exclusion affects software that asks Windows for the screen, and nothing else. It does nothing about:
- A webcam. Your camera sees your face and your room. It is a separate device on a separate pipeline and it is completely unaffected.
- A phone or a second camera pointed at your monitor. The panel is emitting light. Anything photographing that light records every pixel on it, excluded or not.
- A lockdown browser or a dedicated proctoring client. These take over the machine, apply their own rules, commonly require other applications to be closed before an assessment starts, and may simply refuse to begin. Capture behaviour does not change what those rules say, and this is not a workaround for them.
- Eye tracking, or a human watching your gaze. Reading is visible. Eyes moving along a line of text while you are supposed to be talking is legible to a person on a video call with no technology involved.
- Someone standing behind you. Worth writing down, because it is the failure that actually happens.
- Software running on your own computer. An excluded window is still a window. It has a process, a handle and an entry in Task Manager. A monitoring agent enumerating running software is not looking at pixels, so none of this touches it.
- A hardware capture card, or audio. A card between your GPU and your display taps the signal after composition, and nothing here affects your microphone.
Every item there follows from what the flag is. It removes one window from one data path. Treating that as invisibility is the mistake.
Where this is the wrong tool
If your assessment is proctored under rules you have agreed to, with a lockdown browser or a live invigilator, none of the above helps you and OfferPilot AI is the wrong product for that situation. The honest uses are preparation, live assistance in ordinary conversational interviews, and accessibility support for people keeping pace with a fast interviewer in a second language. There is a hard platform limit too: this is a Windows 10 and 11 mechanism, with no macOS, Linux, mobile or browser-extension equivalent. Where you are unsure how a platform behaves, run the test above against the exact software the interview will use. Your own machine is a better source than any article, this one included.
The short version: apps stay off a screen share by flagging their own window so Windows leaves it out of the capture stream. That covers every screen sharing and recording tool at once, and it covers no camera at all.