Visit Website →
← Back to blog

OBS Encoding Overloaded: Causes and Fixes That Work

October 22, 2026
OBS Encoding Overloaded: Causes and Fixes That Work

OBS shows "Encoding overloaded!" when your encoder cannot finish frames fast enough to keep up with your output settings. The fix is almost never your internet connection. It is usually one of four things: a software (x264) encoder doing a job the GPU should do, a preset that is too heavy, a game that eats every bit of GPU headroom, or OBS not getting enough priority from Windows. This guide shows you how to tell which one you have, then fix it in order from least to most invasive.

Tempered
Find the Windows bottleneck behind OBS
Tempered identifies real PC performance constraints and explains proposed changes, so you can decide what to adjust and keep an undo path.
Explore Tempered

TL;DR

  • "Encoding overloaded" is a local hardware problem. Network fixes such as lowering bitrate for upload reasons will not clear it.
  • Open View > Stats in OBS first. It tells you whether encoding, rendering or the network is failing.
  • Switch from x264 to a hardware encoder (NVENC, AMF or Quick Sync), cap your game's frame rate, and run OBS as administrator before you touch resolution.
  • If the message comes with display driver crashes or a VIDEO_TDR_FAILURE blue screen, you are dealing with a GPU timeout, not just an OBS setting.

Table of Contents

What the message actually means

According to OBS forum documentation, the warning appears when the encoder skips more than 0.1% of frames because it could not finish them inside the time budget for your frame rate. At 60 fps that budget is 16.6667 ms per frame. At 30 fps it is double that, which is why dropping the frame rate sometimes helps.

There are two broad reasons a frame misses its slot:

  1. The hardware is not powerful enough for the resolution, frame rate and quality you asked for.
  2. The hardware is powerful enough, but something else is using it: a game running uncapped, a browser with hardware acceleration, an overlay, a background app.

The second reason is far more common on gaming PCs than people expect, and it is why "my CPU is only at 70%" does not rule anything out. A single saturated resource, such as the GPU's 3D engine, is enough to cause the error while the overall CPU graph looks calm.

Step one: find out which status is failing

Before changing anything, separate three problems that people lump together. As OBS community explanations of the status indicators point out, frames that never get rendered or encoded because of CPU or GPU overload cannot be "dropped" later, because they do not exist. Dropped frames are a network matter. Encoding overload is not.

IndicatorWhat is strugglingWhere to look
Encoding overloadedThe encoder (CPU or GPU video engine)Skipped frames due to encoding lag
Frames missed due to rendering lagThe GPU composing your scene (sources, overlays, scaling)Missed frames due to rendering lag
Dropped framesYour network or the streaming serverDropped frames (network)

Open View > Stats, start recording or streaming, and wait until the problem appears. Then watch which counter is climbing. The OBS status indicators guide explains each of them in more depth.

This matters because the fixes diverge. Lowering bitrate fixes network drops. Switching encoders fixes encoding lag. Capping game frame rate fixes both rendering and encoding lag when the GPU is the shared bottleneck.

Step two: move encoding off the CPU

Check Settings > Output and look at the encoder. If it says x264 and you own a GPU with a hardware encoder, this is your most likely culprit. OBS recommends hardware encoders over software x264 because they shift the work from the CPU to a dedicated block in the GPU that handles video encoding more efficiently.

Pick the one that matches your card:

  • NVIDIA: NVENC (H.264 for streaming to most platforms).
  • AMD: AMF.
  • Intel: Quick Sync.

Gamers benefit twice. The CPU stays free for the game, and the encode happens on a separate chip rather than competing for the same shader cores that draw your frames. If you stream, a typical starting point for a modern NVIDIA card (GTX 1660 or newer) is NVENC H.264 with CBR. StreamerW's 2026 setup guide suggests 6000 Kbps for 1080p60, with an upload speed of at least 9 Mbps, which is 1.5 times the bitrate. Check your platform's own recommendations too, since limits differ.

If you have to stay on x264 (for example, no usable GPU encoder), move to a faster preset such as veryfast, and expect to lower resolution or frame rate sooner.

Step three: cap your game's frame rate

This is the fix people skip and the one that most often works. OBS's own encoding performance troubleshooting page explains that an uncapped game can push the GPU to 100%, which leaves nothing for OBS to compose and encode your scene. Even though NVENC is a dedicated chip, scene composition still needs the 3D engine.

What to do:

  1. Set an in-game frame limit equal to your monitor's refresh rate (60, 144 and so on), or enable V-Sync.
  2. If the game is still pegging the GPU, cap it a little lower than the maximum it can sustain.
  3. Retest with the Stats panel open.

Capping often fixes things more effectively than lowering graphics quality, because quality settings change the cost of each frame while an uncapped limit changes how many frames the GPU tries to make. If you want a clean way to see where your GPU time is going, our guide to checking GPU usage by engine type walks through it, and the CPU/GPU bottleneck check helps you tell which part is the limiter.

Step four: run OBS as administrator and keep Game Mode on

On Windows, OBS recommends running the program as an administrator when you game and capture at the same time. According to the OBS troubleshooting knowledge base, this lets Windows give OBS GPU priority over other applications, including the game, which helps with both encoding and rendering lag. It also notes that Windows Game Mode should be enabled for this to work.

To set it permanently, right-click the OBS shortcut, open Properties > Compatibility, and tick Run this program as an administrator. Restart OBS afterward. One side effect to know about: capture tools and some overlays behave differently with elevated programs, so test your scenes once after the change.

Step five: lower the workload, in the right order

If the earlier steps did not clear the warning, reduce what the encoder has to do. Go in this order so you give up as little quality as possible:

  1. Ease the preset. With NVENC, step down one preset at a time (for example P6 to P5 to P4) and retest. With x264, move toward veryfast.
  2. Reduce frame rate. OBS suggests going from 60 to 30 fps to cut the workload, then reducing resolution if that is still not enough.
  3. Reduce output resolution. 1080p to 900p or 720p cuts the pixel count significantly. Many viewers will not notice 720p60 on a fast-moving game.
  4. Reduce canvas complexity. Every browser source, game capture, webcam and animated overlay adds composition work. Remove what you do not need.

If you record gameplay for editing, there is also a smarter way to get a sharp result without a heavy encode. Record at a resolution your system handles comfortably, then improve the clip afterward. For example, this walkthrough on testing upscaling on a short clip before committing to a full video shows how to check for flicker on a few seconds of footage first.

Streaming and recording are different jobs

A common mistake is using one set of settings for both. Streaming is limited by your upload bandwidth, so you use constant bitrate. Recording is limited only by your disk, so you can use quality-based rate control. OBS Versions' recording guide describes CQP with a level around 16 to 20 as a strong balance between quality and file size for local recordings.

If you do both at once from the same PC, you are asking for two jobs at the same time, and that is a classic trigger for the error. Options include recording with the stream's encoder through the "Use stream encoder" option in Simple mode, or accepting a lighter second encode. Our advice: when you only need a local copy, record separately from streaming, with settings made for that purpose.

When it comes with TDR errors and driver crashes

Sometimes encoding overload is not the only symptom. You may also see the screen go black for a second, a pop-up saying the display driver stopped responding, or a blue screen reading VIDEO_TDR_FAILURE.

That is Windows' Timeout Detection and Recovery at work. Microsoft's documentation says the default timeout is 2 seconds. If the GPU does not respond in that time, Windows tries to reset the display driver, and when that recovery fails, you get the 0x116 bug check. In plain terms: the GPU was so busy or so unstable that it stopped answering.

For a streamer, the likely contributors are a driver that is old or misbehaving, a GPU pushed to 100% by an uncapped game plus OBS, an unstable overclock or undervolt, or overheating. Practical steps, in order:

  1. Update your GPU driver from the vendor, using a clean install if problems began after an update. Our guide to updating GPU drivers for gaming covers the process, and our piece on measuring whether drivers really change FPS shows how to test the result rather than assume it.
  2. Return any overclock or undervolt to stock while you test.
  3. Cap the game frame rate, as above, so the GPU is never pinned.
  4. Check temperatures during a long session.

Tempting as it is, do not start by editing the TDR delay in the registry. A longer timeout hides the symptom, and if the GPU is truly stuck you will just wait longer before it recovers. If crashes continue after drivers, stock clocks and a frame cap, have the hardware tested, because a failing GPU or power supply can cause the same pattern.

Clear the clutter that competes with OBS

Overlays are small but real consumers of GPU time. Discord, game launchers and monitoring tools hook into the game's rendering, and OBS hooks in as well. Turning off the ones you do not use frees resources and reduces capture conflicts. Our walkthrough on disabling overlays on Windows shows how, starting with Discord.

Also check for:

  • Browsers with hardware acceleration running video in the background.
  • Startup apps that run permanently and use disk, CPU or GPU.
  • Other capture or recording software running at the same time.

For broader tuning of the machine you game on, see our guides on optimizing Windows 11 for gaming and on stopping FPS drops with frametime traces. If input delay matters to you, cutting input lag is the next read, and choosing fullscreen or windowed can affect capture behavior too.

Our view: measure, change one thing, keep an undo

We build Tempered for people who want a faster Windows PC without gambling on it, and OBS overload is a good example of why we think that way. The internet is full of one-click cures and registry tweaks for this error. Most of them skip the first question: what is actually being overloaded?

Our view: measure, change one thing, keep an undo — overview diagram

Our approach is simple. Look at live numbers (CPU, RAM, GPU, disk), identify the real limiter, make one change, and test. Overload from a GPU that is pinned at 100% by an uncapped game needs a frame cap, not a registry cleaner. Overload from x264 on a six-core CPU needs a hardware encoder, not a "boost". Overload from a pile of startup apps needs fewer startup apps. If a tool changes ten things at once, you cannot know which one helped, and you cannot cleanly reverse the one that hurt.

That is also why every change in Tempered needs your approval, comes with a plain-language explanation and an expected result, and can be undone. A streaming PC is a system you rely on live, and you should never be afraid to touch it before a broadcast. Whatever tools you use, keep that discipline: change one variable, retest with OBS Stats open, and write down what you changed.

— Ian

Where Tempered fits

If you would rather not hunt through Task Manager, startup lists and background processes by hand, Tempered shows live CPU, RAM, GPU, disk and uptime numbers, explains in plain language what is holding your PC back, and proposes changes you approve one at a time, with one-click Undo. It can manage background processes, customize startup, and turn on Game Mode, which the OBS administrator tip above relies on. It does not need an AI API key or technical knowledge. You can start on the Free plan with limited AI scans. Paid plans on the pricing page start from $5.99 per month for Torque and from $12.99 per month for Torque Max. You can also read more on the Tempered home page.

A quick checklist to run before every stream

  • Encoder set to your GPU's hardware encoder, not x264 (unless you have no choice).
  • Game frame rate capped to your refresh rate or lower.
  • OBS running as administrator, Windows Game Mode on.
  • Unneeded overlays, browser tabs and capture tools closed.
  • Stats panel open for the first minutes of a session, so you see the counter move before viewers do.
  • Streaming and recording settings chosen separately.

FAQ

Is encoding overloaded caused by my internet?

No. It is a local processing problem: the encoder could not finish frames in time. Network trouble shows up as dropped frames (network) in the Stats panel. Lowering your bitrate may help your upload but will rarely clear an encoding warning by itself.

Should I lower resolution or frame rate first?

Try the cheaper changes first: a hardware encoder, a lighter preset and a game frame cap. If you still need to cut load, OBS suggests going from 60 to 30 fps and then reducing resolution. Many streamers prefer 720p60 to 1080p30 for fast games, so test both on your own content.

Can a driver problem cause both encoding overload and a TDR error?

Yes, because both come from the GPU being unable to keep up or respond. Microsoft explains that Windows resets the display driver after a timeout, which is 2 seconds by default, and a failed reset causes the VIDEO_TDR_FAILURE stop error. Update the driver, return overclocks to stock, and cap the frame rate before looking at anything exotic.

Does running OBS as administrator really help?

For gaming and capturing together on Windows, OBS's own troubleshooting page recommends it, with Game Mode enabled, because it lets OBS get GPU priority over the game. Try it, then check whether the skipped frame counter still rises.

Sources