For YouTube Live at 720p and 30 frames per second, use the bitrate range for your video codec: YouTube lists H.264 at 3 Mbps minimum and 8 Mbps recommended, and AV1 or H.265/HEVC at 2 Mbps minimum and 6 Mbps recommended. The minimum is a constrained-connection floor, not a quality target or a promise that a connection at that rate will deliver reliably.
Set the encoder to constant bitrate (CBR), use a two-second keyframe interval, and budget upload capacity for video, audio and a margin. YouTube recommends leaving 20% headroom; test with movement and sound like your real programme before you rely on the setup overnight.
The 720p30 bitrate quick answer
The relevant figures are YouTube’s live encoder settings, not its separate recommendations for files uploaded to YouTube. For the live stream, the published table varies by codec. At 720p30, the H.264 minimum is 3 Mbps and its recommended rate is 8 Mbps. For AV1 and H.265/HEVC, the minimum is 2 Mbps and the recommended rate is 6 Mbps. See YouTube’s encoder settings and bitrate table for the current guidance.
If your connection is tight, the minimum is the floor to consider, not the rate YouTube recommends for quality. There is no special low-bandwidth mode that makes a stream stable regardless of the connection. At the minimum, a little variation in available upload capacity can leave too little room for the outgoing stream. A line that measures exactly 3 Mbps does not therefore provide a sensible budget for 3 Mbps of H.264 video, let alone audio.
Treat the figures as settings guidance, not a guarantee of stable delivery. Your practical choice depends on the encoder’s supported codecs, sustained upload capacity, concurrent network use and what the video looks like during a realistic test. The goal is not to select the smallest number and stop checking; it is to fit a sensible stream within capacity while retaining enough margin for ordinary network variation.
Also keep live streaming distinct from uploading a finished video. YouTube’s separate upload encoding settings cover files sent for on-demand playback, and their rates are not a substitute for the live encoder table. When you are configuring a live channel, start with the live-specific table above.
Choose the row for your video codec
| Video codec | 720p30 minimum | 720p30 recommended | How to use the figures |
|---|---|---|---|
| H.264 | 3 Mbps | 8 Mbps | Use the minimum only as a constrained-connection floor; the recommended rate is YouTube’s quality target. |
| AV1 | 2 Mbps | 6 Mbps | YouTube lists the same 720p30 rates for AV1 and H.265/HEVC. |
| H.265/HEVC | 2 Mbps | 6 Mbps | Confirm that your encoder and workflow support it, then validate the actual stream in a test. |
YouTube lists H.264, H.265/HEVC and AV1 among its live video codec options, but your encoder may not offer all of them. Select a codec that your encoder supports and that you can test end to end. The lower published minimum for AV1 and H.265 does not establish that either will look better than H.264 at a given bitrate on every encoder. Avoid choosing by a universal quality claim that the official table does not make.
If you already have a working H.264 workflow, do not change codecs solely to chase a lower floor without testing. A codec change can affect compatibility with the encoder and the live setup. Check that the chosen codec is accepted by your encoder, keep the same resolution and frame rate for the test, and inspect the resulting picture and YouTube’s stream-health feedback. If you are comparing workflows, change one setting at a time so you know what caused a difference.
Some operators use command-line encoders or a virtual machine for a looping stream. If that is your setup, the practical details of an FFmpeg loop stream on an Indian VPS are separate from the bitrate decision: first ensure the encoder can produce the selected codec and rate, then check that the outgoing stream behaves as expected. The same principle applies to a desktop encoder.
Configure rate control and keyframes
Use CBR, or constant bitrate, for the video stream. In practical terms, CBR aims to keep the encoder output near the selected rate rather than allowing it to swing widely with each scene. That makes it easier to plan against limited upload capacity. It does not make the internet connection itself constant, so CBR cannot prevent a drop caused by congestion or a weak connection.
Set the keyframe interval to two seconds. YouTube recommends a two-second interval and says not to exceed four seconds. A keyframe is a complete reference frame from which subsequent compressed frames can be decoded; setting a regular interval helps the platform receive a predictable stream. If your encoder expresses the interval as a count rather than seconds, consult its documentation for the conversion at 30 fps rather than guessing.
For the connection to YouTube, use RTMPS where your encoder supports it. YouTube recommends RTMPS and lists RTMP/RTMPS as protocols. Follow the current stream setup details in YouTube’s live stream settings help, including the stream key and destination information. Keep a stream key private; it is the credential for sending video to your channel.
Set the output to 1280 by 720 at 30 fps. YouTube normally detects the resolution and frame rate sent by the encoder. Manual selection in Live Control Room requires a custom stream key with manual settings enabled, according to YouTube’s encoder guidance. Do not assume that changing a label in the control room will resize or re-encode the output; confirm the actual encoder output is 720p30.
Audio belongs in the configuration as well as the bandwidth calculation. YouTube lists AAC or MP3 for RTMP/RTMPS and lists 128 kbps for stereo audio in its advanced settings. Include the audio stream in your total rather than treating the video bitrate as the whole connection requirement. A devotional channel with continuous music or a news loop with spoken updates may depend on clear audio even when the picture is static.
Measure upload and leave headroom
Measure upload capacity, not download speed. YouTube advises using a speed test focused on upload and says the total bitrate being streamed cannot exceed available upload bandwidth. Its guidance recommends 20% headroom. That margin is for the complete outgoing stream budget: video, audio and any other stream you send, not just the nominal video rate. The details are in YouTube’s streaming tips.
As a planning exercise, if you set H.264 video to its 3 Mbps minimum, the connection still needs to carry audio as well. With YouTube’s 20% headroom recommendation, do not plan as if a speed test that reports 3 Mbps leaves room for a 3 Mbps video stream. The required measured capacity must be higher than the combined stream bitrate to leave the recommended margin. This is a way to reason about the budget, not a claim that one speed-test result guarantees delivery.
Run tests at the place and time you expect to stream, preferably more than once. A shared home or shop connection may be used by phones, televisions, cloud backups or other people during the broadcast. YouTube notes that shared network activity can reduce the bandwidth available to an individual stream, and disruptions can interrupt delivery. A quiet test taken when nobody else is online may not represent a busy evening.
Write down the codec, video bitrate, audio setting, speed-test upload result and whether other devices were active. Then decide whether your sustained upload budget covers the total stream with the margin left over. If not, do not conceal the shortfall by focusing on the video number alone. Reduce the bitrate, consider a lower resolution, or arrange a more suitable connection. The official sources do not publish a universal lower 720p30 bitrate below the stated minimums, so any lower figure should not be presented as a YouTube-approved floor.
For a channel that runs continuously, the computer and local network matter too. A PC running a long loop can be affected by sleep settings, updates or a shared connection; running a continuous YouTube stream from a Windows PC involves those operational choices as well as encoder settings. Keep those factors distinct: lowering the bitrate may ease bandwidth demand, but it will not prevent a computer from sleeping or a router from losing its connection.
Test with motion and audio
A static title card is a poor test for a stream that normally shows movement. Before the event or unattended run, send a private or otherwise appropriate test stream using the same encoder, codec, resolution, frame rate, bitrate and audio configuration you intend to use. YouTube’s encoder guidance recommends testing with representative movement and audio before going live.
Include the hardest ordinary material your channel will show. For a bhajan channel, that might mean moving visuals or transitions alongside uninterrupted music. A local news loop should include a presenter segment, lower-third graphics and any clip with camera motion. A lofi or ambience stream may be visually quiet but can still have audio that should not crackle, cut out or drift. The test should reflect the actual programme rather than an easier substitute.
Watch both the picture and sound from a receiving device if possible. Look for repeated pauses, blocky detail during motion, missing frames, audio dropouts and unexpected changes in the encoder output. Check YouTube’s preview and messages while the test runs. If a problem appears, adjust one variable at a time: first verify the network and stream health, then test a lower video rate or a codec your equipment supports. Record the result so that a later restart does not depend on memory.
A bitrate that passes for a minute may still be a poor choice for an overnight stream. Let a representative test run long enough to expose ordinary activity on your network, including other people using it. Do not treat an uneventful short preview as a guarantee. Your test is evidence about that setup under those conditions, not a promise about every later hour.
If the video is a pre-recorded loop, check the source file as well as the live output. A high-resolution file can be encoded down to 720p30, but verify that the encoder is actually sending the intended output. For long programmes, a guide to looping pre-recorded videos on YouTube from an Azure VM may help you think through a different hosting workflow; it does not replace the need to test the chosen bitrate against your own upload capacity.
Watch stream health and adjust
Once live, keep the stream health messages visible and check them when you make a change or notice a symptom. YouTube can report problems with the incoming stream; read the current message rather than guessing from the viewer’s picture alone. A viewer can experience buffering for reasons beyond the encoder, while a preview that looks acceptable at one moment does not prove the connection has spare capacity.
If health warnings coincide with network use elsewhere, first look for a way to reduce competing upload traffic. If the warnings continue, test a lower bitrate that remains consistent with the codec, resolution and practical quality you need. You can also consider a lower resolution if the available capacity cannot carry video, audio and the recommended margin. The trade-off is straightforward: a lower data rate reduces the load on a constrained link, while reducing resolution can make fine details less clear.
Do not respond to a weak connection by increasing bitrate above the available budget. Nor should you lower the keyframe interval or change several encoder options at random. Confirm CBR and the two-second keyframe setting, confirm actual output resolution and frame rate, and use the stream-health information to isolate the issue. Repeat the representative test after each meaningful change.
If the stream must continue when your personal computer is off, the operating model becomes part of the decision, separate from codec configuration. StreamNeo can remove the need to leave your own computer running for a file-based 24/7 YouTube broadcast, which addresses that specific overnight-computer burden; it does not change YouTube’s bitrate guidance or remove the need to choose and test a suitable stream configuration.
Choose the workable trade-off
A reliable configuration is the one your equipment can produce and your connection can carry with room for the rest of the stream. If you can sustain a budget closer to YouTube’s recommended rate for your codec plus audio and headroom, that is the target to try. If you cannot, the codec-specific minimum is a floor for a constrained connection, not an assurance of quality or stability. A lower output rate or resolution may be more realistic than running at the floor with no margin.
For example, an H.264 setup that measures upload capacity just around its 3 Mbps video setting has no sensible room for audio and variation. Rather than calling it adequate, retest at a lower video bitrate or lower resolution, reduce other upload activity, and inspect the result. The official table does not declare a universal lower 720p30 rate, so judge the compromise through a real test and be candid about what you observe.
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 720p30 on YouTube Live?
YouTube lists H.264 at 3 Mbps minimum and 8 Mbps recommended. For AV1 and H.265/HEVC, it lists 2 Mbps minimum and 6 Mbps recommended. The minimum is a constrained-connection floor, not the recommended quality target.
How much upload speed do I need for 720p30?
Your available upload must carry the full outgoing stream, including audio, and YouTube recommends leaving 20% headroom. Measure upload capacity where you will stream and account for other people or devices using the connection. A speed test result equal to the video bitrate is not enough to establish a workable budget.
Should I use H.264, AV1 or H.265?
Choose a codec your encoder supports and verify it in a representative test. YouTube’s published 720p30 bitrate figures differ by codec, but they do not establish that one codec will always look better on every encoder. Do not switch solely on the assumption that a lower listed minimum guarantees a better result.
What settings should I use besides bitrate?
Use CBR, a two-second keyframe interval, and RTMPS where supported. Set the encoder output to 1280 by 720 at 30 fps and include audio in the bandwidth budget. Test with movement and sound, then monitor YouTube’s stream-health messages while live.