OBS "Encoding Overloaded" Error - Fix

OBS "Encoding Overloaded" Error: Fix

The warning means your encoder could not finish compressing a frame before the next one arrived, so OBS discarded frames to stay in sync. At 60 fps the budget per frame is 16.6 milliseconds. Miss it consistently and your output stutters.

That is the whole concept, and if you want the deadline arithmetic and the five fixes ranked by how much headroom each one buys, OBS Encoding Overloaded: What It Means and How to Fix It covers exactly that.

This page does something different. Generic advice to "switch to a hardware encoder" is useless if you have already done that and the warning persists, and it is actively wrong on an Apple Silicon Mac. So the fix here is routed by the silicon you actually own. Find your hardware below and apply the path for it.

Step 0: Identify Your Encoder Path

Open Settings > Output, set Output Mode to Advanced, and open the Video Encoder dropdown. What you see there tells you which path you are on.

If the dropdown offers only x264 and you know you have a supported GPU, your graphics driver is either missing or too old. Install the current driver from the manufacturer directly rather than through Windows Update, then restart OBS.

Path A: NVIDIA, and Why NVENC Alone Sometimes Is Not Enough

Selecting NVENC moves compression onto a dedicated block of silicon that is separate from the shader cores your game or application is using. For most people that clears the warning immediately.

Set it up:

1. Video Encoder: NVIDIA NVENC H.264, or AV1 on a 40-series card.
2. Rate Control: CQP for local recording, CBR for streaming.
3. Preset: P5 (Quality). Do not use P6 or P7.
4. Tuning: High Quality.
5. Multipass Mode: Quarter Resolution, or Disabled if the warning persists.

If you are still overloaded on NVENC, one of these is the reason:

Your preset is too slow. P1 through P7 run fastest to slowest. P7 asks the encoder to do considerably more work per frame and is the single most common cause of NVENC overload. Drop to P5.

Look-ahead and psycho-visual tuning are on. Both add per-frame work, and on 10-series and 16-series cards they are enough to blow the budget at 1080p60. Turn both off.

Something else is holding the encoder. Consumer GeForce drivers limit how many NVENC sessions can run at once. NVIDIA's own recording overlay, a second OBS instance, a game's built-in capture, or a video call application already using it will push OBS into a degraded path. Close them and retest.

Your driver is stale. NVENC behaviour has changed meaningfully across driver releases. Update before you spend an hour on settings.

Path B: AMD

AMD's encoder is capable but its OBS integration has historically been more sensitive to configuration than NVIDIA's.

1. Video Encoder: AMD HW H.264 (AVC). Use AV1 only on RX 7000-series or newer.
2. Rate Control: CBR for streaming, CQP for recording.
3. Preset: Speed or Balanced. Quality is frequently the cause of the overload on this hardware.
4. Leave Pre-Analysis off. It adds a per-frame pass that older cards cannot sustain at 60 fps.

If the warning persists at Speed preset, the encoder on your card is genuinely at its limit and you need to reduce the workload rather than tune it, which means dropping output resolution or frame rate.

Path C: Intel QuickSync, and the Laptop Trap

QuickSync lives in the integrated graphics block of your Intel CPU. On a desktop, select it and you are usually finished. On a laptop with both integrated and discrete graphics, there is a specific failure that produces this warning and no amount of encoder tuning will fix it.

The problem is that OBS and the application you are capturing can end up assigned to different GPUs. Frames then have to be copied across the PCIe bus before they can be encoded, and that copy is what misses the deadline.

To fix it on Windows:

1. Open Settings > System > Display > Graphics.
2. Find OBS in the list, or add obs64.exe manually.
3. Set it to Power saving to run OBS on the integrated GPU, which is where QuickSync lives.
4. Restart OBS.

If you are capturing a game running on the discrete GPU, do the opposite: set OBS to High performance and use the discrete card's encoder instead of QuickSync. The rule is that OBS should sit on the same GPU as the thing it is capturing. Which GPU that is depends on what you record, which is why there is no universal setting here.

Path D: Apple Silicon

On an M-series Mac, an encoding overload is unusual, and when it happens the encoder is almost never the cause. The media engine on Apple Silicon handles 4K H.264 comfortably.

What actually causes it is canvas size. A Retina display reports an enormous base resolution, and OBS composites at that resolution before encoding. A 5K iMac left on defaults asks OBS to render and scale far more pixels than the output needs.

1. Go to Settings > Video.
2. Leave Base (Canvas) Resolution at your display's reported size so your scene layout does not shift.
3. Set Output (Scaled) Resolution to 1920x1080.
4. Set Downscale Filter to Bicubic.
5. Confirm Video Encoder is Apple VT H.264 Hardware, not the software entry directly below it, which is easy to select by accident.

If the warning persists after that, check whether Low Power Mode is enabled in System Settings, since it throttles the media engine.

Path E: No Hardware Encoder

If x264 is genuinely your only option, you are compressing on the CPU and your only lever is to ask x264 to work less hard per frame.

Go to Settings > Output, find CPU Usage Preset, and move it from veryfast toward superfast or ultrafast. The naming is counterintuitive: faster presets consume less CPU, at the cost of a larger file for the same visual quality.

The full comparison of what you give up making that trade, and how it stacks against hardware encoding, is in OBS Encoder Lag: NVENC vs x264 Fix.

When It Only Happens Sometimes

An overload that appears intermittently has a different cause from one that appears constantly, and the paths above will not help.

Only while gaming. Your game and OBS are competing for the same GPU. Cap the game's frame rate a little below your monitor's refresh rate, which leaves scheduling headroom, and enable V-Sync. An uncapped game rendering 300 fps starves everything else on the card.

Only on battery. Both operating systems throttle aggressively when unplugged. On Windows, set the power mode to Best performance and, in the NVIDIA Control Panel, set Power management mode to Prefer maximum performance. On macOS, turn off Low Power Mode. If the warning disappears the moment you plug in, this was it.

Only with certain scenes. Every browser source runs a full Chromium instance. Three or four active browser sources consume a surprising amount of GPU time before OBS has encoded anything. Disable the ones not visible in your current scene rather than leaving them all running.

Only after running for a while. This is thermal throttling. Check your temperatures, and clean the intakes on a laptop before changing any settings.

Cheat Sheet

The Setting You Should Not Have to Pick

None of this is about making better videos. It is a budget negotiation between your silicon and a frame deadline, and you are the one holding the calculator because OBS exposes the entire pipeline by design.

Cubix Capture selects the encoder for the hardware it finds and does not present a preset ladder, because there is no correct answer a user should be expected to supply. It runs on Windows and Mac, with a free Starter plan and no account required.

Keep Reading

• OBS Encoding Overloaded: What It Means and How to Fix It for the frame-deadline arithmetic behind the warning.
• OBS Encoder Lag: NVENC vs x264 Fix is the deep dive on the software-versus-hardware choice.
• OBS Dropping Frames: Why It Happens and How to Stop It if the dropped frames are network rather than encoder.
• OBS High CPU Usage: How to Reduce It when the whole machine slows down, not just the encode.