OBS

OBS Recording Lag: Find the Cause in the Stats Window

Nemo · · 6 min read

OBS recording lag comes from one of three places: the graphics card can’t draw OBS’s frames in time (rendering lag), the encoder can’t compress them in time (encoding lag), or the disk can’t keep up. Open View > Stats in OBS while you record: two counters there tell you which one it is, and each has a different fix.

Lowering the bitrate does nothing for rendering lag, so read the counters before you change anything.

How do you open and read the OBS Stats window?

  1. In OBS, click View, then Stats. To keep it visible, use the Docks menu and tick Stats, which pins it into the main window.
  2. Start a recording and play the game for a few minutes, including a busy fight.
  3. Watch two lines: Frames missed due to rendering lag and Skipped frames due to encoding lag. Each shows a count and a percentage.
  4. Stop and note which number moved.
Line in Stats What it means Usual cause
Frames missed due to rendering lag OBS could not compose a frame in time The graphics card is at full load, or the scene is too heavy
Skipped frames due to encoding lag The encoder could not finish a frame before the next one was due Encoder settings too demanding, or the CPU is busy (x264)
Dropped frames (network) Frames that never reached the streaming server Your connection. Applies to streaming only, not to recordings
Average time to render frame How long OBS takes per frame, in milliseconds Must stay well under the frame time: 16.7 ms at 60 fps
Disk space available / Disk full in Free space on the recording drive and the time left at the current rate A nearly full drive
FPS The frame rate OBS itself is running at Should match Settings > Video

A few missed frames over an hour are invisible. A percentage that keeps climbing during fights is the stutter you see in the file.

How do you fix rendering lag?

Rendering lag means the graphics card is too busy to give OBS its share. The game is using everything, and OBS’s own drawing waits. The OBS knowledge base’s advice is to stop the card from doing more work than it has to.

  1. Cap the game’s frame rate. An uncapped game takes all of the card. Cap it at your monitor’s refresh rate, or turn on V-Sync. This is the fix that works most often.
  2. Run OBS as administrator (Windows). Close OBS, right-click its shortcut and choose Run as administrator. This lets Windows give OBS priority on the graphics card while a game is running, and the OBS knowledge base lists it as the first thing to try.
  3. Lower the game’s graphics settings a notch. A small drop frees the headroom OBS needs.
  4. Simplify the scene. Browser sources, filters on large sources and high-resolution webcams all cost graphics time. Disable them one by one and watch the average render time.
  5. Close other programs that use the graphics card, such as a second game, a browser playing video or wallpaper animation software.
  6. Lower OBS’s own load. In Settings > Video, lower the Output (Scaled) Resolution or the frame rate, for example from 60 to 30. Treat this as the last resort, because it changes the file you get.

How do you fix encoder overload?

When the encoder falls behind, OBS shows “Encoding overloaded!” in the status bar and the skipped frames counter climbs.

  1. Use a hardware encoder. In Settings > Output, on the Recording tab, pick NVENC (NVIDIA), AMF (AMD), QuickSync (Intel) or Apple VT (Mac) and not x264. The x264 encoder runs on the processor, which the game also needs.
  2. Pick a lighter preset. Hardware encoders have quality presets, and x264 has speed presets. A faster preset costs a little quality and a lot less work.
  3. Lower the resolution or the frame rate in Settings > Video. Encoding 1440p at 60 fps is much more work than 1080p at 60.
  4. Update the graphics driver. Current OBS versions require recent drivers for hardware encoding. As of OBS 32.2, NVIDIA encoding needs driver 570 or newer.

On a modern graphics card, hardware encoding overload is uncommon. If it happens with NVENC or AMF, the card is usually saturated by the game, and the rendering lag fixes above help here too. Encoder choices are compared in OBS recording settings for gameplay.

How do you know if the disk is the problem?

The Stats window has no counter for a slow disk, so this cause is found by elimination. Suspect the drive when both lag counters stay at zero and the file still stutters or has gaps, or when the trouble starts as the drive fills.

  • Check the space. Stats shows the free space and an estimate of when the disk will be full. Recording to a nearly full drive is slow and can end the recording.
  • Record to an internal SSD. A USB hard drive or a network folder can stall when the game is loading from the same place.
  • Mind the bitrate. Very high quality settings write a lot of data per second. Raising the CQP or CQ level by 2 cuts that noticeably.
  • Use a crash-safe format. A stalled disk is one of the ways a recording gets cut off. See OBS recording formats.

What if the recording is fine and only playback lags?

Sometimes the file is healthy and the player is the problem. High-bitrate HEVC or AV1 at 1440p or 4K can stutter in a weak player or on a PC without hardware decoding. Test the file in VLC, or look at the Stats numbers from the session: zero missed and zero skipped frames means the recording itself is clean.

What do you do once the recording is smooth?

A clean file is the starting point. GameClip is a desktop app for macOS and Windows that turns a gameplay recording into clips: one highlights video in 16:9 and vertical cuts in 9:16 for Shorts, Reels and TikTok. It can drive OBS’s recording through OBS’s built-in WebSocket server, mark plays with a key while you play and open OBS’s file as a session when the recording stops. The guide to connecting OBS Studio shows the setup.

To be clear about the limits: GameClip does not fix lag. In OBS mode the encoder, quality, scenes and sources are all OBS’s, and GameClip does not change OBS settings. A recording that stutters in OBS stutters in the clips. Fix the cause with the steps above, then download GameClip for the editing part, described in how to edit OBS recordings.

FAQ

Why is my OBS recording laggy when the game runs fine?

The game is taking all of the graphics card and OBS can’t draw its own frames in time. Open View > Stats: if “Frames missed due to rendering lag” climbs, cap the game’s frame rate and run OBS as administrator.

What does “Encoding overloaded” mean in OBS?

The encoder can’t compress frames as fast as they arrive, so OBS skips some. Switch to a hardware encoder, choose a lighter preset, or lower the output resolution or frame rate.

What is the difference between rendering lag and encoding lag?

Rendering lag happens before the encoder: OBS could not compose the frame, usually because the graphics card is at full load. Encoding lag happens at the encoder: the frame existed and could not be compressed in time.

Do dropped frames matter for recording?

The “Dropped frames (network)” line is about streaming: frames that didn’t reach the server. A local recording is not affected by your connection. For recordings, watch the rendering and encoding lines.

Does lowering the bitrate fix OBS recording lag?

Rarely. Bitrate matters for the disk and for streaming over a slow connection. Rendering lag and encoder overload are about work per frame, which resolution, frame rate, presets and the game’s own load decide.

Contact

Licence keys, billing, bugs and ideas. We reply by email.