For YouTube 720p live streaming, use 8 Mbps video bitrate with H.264. If your encoder supports AV1 or H.265, YouTube lists 6 Mbps for 720p instead, at both 30 and 60 frames per second.
Those figures are encoder targets, not proof that your internet connection can carry the stream reliably. Check your available upload speed, leave about 20% headroom above the total stream bitrate, and test the broadcast with realistic movement and audio before relying on it overnight.
The quick answer for 720p
YouTube’s recommendation depends on the video codec. Its live encoder table gives the same recommended bitrate for 720p30 and 720p60, but a different value for H.264 compared with AV1 or H.265.
| Resolution and frame rate | Codec | YouTube-listed recommended video bitrate | YouTube-listed minimum video bitrate |
|---|---|---|---|
| 720p30 | H.264 | 8 Mbps | 3 Mbps |
| 720p60 | H.264 | 8 Mbps | 3 Mbps |
| 720p30 | AV1 or H.265 | 6 Mbps | 2 Mbps |
| 720p60 | AV1 or H.265 | 6 Mbps | 2 Mbps |
These are video bitrates only. Audio has its own bitrate and uses some additional upload capacity. If you are using the common H.264 setting, start with 8 Mbps for the video track. If you deliberately select AV1 or H.265 and your encoder and YouTube workflow support it, start with 6 Mbps.
Do not assume that 720p60 automatically requires a higher bitrate here. YouTube’s listed recommendation is the same for 720p30 and 720p60 within each codec. The frame rate still changes how motion looks and how much work your computer or encoder must do, but the table does not tell you to raise the bitrate simply because you selected 60 fps.
For a devotional channel showing a mostly static image, 30 fps may be sufficient. For a music visualiser, moving artwork, scrolling news text or a camera feed, 60 fps can make movement look smoother. Choose the frame rate for the content, then apply the codec-specific bitrate rather than increasing it by habit.
What YouTube’s minimums and recommendations mean
A minimum is not the same as a sensible starting target. YouTube lists 3 Mbps as the minimum for H.264 at 720p and 2 Mbps as the minimum for AV1 or H.265. The recommended values are higher: 8 Mbps for H.264 and 6 Mbps for AV1 or H.265.
The lower figures describe the bottom of the listed range, not a promise that a stream set there will look good for every type of content. A quiet bhajan loop with little movement may hide compression more successfully than a local news loop with a presenter, a ticker, a map and frequent cuts. A bitrate that appears acceptable on a still title card can break up when the picture changes.
Use the recommendation as the starting point when your connection can support it. Consider the minimum only as a constrained fallback that you should test carefully. If you lower the bitrate because of a weak connection, inspect the result during movement rather than judging it from a static scene.
YouTube’s live guidance also lists constant bitrate, or CBR, as the relevant encoder mode. CBR aims to keep the outgoing video rate relatively steady instead of allowing large swings. That makes it easier to plan the connection requirement and reduces the risk that a complex scene suddenly consumes much more upload capacity.
Where your encoder exposes the setting, use a keyframe interval of 2 seconds. YouTube’s guidance says the interval should not exceed 4 seconds. A keyframe contains a fuller picture from which later frames can be reconstructed, so the interval affects how the platform receives and processes the stream. It is separate from the bitrate figure, but both settings belong in the same encoder check.
For audio, YouTube’s advanced settings recommend 128 Kbps stereo in the cited encoder guidance. Keep audio separate in your planning: an 8 Mbps video target is not the complete network requirement. Add the audio bitrate and allow room for the small amount of protocol and connection overhead that the raw settings do not show.
YouTube recommends RTMPS for encrypted transfer, while its live encoder documentation lists RTMP and RTMPS as protocols. Your streaming software may ask for the server URL and stream key separately. Copy these from YouTube Studio rather than relying on an old saved configuration, especially when setting up a channel for a long broadcast.
You can check the official YouTube encoder settings before publishing because platform tables can change. The values in this article describe YouTube’s current listed live-ingest recommendations, not a permanent rule for every future encoder version.
Choose the codec and set the encoder bitrate
Start by identifying which codec your encoder is actually sending. Selecting a codec in an encoder menu is not enough if the software, hardware or destination does not support that path correctly. Confirm the active output settings in the encoder and look for any warning from YouTube Studio during a private or unlisted test.
For H.264, set the video bitrate to 8 Mbps for either 720p30 or 720p60. H.264 is often the straightforward choice because it is widely supported by streaming software and hardware. Its higher YouTube recommendation does not mean it is the wrong choice. Compatibility and a predictable workflow can matter more than using a newer codec.
For AV1 or H.265, set the video bitrate to 6 Mbps for either 720p30 or 720p60. These codecs can be useful when your complete setup supports them, but do not switch solely because the listed bitrate is lower. A codec can place different demands on the encoder, and a setting that is available in the software may not be suitable for the computer or capture workflow you are using.
If you run OBS, check the output section rather than changing only the project resolution. Resolution, frame rate, codec, rate control and keyframe interval are separate controls. A canvas set to 1280 by 720 does not by itself guarantee that the outgoing stream is 720p, and changing the preview size does not necessarily change the encoder bitrate.
A useful setup record has at least these fields:
- Output resolution: 1280 by 720, if 720p is your intended stream resolution.
- Frame rate: 30 or 60 fps, chosen for the content.
- Codec: H.264, AV1 or H.265, matching the supported workflow.
- Rate control: CBR, where available.
- Video bitrate: 8 Mbps for H.264, or 6 Mbps for AV1 or H.265.
- Keyframe interval: 2 seconds, and no more than 4 seconds.
- Audio bitrate: set separately from the video bitrate.
Write down the working configuration before you change it. This is particularly useful for a 24/7 channel, where a small change made to solve one test problem can otherwise become difficult to trace later. If the stream becomes unstable after changing both codec and bitrate, you will not know which change caused it.
Content also affects the visible result. A static devotional background with slow text may look acceptable at a lower setting, while falling rain in a lofi scene, moving particles behind a song, or a fast-changing news panel reveals compression more quickly. YouTube’s recommendation is a useful common target, but it cannot replace viewing your own material at the intended frame rate.
If you are building a music channel, a visualiser for a 24/7 YouTube music stream can add movement, but it also creates more detail for the encoder to represent. Test the busiest part of the visualiser, not only the opening title card.
Check upload speed and leave bandwidth headroom
The most important connection question is not whether your broadband plan advertises a high download speed. Live streaming uses upload capacity. You need to know how much upload bandwidth is available to the streaming device at the time and place where the broadcast will run.
YouTube recommends leaving 20% of upload bandwidth available beyond the stream requirement. YouTube’s own short guidance says, “Leave a bit of room (20% recommended).” Treat that as headroom, not as the stream bitrate itself.
For an H.264 video target of 8 Mbps, 20% of the video figure is 1.6 Mbps. Adding those figures gives 9.6 Mbps, so roughly 10 Mbps of available upload capacity is the arithmetic starting point for the video target alone. This is a calculation from the 20% guidance, not a separate YouTube-published universal threshold.
The actual requirement needs more room because audio and connection overhead are separate from the video number. If other people are on the same connection, phones are backing up photos, a cloud drive is synchronising, or another camera is uploading, the stream has less of the connection to itself. In that situation, a speed test that just reaches the arithmetic figure is not a comfortable result.
Run the test on the same network and, if possible, from the same room and device that will send the stream. One test gives you a snapshot. A connection that looks adequate in the afternoon may behave differently when household use increases or when the local network becomes busy.
A high reading is not the same as stability. Watch for upload speed dropping, latency changing sharply, or packet loss during the test. YouTube does not turn an encoder target into guaranteed connection capacity. If the available upload is inconsistent, selecting the lower end of a published range may be more practical than repeatedly attempting a target that the connection cannot hold.
When you have to make a choice, change one thing at a time. First remove other uploads and repeat the test. Then try a lower frame rate if the content permits it. If that does not help, consider a codec and bitrate combination that your setup can maintain. Do not keep raising and lowering several settings together, because the result will be hard to diagnose.
A wired connection can be useful where it is practical, but do not treat a cable as a guarantee. The important question is whether the complete network path remains reliable for the length of the broadcast. If you must use Wi-Fi, keep the streaming device in a stable location and avoid placing other heavy network activity on the same connection during the test.
For a channel intended to run continuously, the connection should be judged over a representative period rather than during a single successful minute. You do not need to invent a pass percentage. Look for recurring interruptions, upload drops and encoder warnings, then decide whether the target remains appropriate for the way you actually operate.
Test the stream and monitor its health
Before a public broadcast, send a test stream with the same resolution, codec, frame rate, bitrate and audio that you plan to use. Include the content that creates the most movement. For a local news loop, that might be a section with a presenter and animated lower thirds. For a bhajan channel, it might be the busiest transition and the loudest audio passage.
Use YouTube Studio’s stream health messages as evidence, not just the preview on the computer sending the stream. The local preview can look normal while the upload is dropping packets or the destination is receiving an inconsistent feed. Check whether the incoming bitrate is near the intended setting and whether YouTube reports connection or encoder problems.
Listen as well as watch. A stream can have a clear picture but clipped, missing or delayed audio. Check the beginning and end of a loop, because transitions can expose a problem that does not appear during a steady scene. If several people will monitor the channel, give them a short checklist rather than asking only whether it looks fine.
The checklist can include:
- Is the public or test stream receiving the expected resolution?
- Does the video remain intact during the busiest movement?
- Is speech or music present without clipping or gaps?
- Does the incoming bitrate remain reasonably steady?
- Does YouTube Studio show any stream-health warning?
- Does the encoder report dropped frames or overloaded output?
- Does the stream continue after the content loops?
Keep latency separate from bitrate. Latency is the delay between capture and playback. Lower latency can make interaction feel more immediate, but YouTube notes that lower latency may increase the chance of playback buffering. A devotional or ambience channel with little audience interaction may have no reason to choose the lowest latency mode. Changing latency should not be presented as a fix for an upload problem.
If the encoder reports dropped frames caused by the network, examine the connection and upload activity. If it reports that the encoder is overloaded, the problem may be the computer, codec, frame rate or scene complexity rather than the available upload speed. These are different failure modes and need different changes.
For a long broadcast, keep a simple log of the time, setting and warning message. If the stream fails overnight, that record can show whether the issue follows a particular scene, a network-use pattern or an encoder change. It also prevents you from treating one successful test as evidence that every later configuration will behave identically.
A 10-minute bitrate test before going 24/7 is a useful place to structure that preflight process. The point is not to create paperwork. It is to test the actual file and settings before your audience depends on them.
Keep live ingest separate from video uploads
YouTube has different guidance for live encoder ingestion and prerecorded video uploads. The 6 Mbps and 8 Mbps figures discussed here are for sending a 720p live stream to YouTube. They should not be copied into an export preset for an uploaded file without checking YouTube’s separate upload recommendations.
A live stream has to be transmitted continuously while viewers watch. The encoder produces the video, sends it over the connection and keeps the broadcast moving in real time. A prerecorded upload is first transferred as a file, then processed by YouTube. The workflows have different constraints, even when both files are labelled 720p.
The distinction matters for a channel made from prepared episodes. You might export a video for storage, upload it as a normal YouTube video, and also send a live version through an encoder. The file’s export settings are not automatically the same as the live ingest settings. Identify which path you are configuring before changing bitrate.
Do not use a file-upload bitrate guide to answer a live connection question. It may lead you to a number that says nothing about whether your internet connection can sustain the broadcast. Likewise, do not assume that the live ingest recommendation is the ideal export setting for a prerecorded master.
You can review YouTube’s live streaming setup guidance alongside its stream latency information. Check the relevant page for the workflow you are using, and recheck the official table when YouTube changes its encoder documentation.
Planning a dependable 24/7 channel
For an always-on channel, bitrate is one part of a chain. The file or scene must continue, the encoder must remain available, the connection must carry the output, and YouTube must continue receiving the broadcast. A correct 8 Mbps setting cannot compensate for a computer that sleeps, a network that disconnects or a source file that reaches its end unexpectedly.
If you run a loop from a local computer, disable sleep and test what happens after a monitor is turned off. Make sure the source continues when the first episode ends. For a news or information channel, check that scheduled changes do not introduce a different resolution or codec setting halfway through the day.
A 24/7 stream from a Windows cloud PC may suit you if you need the encoder to keep running without leaving your personal computer switched on, but it adds another operating environment to understand. Compare the complete workflow, including file access, monitoring and recovery, rather than choosing only by the bitrate field.
If the main burden is keeping a prepared video running continuously after you have configured YouTube, StreamNeo removes the need to leave your own computer switched on by turning the uploaded file into the YouTube broadcast and handling automatic restarts when the stream drops. You still need to select suitable content, check YouTube’s rules and verify the result; the service does not make a bitrate or connection setting universally safe.
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 720p 60fps?
For H.264, YouTube lists 8 Mbps for 720p60. For AV1 or H.265, it lists 6 Mbps. YouTube gives the same recommended bitrate for 720p30 and 720p60 within each codec, so do not raise the figure solely because you selected 60 fps.
How much upload speed do I need to stream 720p on YouTube?
For an 8 Mbps H.264 video target, adding YouTube’s recommended 20% headroom gives 9.6 Mbps, or roughly 10 Mbps for the video calculation. Audio, network overhead and other devices also need room, so a connection that only reaches that figure may not be dependable.
Can I use the minimum bitrate instead?
YouTube lists 3 Mbps as the H.264 minimum and 2 Mbps for AV1 or H.265 at 720p. Those are lower limits, not the recommended starting points. If you use one, test the most detailed and active parts of your stream and watch YouTube Studio for health warnings.
Is bitrate the same for a YouTube video upload?
No. The figures in this article apply to live encoder ingest. YouTube has separate recommendations for prerecorded video uploads, so use the guidance for the workflow you are actually configuring.