If your YouTube live stream drops frames when OBS is recording and streaming at once, first check which counter is rising in OBS Statistics. Network-dropped frames, frames missed due to rendering lag and skipped frames due to encoding lag point to different problems, so recording is not automatically the cause.
Reproduce the problem with the same scene and settings, note the counter and check the OBS log. Then change one thing at a time: connection settings if network drops rise, or workload and output settings if rendering or encoding falls behind.
Start with OBS Statistics, not a guess
In OBS, open View → Stats while the stream and recording are running. Keep the panel visible through the period when the problem usually occurs. The key is not simply whether a number is non-zero, but whether the relevant counter keeps rising during the trouble. A brief fluctuation and a sustained increase are different evidence.
OBS reports several types of missed frames. Dropped frames (network) means OBS is not delivering frames reliably to the streaming server. Frames missed due to rendering lag means OBS is struggling to compose or render the scene on time. Skipped frames due to encoding lag means the encoder is not completing frames quickly enough. Wording and layout can vary slightly by OBS version, but these distinctions are the useful starting point.
Make a short controlled test rather than changing settings during an important broadcast. Use the same game or media, scene, output resolution, frame rate, encoder, and recording setup as the session that failed. Note when recording starts, when the stream begins to stutter, and which counter changes. If the issue takes time to appear, keep the test running long enough to reach the same workload, but do not leave a public test live longer than you intend.
The OBS Project recommends including a log when asking for support. You can find the current session’s log from OBS’s Help menu; save it after reproducing the issue, rather than relying on memory of what happened. A log can help show whether there was an encoder warning or connection event at the time. For a broader preflight routine, the live-streaming checklist is useful alongside this focused diagnosis.
Read the symptom as three different failure classes
| What you see in OBS | What it usually indicates | First area to investigate |
|---|---|---|
| Dropped frames (network) rises | The outgoing connection cannot reliably sustain delivery to the streaming server | Stable upload, Wi-Fi or wired connection, VPN and network path |
| Frames missed due to rendering lag rises | OBS is late compositing or rendering the scene | Game or GPU load, scene complexity, filters, resolution and frame rate |
| Skipped frames due to encoding lag rises | The chosen encoder cannot keep pace with the output | Encoder choice, preset or quality settings, and concurrent workload |
These are diagnostic categories, not guarantees about a single root cause. For example, an overloaded GPU can affect rendering and may also leave less capacity for a GPU-based encoder. A powerful connection will not fix that. Conversely, lowering recording quality cannot repair unstable Wi-Fi if only the network-dropped counter is climbing.
A viewer reporting buffering does not prove OBS is dropping frames. The viewer’s connection, device or location can contribute, so compare reports with OBS Statistics and, where available, YouTube’s live health information. Avoid changing encoder settings solely because one viewer sees a pause. The OBS Project’s stream connection troubleshooting guide explains its network-dropped-frame category; its encoding performance guide covers local rendering and encoding strain.
If network-dropped frames rise, test the connection
The OBS Project describes dropped frames as a sign that the connection to the remote server is unstable or cannot keep up with the configured bitrate. That does not necessarily mean your internet plan is too slow: Wi-Fi interference, congestion, a VPN, a faulty cable or an issue along the route to the ingest server can make an otherwise adequate connection unreliable.
Start by checking whether the computer is on Wi-Fi. If practical, run a comparable test on wired Ethernet. OBS recommends a wired connection for streaming because it avoids some sources of wireless variability. If wired performance improves, investigate the wireless link and placement before making other changes. If it does not, check cables, router or modem behaviour, network utilities, security software and VPN settings. Change only settings you understand, and restore a change if it makes no difference.
Next, consider whether the configured bitrate is sustainable throughout the day, not just during an ideal speed test. Other people or devices may be using the connection, and upload capacity can vary. Reduce the streaming bitrate in a test and watch whether the network-dropped counter stops rising. OBS’s connection guide offers 75% of measured total upload speed as a rough starting point for troubleshooting. Treat this as a general diagnostic suggestion, not a guarantee, and not a YouTube-specific bitrate recommendation. You must also stay within YouTube’s current guidance for your stream format; check its live encoder settings rather than borrowing a bitrate from another platform or an old guide.
A different ingest server can help determine whether the current route or destination is part of the trouble, where OBS and the service provide that option. Record which setting you tested and the result. OBS’s dynamic bitrate option can lower the bitrate when the connection cannot keep up, which may reduce network drops, but the trade-off is lower picture quality during the adjustment. It does not repair the underlying connection, so do not mistake a smoother test for a resolved cause.
If network counters remain high after sensible bitrate and connection checks, contact your internet provider with the times and test results. Avoid randomly switching IP-family settings or network optimisation options; revert a change that does not help. If the stream instead shows missed-rendering or skipped-encoding frames while network drops stay still, return to the local workload checks below. For a longer-running broadcast, the guide to an OBS stream that keeps disconnecting covers connection interruptions as a separate symptom.
If rendering lag rises, reduce scene and game demand
Rendering lag concerns the work OBS must do before it can send a frame to the encoder. The OBS Project notes that OBS needs GPU time and resources to composite and render a scene. A demanding game, high frame rate, multiple GPU-heavy applications, animated browser sources, complex filters or a large output canvas can all compete for that time.
Check GPU use while reproducing the issue, including the game and other applications, rather than assuming the recording process is the only load. If you are streaming a game, cap its frame rate or enable V-Sync and try lower graphics settings. That leaves more rendering capacity available for OBS, at the cost of game frame rate or visual detail. Close or pause other GPU-heavy work during the test. On Windows, OBS suggests trying to run it as administrator for certain GPU overload cases; treat this as a test, not a universal requirement.
Simplify the scene that is live when the counter rises. Temporarily disable demanding filters, unnecessary browser sources, animated overlays and sources that are not visible. If a scene collection has accumulated unused or duplicated elements, test a lean copy before removing anything from the working setup. A devotional channel with a static image and audio has different rendering demands from a gaming stream with capture, transitions and effects, so test the actual scene rather than extrapolating from an empty preview.
If simpler scenes do not stabilise rendering, test a lower output resolution or frame rate. OBS notes that moving from 60 fps to 30 fps may help when 60 fps is not working. The trade-off is less motion smoothness; reducing resolution sacrifices detail. Make each change separately and compare the rendering-lag counter, so you know which adjustment mattered. Do not lower the stream bitrate expecting it to fix a rendering counter that is rising while network drops remain stable.
If encoding lag rises, compare the two outputs
When OBS reports skipped frames due to encoding lag or an encoding-overloaded warning, look at the streaming and recording encoder settings separately. Recording and streaming together can expose a limit if they demand more work than the computer can finish on time, but the warning alone does not identify which output or component is responsible. Rendering strain can also be present, so check both relevant counters and the log.
OBS’s Advanced Output mode allows separate streaming and recording configuration. That can be useful when a recording needs different quality or file-size characteristics from the live stream. It also means you should record what each output is doing before changing settings: encoder type, preset or quality control, and whether recording is set to Same as stream. A separate, demanding recording configuration may add work; a less demanding recording configuration may ease it but produce a larger or less detailed file, depending on the encoder and settings.
Hardware encoding can move some encoding work from the CPU to a supported specialised component, such as NVIDIA NVENC, AMD AMF, Intel Quick Sync Video or Apple VideoToolbox, depending on the computer and encoder generation. It is worth testing when evidence points to encoding strain and your current configuration is software-encoded or otherwise cannot keep pace. It is not a fix for network-dropped frames, and it may not help if the GPU is already struggling to render the scene. Older hardware encoder generations can also produce different image quality from software encoding at comparable settings, so review a local test recording rather than assuming the result will look identical.
If you need a high-quality local archive, preserve that goal while testing rather than blindly lowering every quality setting. OBS’s recording guide lists encoder-specific quality-control ranges, including NVENC Constant QP 16–23 and x264 CRF 16–23. These are recording baselines from the OBS Project, not a universal recipe for streaming or a promise of a particular file size; lower values generally mean higher quality and larger files. Check the current OBS recording guide for your OBS version and encoder, then test the resulting file for both visual quality and playback.
Keep stream and recording goals distinct
A live stream and a local recording do not have to serve the same purpose. A YouTube stream might prioritise a stable, consistent picture for viewers, while the local recording may be intended for later editing or an archive. Separate outputs can help meet those different goals, but the computer still has to render and encode the work in real time. An ambitious recording preset can be a contributor if the evidence is encoding lag; it is not automatically the explanation for every drop.
Make one controlled comparison: first reproduce the issue with both outputs enabled, then change only the recording encoder or its quality demand and repeat with the same scene and stream settings. If encoding lag falls while network and rendering counters stay steady, that is evidence the recording configuration contributed. If nothing changes, revert it and investigate the counter that is actually rising. A test with recording disabled can help isolate a contribution, but it does not establish that recording was the sole cause, because workload and timing may also differ.
For a channel that mainly needs a continuous loop rather than an OBS production setup, keeping a home computer awake and recording locally may be unnecessary work. StreamNeo can remove the need to keep that computer running by turning an uploaded video into a YouTube live stream, but it is YouTube-only and does not provide a replacement for a complex live scene or a local recording workflow.
Retest, compare and keep the evidence
After each change, repeat the same test conditions: same scene, game or media, stream resolution and frame rate, and recording state unless that is the one variable being tested. Watch the same counters for a similar stretch of the problematic workload. Write down the change and result. If you alter bitrate, scene complexity, encoder and resolution all at once, a better result will not tell you which adjustment helped, and a worse one will be harder to undo.
If the counters are stable but viewers still report buffering, investigate the viewing side and YouTube’s stream health rather than repeatedly reducing encoder quality. If network-dropped frames rise, keep working on the connection path and sustainable bitrate. If rendering lag rises, reduce scene or game demand. If encoding lag rises, test encoder and output configuration. More than one counter can rise, in which case address the most prominent evidence and retest rather than assuming a single cause.
Keep the OBS log from a test that reproduces the issue, along with your notes about which settings changed. Include it when requesting help through OBS’s official support channels, and remove private information if needed before sharing. If the counter does not rise in a short test, that does not prove the stream can run reliably overnight; repeat the test under the conditions that normally trigger the fault. For a full broadcast workflow, the continuous OBS playlist guide covers a different operational question from diagnosing frame counters.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does recording cause OBS to drop frames?
It can add workload, particularly if the recording configuration requires additional encoding, but the symptom does not prove that recording is responsible. Check whether network-dropped, rendering-lag or encoding-lag frames rise, then compare a controlled test with only the recording setting changed.
Should I lower bitrate when OBS drops frames?
Only start there if the network-dropped counter is increasing. A lower stream bitrate can help when the connection cannot sustain the configured rate, but it will not fix rendering or encoding lag and may reduce picture quality.
Should I buy a graphics card or faster internet?
Do not buy either until the OBS counter and log point to the relevant limit. Consider network changes when connection checks indicate instability, and hardware encoding only when the evidence indicates encoding strain that your current device cannot handle.
Why do viewers see buffering when OBS shows no dropped frames?
Viewer buffering can arise from their connection, device or location, and does not necessarily mean OBS is dropping frames. Compare OBS Statistics with YouTube’s live health information and ask whether the issue affects multiple viewers before changing your encoder settings.