Few things kill a stream faster than the yellow warning at the bottom of OBS: “Encoding overloaded” or a rising “render lag” counter. Your viewers see stutter and frozen frames while you look fine locally. The good news is these two problems have different causes and clear, ordered fixes.
Encoding lag versus rendering lag
OBS reports two separate stats. “Skipped frames due to encoding lag” means the encoder cannot compress frames fast enough to keep up. “Frames missed due to rendering lag” means the GPU is too busy drawing your scene and the game to composite in time. They look similar to viewers but the solutions differ, so check the Stats dock (View, Docks, Stats) to see which counter is climbing.
Fixing encoding overload
Encoding overload usually means your CPU x264 preset is too aggressive or your GPU encoder is set beyond its real-time ceiling. Walk down this list in order.
| Step | Action | Impact |
|---|---|---|
| 1 | Switch from x264 to NVENC/AMF hardware encoder | Largest single fix; offloads CPU |
| 2 | Lower x264 preset (e.g. medium to veryfast) | Big CPU relief if staying on x264 |
| 3 | Drop NVENC preset one step (P7 to P6) | Frees encoder headroom |
| 4 | Lower output resolution or FPS (1080p60 to 720p60) | Reduces frames to compress |
| 5 | Close background apps stealing CPU/GPU | Reclaims resources |
Fixing render lag
Render lag is a GPU problem. The card is maxed by your game plus OBS compositing. Cap your in-game framerate a few frames below your monitor’s refresh so the GPU always has spare time, lower in-game graphics settings, reduce the number of heavy sources and filters in your scene, and make sure OBS is not adding needless high-resolution browser sources. On a single-GPU setup, a modest in-game settings drop frees exactly the headroom OBS needs.
Preventing lag before it starts
The best fix is avoiding the warning in the first place. Cap your in-game framerate a few frames under your refresh rate so the GPU always has spare time to composite the scene, and enable a hardware encoder from the start rather than defaulting to x264. Keep your scenes lean: every high-resolution browser source, heavy filter, and duplicated video source adds compositing cost that quietly eats headroom.
Monitoring habits help too. Leave the Stats dock visible on a second monitor during your first few streams after any settings change, and watch both the encoding and rendering counters. If you catch a slow climb early, you can drop a preset or trim a source before viewers ever notice. Building this awareness turns lag from a mid-stream emergency into a setting you tuned once and rarely think about again.
Frequently asked questions
Why does OBS run fine but viewers see stutter?
Because the lag happens inside the capture and encode pipeline, not on your display. Your monitor still shows the game smoothly while OBS quietly drops or delays the frames it sends out. That is why you must watch the Stats dock rather than trusting how the stream feels on your own screen.
Should I always use the hardware encoder to avoid overload?
For most single-PC streamers, yes. NVENC or AMF moves encoding onto a dedicated chip and virtually eliminates CPU-side encoding overload while looking excellent at modern presets. Software x264 only makes sense on a dedicated streaming PC or when you specifically want its top-end quality and have CPU to spare.
Bottom line
Open the Stats dock first and identify whether it is encoding or rendering lag. Encoding overload is fixed by moving to a hardware encoder or easing the preset and resolution. Render lag is fixed by capping in-game FPS and lightening both the game and your scene. Work the list top to bottom and the yellow warning disappears.
