To set a bitrate limit in OBS, open Settings → Output and lower Video Bitrate in the streaming controls. Choose a rate that fits YouTube’s recommendation for your resolution, frame rate and codec, while remaining within the upload capacity your connection can reliably sustain.
There is no single bitrate that suits every stream, and a setting cannot guarantee stable delivery. Use YouTube’s figures as a target, leave bandwidth headroom, then test with representative content and watch both OBS and YouTube for signs of trouble.
Where to lower the bitrate in OBS
In OBS, open Settings, select Output, and find Video Bitrate in the streaming output controls. Enter a lower value there if your current rate is too demanding for your connection. If Output is set to Advanced mode, look in its Streaming section. Labels and layout can vary slightly between OBS versions, but the setting is the streaming video bitrate, not the recording bitrate.
This is the control OBS directs streamers to use when investigating dropped frames and intermittent disconnections. If you stream and record at the same time, check which output you are changing: reducing the recording bitrate does not by itself lower the rate sent to YouTube. OBS’s stream connection troubleshooting guide also describes other possible causes of connection problems, so do not assume every dropped frame is a bitrate issue.
Before changing anything, note your current output resolution, frame rate, codec and bitrate. That gives you a baseline for a controlled test: change the stream bitrate, not several unrelated settings at once, and see whether the symptoms change. If you need to revisit the visual side of the stream as well, a guide to why a 4K 60fps live stream can fall back to 1080p can help separate resolution issues from bitrate and connection issues.
Choose a target for resolution, frame rate and codec
YouTube’s recommended video bitrate depends on the resolution and frame rate you send, and on the codec. Its current live encoder settings list separate recommendations for H.264 and for AV1 or H.265/HEVC. These are recommendations, not assurances that your home or office connection can carry the stream without interruption.
The table below reproduces YouTube Help’s recommended rates. The page does not state a publication year; check it again when setting up a stream because guidance can change. Values are video bitrate, not the combined total for video and audio.
| Ingestion resolution and frame rate | AV1 or H.265 recommended video rate | H.264 recommended video rate |
|---|---|---|
| 2160p (4K), 60 fps | 35 Mbps | 50 Mbps |
| 2160p (4K), 30 fps | 30 Mbps | 42 Mbps |
| 1440p, 60 fps | 24 Mbps | 34 Mbps |
| 1440p, 30 fps | 15 Mbps | 21 Mbps |
| 1080p, 60 fps | 12 Mbps | 17 Mbps |
| 1080p, 30 fps | 10 Mbps | 14 Mbps |
| 720p, 60 fps | 6 Mbps | 8 Mbps |
| 720p, 30 fps | 6 Mbps | 8 Mbps |
| 480p, 30 fps | 3 Mbps | 4 Mbps |
| 360p, 30 fps | 3 Mbps | 4 Mbps |
For example, YouTube Help recommends 12 Mbps for AV1 or H.265 and 17 Mbps for H.264 at 1080p60; at 1080p30 its recommendations are 10 Mbps and 14 Mbps respectively. Those figures are useful reference points, not universal answers. If you send H.264, use that column; if you send a different supported codec, use the relevant column rather than choosing a number from a row with a different output mode.
A higher resolution or frame rate has a different recommended rate, but it also needs more bandwidth to send at that target. A codec change can alter YouTube’s recommended figure too. Confirm the codec OBS is actually using for the stream rather than guessing from a recording profile. YouTube’s current encoder guidance lists H.264, H.265/HEVC and AV1, and supports frame rates up to 60 fps.
If your connection cannot reliably sustain the recommendation for a chosen mode, consider whether a lower resolution or frame rate is a better fit than forcing a high rate through an unreliable connection. That is a trade-off: the picture may contain less detail or motion may look less smooth, but a stream that keeps arriving can be more useful than a sharper stream with repeated interruptions. For a demanding 4K setup, the practical choices and constraints are explored in streaming 4K 60fps yoga videos from an Indian PC.
Use CBR and a two-second keyframe interval
Bitrate is one part of the encoder setup. YouTube recommends constant bitrate (CBR) and a two-second keyframe interval, with the interval not exceeding four seconds. These settings make the stream conform to YouTube’s encoder guidance; they do not replace choosing a rate your connection can carry.
In OBS, check the streaming output controls for the rate-control mode and keyframe interval. Set rate control to CBR and the keyframe interval to two seconds where those options are available. YouTube also recommends RTMPS, the encrypted form of RTMP. If you are changing settings in an existing profile, confirm they apply to the stream output rather than just a local recording.
Keep audio separate in your calculations. YouTube’s guidance lists audio settings independently, including AAC or MP3 for stereo and AAC for 5.1 surround. The audio contribution is part of the total data sent, even though OBS’s Video Bitrate box controls video. When assessing available bandwidth, allow for audio as well as video rather than treating the video figure as the entire stream load.
Leave upload headroom
The number shown by an internet provider is not a dependable promise of the upload capacity available to a stream at every moment. Other people and devices may be using the same connection, and network conditions can vary. YouTube’s streaming tips advise leaving 20% of available upload bandwidth as headroom. Treat that as practical guidance, not a formula that makes every connection stable.
Start by measuring upload capacity under conditions that resemble the time and place you plan to stream. A test made when nobody else is online may overstate what you will have during a busy evening. On a shared home connection, a video call, cloud backup or another upload can compete with the stream. In a small business or place of worship, staff devices and other network use can have the same effect.
OBS’s troubleshooting guide gives 75% of total upload speed as a useful starting point when diagnosing connection-related dropped frames. That is troubleshooting guidance, not a universal bitrate calculator. Compare it with YouTube’s headroom advice and the recommendation for your chosen mode, then test. If the connection varies, choose a lower rate rather than relying on a brief high speed reading.
Suppose your connection appears fast enough for a recommended 1080p60 rate in a quiet test, but capacity falls when other household members are online. You might lower the bitrate, stream at a less demanding resolution or arrange a more predictable connection. Each option has a cost: lower bitrate can soften image detail, lower resolution changes the picture size, and changing connectivity may require time or expense. A connection check is a starting point, not proof of what will happen overnight.
If you are planning an always-on stream, consider who or what else depends on that connection for the whole period, not just during setup. A practical look at running a 24/7 stream from an Indian data centre helps frame the wider question of where the broadcast runs; for an OBS stream from your own computer, your local upload connection still matters for as long as that computer is sending the live feed.
Run a representative test
Before making the stream public or relying on a new configuration, test it with material that resembles the real programme. YouTube recommends testing with audio and movement similar to the planned event. A static screen with no sound is a poor stand-in for a bhajan video with a moving visual, a news loop with changing graphics, or a study stream with frequent scene changes.
Run a private or otherwise non-public test using the same resolution, frame rate, codec, audio and bitrate you intend to use. Keep the test long enough to include the parts of the day when your connection may be busy, if practical. Watch whether the stream starts cleanly, whether motion and sound stay in step, and whether OBS’s dropped-frame counter rises. Check YouTube’s stream-health messages as well; a preview that looks acceptable on your own screen does not show every problem at YouTube’s ingest end.
Change one variable at a time. If the test has connection-related dropped frames, lower Video Bitrate and repeat the test under similar conditions. If the counter remains steady but the picture looks too soft, revisit the target rate, resolution and codec together. Avoid raising the rate simply because a single short test passed: capacity that is available for a few minutes may not stay available during a longer broadcast.
For a stream built around prerecorded programmes, test the loop and transitions as well as the encoder. Gaps, abrupt scene changes or a silent section can make a stream look faulty even when the bitrate is not the cause. A guide to keeping church sermon videos playing without gaps in a live loop addresses that separate content-continuity problem.
Monitor stream health and adjust
During the test and the eventual broadcast, keep an eye on OBS’s dropped-frame counter and connection indicator, then check YouTube’s stream-health status and messages. OBS notes that dropped frames can indicate an unstable connection or a bitrate the connection cannot sustain. Yellow or red connection indications, or a counter that keeps increasing, are reasons to investigate rather than to wait for the stream to recover on its own.
If the evidence points to an overloaded or unstable connection, lower the bitrate in Settings → Output → Video Bitrate and observe the result. If the issue persists, look beyond the bitrate: network congestion, security software, a VPN, or the selected ingest server may contribute to instability. Change one factor at a time and retest where possible, so you can tell whether the adjustment helped.
OBS also describes dynamic bitrate under Settings → Advanced → Network as a fallback. It can reduce the sending rate when the connection is struggling, but that means reduced video quality, and it does not fix the underlying connection problem. Treat it as a way to respond to changing conditions, not as a substitute for testing or a promise that a stream will remain uninterrupted.
For an always-on channel, a good setting is one that survives ordinary variation in the connection, not just one that produces a clean preview once. If you cannot be present throughout the night, a lower, tested target may be the more practical choice than a rate that depends on ideal conditions. StreamNeo removes the need to leave your own computer running to send an uploaded video continuously, which can help when the specific pain is keeping a local OBS machine on for an unattended loop; it remains a YouTube-only option and does not change the need to choose suitable content and settings.
Keep a brief record of the settings and test conditions: resolution, frame rate, codec, bitrate, connection use and any health messages. That lets you compare a later change against what worked before. Revisit the test if your internet plan, router, location, stream format or competing network use changes.
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
Where do I lower bitrate in OBS?
Open Settings → Output and lower Video Bitrate in the streaming controls. In Advanced output mode, look in the Streaming section, and make sure you are not changing only the recording bitrate.
What bitrate should I use for YouTube Live?
Use YouTube’s recommendation for the resolution, frame rate and codec you are sending, then check that the rate fits your reliable upload capacity with headroom. There is no one bitrate that is best for every stream; test the chosen setting under representative conditions.
Why is OBS dropping frames?
Dropped frames can indicate that the connection is unstable or cannot keep up with the selected bitrate, but bitrate is not the only possible cause. Check OBS and YouTube’s stream-health messages, try lowering the rate, and investigate other network conditions if the problem continues.
Should I use CBR and a two-second keyframe interval?
YouTube recommends CBR and a two-second keyframe interval, with a maximum interval of four seconds. Those are encoder recommendations; they do not guarantee delivery if the upload connection is unstable.