How Invisible AI Apps Hide From Screen Sharing (and What Still Sees Them)

We build one of these apps, so we'll be specific. AuraCloak is a Windows overlay, and almost all of its "invisibility" comes from a single Win32 call. The rest of the work is making that call cover every window the app opens and being honest about what it doesn't cover.

The parts of an invisible AI overlay

Strip any of these apps down and you find the same building blocks. Only the first one has anything to do with screen sharing.

Notice what's missing: nothing in that table touches Zoom, Teams or Meet. Invisible overlays don't hook into meeting apps or the call. They change how the operating system treats their own window, and every capture tool that asks the OS for the screen gets the result.

On Windows: one flag in the compositor

Since Windows 8, the Desktop Window Manager (DWM) composes every frame on screen. Capture APIs (Windows.Graphics.Capture, DXGI Desktop Duplication and plain GDI screenshots) all receive frames from DWM. When an app calls SetWindowDisplayAffinity(hwnd, WDA_EXCLUDEFROMCAPTURE), DWM draws the window on your monitor and omits it from the frames those APIs get. Microsoft's description is that the window "is displayed only on a monitor. Everywhere else, the window does not appear at all" (Microsoft Learn).

Three practical rules follow from how it's built:

• It needs Windows 10 version 2004 (build 19041) or later. Older builds treat the request like WDA_MONITOR, which shows viewers a black box.
• An app can only flag its own top-level windows. Each dialog, menu and pop-up is a separate window that needs the flag too. We learned that the hard way with file pickers and WebView2 sign-in pop-ups.
• It's easy to turn off. WDA_NONE puts the window back in captures, which is useful when you actually want it in a tutorial recording.

We go deeper, with C# and C++ code and the bugs we fixed, in WDA_EXCLUDEFROMCAPTURE explained.

On macOS: sharingType, with an asterisk

AppKit has had a sharingType property on NSWindow for years (Apple Developer: sharingType). Setting it to .none asks the window server to keep the window's content out of capture. Electron exposes both platforms behind one method, win.setContentProtection(true), which is why many cross-platform overlays are Electron apps.

The asterisk is ScreenCaptureKit, Apple's newer capture framework. Developers on Apple's own forums have reported inconsistent results: a window with sharingType = .none missing from a ScreenCaptureKit stream at first and then appearing after a filter change, and windows excluded from screenshots but still showing in some recordings (Apple Developer Forums). Behavior has shifted between macOS releases. If you rely on a Mac overlay, test it with the exact meeting app and macOS version you'll use. (AuraCloak is Windows only, so we don't have a dog in this fight beyond wanting people to test.)

Does screen recording capture overlay windows?

A regular overlay, yes. A capture-excluded overlay, no, as long as the recorder captures through the operating system, which nearly all of them do. Here's how the common tools behave with an overlay that sets WDA_EXCLUDEFROMCAPTURE on Windows 10 version 2004 or later:

Does OBS capture hidden windows?

OBS's Display Capture source reads the screen through Windows capture APIs, so a window with WDA_EXCLUDEFROMCAPTURE isn't in the OBS preview or recording; you see whatever is behind it. This trips up streamers in the other direction too: if you want your overlay on stream, turn off the app's capture exclusion first. In AuraCloak that's a Settings toggle or [Privacy] ExcludeFromCapture=false.

What still sees an "invisible" app

This is the section most vendors leave out. Microsoft's own documentation says the function is not a security feature and won't protect content "where someone takes a photograph of the screen." In practice:

• Cameras. A phone, a webcam pointed at the desk, a document camera shared as a second camera in Zoom. They film the monitor.
• Projectors and duplicated displays. To Windows these are monitors, and the flag only hides windows from capture, not from displays. Presenting in a meeting room with your screen mirrored to a projector means the room sees the overlay.
• Hardware capture cards. A card recording your HDMI output gets the same signal as a monitor.
• Remote Desktop and some virtual machines. IOActive's 2026 analysis reports that the control can fail open in Remote Desktop sessions and in VMs without GPU acceleration (IOActive).
• Local software. Any program on the same PC can list windows and call GetWindowDisplayAffinity to see which ones are excluded. Meeting apps don't report this to participants, but employer monitoring tools on a managed laptop are a different matter.

So "invisible" really means "left out of screen shares and recordings". That's the claim we make for AuraCloak and it's the only honest one for any app in this category. Anyone advertising "100% undetectable" is selling something the operating system doesn't provide.

How the AI part works

The "AI" in an invisible AI app is usually the least exotic part. The overlay sends your text, and optionally a screenshot or a voice transcript, to a model provider and streams the answer back into the window. The differences between apps are in where that request goes and who pays for it.

AuraCloak, our invisible AI overlay for Windows, does it two ways:

• Your own API key. OpenAI, Anthropic Claude, Google Gemini, GitHub Copilot, Azure OpenAI or any OpenAI-compatible endpoint such as Ollama or LM Studio. Requests go straight from your PC to that provider; keys are encrypted with Windows DPAPI on your machine.
• Browser mode. The overlay embeds a browser, so you can log into ChatGPT, Claude.ai, Gemini or Perplexity with your normal account and use the subscription you already pay for. The browser window gets the same capture exclusion as the rest of the overlay.

Screenshots are where a careless implementation leaks. When you press Alt + S, AuraCloak hides itself for 250 ms, captures every monitor and attaches the image, so the overlay never appears in its own screenshot even if you've switched capture exclusion off. Voice input works only when you start it, using your microphone; it doesn't listen to the call. With the local Whisper engine, no audio leaves your PC at all.

Overlays vs meeting bots

The other common design for "AI in meetings" is a bot that joins the call as a participant, records it and transcribes it. Everyone sees the bot in the participant list. An overlay is the opposite: it never joins the call, never records it, and only knows what you type, say or screenshot. Different tools for different jobs. If you want minutes for the whole team, use a notetaker. If you want a private scratchpad and assistant while you present, use an overlay. The meetings use case covers that second setup.

Test any invisible app yourself

1. Check your Windows version with winver: 2004 (build 19041) or later.
2. Open the app over a recognizable background.
3. Take a full-screen capture with Win + Shift + S and inspect it.
4. Join a Zoom or Teams meeting from your phone and share your entire screen from the PC.
5. Open the app's settings, menus and file dialogs, and repeat steps 3 and 4. Pop-ups are where apps slip.
6. If you present in rooms, mirror to a TV or projector and see for yourself that the room sees it.

Our screen share visibility test turns this into a printable checklist.

FAQ

Are invisible AI apps really invisible?

They're invisible to screen sharing, screenshots and recordings that capture through the operating system. They're still visible on your monitor, to cameras, on projectors and duplicated displays, and to hardware capture cards. No app can honestly claim to be 100% undetectable.

Do invisible AI apps work on Mac?

Some do, using NSWindow.sharingType set to none. Developers have reported inconsistent results with Apple's newer ScreenCaptureKit capture, so behavior can vary by macOS version and meeting app. AuraCloak runs on Windows 10 and 11 only.

Can screen recording software capture an invisible overlay?

Not if it records through Windows capture APIs and the overlay sets WDA_EXCLUDEFROMCAPTURE on Windows 10 version 2004 or later. OBS Display Capture, Xbox Game Bar, Loom and the Snipping Tool leave such windows out. Older Windows builds show a black box.

Can other software on my PC tell an invisible app is running?

Yes. Any local program can list windows and check whether one is excluded from capture with GetWindowDisplayAffinity. Meeting apps don't report this to participants, but monitoring software on employer-managed devices may see it.

Do invisible AI apps join or record my meetings?

Overlay apps like AuraCloak don't join the call or record it. They run locally on your PC and only process what you type, say through your own microphone, or capture in a screenshot.