In OBS, open the streaming encoder settings and set Rate Control to CBR (Constant Bitrate). YouTube specifies CBR for live encoding, but this sets the encoder’s target; it cannot guarantee a perfectly steady delivered bitrate over an unstable connection.
Set a suitable target for your codec, resolution and frame rate, then use a two-second keyframe interval. If the rate still appears to change, distinguish what OBS is encoding from what it is sending and what YouTube is receiving before adjusting anything.
What CBR does—and does not do
CBR tells the encoder to aim for a configured bitrate over time rather than freely varying the rate to match each moment’s complexity. A quiet frame may need less detail to encode than a scene with moving faces, scrolling text or a busy temple crowd, but the encoder still works towards the selected target. YouTube’s encoder guidance lists CBR for RTMP/RTMPS live streams.
The term can be confusing because “bitrate” may refer to three different things: the bitrate configured in OBS, the bitrate OBS reports sending, or the rate YouTube reports receiving. The first is a setting; the other two describe activity during a stream. Even with CBR selected, those observed values can vary because they are measured over intervals, include changing audio and video data, or reflect transmission conditions. A fluctuating display alone does not prove the encoder is set to variable bitrate.
CBR also does not repair a connection that cannot sustain the target. If upload capacity is inconsistent, Wi-Fi is congested, or software on the computer is interfering with network traffic, delivery may be interrupted or fall behind. OBS’s connection troubleshooting guidance recommends examining dropped frames and connection status and identifies unstable connectivity and network software that deprioritises OBS as possible causes.
So start by verifying the setting, then diagnose the path from OBS to YouTube. This avoids lowering quality just because a graph moves, or assuming that CBR is broken when the real issue is delivery.
Open OBS streaming encoder settings
In OBS, open Settings → Output and look for the streaming encoder controls. If Output Mode is set to Simple, change it to Advanced so that the streaming encoder settings are visible. The exact layout and labels can differ by OBS version, operating system and encoder; look specifically for controls associated with streaming, not recording.
Confirm which encoder is selected before changing options. OBS may offer a hardware encoder or a software encoder, and available controls can vary between them. Make sure you are editing the encoder used for the live stream. Recording settings do not necessarily govern streaming, even if their controls look similar.
If you use a separate profile or scene collection for a channel, check the active profile as well. A common source of confusion is changing settings in one profile and then starting the stream with another. After making the change, return to the main OBS window and confirm that you are about to start the intended stream.
For a continuous prerecorded channel, stability matters as much as peak picture quality: a setting suitable for a short test on a fast office connection may not suit the machine and connection you expect to leave running. The practical trade-off between quality and a machine that must keep operating is also relevant when considering moving a 24/7 aarti stream from a local PC to a VPS. That is a broader operating choice, not a prerequisite for enabling CBR.
Set Rate Control to CBR
Within the streaming encoder settings, locate Rate Control and choose CBR. Some encoder interfaces use slightly different labels, but CBR should be identifiable as the constant-bitrate mode. Apply the setting and check that it remains selected in the active streaming configuration.
Then choose the video bitrate field. This is the target, not a promise that the network will deliver that exact figure at every moment. Avoid picking a target solely because it is the highest value the encoder accepts. It must suit the codec and output format, and your internet connection must be able to sustain it alongside normal network use.
If you also stream and record at once, confirm which encoder settings belong to each output. A stream can use one encoder configuration while a recording uses another. Changing a recording bitrate will not correct the live stream if the streaming output remains configured differently. For a related workload question, see the checks for dropped frames when OBS records and streams at once.
Use RTMPS where it is available in your YouTube streaming setup. YouTube describes RTMPS as the encrypted version of RTMP in its live encoder settings. Protocol choice is separate from rate control: selecting RTMPS does not itself make a variable-rate encoder constant, and selecting CBR does not resolve a weak connection.
Choose bitrate for codec, resolution and frame rate
Bitrate choice depends on what you send, not only on the number shown in OBS. YouTube publishes different recommendations by codec, resolution and frame rate. The table below shows selected H.264 examples from YouTube’s guidance; values are platform recommendations, not a guarantee that a particular connection can sustain them.
| H.264 output | YouTube minimum | YouTube recommended |
|---|---|---|
| 720p at 30 fps | 3 Mbps | 8 Mbps |
| 720p at 60 fps | 3 Mbps | 8 Mbps |
| 1080p at 30 fps | 5 Mbps | 14 Mbps |
| 1080p at 60 fps | 6 Mbps | 17 Mbps |
For example, a devotional channel with a mostly static image and spoken or musical audio might not need the same output format as a fast-moving local news loop. Do not use that observation to ignore YouTube’s recommendations: use the appropriate codec and output format guidance, then test the actual content. Movement, text and fine detail can make compression more visible, while a higher target is only useful if your connection can carry it reliably.
The table is not a complete matrix. YouTube also provides recommendations for AV1 and H.265/HEVC, and format choices can have compatibility implications. Consult the current YouTube codec and bitrate table for the precise combination you intend to use, especially for HDR. Its current guidance covers RTMP/RTMPS ingestion and streams up to 60 fps; do not assume that the H.264 row applies to another codec.
Choose one output resolution and frame rate, then select the corresponding recommendation as a starting point. Compare that target with what your upload connection can sustain while other household or business devices are active. If the connection cannot reliably support the chosen target, reducing resolution, frame rate or bitrate is more sensible than keeping a high setting and hoping CBR will overcome the limitation.
Set the two-second keyframe interval
In the same streaming encoder settings, set Keyframe Interval to 2 seconds. YouTube recommends a two-second interval and says not to exceed four seconds. Depending on the encoder, OBS may ask for seconds or for a related interval value; use the field’s stated units rather than guessing. If the setting is left on automatic, check what value the encoder actually uses.
A keyframe is a complete reference image from which later frames can be reconstructed. A predictable interval gives the platform and viewers’ playback paths regular reference points. YouTube transcodes live streams into multiple output formats; its transcoding explanation notes the role of consistent keyframe timing in helping viewers move smoothly between quality options.
This setting is distinct from CBR. CBR controls the encoder’s bitrate behaviour; the keyframe interval controls how often a complete reference frame is inserted. Setting one correctly does not compensate for the other being unsuitable. If the channel includes rapid cuts or changing text, the two-second interval remains the setting to verify rather than something to vary by scene.
Before going live, review the other format settings alongside the keyframe interval. YouTube’s advanced guidance includes progressive scan, square pixels, two B-frames and one reference frame; codec and HDR qualifications may affect what applies. Use the official page for the encoder and format you actually selected rather than treating a checklist for one setup as universal.
Test and diagnose remaining fluctuations
Run a test stream with representative audio and movement before relying on the configuration overnight. A still image and silence do not exercise the same encoding behaviour as a music visualiser, moving news ticker, or live camera. Check both OBS and YouTube Live Control Room during the test. YouTube’s stream-health messages and OBS’s statistics describe different points in the path, so compare them rather than expecting matching graphs.
Use this short diagnostic path:
- Verify configuration. Reopen the active streaming encoder settings and confirm CBR, the intended bitrate, and a two-second keyframe interval. Confirm the selected encoder and profile are the ones used by the stream.
- Check OBS statistics. Open View → Stats in OBS. Look at dropped frames related to network and the connection indication. Network-dropped frames point towards delivery rather than proof that rate control reverted to variable. Also note whether rendering or encoding lag is reported, as those are separate problems from network delivery.
- Check YouTube stream health. In Live Control Room, read the stream-health status and any specific messages while the test is running. If OBS shows a stable send while YouTube reports a problem, use YouTube’s message to narrow the issue; if OBS reports network drops, start with the connection path.
- Change one thing at a time. If the connection cannot sustain the target, lower the video bitrate and test again. If the bitrate is appropriate but drops continue, check for unstable Wi-Fi or network software that may deprioritise OBS, as outlined in OBS’s troubleshooting page. Avoid changing resolution, encoder, network and bitrate together, because the result will not tell you which change mattered.
A short-lived movement in a displayed rate is not enough to diagnose the cause. Statistics are sampled over time, and the encoded content can have changing complexity. The more useful question is whether OBS reports dropped network frames, whether YouTube reports unhealthy delivery, and whether the configured target is plausible for the available upload connection.
For a channel that runs continuously, keep a note of the working settings and the time of any failures. This helps you compare the OBS log and YouTube messages rather than relying on memory after a restart. Do not infer a general fix from one night: a connection may behave differently when other devices are active. If you need to change the stream’s visual layout as well, keep that work separate from bitrate diagnosis; the guide to running a 24/7 Tamil songs playlist in OBS is a more relevant reference for playlist setup.
If repeated connection interruptions make it impractical to keep a computer running and restart the broadcast yourself, StreamNeo removes that particular operational burden by running an uploaded video as a YouTube live stream without your computer left on. It does not change YouTube’s encoder recommendations or make an unstable local connection stable during setup, so still test the file and stream health before relying on a continuous channel.
If you have decided the file and channel are ready, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
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
Why does the bitrate number still move after I select CBR?
CBR sets the encoder’s target, but OBS and YouTube may be showing measured rates over time rather than the configured target. Content complexity and transmission conditions can affect those measurements. Check dropped frames in OBS and stream health in YouTube before deciding the setting failed.
Should I raise the bitrate to stop dropped frames?
Not automatically. If the upload connection cannot sustain the current target, raising it can make delivery less reliable; OBS recommends lowering video bitrate where appropriate. Check the connection and the relevant YouTube message, then test a lower target if the evidence points to insufficient upload capacity.
Is CBR the same as a two-second keyframe interval?
No. CBR is the encoder’s rate-control mode, while the keyframe interval determines how frequently complete reference frames are sent. YouTube recommends CBR and a two-second keyframe interval for live encoding, so check both settings separately.
Which bitrate should I use for my channel?
Start with YouTube’s recommendation for your codec, resolution and frame rate, then confirm that your upload connection can sustain it. The H.264 examples above are not universal settings for AV1 or H.265/HEVC. Test with the actual content and consult YouTube’s current table before changing formats.