Choosing a capture mode in OBS feels like a privacy decision. It isn't. It's a scope decision — you're choosing how much of your screen is eligible to leak, not whether leaking is possible. Here's what each mode actually sees, and why even the "safe" ones have holes.
OBS documents the capture source differences here.
Game Capture: The Tightest Scope, With Overlays
Game Capture hooks the game's rendering pipeline directly. Your desktop, taskbar, and other windows never enter the frame.
What it protects: everything outside the game window.
What it doesn't:
- Any app that draws over the game — Discord overlay, GeForce Experience, MSI Afterburner, achievement toasts — can appear in the captured frame.
- The moment you switch scenes to show a browser, launcher, or queue screen, you're no longer in Game Capture.
- Some games (borderless-window edge cases, anti-cheat conflicts) fall back to Window Capture or Display Capture silently. You won't notice. Your chat will.
Window Capture: One Window, Plus Whatever Sits on Top
Window Capture grabs a specific application window. Fine for showing your browser or launcher.
What it doesn't protect:
- Notifications from other apps rendering above the window.
- Popups and dialog boxes from the same app — a download prompt, a cookie banner, an update dialog.
- The window title itself, which remains visible to scrapers and enumeration tools even when the window is minimized.
Display Capture: Your Entire Monitor, No Exceptions
Display Capture duplicates the whole screen through DXGI Desktop Duplication. Everything visible to you is visible to the stream: taskbar previews, notification banners, desktop icons, wallpaper, that folder named "stuff."
When gamers end up here without realizing: Display Capture is the default fallback when Game Capture fails, when a game runs in exclusive fullscreen that hooks can't touch, or when a streamer copies a scene from a tutorial. It's also the mode most capture cards and "share screen" buttons in Discord and Zoom use.
The Mode Doesn't Matter If the Window Is Cloaked
Here's the shift most guides miss: capture mode is your choice, but capture APIs are everyone's choice. Discord's screen share, a friend's recording, a clip tool, an AI assistant with screen access — they don't respect the scene you built in OBS.
The only layer that holds regardless of mode is OS-level cloaking. A window excluded via WDA_EXCLUDEFROMCAPTURE is absent from Game Capture, Window Capture, Display Capture, DXGI duplication, and Discord screen share alike. It isn't blurred. It isn't covered. It's not in the frame.
We covered the honest limits of every WDA-based tool here.
Recommended OBS Setup for Gamers
- Game Capture for the game, with "allow transparency" and overlay hooks reviewed.
- Window Capture only for apps you intend to show.
- Avoid Display Capture unless nothing else works — and if you must use it, assume your entire monitor is broadcast.
- NoCapture (or Evanesco/CaptureGuard) cloaking everything private, so the capture mode stops being a load-bearing decision.
The Bottom Line
Game Capture is a good habit. It's not a guarantee. Guarantees live one layer lower — at the compositor, where the OS decides what exists in the capture stream at all.
NoCapture provides OS-level window cloaking, title masking, and notification shielding for Windows. Free for two windows. Because "being careful" isn't a strategy.
