How to hide an application from screen share on Windows
Minimising a window does not hide it from a screen share, and moving it to a second monitor only works until someone asks you to share your whole desktop. The reliable mechanism is capture exclusion — a Windows flag that removes a window from the frames capture APIs receive. This guide explains why the usual workarounds fail, how capture exclusion differs from them, and how to verify that a window is genuinely invisible to the other side of a call.
Why the usual workarounds fail
Most advice on this topic recommends one of four things. Each of them breaks in a predictable way, and it is usually mid-call.
Sharing a single window instead of the desktop
This genuinely works — right up to the moment the interviewer asks you to share your entire screen so they can watch you navigate. Then every workaround built on window-only sharing evaporates at once.
Using a second monitor
Fine for desktop sharing of monitor one. But a full-desktop share on many setups spans displays, and screen-share pickers frequently list both. It also fails on a laptop with no second display, which is most interviews.
Alt-tabbing away when sharing starts
You are relying on reflexes while simultaneously answering a technical question. It also does nothing about the moment before you react, which is exactly when a recording captures it.
Virtual desktops
Switching virtual desktops mid-share is visible as an obvious full-screen transition, and a full-desktop capture follows you to the new desktop on many configurations.
What capture exclusion does differently
Windows lets an application mark one of its own windows as excluded from capture. When the compositor assembles the frame that a capturing application will receive, it leaves that window out. The window is still drawn to your physical display at full quality — the difference exists only in the copy handed to the capture API.
Because the exclusion is applied at the compositor rather than inside the conferencing app, it does not depend on which conferencing client is running, and it does not require modifying that client. It depends only on the client using a capture path that goes through the Windows compositor, which the current builds of the major clients do.
The important consequence: it survives a full-desktop share. You can hand over your entire screen, spanning every monitor, and the excluded window is still absent from what the other side receives.
Workarounds compared
How each approach holds up under the conditions that actually occur in a live interview.
| Approach | Survives full-desktop share | Needs a second monitor | Fails silently |
|---|---|---|---|
| Share one window only | No | No | No — the failure is obvious |
| Second monitor | Often not | Yes | Yes |
| Alt-tab away | No | No | Yes |
| Virtual desktops | Often not | No | Yes |
| OS capture exclusion | Yes, on supported paths | No | No — testable in advance |
Test it before you need it
Every method above can be verified in three minutes, and any method you have not verified should be assumed broken.
Open a solo meeting
Start a meeting in the client you will use for the interview, with no other participants.
Share your entire screen
Choose the most demanding case — the full desktop — rather than the one that is easiest to pass.
Watch from a phone
Join the same meeting from a phone and inspect the shared view. That view is what the interviewer receives, pixel for pixel.
Re-test after major updates
Conferencing clients occasionally change capture methods between major versions. A re-test costs three minutes.
Frequently asked questions
- Does minimising a window hide it from a screen share?
- No. On a full-desktop share, a minimised window is not rendered so it is not captured — but the moment you restore it to read anything, it is captured. Minimising is not a privacy mechanism, it is a delay.
- Can I hide a window from screen share without extra software?
- Only by not sharing the surface it is on — sharing a single window, or a monitor it does not sit on. Windows exposes capture exclusion to applications rather than to users, so a window can only exclude itself. There is no user-facing toggle that hides an arbitrary third-party window from capture.
- Does capture exclusion work when the whole desktop is shared?
- Yes, on supported capture paths. That is the property that separates it from every monitor- or window-based workaround, all of which assume the shared surface is one you control.
Try CueNova before it matters
Creating an account is free and needs no payment method. Set up your resume, run one practice round, and confirm your audio and screen-share behaviour on your own machine.