Stream-proof means the cheat overlay is visible on your monitor but absent from anything that captures your screen. It is not a filter or a delay — it is a consequence of where the overlay is drawn. Capture software gets its frames from one of a few places. OBS and Streamlabs typically use game capture, which hooks the game's own presentation call and copies the frame the game produced. Discord screenshare and Xbox Game Bar use desktop duplication, which asks Windows for the composited desktop image. NVIDIA ShadowPlay hooks at the driver level. An overlay drawn inside the game's rendering pipeline becomes part of the frame the game presents, so every one of those methods sees it. That is how
means the cheat overlay is visible on your monitor but absent from anything that captures your screen. It is not a filter or a delay — it is a consequence of where the overlay is drawn. Capture software gets its frames from one of a few places. OBS and Streamlabs typically use game capture, which hooks the game's own presentation call and copies the frame the game produced. Discord screenshare and Xbox Game Bar use desktop duplication, which asks Windows for the composited desktop image. NVIDIA ShadowPlay hooks at the driver level. An overlay drawn
the game's rendering pipeline becomes part of the frame the game presents, so every one of those methods sees it. That is how most people get caught with evidence attached: they share a clip and the boxes are in it. Stream-proof implementations draw the overlay in a separate layer that is composited onto the display after the capture path has already taken its copy. The game presents a clean frame, the capture takes that clean frame, and the overlay is added on the way to your screen. The practical consequence is worth stating plainly:
stream-proofing protects you from your own recordings, not from the anti-cheat
. BattlEye does not detect cheats by taking screenshots of your desktop. Treat it as protection against self-incrimination rather than as a detection bypass.
This is where people get complacent, so it is worth being specific about the gaps. Phone cameras. Obvious, but it happens — someone films their monitor for a clip and the overlay is in shot. Hardware capture cards. A capture card reading the HDMI output sees exactly what the monitor sees, including the overlay, because the compositing happened before the signal left the GPU. If you stream from a second machine through a capture card, stream-proofing does nothing for you. Screenshots by some tools. Print Screen and certain screenshot utilities use different paths from video capture. Test yours specifically rather than assuming. Multi-monitor mirroring. If you mirror your display, the mirrored
This is where people get complacent, so it is worth being specific about the gaps.
Obvious, but it happens — someone films their monitor for a clip and the overlay is in shot.
A capture card reading the HDMI output sees exactly what the monitor sees, including the overlay, because the compositing happened before the signal left the GPU. If you stream from a second machine through a capture card, stream-proofing does nothing for you.
Print Screen and certain screenshot utilities use different paths from video capture. Test yours specifically rather than assuming.
If you mirror your display, the mirrored output may include the overlay depending on how the mirroring is done.
This is the big one. A viewer does not need to see boxes to know something is wrong. Pre-aiming at unseen enemies, reacting to a flank before it happens, or calling positions you should not know are all visible with a completely clean overlay. Stream-proofing hides the software, not the play — the same division of labour described in the BattlEye bypass guide.
Remote desktop and streaming-to-device tools.
Steam Link, Moonlight and similar tools use their own capture paths, which may or may not be covered.
If you produce content at all, these rules matter more than any setting. Test before you go live, on the exact software you use. Record thirty seconds, stop, and watch the file. Do this again after every update to OBS, your GPU driver, or the cheat itself. A stream-proof implementation that worked last month can break when a capture method changes. Bind a panic key. One key that disables every visual feature instantly. You want this for the moment a friend asks to look at something on your screen, not just for streaming. Disable overlays that composite on top. Discord overlay, Steam overlay and GeForce Experience all inject into the game and can interact badly with the cheat's rendering. The
If you produce content at all, these rules matter more than any setting.
Test before you go live, on the exact software you use.
Record thirty seconds, stop, and watch the file. Do this again after every update to OBS, your GPU driver, or the cheat itself. A stream-proof implementation that worked last month can break when a capture method changes.
One key that disables every visual feature instantly. You want this for the moment a friend asks to look at something on your screen, not just for streaming.
Disable overlays that composite on top.
Discord overlay, Steam overlay and GeForce Experience all inject into the game and can interact badly with the cheat's rendering. They are also additional capture paths.
If you post a highlight, assume someone will frame-step it. The question is never whether the boxes are visible; it is whether the movement makes sense without them.
Do not narrate information you should not have.
Saying there is a Bandit on the wall before you drone is worse than any overlay leak, because it is unambiguous and it is in the audio track.
Play more conservatively on camera than off.
The most common way streamers get caught is not a visual leak, it is a highlight reel of impossible reads. If you are recording, turn the assistance down or off — the ranked climb guide covers pacing.