OBS Studio includes a setting called "Hide OBS windows from screen capture." It is useful. It is also narrowly scoped. A surprising number of streamers and presenters assume this setting protects their Discord, Slack, or password manager from OBS. It does not.
This post clarifies the exact boundary between what OBS does natively and what NoCapture adds.
What OBS Window Exclusion Actually Does
In OBS Settings → General, the checkbox "Hide OBS windows from screen capture" applies WDA_EXCLUDEFROMCAPTURE to OBS's own windows. This prevents the classic recursive capture problem: OBS capturing its own preview, which captures OBS again, creating an infinite tunnel.
OBS documents this setting here.
What it does not do:
- Hide Discord from OBS
- Hide Slack from OBS
- Hide your browser or password manager from OBS
- Hide any application that is not OBS itself
If you use OBS Display Capture to stream your desktop, every window on that display is visible to your audience unless you take additional steps.
The OBS Native Alternative: Window Capture
OBS Window Capture lets you capture a single application window rather than the entire display. This is a valid privacy strategy if you only ever show one app.
The friction appears when your workflow requires multiple apps:
- A code editor and a browser
- A design tool and a reference document
- A game and a chat overlay
You either create multiple Window Capture sources (performance cost, layout complexity) or you switch scenes constantly. For streamers who demo workflows, this is impractical.
Where NoCapture Fits
NoCapture operates below OBS, at the Windows compositor level. It removes designated windows from the capture stream before OBS ever receives the frame buffer.
This means:
- You can use OBS Display Capture for convenience
- Discord, Slack, email, and your password manager remain visible to you
- Those windows simply do not exist in the OBS canvas
- You verify this in NoCapture's live preview before going live
Additional protections OBS does not provide:
- Title masking. Even if a window is cloaked, its title may appear in Alt-Tab or taskbar previews if you switch apps mid-stream. NoCapture sanitizes these.
- Notification shield. A cloaked app can still throw a banner over your captured window. NoCapture suppresses notifications from protected apps.
- Routines. A "Streaming" routine can auto-cloak designated apps when NoCapture launches, removing the manual step.
When You Only Need OBS
If your setup is:
- One game or one app
- No sensitive windows on the same display
- You never Alt-Tab or switch contexts on stream
Then OBS Window Capture or Game Capture is sufficient. You do not need a third-party tool.
When You Need NoCapture
If your setup is:
- Desktop sharing with multiple apps
- Sensitive apps (Discord DMs, email, password manager) on the same monitor
- You switch contexts frequently
- You cannot afford to leak a notification or tab title
Then NoCapture adds a deterministic layer that OBS's native features do not cover.
Recommended Setup for Streamers
- OBS: Use Game Capture for the game. Use Window Capture for overlays if needed.
- NoCapture: Cloak Discord, Slack, email, password manager, and any browser with personal tabs.
- NoCapture Live Preview: Verify the OBS canvas before starting the stream.
- NoCapture Routine: Save a "Streaming" preset that auto-cloaks your standard list.
We wrote about the specific leak vectors streamers face here.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
