I spent a week convinced my internet upload was the problem because my stream turned into a blocky mess every time I played Apex Legends, even though the exact same settings looked clean when I played a slower game. My upload was fine the whole time. The actual issue was that fast, chaotic games need more bitrate to look clean than calm ones do, at the exact same resolution and frame rate, and nobody explains that part before you start streaming.
Why the Same Bitrate Looks Different in Different Games
Blurry or pixelated video during a stream is almost always a bitrate problem, not a hardware problem. When there isn’t enough bitrate for what’s happening on screen, the encoder can’t preserve detail during high-motion scenes, and you get the blockiness, blur, or smeared “macroblocking” look people usually blame on their internet. The catch is that a slow-paced game and a fast one need genuinely different amounts of bitrate to look equally clean, because a fast game is asking the encoder to compress far more changing information every second. The same 6000kbps that looks fine in a slower title can visibly fall apart in something like Apex or a fast-paced shooter with constant motion and particle effects.
Twitch’s official guidance has actually moved on this: for years 6000kbps was the standard recommendation for 1080p60, but Twitch raised its recommended bitrate to 8000kbps for 1080p60, specifically because the older number wasn’t holding up for modern, faster-motion games.
The AV1 Option Most Streamers Don’t Know They Have
If you’re on a modern RTX GPU, there’s a genuinely underused option here: AV1 encoding is roughly 30-40% more efficient than the older H.264 encoding most people default to, which means a lower bitrate in AV1 can look better than a higher bitrate in H.264 during exactly the fast-motion scenarios that break the old settings. In practice, this means something like 5500kbps in AV1 can look cleaner in a fast game like Apex or Marvel Rivals than 8000kbps did in H.264. This requires enabling Twitch’s Enhanced Broadcasting in OBS 30 or newer (a checkbox in your stream settings after logging into your account), since that’s what lets Twitch’s pipeline actually accept and process the newer codec properly instead of falling back to standard H.264.
The Other Reason Your Stream Might Be Choppy: What’s Actually Doing the Encoding
Separate from bitrate, there’s a second, completely different problem that gets confused with it: what hardware is doing the actual encoding work. NVENC, the hardware encoder built into RTX graphics cards, uses only about 1-2% of your CPU to produce solid 1080p60 video. The older x264 software encoder, by contrast, uses roughly 18-25% of your CPU at a medium quality preset, and that CPU load is shared with whatever the game itself needs — which is exactly why x264 can cause stutters and frame drops during fast action on a single-PC setup, even though the visual quality difference between the two encoders has become nearly indistinguishable to viewers at normal streaming bitrates.
If OBS is showing “Encoding overloaded” warnings, rising render times, or dropped frames specifically during busy scenes, that’s a strong sign you’re CPU-bottlenecked on x264 and should switch to NVENC rather than continuing to chase bitrate settings. The only real exception is if you’re running a dedicated second PC just for encoding, or you have an unusually strong CPU paired with a weaker GPU — in either of those specific cases, x264 can still make sense.
What to Actually Set
For most single-PC streamers on an RTX card: use NVENC, not x264, and if your card supports it, enable AV1 through Twitch’s Enhanced Broadcasting rather than defaulting to H.264. For bitrate, treat 8000kbps as the realistic baseline for 1080p60 in fast-paced games, not 6000, and if you’re using AV1, you can often drop to around 5500kbps and still look cleaner than the old H.264 default. If your stream still looks rough at these settings, the next thing to check isn’t your bitrate at all, it’s whether OBS is reporting dropped or skipped frames, which points to a CPU or network problem rather than a codec problem.
For a closely related buying question, see Best Streaming + Gaming Setup (2026).
We cover the related angle in The Games That Actually Make You Faster (And the Ones That Don’t).
FAQ
Why does my stream look worse in fast games than slow ones at the same settings?
Fast games generate far more changing visual information per second, which requires more bitrate to encode cleanly. The same bitrate that looks fine in a slow game can produce visible blur or blockiness in a fast one.
Should I use NVENC or x264 for streaming?
For almost all single-PC streamers with an RTX GPU, NVENC. It uses a fraction of the CPU that x264 does (roughly 1-2% versus 18-25%), and modern quality is nearly indistinguishable from x264 at typical streaming bitrates.
Is AV1 worth switching to for streaming?
Yes, if your GPU and OBS version support it through Twitch’s Enhanced Broadcasting. It’s roughly 30-40% more efficient than H.264, meaning a lower bitrate in AV1 can look better than a higher bitrate in H.264, especially in fast-motion games.

1 thought on “Why Your Stream Looks Blurry in Fast Games Even at ‘Good’ Bitrate”