How to Fix Livestream Lag, Dropped Frames, and Buffering

Overview

Before changing settings at random, determine what “lag” means in your case. A stream can appear delayed or choppy to you, while the recording remains smooth. Viewers may see buffering even though OBS reports no dropped frames. These symptoms point to different causes.

In OBS Studio, open the View > Stats window while streaming or testing. The most useful indicators are dropped frames, skipped frames, and frames missed because of rendering lag. Treat the labels as a decision tree:

• Dropped frames generally indicate a connection problem between your computer and the streaming platform. Upload congestion, Wi-Fi interference, an unstable route to the platform, or a bitrate that is too high can contribute.
• Skipped frames due to encoding lag suggest that the selected encoder cannot process the video quickly enough. The issue may involve an overloaded CPU, an unsuitable software encoder preset, or a hardware encoder that is being used inefficiently.
• Frames missed due to rendering lag mean the computer is having difficulty preparing the scene. A demanding game, complex browser sources, animated overlays, high-resolution capture, or an overloaded graphics card can be responsible.
• Viewer-side buffering may occur after your stream reaches the platform. It can be related to a viewer’s connection, device, browser, or platform delivery conditions rather than your OBS configuration.

Run a short private or unlisted test before making several changes at once. Record your resolution, frame rate, bitrate, encoder, connection type, and OBS statistics. That baseline makes it easier to identify which adjustment helped.

Checklist by scenario

If OBS reports dropped frames

1. Check whether you are streaming over Wi-Fi. If practical, test with a wired Ethernet connection. If Wi-Fi is your only option, move closer to the router, reduce competing traffic, and avoid placing the computer behind large obstructions or near sources of interference.
2. Pause downloads, cloud backups, game updates, video calls, and other uploads on the network. Remember that another person or device in the household can consume upload capacity.
3. Review the stream bitrate in Settings > Output. A higher bitrate is not automatically better if your upload connection cannot sustain it. Lower the bitrate in a controlled step and test again.
4. Confirm that the selected server or ingest destination is appropriate for your platform and location. If the platform offers more than one ingest option, test another one when the problem appears limited to a particular route.
5. Restart the router only when appropriate, and retest at a different time if the connection is consistently unstable. A speed test can show available bandwidth, but it does not fully measure sustained upload reliability or the route to a specific platform.

If OBS reports encoding overload

1. Open Settings > Output and review the encoder. If hardware encoding is available and compatible with your graphics hardware, it may reduce CPU pressure. If you use software encoding, try a less demanding preset rather than pushing for maximum quality.
2. Reduce output resolution or frame rate if the encoder remains overloaded. Moving from a higher frame rate to a lower one can significantly reduce the amount of video that must be processed.
3. Close unnecessary applications, browser tabs, recording tools, and background utilities. Check the CPU and GPU usage in your operating system’s task manager while the stream is running.
4. Use a simpler scene temporarily. Browser sources, animated alerts, filters, and multiple capture sources can add processing work even when they look small on screen.

If OBS reports rendering lag

1. Lower demanding game settings, especially effects that place sustained load on the GPU. Limiting the game’s frame rate can leave headroom for OBS to render and composite the stream.
2. Run OBS with appropriate permissions if your operating system or game setup requires it, and avoid running several graphics-intensive programs at the same time.
3. Reduce the number of animated overlays, video backgrounds, browser widgets, and high-resolution sources. Disable sources one at a time to find the largest contributor.
4. Test a basic scene containing only the game or camera source. If the simple scene is smooth, rebuild the full scene gradually rather than replacing all of your equipment.

If viewers report buffering but OBS looks healthy

Ask whether the issue affects everyone or only one viewer, and whether it occurs on every platform if you multistream. Check the platform’s preview, playback on another device, and the completed recording after the broadcast. If your local preview and recording are smooth and OBS shows no network or performance warnings, investigate the platform ingest status, distribution path, or viewer connection before changing your encoder.

What to double-check

Bitrate, resolution, and frame rate must work as a group. Increasing resolution without checking encoder load and upload stability is a common cause of new problems. Start with a format your computer and connection handle consistently, then improve one variable at a time.

Review Settings > Video for the base canvas and output resolution. A large base canvas is useful for arranging sources, but the output resolution determines what OBS sends to the platform. Confirm the frame rate matches the type of content: fast gameplay may benefit from a higher frame rate, while a talking stream may not need the same processing demand.

Also check audio separately. Severe audio desynchronization or crackling may be caused by sample-rate mismatches, overloaded filters, or a microphone application rather than video lag. For a broader setup review, see the live stream audio setup guide.

Make a local recording during each major test. If the recording is also choppy, focus on rendering or encoding. If the recording is clean but the live broadcast drops frames, focus on the network, bitrate, and platform ingest route. This simple comparison prevents many unnecessary hardware changes.

Common mistakes

• Changing every setting at once: You lose the ability to identify the actual cause. Change one variable, test for several minutes, and record the result.
• Choosing bitrate from a speed test alone: Peak upload speed does not guarantee stable performance during a full broadcast.
• Blaming the internet for every stutter: Skipped or missed frames point toward encoding or rendering, not necessarily the connection.
• Ignoring game frame-rate limits: Allowing a game to use all available GPU capacity can leave too little headroom for OBS.
• Testing only in a busy live broadcast: Use a private or unlisted test when the platform supports it, so troubleshooting does not disrupt viewers.
• Adding more software as a first fix: Multistreaming tools, animated overlays, virtual cameras, and recording applications can increase system or network demand.

If you are rebuilding your setup, the OBS Studio setup guide can help you review core configuration choices. For hardware-related symptoms, compare this process with the beginner streaming setup guide.

When to revisit

Recheck this workflow before an important broadcast and whenever you change resolution, frame rate, game, camera, encoder, streaming platform, or internet connection. Revisit it after major OBS or operating-system updates, after adding animated scenes or multistreaming, and when seasonal household traffic changes your upload conditions.

Keep a small troubleshooting note with your reliable settings, the date tested, connection type, encoder, bitrate, and OBS statistics. Before your next stream, run a short test using the same scene and content load you expect during the broadcast. If the test is clean, save a backup of your OBS profile and scene collection. If it fails, follow the decision tree: dropped frames means network and bitrate; encoding overload means encoder and CPU; rendering lag means GPU and scene complexity; viewer-only buffering means platform delivery or the viewer’s environment. That repeatable process is more useful than continually upgrading equipment without identifying the bottleneck.