START HERE

Prove the failure in the finished output first.

Run the problem scene briefly, stop output, and inspect the end-of-session skipped-frame counter plus the relevant OBS log block.

What it may mean

The selected encoder, preset, resolution, frame rate, concurrent recording, filters or overall workload may exceed available encoder capacity.

What it does not prove

Encoding lag is different from network-dropped frames and rendering lag. Lowering bitrate alone may not reduce encoder workload.

Match the evidence before changing settings

IF YOU SEESkipped frames due to encoding lag riseIT MAY MEAN

The encoder stage cannot complete frames in time.

NEXT TEST

Use one faster supported encoder preset and repeat the same scene.

IF YOU SEERendering lag rises firstIT MAY MEAN

OBS may lack GPU time before encoding begins.

NEXT TEST

Cap game FPS or simplify one heavy source, then compare the rendering counter.

IF YOU SEEOnly concurrent recording triggers overloadIT MAY MEAN

The combined output workload may exceed the available encode or storage path.

NEXT TEST

Repeat once without the secondary output, then narrow its encoder and recording settings separately.

One conservative free test

Change one workload variable: use a faster supported preset or lower output resolution/frame rate. Repeat the same scene and compare skipped-frame deltas.

Analyze the completed OBS log →

Preserve the rollback

Export or screenshot the original output settings and restore them if the repeated test does not materially reduce skipped frames.

Technical reference: OBS Project: Encoding Performance Troubleshooting ↗

Common questions

01Does lowering bitrate fix encoding overload?+

Not necessarily. Bitrate concerns how much data is sent; encoding overload means frames are not being encoded in time. Diagnose the logged stage first.

02Why is OBS overloaded when GPU usage is below 100%?+

A dedicated encoder, GPU scheduling, a specific engine, scene composition or another bottleneck can fail before an overall utilization number reaches 100%.

KEEP THE TEST CONTROLLED

Did the relevant counters improve?

For dropped frames, encoding lag or rendering lag, compare a completed log from before and after your change. For audio and black-screen problems, inspect the recording itself; counters cannot establish picture or sound quality.

Compare logs free →