The most common privacy mistake in streaming is also the easiest to make: using OBS Display Capture because it's convenient, then forgetting that everything on that monitor is now broadcast to Twitch, YouTube, or a local recording.
OBS offers two built-in ways to limit exposure. Both work, but both have limits that break down when your workflow gets complex.
OBS Built-In Option 1: Window Capture
Instead of Display Capture, use Window Capture or Game Capture to grab only the application you want viewers to see. Discord, Slack, and your password manager can sit on the same monitor and never enter the stream.
The catch: If you need to show multiple apps — a browser, a code editor, a design tool — you either need multiple Window Capture sources (performance-heavy) or you keep switching scenes. For streamers who demo workflows, this is impractical.
OBS documents the difference here.
OBS Built-In Option 2: Hide OBS Windows from Screen Capture
In Settings → General, check "Hide OBS windows from screen capture." This prevents OBS from recursively capturing its own UI.
The catch: This only hides OBS. It does nothing for Discord, Slack, email, or any other app.
The Real Fix: OS-Level Window Cloaking
If you need Display Capture (because you switch apps constantly) but want specific windows permanently excluded, you need a tool that operates below OBS, at the Windows compositor level.
Option A: CaptureGuard (Free)
GitHub: xzulab/CaptureGuard
A lightweight Rust GUI. Pick your process, click Protect, close the GUI. The window stays visible to you but disappears from OBS.
Limitation: 64-bit only. No title masking, so if you Alt-Tab during stream, viewers might see "Discord — DMs with [Name]" in the taskbar even if the window itself is hidden.
Option B: NoCapture (Freemium)
NoCapture adds the metadata layer that CaptureGuard and Evanesco skip. It can:
- Cloak the window from capture
- Mask the title in taskbar and Alt-Tab
- Suppress notification banners from protected apps
- Show a live preview of exactly what OBS sees before you go live
- Save routines like "Streaming" that auto-cloak Discord, Spotify, and your password manager with one hotkey
Why this matters for streamers: You don't want to manually toggle protection every time you start a stream. A routine that auto-applies on launch — or a global hotkey you hit before going live — removes the human error factor.
We wrote about how streamers specifically leak personal messages here.
Recommended Streamer Setup
- OBS: Use Display Capture only if you need to demo multiple apps. Otherwise, prefer Game Capture for the specific game/app.
- NoCapture (or CaptureGuard): Cloak Discord, Slack, password manager, email, and any browser with personal tabs.
- NoCapture Live Preview: Verify the OBS canvas shows only what you intend before you hit "Start Streaming."
- Separate audio: Route music and alerts through OBS; route Discord and system notifications to your headphones only.
What None of These Tools Stop
A kernel-level capture bypass or a camera pointed at your monitor will still work. Microsoft explicitly states that WDA_EXCLUDEFROMCAPTURE is not a security boundary. What it does stop is the accidental leak — the notification, the background window, the tab title — which is how 99% of streamers get burned.
We covered the three layers of screen-share privacy here. Pixel protection is table stakes. Metadata protection (titles, notifications, taskbar) is what separates a close call from a viral clip you can't undo.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
