We get this question almost every day: "If I use NoCapture, can someone still take a picture of my screen with their phone?"
The answer is yes. And if any screen privacy tool tells you otherwise, they are lying.
What WDA_EXCLUDEFROMCAPTURE Actually Does
The Windows API that powers NoCapture, Evanesco, CaptureGuard, WinHider, and Cloakly operates at the software compositor level. It tells the Desktop Window Manager: "do not include this window in the frame buffer sent to supported capture APIs."
Supported APIs include:
- GDI/BitBlt
- DXGI Desktop Duplication
- Windows.Graphics.Capture
- Most screen recorders and conferencing tools
Microsoft documents this explicitly: "This is not a security boundary and is not intended to protect against malicious code or hardware."
What It Cannot Do
Physical cameras. A phone pointed at your monitor captures photons, not pixels. No software API can block light.
Kernel-level bypasses. Public proof-of-concept tools demonstrate that kernel drivers can read the display buffer below the DWM compositor. These bypasses are not theoretical. They exist.
EDR and monitoring software with system access. If your employer runs monitoring software with kernel-level or hypervisor-level access, it can capture the display before the DWM applies exclusion.
Hardware capture devices. An HDMI splitter and capture card sit between your GPU and your monitor. They see the raw signal.
Why This Honesty Matters
Some competitors use phrases like "undetectable" or "whole-PC shield." These claims create false confidence. A user who believes their screen is "unhackable" may share more sensitive information than they would if they understood the actual protection boundary.
We believe the opposite. Honesty about limitations builds trust. A user who knows that NoCapture stops Zoom, Teams, OBS, Snipping Tool, and AI screenshot agents — but not a camera — makes better decisions. They do not share nuclear launch codes over Zoom because a privacy tool is running. They use NoCapture for its actual purpose: preventing accidental software capture of background windows, notifications, and metadata during normal professional screen sharing.
What NoCapture Actually Protects Against
- Zoom, Teams, Google Meet, Discord screen sharing
- OBS, Streamlabs, and standard screen recording
- Snipping Tool and Windows Game Bar capture
- Screenshot-hungry AI agents using standard capture APIs
- DWM thumbnail enumeration and window title scraping
These are the threats that cause 99% of real-world screen-share leaks. The accidental notification. The background terminal. The forgotten tab title. NoCapture is deterministic protection against these specific, common failures.
We wrote about the three layers of privacy here.
The Bottom Line
NoCapture is not a security boundary. It is a privacy tool. It removes specific windows from specific software capture paths. It does not make your screen invisible to the physical world.
If you need protection against cameras, use a privacy screen filter. If you need protection against kernel-level capture, use a dedicated secure workstation. If you need protection against accidentally leaking Slack, email, or your password manager during a Zoom call, use NoCapture.
Know the tool's limits. Use it for what it does. Do not ask it to do what it cannot.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
