Every streamer has the same nightmare: a Discord DM, a Whisper, or a system notification appears on screen at the worst possible moment. The clip goes viral. The context is lost. The reputation damage is permanent.
Professional streamers don't rely on luck. They rely on architecture that guarantees private content never enters the broadcast pipeline.
The Standard Setup (And Why It Fails)
Window Capture instead of Display Capture. OBS can capture a single game or app window. Everything else on your monitor is ignored.
Why it fails:
- If you demo multiple apps — a browser, a design tool, a code editor — you need multiple Window Capture sources or constant scene switching.
- Notifications from other apps can still appear over the captured window if they draw on top.
- Browser tab titles, taskbar previews, and Alt-Tab switchers expose metadata even when the app itself isn't captured.
OBS documents capture source differences here.
The Second Monitor Setup (And Why It Fails)
Monitor 1: Stream content. Monitor 2: Discord, email, browser.
Why it fails:
- OBS Display Capture can be pointed at the wrong monitor by accident.
- Some capture cards and software default to "all displays."
- If you drag a window across monitors mid-stream, it enters the capture zone.
Monitors are a convenience, not a privacy guarantee.
The Deterministic Setup: OS-Level Cloaking
The only way to keep Discord, Slack, DMs, and email visible to you while guaranteeing they're invisible to OBS is to exclude them at the Windows compositor level.
Free Option: Evanesco
GitHub: k4yt3x/Evanesco
Select your Discord process, hide it from capture. It works against OBS, Snipping Tool, and most recorders.
Limitation: No title masking. If you Alt-Tab during stream, viewers see "Discord — DMs with [Username]" in the taskbar.
Free Option: CaptureGuard
GitHub: xzulab/CaptureGuard
A newer, lighter alternative with a clean process picker. Single EXE, no install.
Limitation: 64-bit only. No metadata protection.
Workflow Option: NoCapture
For streamers who switch scenes, apps, and games regularly:
- Cloak Discord, Slack, email, password manager from capture
- Mask titles so taskbar and Alt-Tab show generic names
- Suppress notification banners from protected apps
- Live preview to verify OBS canvas before going live
- "Streaming" routine that auto-cloaks designated apps on launch
We wrote about the specific leak vectors streamers face here. Tab titles and notification metadata leak more often than full window content — and they're harder to spot in the moment.
Recommended Streaming Architecture
- OBS: Game Capture for the game. Window Capture for browser overlays. Avoid Display Capture unless necessary.
- NoCapture (or Evanesco/CaptureGuard): Cloak all non-stream apps.
- NoCapture Live Preview: Verify the canvas before starting the stream.
- Audio routing: Discord and system alerts to headphones only. Game and music to OBS.
- Panic scene: A "BRB" or "Starting Soon" scene bound to a hotkey. If something goes wrong, switch instantly.
What "Streamer Mode" Actually Does
Discord's Streamer Mode hides personal information and disables sounds. It does not hide Discord from OBS. If Discord is visible on your shared display, it's in the stream. Streamer Mode is a Discord UI feature, not a capture-exclusion feature.
The Bottom Line
The streamers who never leak aren't more careful. They're more systematic. They assume they will make a mistake and build a pipeline where the mistake doesn't matter.
We covered the full three-layer privacy model here. Pixels are layer one. Metadata — titles, notifications, taskbar previews — is where most streamers actually get burned.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
