For YouTube Live at 1080p and 30 fps, the bitrate depends on the codec: YouTube recommends 14 Mbps for H.264 and 10 Mbps for AV1 or H.265/HEVC. In OBS, match the output resolution and frame rate, use CBR with a two-second keyframe interval, then choose a rate your connection can sustain in a representative test.
Those recommendations are platform guidance, not a promise that a particular internet connection will deliver a stable stream. If your upload varies, a lower rate that holds steady can be more useful than aiming at the table’s recommended figure and dropping frames.
Set the OBS output to 1080p30
Start by confirming the picture that OBS sends, not just the size of the canvas you see while arranging scenes. In OBS, open Settings → Video. Set Output (Scaled) Resolution to 1920×1080 and Common FPS Values to 30. The official OBS overview guide describes these video settings and the distinction between the canvas and scaled output.
If your base canvas is a different size, OBS may scale it to the output dimensions. That can be intentional, but check the preview for cropped edges, stretched logos or text that has become difficult to read. For a simple still background, devotional image, or lofi scene, a mismatch might not be obvious at first; inspect the actual output preview rather than assuming that a 1080p canvas guarantees a 1080p stream.
Frame rate matters too. Choose 30 fps for a channel built around slides, a fixed camera, artwork or modest movement. If the source content moves quickly, test it at the intended frame rate and watch for judder or encoding artefacts. This article is about 1080p30; changing to a different resolution or frame rate changes the task, so re-check YouTube’s current live encoder guidance rather than carrying these figures over.
Choose the encoder codec
In OBS, select the encoder under Settings → Output, with output mode set to Advanced if needed to expose the streaming controls. The options shown depend on your OBS version, operating system and available hardware. YouTube accepts H.264, H.265/HEVC and AV1 for live ingestion, but the bitrate recommendations are not identical across them.
H.264 is a common choice and is often available through hardware encoders as well as software encoding. AV1 and HEVC can be available on newer systems, but compatibility depends on your encoder, OBS setup and YouTube’s current ingestion support. Do not choose a codec merely because it has a lower recommendation in the table: first confirm that OBS actually offers it for streaming and that the resulting broadcast is accepted and plays as expected.
For a channel already running reliably on H.264, the simplest course may be to keep that codec and tune its rate. If you are changing codecs, make a private or otherwise suitable test before a public broadcast. You are changing the encoded feed as well as its bitrate, so verify the whole path rather than treating the number alone as the setting.
A looping channel with several audio tracks may have a different production workflow from a single-scene stream, but the output still needs to be checked as sent. If audio configuration is part of your setup, see how to run a continuous YouTube stream with multiple audio tracks; keep the bitrate decision tied to the video codec and observed connection behaviour.
Apply the codec-specific bitrate recommendation
The table below reproduces YouTube’s published 1080p30 ingestion guidance. Mbps means megabits per second. Treat the recommended values as starting points for a capable connection, not as a universal number for every encoder or household.
| OBS streaming codec | YouTube minimum | YouTube recommended |
|---|---|---|
| AV1 | 4 Mbps | 10 Mbps |
| H.265 / HEVC | 4 Mbps | 10 Mbps |
| H.264 | 5 Mbps | 14 Mbps |
For H.264, enter 14,000 Kbps in OBS to target 14 Mbps. For AV1 or H.265/HEVC, enter 10,000 Kbps to target 10 Mbps. OBS commonly labels this field in Kbps; check the unit displayed in your version before entering a value. A mismatch between Mbps and Kbps can produce a setting that is far from what you intended.
The YouTube figures are specifically for the 1080p-at-30-fps row and the listed codec. Do not substitute the H.264 rate for AV1 or HEVC, or assume the lower AV1/HEVC recommendation applies to H.264. Likewise, these are video bitrate settings, not a measurement of your entire internet use. Your live connection also carries audio and other traffic, and competing household or workplace use can affect what remains available to the stream.
YouTube’s live encoder settings page is the primary place to confirm the current table before you configure a new channel. Guidance can change, and the settings shown here reflect the English table checked on 4 October 2026. YouTube also advises choosing a quality that can be streamed reliably on your internet connection.
Understand the minimum rates
A minimum is not a recommended target for ordinary use. YouTube lists minimums of 5 Mbps for H.264 and 4 Mbps for AV1 or H.265/HEVC at 1080p30. Those figures define a lower boundary in its table; they do not establish that every stream at that rate will look acceptable or remain connected.
A lower bitrate gives the connection less video data to carry each second, which can help when upload capacity is constrained. The trade-off is picture detail. Fine patterns, moving leaves, water, scrolling text or a camera moving across a scene can look softer or show blockiness when there is less data available. A still image with quiet audio may appear acceptable at a lower rate than a scene with frequent motion, but only a test of your actual material can tell you what compromise is tolerable.
Do not use the minimum as a shortcut around an unstable connection. Dropped frames may reflect a fluctuating connection, congestion or another issue rather than an incorrect codec recommendation. OBS’s connection troubleshooting guide explains that dropped frames mean the connection to the remote server is unstable or cannot keep up with the configured bitrate. Lowering the video bitrate is one troubleshooting step, not proof that the underlying cause is fixed.
If you lower a setting to make a test usable, compare the picture as well as the connection status. Read small text in a news ticker, check the edges of devotional artwork and listen for audio interruptions. For a bhajan stream that uses long static images, image quality priorities may differ from a local news loop with moving footage; the point is to choose a rate that works for your material and connection, not to hit a number in isolation.
Set CBR and the keyframe interval
YouTube’s live encoder guidance calls for constant bitrate encoding. In OBS, set the rate control to CBR for the stream. CBR aims to keep the encoded bitrate steady rather than allowing it to vary substantially with scene complexity. That makes the stream’s data rate more predictable, although it cannot make an inconsistent upload connection stable.
Set the keyframe interval to 2 seconds. YouTube recommends a two-second interval and says not to exceed four seconds. In OBS the control may appear as a keyframe interval in seconds, or as a value in frames depending on encoder and interface. If the interface asks for frames at 30 fps, two seconds corresponds to 60 frames. Confirm the unit before applying the setting.
Do not extend the interval beyond YouTube’s guidance in an attempt to compensate for limited upload capacity. Keyframe interval and bitrate solve different problems: the first controls how often a full reference frame is sent, while the second controls the data budget for the encoded video. For this 1080p30 setup, use the recommended interval and adjust bitrate only after testing the connection and picture.
Check upload capacity and headroom
A speed test can help you understand the upload rate available at the moment you run it, and YouTube recommends testing upload bitrate when choosing live settings. It cannot guarantee a stable broadcast later. The result may differ when the stream runs, when other devices are active, or along the route between your connection and YouTube’s ingest point.
Compare a measured upload result with the bitrate you intend to send, but do not treat the whole reported result as a safe, dedicated stream budget. Leave room for audio, other network traffic and variation. If the household connection is also carrying video calls, backups or other uploads, those uses can compete with the broadcast. A wired connection can be useful as a troubleshooting comparison where practical, but it does not raise YouTube’s limit or resolve every cause of instability.
Use the bitrate table as the platform reference, then find the highest rate that behaves reliably under realistic conditions. For example, if you plan to run a 10 Mbps AV1 stream, test around that rate while the other normal devices and services are in use. If OBS reports dropped frames or YouTube’s health notices problems, reduce the rate and repeat the test. Avoid making a decision from one speed-test result alone.
For a 24/7 devotional channel, it is worth testing at a time when your home or venue connection is typically busy, not only during a quiet period. The practical question is not simply whether an upload test can momentarily report a high figure; it is whether your actual broadcast remains healthy for a representative stretch. See also what upload speed is needed for a 24/7 bhajan stream on YouTube for considerations specific to an always-on devotional channel.
Test the stream and inspect its health
Before a scheduled public stream, send a test using the same codec, resolution, frame rate, bitrate and keyframe interval you plan to keep. Include representative motion and audio: a static title card is not a good stand-in for a camera pan, animated visualiser, busy ticker or changing video loop. If the channel uses a long playlist, test transitions as well as a single clip.
Watch OBS’s status for dropped frames and connection changes, and review YouTube’s stream-health messages in the live control room. YouTube recommends testing and monitoring; the signal in the interface is more informative than assuming that a configured bitrate has worked. If there is a warning, note when it occurs and what else was happening on the network. Lowering bitrate may help if the connection cannot sustain the chosen rate, but repeated drops at a much lower rate call for broader connection troubleshooting.
Check the picture at the receiving end if you can. Look for soft detail, visible blocks in motion, audio that falls out of sync, or a stream that pauses. A local OBS preview shows what is being composed, not necessarily what YouTube has received and delivered. Give the test enough time to include ordinary changes in your stream and network; a brief clean start does not establish overnight reliability.
If the channel is based on a prerecorded loop and you prefer not to keep a local computer running, the operating arrangement is a separate decision from bitrate. StreamNeo turns an uploaded video into a YouTube live stream so you do not have to leave your computer on to keep that file broadcasting; you still need to prepare the file and choose settings appropriate to the channel. For more on the trade-off between a local machine and a hosted approach, read whether a cloud service is cheaper than running a PC for YouTube Live in India.
Keep a short record of the settings that passed your test: codec, output resolution, frame rate, bitrate, keyframe interval and any health warnings. If you later change the scene, codec, network or source footage, test again rather than assuming the earlier result still applies. YouTube’s general live-stream settings guidance is also worth checking when you revisit the configuration.
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 at 1080p30 in OBS?
Use the recommendation for the codec you selected: 14 Mbps for H.264, or 10 Mbps for AV1 and H.265/HEVC in YouTube’s current table. Then test whether your connection can sustain it, and reduce the rate if the stream shows connection trouble. These figures are not a guarantee of stable delivery.
Is the YouTube minimum bitrate enough for a good-looking stream?
The minimums are 5 Mbps for H.264 and 4 Mbps for AV1 or HEVC at 1080p30, but a minimum is not the same as a general quality target. The result depends partly on what is on screen: motion and detail can suffer at a lower rate. Test with the material you actually intend to broadcast.
What CBR and keyframe settings should I use?
Set OBS rate control to CBR and the keyframe interval to two seconds. YouTube says not to exceed four seconds. Check whether your OBS keyframe field uses seconds or frames before entering a value.
Does a fast upload speed test prove my stream will stay stable?
No. A speed test is a useful snapshot, but it does not guarantee that the connection will sustain the same rate during a live stream. Test in realistic conditions and monitor OBS dropped frames and YouTube stream health.