It arrives mid-fight. A toast slides in from the bottom-right corner of your screen — a Discord DM, a calendar reminder, an email preview with a client's name in the subject line. It sits on top of your game for five seconds. On stream, those five seconds are a lifetime.
Notifications are the most common leak in gaming streams, and the most underestimated, because they don't require a single mistake. You don't alt-tab. You don't change scenes. You just play, and Windows announces your private life over your gameplay.
Why Notifications Ignore Your Capture Setup
A notification banner is rendered by Windows itself, above everything — including your game and including whatever OBS is capturing. It doesn't matter whether you're on Game Capture, Window Capture, or Display Capture:
- On Display Capture, the banner is a full leak — text, sender, preview.
- On Window/Game Capture, the banner may still composite into the frame in borderless or capture-card setups, and it always covers your game for your viewers' experience.
- In Discord screen shares and clip tools, banners are captured identically. The mode is irrelevant.
The banner draws on the same surface your audience watches.
Focus Assist Isn't the Answer
Windows Focus Assist (Do Not Disturb) is a blunt instrument:
- It's system-wide. Silence everything or nothing. Your team captain's ping dies alongside the promo email.
- Priority lists are manual and fragile. One missed setting and a "priority" app leaks.
- It doesn't know you're streaming. It turns on by schedule or by fullscreen detection — which misfires constantly on borderless games.
- Game Mode and Streamer Mode don't coordinate with it. Three systems, none of them aware of the others.
A gamer shouldn't need to reconfigure Windows notifications before every stream and remember to undo it after.
What Surgical Shielding Looks Like
Notification shielding is different from Do Not Disturb in one key way: selectivity.
- Per-app suppression. Discord DMs? Held. Your music app? Held. Your calendar? Held. The alerts you actually want — none of them leak.
- Stream-aware. Protection activates when your streaming routine starts, not on a schedule. Queue a casual offline session and nothing changes.
- Queued, not deleted. Held notifications arrive after the stream. You miss nothing — your audience sees nothing.
- Local visibility preserved. You can still pull up the notification center yourself. The shield blocks the capture stream, not your own access.
This is Layer 2 protection in the three-layer privacy model — metadata and surface defense that sits on top of pixel cloaking.
The Compounding Problem
Notifications don't just leak on their own — they cause other leaks. A banner appears, you reflexively alt-tab to dismiss it, and now the taskbar switcher is on screen. A ping sound plays, you glance at the wrong monitor mid-fight. Kill the notifications and you kill most of the triggers that lead to everything else.
The Bottom Line
You can't out-discipline a toast. It's engineered to grab attention — that's its entire job. The only winning move is making sure the toast never reaches the surface your audience sees.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
