Basic Troubleshooting

OBS Studio

Chapter 8 · Basic Troubleshooting

Chapter 4 covered bitrate and encoders as settings to configure correctly up front. This chapter is what to do when something still goes wrong — diagnosing exactly which earlier concept is actually the problem, rather than guessing.

The Stats Dock

OBS's own built-in Stats Dock is the actual first place to look when something seems wrong — showing dropped frames, CPU usage, encoding lag, and render lag in real time. Diagnosing a problem starts here, not with guessing at a cause.

Two Different Kinds of Dropped Frames

Network-related dropped frames mean the encoded video can't be sent out fast enough — usually a bitrate-versus-upload-bandwidth mismatch, tying directly back to Chapter 4's own bitrate material. Rendering/encoding-related dropped frames mean the computer itself can't encode fast enough, tying back to Chapter 4's own x264-vs-hardware-encoder material. These are two entirely different problems with two different causes and two different fixes — easily confused, since both simply show up as "dropped frames" in the Stats Dock without further inspection.

Encoding Overload

A specific stat directly in the Stats Dock warns when the chosen encoder can't keep up in real time — the direct, measurable symptom of Chapter 4's own x264-CPU-contention scenario, or simply an underpowered CPU or GPU for the currently configured settings. The fix: switch to a hardware encoder if one's available, lower the output resolution or framerate, or reduce the encoder's own preset/complexity setting.

A Basic Troubleshooting Checklist

Check the Stats Dock first — which kind of dropped frame is actually occurring, network or rendering?
If network — check actual upload bandwidth against the configured bitrate (Chapter 4).
If rendering/encoding overload — check CPU/GPU usage, consider switching encoders (Chapter 4), lowering resolution/framerate, or closing other demanding applications.

Symptom	Likely cause	Chapter with the fix
Network-related dropped frames	Bitrate exceeds upload bandwidth	Chapter 4
Rendering/encoding overload	CPU/GPU can't keep up with the encoder	Chapter 4

This chapter is diagnosis; Chapter 4 is the fix

This chapter's own real value is figuring out which of Chapter 4's own two concepts — bitrate/bandwidth, or encoder choice — is actually the problem in a specific case. The Stats Dock is the tool that answers that question; Chapter 4 already covers what to actually do once the cause is known.

Dropped frames don't always mean your internet is too slow

It's a common assumption that any dropped frames mean an internet connection is too slow. Per this chapter's own core distinction, dropped frames can be caused by either a genuine network/bandwidth problem, or a rendering/encoding problem on the computer itself that has nothing to do with the internet connection at all. Blindly blaming internet speed and upgrading a connection wouldn't fix an encoding-overload problem in the slightest — wasting real money and effort on the wrong fix entirely. The Stats Dock is specifically what tells you which one is actually happening, rather than guessing.

Hands-On Exercises

Exercise 1

The Stats Dock shows encoding overload, with CPU usage near 100%, while network-related dropped frames show at zero. A streamer concludes their internet is too slow and upgrades their plan. Using this chapter's own material, explain why this fix wouldn't actually help.

📄 View solution

Exercise 2

Using this chapter's own troubleshooting checklist, walk through the steps you'd take if a stream is experiencing dropped frames, but you don't yet know whether the cause is network-related or rendering-related.

📄 View solution

Exercise 3

Explain why network-related dropped frames and rendering/encoding-related dropped frames require genuinely different fixes, even though both appear as "dropped frames" in the Stats Dock without further investigation.

📄 View solution

Chapter 8 Quick Reference

The Stats Dock is the real diagnostic starting point — check it before guessing at a cause
Network dropped frames (bitrate/bandwidth mismatch) and rendering/encoding dropped frames (CPU/GPU can't keep up) are genuinely different problems with different fixes
Encoding overload is a specific, measurable Stats Dock warning — the fix is a hardware encoder, lower resolution/framerate, or a lighter encoder preset
Dropped frames do not always mean slow internet — the Stats Dock reveals which cause is actually occurring