World of Warcraft looks like an easy game to stream until raid night. Questing through an open zone is slow, predictable motion that any encoder handles at modest bitrates. Then a 20-player Mythic pull starts, forty spell effects fill the screen at once, and the same settings turn into a blocky mess. On top of that, WoW viewers actually read your screen: tooltips, chat, weakauras, and damage meters all need to stay legible. Here is how to set up OBS for both halves of the game.
Quick Answer
Stream World of Warcraft at 1080p 60fps with 6,000 Kbps CBR on Twitch using NVENC preset P5, keyframe interval 2 seconds, and the Lanczos downscale filter for sharp UI text. If raids still look muddy, drop the output to 1664x936 (936p) at the same 6,000 Kbps.The 936p trick works because you keep the full Twitch bitrate but spread it across fewer pixels, which sharpens both spell effects and the small interface text viewers are squinting at.
Why World of Warcraft Is Two Games for Your Encoder
WoW has two completely different encoding profiles, and you have to tune for the harder one:
- Questing and open world: the camera glides, the ground barely changes, and temporal compression works beautifully. Even 3,500 Kbps looks clean here.
- Raids and Mythic+ dungeons: 20 to 40 players stacking ground effects, procs, trinket animations, and boss mechanics is pure particle spam. Every frame is full of high-frequency detail that did not exist one frame earlier, which breaks motion prediction and crushes the encoder.
- UI text everywhere: cast bars, chat, tooltips, and damage meters are thin, high-contrast text. Compression artifacts hit small text first, and WoW viewers notice immediately because reading your UI is half the reason they are watching.
- Dark dungeon lighting: shadowy areas show banding and blocking more readily than bright scenes.
If you tune for questing, raid night will look terrible. Tune for raid night and questing simply looks flawless. That means running the full bitrate cap at all times. For the underlying theory, see our best OBS bitrate settings guide.
Recommended OBS Settings by Platform
Twitch (6,000 Kbps cap)
- Resolution: 1920x1080, or 1664x936 for extra sharpness
- FPS: 60
- Encoder: NVENC (New), H.264
- Preset: P5 (Slow)
- Rate Control: CBR
- Bitrate: 6,000 Kbps
- Keyframe Interval: 2 seconds
- Profile: High
- B-frames: 2
- Downscale Filter: Lanczos (critical for UI text)
Details on ingest limits are on the Twitch platform page.
YouTube Live
- 1080p 60fps: 9,000-12,000 Kbps
- 1440p 60fps: 15,000-20,000 Kbps if your upload allows it
- Encoder: NVENC P5, or NVENC AV1 on RTX 40-series and newer
YouTube's higher ceiling is a genuine gift for raid streamers. At 12,000 Kbps, a 25-player pull with full ground effects stays readable in a way Twitch simply cannot match.
Kick
Kick accepts roughly 8,000 Kbps, so run 7,000-8,000 Kbps at 1080p 60fps. That extra 1,000-2,000 Kbps over Twitch noticeably cleans up dense spell effects.
Encoder Settings
NVENC (NVIDIA GPU): recommended
WoW is CPU-bound in raids, not GPU-bound, so your graphics card usually has plenty of headroom for its dedicated encoder chip:
- Rate Control: CBR
- Bitrate: 6,000 Kbps (Twitch) or 9,000+ (YouTube)
- Preset: P5 (Slow), or even P6 since WoW rarely maxes the GPU
- Profile: High
- Look-ahead: Off
- Psycho Visual Tuning: On
- B-frames: 2
x264 (CPU) fallback
Be careful here. WoW raids hammer the CPU with 20-plus player calculations, and x264 competes for those same cores. If you must use it:
- Preset: Medium at most, Fast if raid frames stutter
- Bitrate: same as NVENC
- Profile: High
If your raid FPS drops when the encoder kicks in, that is x264 stealing cycles from the game. The tradeoffs are covered in NVENC vs x264 for streaming.
In-Game Settings That Help Your Stream
A few WoW settings directly reduce the compression load without hurting your gameplay:
- Projected Textures: keep On (you need swirlies), but lower Particle Density to Medium. High particle density is the single biggest bitrate eater in raids.
- Spell Density: Essential or Some. This hides other players' unnecessary effects, which cleans up both your screen and your stream.
- Shadow Quality: Medium. High shadows add dark gradient areas that band badly at 6,000 Kbps.
- Camera shake and full-screen glow effects: reduce where possible; full-frame flashes force keyframe-sized data spikes.
- UI Scale: consider nudging it up slightly. Text rendered a little larger survives compression far better, and viewers on phones will thank you.
- Motion Blur: WoW does not have aggressive motion blur, but disable any camera smoothing addons that add sweeping pans.
Keep your damage meter and chat windows away from the very edges of the screen, where encoding quality is often weakest.
Internet Requirements
For 1080p 60fps at 6,000 Kbps on Twitch, you want at least 10 Mbps upload so the stream never saturates the line during a pull. For YouTube at 9,000-12,000 Kbps, aim for 15-20 Mbps upload. Raid nights are long sessions, so stability matters more than raw speed: use ethernet, not Wi-Fi, and run a speed test at your normal raid hour, not at noon. If you also run Discord voice for your raid team, budget another 0.5-1 Mbps on top. Our streaming bitrate calculator will match your measured upload speed to a safe bitrate, and the frame rate question is settled in 30fps vs 60fps streaming: for WoW, 60fps wins because smooth camera turns and ability queues read much better in motion.
Bottom Line
Tune WoW for raid night, not for questing. Run the full 6,000 Kbps on Twitch with NVENC P5 and the Lanczos filter, push 9,000-12,000 Kbps on YouTube, trim particle density and spell density in game, and try 936p if Mythic pulls still smear. Your open-world content will look perfect by default, and your raid content, the part people actually tune in for, will stay sharp enough to read every tooltip.