How it works
Streamproof Explained: How Capture Bypass Works and Where It Stops
Streamproof answers exactly one question: will the cheat menu appear in your recording. It does not answer whether the recording makes it obvious you are not playing unaided.
Streamproof describes a build whose interface does not appear in screen capture — not in an OBS recording, not in a Discord screen share, not in a screenshot. You see the menu on your monitor; the recording does not.
How it works
There are two technical routes.
Window properties. Windows lets an application mark a window so the system excludes it from capture. The relevant display-affinity flag is documented by Microsoft and supported from Windows 10 version 2004 onwards. The marked window remains visible on the physical display while capture APIs receive nothing. This is the standard approach for external builds with a separate overlay window.
Moving rendering off the captured surface. In DMA setups the question never arises: the overlay is drawn on a second computer, so there is nothing on the gaming machine to capture.
It also helps to know how OBS capture modes differ:
| Capture mode | What it grabs | Overlay behaviour |
|---|---|---|
| Game Capture | frames from the game engine | an external overlay is absent by definition |
| Window Capture | contents of one window | depends on the affinity flag |
| Display Capture | the entire screen | the strictest case, always test it |
Which is why “it’s invisible in Game Capture” proves nothing on its own. All three need testing.
Which builds have it
- External builds with overlays — most often, because a separate window is easy to control.
- Internal builds — less often: they draw inside the game frame, which gets captured whole, so hiding requires dedicated work. See internal vs external cheats.
- DMA setups — by construction, with no special measures at all.
Listings normally state streamproof on its own line. If the line is missing, assume the feature is missing.
Five limits that never go away
- It does not hide behaviour. This is the big one. A viewer sees the snap into an empty wall, the turn onto someone behind you, the route straight to the right container. The menu can be perfectly hidden while the gameplay is not.
- It does not defeat a camera. A phone pointed at the monitor bypasses every streamproof implementation ever written, as does a photo or a recording made on another device.
- It is not universal across capture paths. Game capture, window capture, display capture, messenger screen share and remote desktop are different mechanisms with different behaviour.
- Windows updates break it. Major updates change compositor behaviour and capture APIs. Something that worked a year ago can stop working after an update, and a live stream is the worst place to discover it.
- It has nothing to do with detection. Anti-cheats do not watch your stream. A hidden overlay does not impede signature or behavioural detection — see why cheats get detected.
Verifying it properly
- Record two or three minutes locally in OBS with Game Capture, Window Capture and Display Capture separately.
- Watch the whole file rather than the first seconds — some elements only appear during combat.
- Repeat in whatever messenger you actually share your screen through.
- Repeat after Windows updates, GPU driver updates and build updates.
- Only then record a real match.
The practical takeaway
Streamproof is useful and narrow. If you play Counter-Strike 2 or Valorant and post clips, treat it as mandatory — but the safety comes from how you play and how the settings are tuned, not from the feature itself. Demand it in the listing, verify it by hand, and never rely on it as protection.
The rest of the routine is in the safe launch checklist.