When OBS shows "Encoding overloaded", its own troubleshooting guide reads that as a resources problem — you "may need to take some steps to leave some resources free for OBS Studio to use". It is not a corrupt install, and it is not usually a single wrong checkbox.
The interesting part is which step OBS puts first. Most articles on this error open with "lower your resolution" and bury the official first move around item seven.
What "Encoding overloaded" actually means
OBS states the trigger condition plainly: "If you are struggling with choppy/laggy output, and you are getting 'encoding overloaded' messages, you may need to take some steps to leave some resources free for OBS Studio to use."
Then it names the two candidate causes, and it is careful to separate them:
"This is probably because you have either overloaded your GPU or you have a bottleneck between your GPU and the rest of your system. These are subtly different issues, but both are important."
That distinction matters once you start testing fixes: a saturated GPU and a starved one respond to different changes, which is why one person's "just cap your frame rate" does nothing for someone else.
The reason the GPU is involved at all, in OBS's words: "OBS needs GPU time and resources because it has to composite and render a scene." Before a single frame reaches an encoder, OBS has to draw your scene — every source, every filter, every layer — and that is GPU work too.
The fastest fix: run OBS Studio as administrator
This is the first thing OBS's troubleshooting page tells you to do, and it comes with a mechanism rather than a shrug:
"OBS Studio can ask Windows to reserve some GPU capacity for its use. In many cases, GPU overload issues can be resolved simply by running OBS Studio as administrator; try that before continuing with this guide."
Two things worth reading closely. First, the mechanism is a request to Windows for reserved GPU capacity, not a generic "admin rights make things faster" superstition — which is why it lands on this specific error rather than on every OBS problem.
Second, note the wording: OBS Studio asks Windows. OBS's page does not state an equivalent step for macOS or Linux, so if you are not on Windows, skip to the next section rather than hunting for a sudo version of this advice.
OBS also tells you when to try it — "before continuing with this guide". Do it first, reproduce your recording or stream, and only then start changing settings.
The second move: give the GPU room by capping the game
If admin rights do not clear it, OBS's next recommendation is aimed squarely at the thing competing with it for the GPU:
"The best option is to limit the game's framerate or enable vertical sync; this will free up processing power for OBS Studio to composite."
And a qualifier that people skip, from the same page: "running the game with an uncapped framerate that exceeds your refresh rate brings diminishing returns, as neither you nor OBS Studio will be able to see them."
Frames above your refresh rate are frames nobody watches — not you, not OBS — while the GPU time spent producing them is real. Capping is usually the cheapest quality-neutral change on this list.
A related habit: stop asking the live encoder to do work you could do afterwards. Record at a load your machine handles comfortably, then shrink the file once recording has stopped and nothing is competing for the GPU.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs in your browser tab — read from disk, re-encoded locally, handed back, no upload step. The "high" preset suits a session recording you still intend to edit or archive. The standalone version is compress video.
Other causes, in order of likelihood
Work down this list one change at a time, testing after each.
1. A recording quality or encoder that is not "Same as stream". OBS's Standard Recording Output Guide is explicit about the cost: "Recording Quality when in Simple view will let you select what quality you'd like your recording to be at, anything that is not Same as stream will take extra resources from your computer." It repeats the warning for the encoder dropdown. If the overload started when you raised recording quality while streaming, that is why.
2. The Lossless preset specifically. OBS describes it as producing "tremendously large file sizes, around 7 GB of data per minute of video, in lossless quality" and adds: "This also uses the CPU encoder." That second sentence is the performance-relevant one — Lossless takes you off a hardware encoder. OBS describes Indistinguishable as carrying "a potential performance impact on older or weaker hardware, depending on the choice of encoder".
3. Frame rate. "Frame rate also impacts both rendering and encoding performance. Having to do the work on fewer frames will lessen the load." It cuts the rendering side and the encoding side at once.
4. Too many sources in the scene. "Every source requires some amount of resources to be shown in the scene." Scenes accumulate — a source you stopped using months ago still costs you every frame it is visible.
5. Filters. OBS is blunt: "filters, like everything else, require some resources to compute and render their effects. In fact, some filters can be pretty resource hungry." If a scene went from fine to overloaded right after you added a filter chain, start there.
6. Game DVR on Windows. OBS's reasoning: "Game DVR is a related feature that allows Windows to record game footage in the background very much like OBS Studio's Replay Buffer feature. However, since this uses additional system resources, you should disable this Windows feature if you are using OBS Studio."
7. Game Mode — but read the version limit. OBS's actual sentence: "On recent versions of Windows 10, Game Mode can be left on. However, on Windows 10 versions older than 1809, you should disable Game Mode to ensure that Windows isn't pulling resources away from OBS Studio behind the scenes." OBS does not tell you to turn Game Mode off — it says to turn it off on Windows 10 builds older than 1809, and that recent builds can leave it on. Anyone advising a blanket disable has dropped the condition.
8. Multi-adapter Compatibility in Game Capture. On this option OBS says: "There aren't many situations where you actually want to have this option enabled." If it is on and you do not know why, that is a candidate.
What about the encoder itself?
OBS's Hardware Encoding page says hardware encoders "are generally recommended for best performance as they take the workload off the CPU and to a specialised component in the GPU that can perform video encoding more efficiently", and that "Modern hardware encoders provide very good quality video with minimal performance impact."
Keep the qualifier that follows, because it is doing real work: "earlier generation hardware encoders provide a lower-quality image. They offer minimal performance impact in exchange for a reduction in quality at the same bitrates as software encoding using the default preset of veryfast. As such, they can be a last resort if software encoding is not possible such as due to performance constraints."
So the honest version is not "hardware encoding is always better" — it is that modern hardware encoders cost very little quality and older ones cost noticeably more, making the switch a trade rather than a free win on an older GPU.
How to tell it worked
The two symptoms OBS pairs together are the two to check: the "encoding overloaded" messages stop appearing, and the output is no longer choppy or laggy. Test with a real recording, not an idle preview — an idle scene does not reproduce the load that triggered it.
Change one thing per test, in the order above. Flip six settings at once and you get a working setup with no idea which change mattered, so the next scene you build breaks the same way.
FAQ
Why does running OBS as administrator fix encoding overloaded? Because, per OBS's troubleshooting page, "OBS Studio can ask Windows to reserve some GPU capacity for its use". OBS says GPU overload issues "can be resolved simply by running OBS Studio as administrator" in many cases, and tells you to try it first.
Should I disable Game Mode to fix OBS encoding overloaded? Only on old builds. OBS says Game Mode "can be left on" on recent versions of Windows 10, and that you should disable it on Windows 10 versions older than 1809. The blanket "turn off Game Mode" advice drops that condition.
Is encoding overloaded a CPU problem or a GPU problem? OBS points at the GPU side: it says you have "either overloaded your GPU or you have a bottleneck between your GPU and the rest of your system", and calls those subtly different issues. Note that encoder choice still pulls the CPU in — the Lossless preset, for example, "uses the CPU encoder".
Can I make OBS render the scene on the CPU instead? OBS addresses this directly and advises against it: "While this is probably technically possible, GPUs are still way more efficient at this kind of task than CPUs. In the vast majority of cases, this would be a net negative impact on system, rendering, and encoding performance."
Does the recording container affect encoding load? OBS's formats guide does not make that claim, so do not assume it does. Container choice matters for crash resistance and editor compatibility instead — see MKV or MP4 for OBS recordings and what to do with a corrupted OBS MP4.
All quotes from OBS Studio's knowledge base — the Encoding Performance Troubleshooting page, the Hardware Encoding page, the Standard Recording Output Guide, and the Recording Encoder Presets Guide — checked 23 September 2026. Start at OBS Studio Help for the current pages. More on the same shelf: fix guides, or all Clapr tools.
