If you play a pre-made video through an encoder into YouTube Live, your 720p bitrate is the bitrate of the live signal sent from the encoder to YouTube. YouTube lists 8 Mbps as the recommended 720p/30 fps H.264 live bitrate, or 6 Mbps for AV1 or H.265; neither figure is a promise that a slow or variable connection will carry it reliably.
If you are uploading a video file as a normal YouTube video, use the separate upload guidance instead. For a live stream, measure your available outbound upload under realistic conditions, leave room beyond the stream's total bitrate, and lower resolution if the connection cannot support the setting you have chosen.
What 720p bitrate means for a pre-recorded live stream
“Pre-recorded” describes the content, not necessarily the delivery method. If you load a finished bhajan programme, lofi mix or local-news loop into an encoder and send it to YouTube as a live broadcast, YouTube receives a live ingest. The encoder packages the video and audio and transmits them continuously; bitrate is the amount of data sent each second.
That distinction matters because the settings for a live encoder and the recommendations for uploading a finished file answer different questions. In a live workflow, the outbound connection between the encoder and YouTube must carry the encoded stream while the broadcast is running. In a regular upload, a file is transferred and processed as an upload; its suggested video bitrate is not a live connection target.
A stream's video bitrate is not the only traffic involved. Audio also consumes bitrate, and the total stream has to fit within the available upload bandwidth. YouTube's live encoder settings and bitrate table gives live-ingest recommendations by resolution, frame rate and codec. Its separate upload encoding recommendations label their figures as guidance for uploaded files.
For 720p/30 fps SDR uploads, YouTube lists 5 Mbps for standard frame rates and 7.5 Mbps for high frame rates. Those numbers apply to the file-upload workflow, not to an encoder sending a pre-recorded programme as a live stream. Do not choose a live encoder setting by copying the upload figure simply because the footage was recorded earlier.
If your actual aim is to publish a video that viewers watch on demand, upload it normally. If you need a scheduled or continuous live channel, treat the signal as live ingest even when the programme itself is a looped file. The guide to starting a 24/7 lofi stream covers the broader channel workflow; this page focuses on a connection and bitrate decision.
YouTube's 720p/30 fps ingest recommendations
YouTube's published live table gives these 720p/30 fps figures:
| Ingest codec | Listed minimum | Recommended bitrate |
|---|---|---|
| H.264 | 3 Mbps | 8 Mbps |
| AV1 or H.265 | 2 Mbps | 6 Mbps |
These are YouTube's stated live-ingest values, not thresholds that prove a particular connection will remain stable. The recommended figure is the clearer starting point when your connection can accommodate it. The listed minimum is useful context when comparing settings, but it should not be read as a guarantee of continuity, image quality or approval.
The same table currently lists those bitrate values for 720p/60 fps as well. That does not mean 60 fps will look or behave the same as 30 fps in every programme, or that choosing 30 fps automatically changes YouTube's recommendation. For a mostly static prayer image, an album cover or a slow ambience scene, 30 fps may be a reasonable production choice. For rapid movement, it may not suit the content. Choose frame rate for the programme and test the actual output rather than assuming a lower frame rate earns a specific bitrate reduction in the table.
The codec rows also should not be treated as a shortcut for an inadequate connection. The table gives different recommended bitrates for the listed codecs; it does not promise that AV1 or H.265 will provide identical visual results at a lower setting or cure fluctuations in upstream service. Use a codec your encoder supports reliably and that you can configure correctly.
A practical decision path is straightforward. First establish whether you are sending a live stream or uploading a file. For live 720p/30, identify the codec and use the corresponding recommended figure as a target only if your measured connection has sufficient capacity plus headroom. If it does not, reduce the live output resolution or reconsider the connection before the scheduled broadcast.
H.264 versus AV1 or H.265
H.264 is widely supported by streaming software and hardware, which can make it the simpler choice when your encoder setup is already proven. In YouTube's 720p/30 live table, its listed recommendation is 8 Mbps. AV1 and H.265 have a 6 Mbps recommendation in that table, with lower listed minimums as shown above.
Those figures can help you check whether a planned stream fits your upstream capacity, but they are not a universal quality comparison. Source material, encoder implementation, movement, noise, fine detail and audio all affect the result viewers receive. A static icon over calm music is a different picture to encode from a scrolling news ticker or a game replay with frequent movement. YouTube does not say in this table that one codec will always look better at a given rate.
Start with compatibility and a representative test. Check that the encoder can output the chosen codec and that YouTube accepts the settings. If you are using H.264 and the connection cannot reasonably carry the recommended bitrate with headroom, changing codecs may be worth testing only if your equipment and workflow support it. Do not reduce the planned bitrate on the assumption that a codec change alone makes the connection stable.
For a small business channel or a devotional loop, operational simplicity can matter more than experimenting with codecs just before a long broadcast. Keep a known-good configuration, record its resolution, frame rate, codec and bitrate, then change one setting at a time during a test. That gives you a useful comparison without confounding connection changes and encoder changes.
Measure upload speed and leave headroom
Measure outbound upload speed, not download speed. A speed test that reports a strong download result does not show how much data your connection can send to YouTube. Run a test when the network is being used in the way it will be during the broadcast: at a similar time of day, over the same Wi-Fi or wired connection, with the same household or office devices active where possible.
YouTube's streaming tips say the total stream bitrate cannot exceed available upload bandwidth and recommend leaving 20% of upload bandwidth unused as room. The margin is there because a test result is a measurement at a moment, while a live event has to keep sending data. Other users, cloud backups, video calls or changes in wireless conditions can reduce the bandwidth available to the encoder.
Use that recommendation as a planning check, not as a stability formula. For example, if your measured upload capacity is 10 Mbps, leaving 20% unused means the stream's total bitrate should stay within the remaining 8 Mbps under that measurement. That arithmetic does not establish that the connection will sustain 8 Mbps throughout the event, and the audio bitrate is part of the total. If the measured result varies, plan around the lower results you actually observe rather than the best one.
For H.264 at YouTube's recommended 720p/30 live bitrate, an 8 Mbps video setting alone already uses the illustrative 8 Mbps remaining from that 10 Mbps measurement, before accounting for audio. That is not a sensible fit under YouTube's headroom recommendation. A higher and consistent upstream result, or a lower total stream bitrate and resolution, is needed for a more cautious plan. The 8 Mbps example is not a universal minimum for every ISP or household; it demonstrates why available capacity and stream bitrate must be considered together.
Include all simultaneous outbound traffic in your thinking. If another encoder, remote backup stream or regular video call uses the same connection, its traffic competes for capacity. YouTube notes that shared network use can limit upload available to an individual stream. Its live-stream troubleshooting guidance is useful if YouTube reports errors, but a speed test and a successful preview do not remove the need to watch the stream during the event.
If the source programme is played from a computer in your home or office, test that computer on the exact network path you will use. Wi-Fi can vary with distance, walls and other users; a wired connection may remove some wireless variability, but it cannot create upstream capacity that your internet service does not provide. Do not buy an adapter or encoder as a substitute for checking the actual upload available.
When to lower resolution
Lower the resolution when you cannot carry the chosen live bitrate with useful headroom under representative network conditions, or when the encoder repeatedly reports dropped frames or YouTube indicates insufficient incoming data. YouTube's troubleshooting advice includes considering a lower resolution when upstream capacity is not sufficient. The point is to choose a stream that fits the connection you have, rather than preserving a 720p label while the signal struggles to reach the platform.
For a calm devotional image, static artwork or study timer, viewers may find a consistent lower-resolution picture more usable than a sharper picture that repeatedly breaks up. For a local-news ticker or detailed text, reducing resolution can make small lettering harder to read. Test the content itself at the lower output size; check text, faces and any on-screen schedule on a phone as well as a larger display.
YouTube's table includes lower-resolution options such as 480p/30 and 360p/30 with codec-specific values. Consult the current table for the exact figures for the codec you use rather than transferring the 720p values or inventing a universal “slow internet” threshold. A lower resolution is a choice to test, not proof that the connection will now remain stable.
Try the fallback before the event, not in the middle of a long scheduled broadcast. Make a short private or unlisted test if appropriate to your workflow, with the actual audio and representative motion. Confirm that the image is readable, audio is present, and YouTube's stream health does not show a problem. If the connection fluctuates enough that even the lower setting is unreliable, investigate the network or choose a different connection rather than continuing to lower settings blindly.
For a channel planned to run unattended, the consequences of a mid-stream change are worth considering. Document the tested resolution and encoder settings, and ensure someone knows how to check stream health and respond to warnings. The remote monitoring guide for an always-on YouTube stream offers a wider checklist for noticing problems after a broadcast has started.
Encoder bitrate and connection checks
Once you have chosen a resolution and codec, configure the encoder to send a consistent signal. YouTube's general live encoder guidance includes RTMP or RTMPS, supported video codecs such as H.264, H.265 and AV1, constant bitrate encoding (CBR), and AAC or MP3 audio. It recommends a keyframe interval of two seconds and says not to exceed four seconds. For a 30 fps stream, a two-second interval corresponds to 60 frames.
Use the settings YouTube currently supports for the chosen workflow and verify that the encoder's bitrate means what you think it means. Some software presents video bitrate separately from audio; other displays may show a total. When applying YouTube's headroom guidance, compare the total outgoing stream to available upload capacity, not only the video field. If you have set 8 Mbps for video and added audio, the total is higher than 8 Mbps.
Check the ingest destination and stream key carefully, and avoid sharing the key. YouTube's instructions for creating a live stream with an encoder explain the platform-side setup. RTMPS is YouTube's recommended secure transport; use it when your encoder and workflow support it. Transport choice does not compensate for insufficient bandwidth.
Before committing to a long or overnight broadcast, test with the programme's real audio and movement. A still image with silence is not representative of a music loop, scrolling headlines or a video with scene changes. Watch YouTube Studio's stream health and messages during the test. If errors appear, change one relevant setting at a time and repeat the test so you can tell whether the change helped.
Separate connection faults from configuration faults. If YouTube reports an unsupported setting, incorrect keyframe frequency or bitrate problem, verify the encoder configuration against the current help page. If dropped frames coincide with a connection that is under capacity or fluctuating, lowering resolution or improving the available upstream connection may be more relevant than changing a codec. A computer showing that playback is smooth locally does not prove that the outgoing signal is reaching YouTube cleanly.
If keeping a machine awake and watching its connection through the night is the pain point, StreamNeo removes that particular need by letting you upload the video, provide your YouTube stream key and leave the continuous broadcast running without your computer on. It remains a YouTube live-stream workflow: you still need to choose a suitable source file, set up the channel and check that the result meets your needs. It does not turn YouTube's published ingest figures into guarantees for a home connection or for a file upload.
For a locally hosted approach, the 24/7 stream from a laptop with its lid closed explains the different power and unattended-running considerations. Your bitrate decision still begins with the route that actually sends the stream to YouTube and the upload capacity available on that route.
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
Do YouTube's 720p upload bitrate figures apply to a pre-recorded live stream?
No. The 5 Mbps and 7.5 Mbps 720p SDR figures are YouTube's recommendations for standard video-file uploads at different frame rates. When a pre-recorded file is sent through an encoder as a live broadcast, use the live-ingest table instead.
Is 3 Mbps enough for 720p/30 H.264 live ingest?
YouTube lists 3 Mbps as the minimum for that mode and 8 Mbps as recommended. The listed minimum is not a promise that a connection will be stable at 3 Mbps, and total traffic and available upload headroom still matter.
Should I switch to H.265 or AV1 on a slow connection?
YouTube's live table lists 6 Mbps recommended for AV1 or H.265 at 720p/30, compared with 8 Mbps for H.264. That difference does not guarantee equivalent picture quality or stability, so use a codec your encoder supports and test the actual stream.
What should I do if my upload speed changes during the day?
Test at the times and under the network conditions expected during the broadcast, including ordinary shared use. Leave the recommended headroom, watch stream health during a representative test, and choose a lower resolution if the connection cannot support the selected setting.