Can Zoom Detect Screen Overlay Software? The Technical Answer

What Zoom Captures During Screen Share

Understanding what Zoom actually captures — versus what it can hypothetically capture — is important for anyone asking about overlay visibility. This post covers the technical reality accurately.

When you share your screen on Zoom, the client captures the Desktop Window Manager (DWM) composited output: the rendered bitmap that your operating system sends to the display. Zoom has no special OS-level access beyond what a standard screen capture application receives. It captures what's visible in the composed frame sent by the OS graphics stack.

The critical technical point: what Zoom captures is determined by how each application window is flagged in the OS, not by Zoom's own capabilities.

How Window Display Affinity Works

Windows provides a system call — SetWindowDisplayAffinity — that allows applications to control how their windows appear in screen capture contexts. The relevant flags:

• WDA_NONE (0x00000000): Default. Window appears in all captures.
• WDA_MONITOR (0x00000001): Window appears on the physical monitor but is excluded from screen capture output. The window renders as a black rectangle or is entirely absent from capture streams.
• WDA_EXCLUDEFROMCAPTURE (0x00000011): Available in Windows 10 build 2004+. Window is excluded from all capture APIs, including BitBlt, DXGI, and Windows Graphics Capture.

Applications that use WDA_EXCLUDEFROMCAPTURE combined with WS_EX_NOACTIVATE (prevents the overlay from stealing focus) achieve both capture exclusion and non-intrusive UI behavior. This is the technical basis for display affinity in desktop overlay applications.

Why Browser Extensions Don't Achieve This

Browser-based assistants and Chrome extensions cannot use SetWindowDisplayAffinity because they run inside the browser process, not as separate OS-level windows. When you share a browser tab or the full browser window, Zoom captures the entire browser render — including any in-browser overlay, popup, or extension UI that's visible within that tab.

This is a fundamental architectural constraint, not a configuration option. Extensions that claim to be "invisible on screen share" while running inside the browser are, in most cases, misrepresenting their capability.

AissenceAI's Technical Approach

AissenceAI's stealth mode is a native desktop application that uses the OS-level display affinity API described above. The overlay window is a separate OS process from any shared application. When you share your screen, browser, or any other window in Zoom, the AissenceAI overlay is excluded from the capture stream at the OS level before Zoom ever receives the frame.

This is a technical property of how the OS handles window capture, not a cat-and-mouse workaround. It works because the OS decides what to include in capture output, and the display affinity flag is an official OS mechanism for that purpose.

Zoom Terms of Service Context

Using third-party applications during a Zoom meeting is not inherently a Terms of Service violation. Zoom's ToS primarily governs data privacy, recording consent, and platform abuse — not the applications running on your device. That said, specific company or institution policies (employer, university, testing platform) may have their own rules about what software can be running during interviews or assessments. Always check the specific rules of your context, not just the platform's ToS.

For interview prep (not live interviews), using AissenceAI is unambiguously appropriate — it's a practice tool, equivalent to using a book or flashcards.

FAQ

Can Zoom detect that I have other applications open during a meeting?

Zoom can see what's visible in your screen share. It cannot enumerate all running processes on your device — it has no access to your process list, file system, or application memory outside its own process.

Does SetWindowDisplayAffinity work on macOS?

macOS uses a different API (CGWindowListCopyWindowInfo and SCContentFilter with exclusion lists). The principle is the same — OS-level exclusion of specific windows from capture — but the implementation differs from Windows.

If I use a desktop overlay app during an interview, is that detectable?

A properly implemented native desktop overlay using WDA_EXCLUDEFROMCAPTURE does not appear in Zoom screen share output. What's detectable is behavior: long pauses, reading eye movements, unnatural answer timing. The interview performance is always the primary signal.