Can Zoom Detect a Screen Overlay? How Screen-Share Capture Works (2026)

People ask “can Zoom see a screen overlay” and get confident answers in both directions. The reason the answers conflict is that the questioners mean different things and the technology is genuinely specific. Whether a window shows up in a screen share is not luck or marketing. It comes down to how the operating system builds the picture that gets captured. Once you understand that, you can tell which tools survive a screen share and which never will, without trusting anyone’s claim. Here is the plain-English version.

How screen sharing actually captures your screen

When you share your screen in Zoom, Google Meet, or Teams, the app does not photograph your monitor. It asks the operating system for the composited image, the final picture the OS assembles from every visible window. The meeting app receives that image and sends it to the call. So the real question is never “can Zoom see the window,” it is “did the operating system include that window in the image it handed over.”

That distinction is everything, because the OS decides what goes into the image, and there is a specific instruction that tells it to leave a window out.

The instruction that makes a window invisible to capture

Both major desktop operating systems have an API for exactly this. On Windows it is a window flag often referred to through the SetWindowDisplayAffinity call, which can mark a window to be excluded from capture. On macOS there is an equivalent screen-capture exclusion for a window. When an app sets this, the OS keeps drawing the window on your physical screen so you can see it, but omits it from the composited image used for capture. The result is a window that is fully visible to you and absent from the share.

This is not a hack or a loophole. It is a documented feature, originally meant for things like DRM-protected video and password fields. Screen-capture tools use it for legitimate reasons too. AI overlays use the same mechanism to stay out of a shared screen.

Why browser tools cannot do this

Here is the hard limit. A browser tab or extension does not control how the OS composites the screen. It lives inside the browser, which is itself just one window in the OS picture. A web page cannot call the OS-level capture-exclusion API for its own tab. So a browser-based assistant renders as normal content and is included in any full-screen share. This is the technical reason, not a matter of quality, that browser-based interview and meeting tools show up on a screen share while native desktop apps can hide. If a tool runs in your browser, assume it is visible.

What breaks it

The exclusion is reliable but not eternal, because the operating systems keep changing. Newer macOS releases tightened screen-recording permissions and changed how some capture paths work, which has caused overlays that used to hide to reappear on certain setups. Windows behavior before Windows 11 is less consistent. And the exclusion applies to the specific capture path the app requested; an unusual capture method or a hardware-level grab can behave differently. None of this means the feature does not work. It means you cannot assume it works forever without checking.

The one test that settles it

You never have to trust a claim about this. Start a meeting with just yourself in Zoom or Meet, share your entire screen, and then either record the meeting or join from a second device. Look at the shared or recorded view. If the overlay window is there, it is not excluded on your setup, whatever the marketing says. If it is gone, the exclusion is working. Do this again after any operating-system update, because that is precisely when it silently changes.

What this means when you pick a tool

Two practical rules fall out of the technology. First, if a tool is not a native desktop app, it cannot reliably hide from a full-screen share, full stop. Second, even a desktop app should be tested on your machine, because OS updates change the picture. The tools that take this seriously let you test for free rather than asking you to pay first. Craqly, for example, ships its stealth overlay on the free plan, so you can run the test above before spending anything. You can read how detection plays out in real interviews in our undetectable AI for interviews guide, or see a specific case in is Cluely detectable.

Why this feature exists in the first place

It helps to know that capture exclusion was not built for AI overlays. Operating systems added it for ordinary reasons. Streaming apps use it so that DRM-protected video does not end up in a screen recording. Password managers and banking apps use it so a sensitive field is not accidentally captured in a shared screen or a screenshot. Enterprise software uses it to keep confidential data out of casual recordings. In other words, the ability for a window to say “draw me, but do not capture me” is a mature, legitimate part of the platform. AI overlays did not invent a trick; they used a door the OS already built for privacy and content protection. That history is why the feature is stable and documented rather than a fragile exploit.

Where the exclusion can still fail

Understanding the mechanism also tells you its blind spots. The exclusion applies to the standard software capture path, the one Zoom, Meet, and Teams use. It does not necessarily cover every possible way to grab a screen. A hardware capture card filming an HDMI output sees the physical display, not the OS composite, so exclusion means nothing there. A phone camera pointed at your monitor obviously captures whatever your eyes see. And some specialized proctoring or monitoring software uses lower-level capture methods that can behave differently. For a normal remote interview or meeting over a standard app, none of this applies, but it is why “hidden from screen share” is a precise claim, not a blanket invisibility.

Three common myths

First, “if I can see it, they can see it.” False, and this is the whole point: the OS deliberately shows the window to you while omitting it from capture. Second, “browser extensions can hide too if they are good enough.” False, because a browser cannot reach the OS-level API for its own tab, no matter how well built. Third, “once it is hidden, it stays hidden.” False, because OS updates change capture behavior, which is why the only reliable knowledge is a fresh test on your current setup.

Screen-share detection FAQ

Can Zoom detect a screen overlay?

Zoom captures the image the OS composites. If a window uses the OS capture-exclusion API, it is left out of that image, so Zoom never receives it. Windows without that exclusion are captured normally.

Why do some AI tools show on a screen share and others do not?

Native desktop apps can call the OS capture-exclusion API; browser tabs cannot. That is the whole difference. Browser-based tools are captured; properly built desktop apps can be excluded.

Does this work on Google Meet and Teams too?

Yes, because they all capture the same OS-composited image. The exclusion is set at the operating-system level, not per meeting app.

Can a screen recording still catch the overlay?

A standard recording captures the same composited image, so an excluded window stays out of it. Unusual capture methods or OS updates can behave differently, which is why you test.

How do I know it works on my computer?

Share your full screen in a solo meeting and record it or view from a second device. If the overlay appears, it is not excluded on your setup.

What about the full job search pipeline?

If you are reading this comparison, you are probably either preparing for interviews or actively in a loop. Craqly helps you during the live conversation. It does not help you get the interview in the first place.

That gap is what LastRoundAI covers, and it is worth naming because it is our sister product and because it genuinely fills a hole Craqly leaves open. LastRoundAI builds your resume and scores it for ATS parsing, searches live job boards from Greenhouse, Lever, and Ashby, auto-applies with tailored resumes and cover letters (you approve every one), runs voice mock interviews with feedback, and gives you a live copilot for the calls that come out of it. The whole pipeline from “I need a job” to “I am in the room” lives on one account.

Plenty of people use both: LastRoundAI to get the interview, Craqly in the room for everything after it. The free plans on both sides are enough to decide whether the handoffs work for your search.

The bottom line

Screen-share detection is not mysterious. Your operating system builds the image that gets shared, and a documented API lets a window opt out of that image while staying on your screen. Desktop apps can use it; browser tools cannot. It is reliable but changes with OS updates, so the only real proof is testing your own setup, and the tools worth using let you do that for free.

Based on documented Windows and macOS screen-capture exclusion behavior as of 2026. Capture behavior changes with OS updates; always test your own configuration.