OBS Lagging - How to Fix Recording and Streaming Lag

Almost everything written about OBS lag is a list of settings to change, and that is why people spend a weekend on it and end up back where they started.

OBS has three separate kinds of lag. They have different causes, they need different fixes, and a fix for one does absolutely nothing for the other two. Switching to a hardware encoder will not save a bad Wi-Fi connection. Lowering your bitrate will not help a GPU that is being starved by your game.

So do not change a single setting yet. Spend two minutes finding out which one you actually have.

Step 1: Open the Stats dock

OBS keeps a running count of exactly which frames it lost and why. It is just hidden.

View, Docks, Stats.

Dock it somewhere you can see, then reproduce the lag: run your game, run the recording, do whatever makes it stutter. Watch which of these three numbers climbs.

Step 2: Read the three counters

Three counters, three completely different worlds. Note the last one carefully:

If you are only recording to disk and not streaming, the network counter is permanently zero. It has to be. There is no network involved. So if you are recording locally and someone tells you to lower your bitrate to stop "dropped frames", they have misdiagnosed you. Whatever is wrong is one of the other two.

Step 3: Go to the right fix

Once you know which counter is climbing, the rest of the work is specific and short:

Skipped frames, encoding lag. Your encoder missed its deadline. This is the most common OBS lag by far, and it is usually one setting away from fixed. It is also what produces the red "Encoding overloaded" warning. Full fix: OBS encoding overloaded, what it means and how to fix it.

Missed frames, rendering lag. Your GPU is out of headroom, usually because a game is consuming all of it and OBS is queued behind it. The fixes are capping your in-game frame rate, running OBS as administrator, and cutting the canvas and source load. Covered in the rendering-lag section of OBS dropping frames.

Dropped frames, network. Streaming only. Your bitrate exceeds what your connection can actually sustain. Full fix: OBS dropping frames, why it happens and how to stop it.

All three counters are zero, but OBS still feels sluggish and your machine is loud. Your recording is fine. What you have is a resource problem, not a lag problem. That is OBS high CPU usage.

Before you go: two lags that are not lags

A meaningful number of people trying to fix OBS lag do not have an OBS problem at all. Rule these out first, because they are free.

The preview is choppy but the file is fine

The OBS preview panel is a live composite that runs at a deliberately low priority. When the machine is under load, OBS will happily let the preview stutter in order to protect the frames that go to your file or your stream. That is the correct trade and it is working as designed.

Never diagnose lag from the preview. Record thirty seconds, stop, and open the file. If the file is smooth, nothing is wrong and you can close this article. You can also right-click the preview and choose Disable Preview, which frees up real resources during a recording.

The file is fine but your player is struggling

If your recording stutters in Windows Photos, or VLC drops frames on it, try opening the same file in a different player, or drop it onto a video editor timeline.

High-bitrate, high-frame-rate, variable-frame-rate footage is genuinely hard to play back in real time, and some players handle it badly on some machines. The file can be perfect while the playback is not. This wastes an astonishing amount of people's time.

The two fixes that help every kind of lag

Once you have your diagnosis, go to the specific article. But there are exactly two changes that help across the board, so if you are in a hurry, start here.

Run OBS as administrator (Windows)

Right-click the OBS shortcut, Run as administrator.

Windows gives GPU scheduling priority to whatever has focus, and if the app with focus is an elevated, full-screen game, OBS gets whatever is left over. Running OBS at the same privilege level lets it compete for GPU time on equal terms instead of waiting in line behind your game. This is the single highest-value change for rendering lag, it takes five seconds, and it costs nothing.

To make it permanent: right-click the shortcut, Properties, Compatibility, tick Run this program as an administrator.

Cap your game's frame rate

If your game is rendering at an uncapped 300 fps, it is consuming 100 percent of your GPU to produce frames nobody sees, and OBS is fighting for scraps.

Cap it. In-game frame limiter, or your driver control panel. Set it to your monitor's refresh rate, or a little under. Your game will look identical and OBS will suddenly have room to work.

Uncapped frame rate in a demanding game is, in practice, the most common single cause of OBS rendering lag.

The fourth bottleneck, and the Stats dock will not show it to you

There is a failure that produces exactly the same symptom as encoding lag, sits in none of the three counters, and wastes a great deal of people's time: your disk cannot absorb the file fast enough.

OBS is writing a continuous, high-bitrate stream to storage for the entire recording. If the write stalls, the recording stutters or stops, and every counter you were told to check reads zero.

Four ways people cause it without realising:

• Recording into a synced folder. If your output path is inside OneDrive, Dropbox, Google Drive or iCloud, the sync client is trying to upload a multi-gigabyte file while it is still being written to. This is a genuinely common and genuinely destructive mistake. Record somewhere local and move the file afterwards.
• Recording to an external drive over a slow bus, or to a network drive. USB 2.0 and Wi-Fi network shares cannot sustain a high-bitrate video write.
• A nearly full SSD. SSDs slow down significantly once they are close to capacity, because they run out of free blocks to write into. If your drive is above about 90 percent full, that is your problem.
• A mechanical hard drive, especially one that is also being read by the game you are recording.

The fix: record to a local SSD with real free space on it. If OBS is warning about high disk usage in the status bar, or your recording quietly stops on its own, this is your answer and nothing else on this page is.

Lag that gets worse the longer you record

If your first five minutes are clean and it falls apart at the twenty-minute mark, stop looking at settings. Settings do not change themselves halfway through a take.

Two things do get worse over time:

Thermal throttling. Your CPU and GPU are slowing themselves down to avoid cooking, which is very common in laptops and in any machine with a year of dust in it. The signature is unmistakable: fine when cold, degrades steadily as it heats up, and completely fine again after the machine has sat idle for ten minutes.

Running on battery. Many laptops aggressively cut GPU and CPU power the moment they are unplugged, and will happily do it mid-recording when the charger falls out. Plug the laptop in and set the Windows power mode to Best Performance, or on macOS, disable Low Power Mode. This is a thirty-second fix that people spend hours not finding.

If you just want settings that work

For a screen recording, where nothing on screen is moving fast enough to need 60 frames a second, this configuration will not overload almost any machine made in the last several years:

That is the whole configuration, and if you are recording tutorials rather than gameplay, you should not need to revisit it. If you want the reasoning behind each of these, it is in OBS encoding overloaded and OBS best settings for screen recording.

If you are recording tutorials, most of this is self-inflicted

Every fix above exists to manage a tension OBS creates on purpose: it hands you full control of the encoder, the canvas, the frame rate and the bitrate, and full control means full responsibility when the combination does not fit your hardware.

That trade is worth it if you are running a multi-camera live production. It is a strange trade if you are recording a five-minute product walkthrough, where the correct settings are the same every single time and you are only touching them because the tool made you.

Cubix Capture picks the encoder and the capture path for your machine and does not ask you about frame budgets. It also does the part OBS never will: it follows your cursor, zooms in on what you are clicking, and smooths the mouse movement, so what you get when you stop is a finished, watchable tutorial rather than a raw canvas that still needs editing.

Keep reading: OBS encoding overloaded · OBS high CPU usage · OBS dropping frames · OBS best settings for screen recording