For YouTube Live in OBS, select CBR and set the video bitrate target to match YouTube’s recommendation for your ingest codec, resolution and frame rate. If you use OBS NVENC, do not treat the maximum bitrate field as a second active CBR ceiling: OBS documents that maxBitRate is used for VBR and ignored in CBR mode.
The target and maximum controls are easy to confuse because OBS exposes both in some encoder settings. The important distinction is encoder-specific: the documented ignore behaviour applies to NVENC, not automatically to every OBS encoder. Choose a sustainable target, check your stream health, and verify the controls for your selected encoder before relying on them.
Set a CBR target for YouTube Live
In OBS, open Settings → Output → Streaming and choose the encoder you intend to use. Select CBR for rate control, then set the video bitrate target. YouTube’s live encoder guidance recommends CBR; the right target depends on the codec, output resolution and frame rate, rather than a universal value that works for every channel.
The bitrate field is usually expressed in kilobits per second (Kbps), while YouTube’s recommendations are shown in megabits per second (Mbps). One Mbps is 1,000 Kbps, so a recommendation of 14 Mbps corresponds to an OBS target of 14,000 Kbps. Check the unit shown in your OBS version before entering a figure, and make sure you are editing the streaming output rather than a recording profile.
Set your canvas and output resolution, frame rate, and codec before selecting the target. If you change any of those later, revisit the bitrate choice. For example, a 1080p30 H.264 stream uses a different recommendation from a 1080p60 H.264 stream, and the H.264 recommendation differs from AV1 or H.265 at the same output size. The OBS setup guide for a 24/7 YouTube stream on JioFiber covers the broader connection and configuration decisions; use the current official YouTube table for the target itself.
CBR does not mean that your network delivers a perfectly unchanging flow of bits at every instant. It describes the encoder’s rate-control mode: the encoder aims to maintain the selected rate over time. Network conditions and transport overhead can still affect what reaches YouTube, so choose a target your connection can sustain rather than assuming the CBR setting makes an unstable connection reliable.
Match the target to codec and output
Use YouTube’s live ingest recommendations, not a bitrate table intended for uploading a finished video. The table below reproduces YouTube Help’s recommendations for live video ingest. These are recommended video rates, not a promise of picture quality or an instruction to push the same rate regardless of your upload capacity. YouTube’s live encoder settings and bitrate table also includes minimum settings and additional guidance.
| Output resolution and frame rate | AV1 or H.265 recommendation | H.264 recommendation |
|---|---|---|
| 720p at 30 fps | 6 Mbps | 8 Mbps |
| 720p at 60 fps | 6 Mbps | 8 Mbps |
| 1080p at 30 fps | 10 Mbps | 14 Mbps |
| 1080p at 60 fps | 12 Mbps | 17 Mbps |
| 1440p at 30 fps | 15 Mbps | 21 Mbps |
| 1440p at 60 fps | 24 Mbps | 34 Mbps |
| 2160p (4K) at 30 fps | 30 Mbps | 42 Mbps |
| 2160p (4K) at 60 fps | 35 Mbps | 50 Mbps |
These values are the recommendations published by YouTube Help, as accessed on 3 October 2026. Match the row to the codec YouTube will receive and the output resolution and frame rate set in OBS. If you are unsure which codec is in use, inspect the selected encoder and its output settings rather than assuming that the name of the graphics card determines the codec. YouTube says it detects encoder settings by default and transcodes a live stream into multiple formats for viewers; those downstream formats do not change the ingest target you choose in OBS.
The higher row is not automatically the better choice for every channel. A static devotional image with a softly animated background may not need the same detail as a fast-moving demonstration, but the recommendation still gives you a useful starting point for the selected codec and output. If your computer struggles to encode a higher frame rate, or your upload connection cannot sustain the corresponding target, a lower output resolution or frame rate with a matching recommendation may produce a steadier broadcast. OBS notes that 60-fps streaming can use more system resources than 30 fps in its overview of output settings.
YouTube also lists minimum rates. For instance, its table gives 1080p30 AV1/H.265 a 4 Mbps minimum and 10 Mbps recommendation, while H.264 has a 5 Mbps minimum and 14 Mbps recommendation. At 1080p60, the corresponding figures are 4 Mbps minimum and 12 Mbps recommendation for AV1/H.265, and 6 Mbps minimum and 17 Mbps recommendation for H.264. A minimum is not the same as the recommended target; treat it as a lower bound in the table, not as a guarantee that every scene will look acceptable at that rate.
A sensible workflow is to settle the output first, identify the ingest codec, and then pick the matching YouTube recommendation. If you are configuring a long-running music stream, also check that source audio levels are consistent; bitrate changes cannot fix a track that is much louder than the next one. The guide to normalising audio across an FFmpeg playlist addresses that separate part of the stream quality problem.
Keep the maximum field in context
When you choose CBR, the target is the rate-control setting to focus on. It is the bitrate OBS is asked to maintain on average through the encoder’s CBR mode. Readers often ask what to enter as “maximum bitrate” after choosing CBR, but the question has no encoder-independent answer. For OBS NVENC, the documented maxBitRate option is ignored in CBR mode, so it is not a second active ceiling that you should set above the target.
That does not mean every field labelled “maximum” can be disregarded for every encoder. OBS has different encoder implementations and settings, and a field’s behaviour depends on the encoder. The general rule is to identify your encoder first, then check its documentation or interface. This article’s specific maximum-field conclusion concerns the documented NVENC parameter, not every setting with a similar label.
It is also useful to separate the encoder target from the connection limit. A configured target is not permission for the stream to exceed your available upload capacity. Audio and transport overhead add to the video stream’s outgoing traffic, and household use or connection variation can reduce the bandwidth available while you are live. YouTube advises leaving about 20% of upload capacity unused; its streaming tips explain the upload-bandwidth headroom recommendation. That 20% is YouTube’s guidance, not a measured guarantee for your individual connection.
Suppose your selected H.264 output is 1080p30. The YouTube recommendation is 14 Mbps of video. If that target leaves too little room for audio, overhead and variation on your upload connection, moving the maximum field to a higher value will not solve the mismatch. Instead, test the connection under realistic conditions and consider a lower output or target you can sustain. The guide to moving a 24/7 music stream from a PC to a VPS discusses continuity trade-offs for a different operating arrangement; the bitrate decision still depends on the stream settings and available connection.
What OBS documents for NVENC
The OBS Advanced NVENC Options documentation says maxBitRate specifies the maximum bitrate for the encoded output, and states that it is “used for VBR and ignored for CBR mode.” The page describes NVENC options introduced starting with OBS 31.0 and is dated 21 August 2024. In practical terms, if you select NVENC CBR, set the CBR target according to the YouTube recommendation and your connection. Do not enter another number in the maximum field under the assumption that it caps the CBR stream at that separate value.
This is a narrow but important reading of the documentation. The NVENC maximum parameter has a role in VBR, where the encoder may vary its rate and the maximum constrains that variable output. Under CBR, the documented parameter is ignored. It does not make the maximum field a hidden way to make CBR safer, nor does it mean the CBR target itself should be set without regard to upload capacity.
Use the exact name and context in OBS when checking your settings. OBS updates can change interfaces, and different encoder choices can expose similar words for different controls. If your interface does not match the NVENC documentation, confirm the chosen encoder and OBS version before drawing conclusions. The OBS NVENC options page is the primary reference for that documented behaviour.
Why another encoder may behave differently
The term CBR is common across encoders, but not every encoder exposes the same controls or implements them in an identical way. The finding here is not that a “maximum” setting is meaningless throughout OBS. It is that the specific OBS NVENC maxBitRate parameter is documented as a VBR setting that is ignored in CBR mode. You should not transfer that statement to x264 or another encoder without checking its own controls and documentation.
If you use a different encoder, inspect its rate-control menu and the meaning of any maximum, peak or buffer fields it offers. Those labels can refer to distinct concepts. A maximum may constrain a variable-rate mode, while a buffer-size control can affect rate-control behaviour without being the same thing as a maximum. Avoid changing several controls at once based on a tutorial for a different encoder; otherwise, a successful or failed test will not tell you which setting mattered.
For a channel that must run overnight, keep a note of the encoder, rate-control mode, output settings and target that passed a test. If you later change the encoder or upgrade OBS, revisit the relevant documentation and test again. That is more reliable than copying a screenshot where the encoder, OBS version or codec is not visible. The guide to looping videos in OBS for YouTube Live can help with the content side of a loop, but it does not replace checking encoder-specific rate controls.
Leave upload headroom and test the connection
Choose the target based on stable upload capacity, not only the download speed shown on an ISP plan. YouTube’s streaming tips recommend leaving around 20% of upload bandwidth available as headroom. If your measured upload capacity varies, base the decision on a stable, realistic result and not a brief peak. A household in which somebody starts a large upload during your broadcast is a different operating condition from an otherwise idle connection.
OBS’s connection troubleshooting guidance treats dropped frames as a sign that the network connection may be unstable or unable to maintain the configured bitrate. Its recommended first configuration step is to lower the video bitrate, taking stable upload speed and the streaming service’s limits into account. The guide suggests 75% of total upload speed as a starting point in that troubleshooting context. This is guidance for diagnosing a connection problem, not a universal target or a promise that the stream will remain stable at that fraction. See the OBS stream connection troubleshooting page for the full steps.
A useful test resembles the real broadcast. Include audio and representative movement, then watch OBS statistics and YouTube’s stream health while it runs. For a still-image bhajan channel, test the actual audio chain and any motion or scene changes you expect to use. For a news loop, include clips with motion and transitions. YouTube recommends testing with audio and movement similar to what will be in the stream; a static test scene can miss a problem that only appears during the real programme.
If the test reports dropped frames, first distinguish network drops from rendering or encoding lag in OBS’s statistics. A network problem points towards a bitrate the connection cannot sustain, connection instability, or competing traffic. Encoding lag instead suggests the computer or encoder is struggling with the chosen output. Lowering the video bitrate is a reasonable response to network instability, but it may not fix a machine that cannot render or encode the chosen resolution and frame rate. Change one setting at a time, repeat the test, and retain the working configuration.
During a long broadcast, keep an eye on stream health and any warning messages rather than assuming the opening minutes prove the setup. A stable test is evidence for that connection and workload at that time, not a guarantee for every night. If you are running an always-on channel, this is also where a computer-dependent workflow can become operationally inconvenient: if the machine sleeps, reboots or loses power, someone may need to restore the broadcast. StreamNeo removes that particular need to keep your own computer running by turning an uploaded file into a YouTube live stream, while leaving your channel and stream settings your responsibility.
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
What bitrate should I use for YouTube Live in OBS?
Choose the recommendation in YouTube’s live ingest table for your codec, resolution and frame rate, then check that your upload connection can sustain it with headroom. For example, YouTube recommends 14 Mbps for 1080p30 H.264 and 10 Mbps for 1080p30 AV1 or H.265. Those are YouTube Help recommendations, not guarantees of a particular picture quality or connection result.
Should OBS be CBR or VBR for YouTube Live?
YouTube’s live encoder settings call for CBR, so use CBR as your starting point in OBS. Match the target to YouTube’s recommendation and your sustainable upload capacity. If you choose another mode for a specific reason, confirm the encoder behaviour and test the result before relying on it.
What should I put in NVENC’s maximum bitrate field with CBR selected?
OBS documents NVENC maxBitRate as used for VBR and ignored for CBR. That makes the CBR target the relevant rate-control value in this documented case; the maximum is not a separate active CBR cap. Do not assume the same behaviour applies to a different encoder without checking its documentation.
Why does OBS show a maximum field if CBR ignores it?
A control can be available for an encoder’s other rate-control modes even when it has no effect in the mode you selected. In OBS’s documented NVENC case, the maximum parameter applies to VBR and is ignored in CBR. Check which encoder is selected and read its specific documentation before changing a similarly named field.