How Invisible Screen Share Technology Actually Works
It's not a hack. It's not a workaround. Modern operating systems provide official APIs to exclude windows from screen capture. Here's exactly how they work.
When people hear that an overlay window can be "invisible to screen sharing," the first reaction is skepticism. How can something be visible on your screen but not on a Zoom call? It sounds like a magic trick.
It's not magic — it's a deliberate feature built into Windows and macOS. Both operating systems provide APIs that let applications mark their windows as excluded from screen capture. These APIs exist for legitimate reasons: password managers, DRM-protected content players, and enterprise security tools all use them.
This article explains exactly how these APIs work, what they protect against, and where the current limitations are.
Windows: SetWindowDisplayAffinity
On Windows 10 version 2004 and later, Microsoft provides a function called SetWindowDisplayAffinity in the Win32 API. This function controls how the Desktop Window Manager (DWM) handles a specific window during screen capture operations.
The API call
SetWindowDisplayAffinity(hwnd, WDA_EXCLUDEFROMCAPTURE)When a window has WDA_EXCLUDEFROMCAPTURE set, the DWM excludes it from all capture surfaces. This means the window is invisible to:
- → Zoom, Google Meet, Microsoft Teams screen sharing
- → Discord Go Live and screen share
- → OBS Studio and other recording software
- → Windows Snipping Tool and Print Screen
- → Any application using BitBlt, DirectX, or DXGI capture
How It Works Under the Hood
The Desktop Window Manager (DWM) is the compositing engine that renders all windows on your screen. When a capture API requests a frame of the desktop, DWM composes the final image. Windows with the exclusion flag are simply not included in that composition — they're rendered to your physical display but omitted from the capture surface. This happens at the OS level, below any application code.
The key insight is that the exclusion happens in the compositor, not in the capture application. This means individual apps (Zoom, OBS, etc.) cannot override it. They receive a frame that never contained the excluded window in the first place.
What about WDA_MONITOR?
An older flag, WDA_MONITOR, replaces the window with black in captures. This was the only option before Windows 10 2004. WDA_EXCLUDEFROMCAPTURE is strictly better — it removes the window entirely instead of showing a suspicious black rectangle.
Requirements and Limitations
Minimum version: Windows 10 version 2004 (build 19041) or later. Older versions fall back to WDA_MONITOR.
Hardware acceleration: DWM must be enabled (it is by default on all modern Windows). Remote Desktop sessions disable DWM, which breaks the exclusion.
Virtual machines: Works in most VM configurations where GPU passthrough or virtual GPU is available. May not work in basic VMs without GPU acceleration.
macOS: NSWindow.sharingType
On macOS, Apple provides a similar mechanism through the NSWindow.sharingType property. Setting it to .none excludes the window from screen capture, screenshots, and screen recordings.
The API call
window.sharingType = .noneThis works identically to the Windows approach — the window manager (WindowServer on macOS) omits the window from capture surfaces at the compositor level. The API was originally designed for DRM content protection, which is why QuickTime Player and other video players use it for protected content.
macOS 15 (Sequoia) Warning
Apple changed the behavior of sharingType = .none in macOS 15 Sequoia. Windows with this property may now appear as black rectangles in some capture APIs rather than being fully excluded. This is a known regression that affects all applications using this API, not just interview tools. If you're on macOS 15+, test carefully before relying on this feature.
What This Protects Against (and What It Doesn't)
Protected
- + All software-based screen capture
- + Video conferencing screen share
- + OS-level screenshots (Print Screen, Snipping Tool)
- + Recording software (OBS, Game Bar)
- + Remote desktop viewing by others
Not Protected
- − Someone physically looking at your monitor
- − External HDMI capture cards
- − A phone camera pointed at your screen
The protection is comprehensive against all digital capture methods because it operates at the compositor level. Physical capture (cameras, capture cards) bypasses the software stack entirely and cannot be prevented by any OS-level mechanism.
Why Operating Systems Provide This Feature
These APIs weren't built for interview tools. They exist because the OS needs to support applications that display sensitive content:
- →Password managers — need to show credentials without them appearing in screen recordings or shared screens during presentations
- →DRM video players — Netflix, Disney+, and other streaming services use capture exclusion to prevent screen recording of protected content
- →Enterprise security tools — data loss prevention (DLP) overlays and security dashboards that shouldn't be visible in shared presentations
- →Banking applications — financial apps that display sensitive account information
The APIs are public, documented, and available to any application. There's no special permission or certificate required. Any window can set these flags.
How Shadow Claude Implements Stealth Mode
Shadow Claude applies the display affinity flag immediately when the application window is created. The overlay window is configured as always-on-top, frameless, transparent, and excluded from screen capture — all before any content is rendered.
On Windows, this means calling SetWindowDisplayAffinity with the window handle during the Tauri setup hook. The window is also hidden from the taskbar and configured without decorations (no title bar, no borders), so there's no visual trace of the application in the Windows UI.
The stealth mode can be toggled at runtime if needed — for example, if you want to screenshot the overlay itself for debugging. But during normal operation, it stays enabled from launch to close.
How to Verify Invisibility
Test checklist
- □Open the overlay and share your screen on Zoom — the overlay should not appear on the shared screen preview
- □Try the Windows Snipping Tool while the overlay is visible — the overlay should not appear in the screenshot
- □Start an OBS recording, then review the footage — no trace of the overlay
- □Share your screen on Discord — the overlay should be completely absent from the stream
- □Try Print Screen and paste into Paint — the overlay region should show the desktop behind it
See It in Action
Download Shadow Claude and test the invisibility yourself. It's free to start — no credit card required.