For YouTube Live at 720p and 60 fps, use the bitrate listed for the video codec your encoder actually sends: YouTube recommends 8 Mbps for H.264 and 6 Mbps for AV1 or H.265/HEVC. The corresponding minimums are 3 Mbps for H.264 and 2 Mbps for AV1 or H.265/HEVC.
These are video-ingest settings, from your encoder to YouTube, not a promise that every viewer will receive video at that same bitrate. If by “playlist” you mean a sequence of videos you want to loop, the content arrangement does not change the codec’s 720p60 recommendation.
Recommended 720p60 video bitrate by codec
Choose a row by the codec being sent to YouTube, not simply by the output resolution or by what your playback software can decode. YouTube Help lists these recommended video bitrates for a live stream at 720p and 60 fps:
| Ingest video codec | Recommended video bitrate | Minimum video bitrate |
|---|---|---|
| H.264 | 8 Mbps | 3 Mbps |
| AV1 | 6 Mbps | 2 Mbps |
| H.265/HEVC | 6 Mbps | 2 Mbps |
The AV1 and H.265 figures share a row in YouTube’s guidance. The H.264 recommendation is different, so do not copy 6 Mbps into an H.264 encoder on the assumption that every codec uses one 720p60 rate. The minimum is a lower bound in the table, not the setting to aim for when the connection can reliably sustain the recommendation.
“Video bitrate” also means the video stream, not the combined total of video and audio. Your encoder may show separate controls for video and audio, or show an overall output figure. Check which value you are changing before applying a number from YouTube’s table.
The practical choice is the recommended rate for the codec you can sustain consistently. If your H.264 encoder is in use, begin at 8 Mbps and test the complete output. If you send AV1 or H.265, use 6 Mbps as the recommended reference. If that rate is not stable on your connection, investigate the cause and test a sustainable setting rather than treating an unstable recommendation as more important than a continuous broadcast.
YouTube’s live encoder settings and bitrate table is the primary reference for these values. Check the current page before going live if your encoder, codec, or output resolution changes; do not substitute the separate recommendations for uploading a video file, which are for a different workflow.
Minimums are not recommended targets
The minimums in the table are 3 Mbps for H.264 and 2 Mbps for AV1 or H.265 at 720p60. They help distinguish what YouTube lists as a floor from the recommended input rate. A minimum should not be read as a guarantee of acceptable motion, uninterrupted ingest, or a particular viewer experience.
A lower video rate can be useful when a connection cannot hold the recommended setting. But reducing bitrate also reduces the information available to represent each frame. In a devotional channel with a mostly still image, that may be less visible than in a dance performance, a moving camera, or a news loop with scrolling text. That difference in content does not alter the official table; it helps you judge the trade-off when testing your own material.
If you do test below the recommendation, change one setting at a time and watch the encoder and YouTube’s stream health messages. A brief connection test is not the same as a full night of broadcasting. In particular, check at the time and place your channel will operate: a home connection shared with other users may behave differently during a busy evening than it did during a quiet setup session.
Do not try to compensate for a bitrate your connection cannot maintain by assuming that viewers will see the same result as you do in the encoder preview. The preview can be fed from the local output, while YouTube is receiving and processing a separate stream. For a broader look at connection problems in a continuous broadcast, see the practical guidance on preventing buffering in a 24/7 worship stream.
Why H.264 and AV1/H.265 rates differ
A bitrate is the amount of video data the encoder sends each second. How much detail that data can represent depends partly on the codec: different codecs use different methods to compress video. YouTube therefore gives distinct bitrate recommendations rather than one rate that applies identically to every supported codec.
At this resolution and frame rate, the listed H.264 recommendation is higher than the recommendation for AV1 or H.265. That is not a reason to multiply or convert one row into another yourself. Use the row matching the codec selected for the outgoing stream. The rates are YouTube’s ingest guidance, not a general claim that one codec always looks better than another at every setting.
Encoder software can make this confusing. It may offer H.264, HEVC, or AV1, or it may show only options available for your computer or hardware. Some tools display the codec in an output or streaming panel, while others place it under advanced video settings. Confirm the actual output codec, not just a codec supported by your graphics card or listed as an import format. A source file encoded in one format can be decoded and sent using another.
If the encoder offers only H.264, use the H.264 row. There is no need to buy a new computer or encoder solely to use a lower bitrate row; YouTube describes software and hardware encoders as possible ways to send a stream. If the codec can be changed without making the workflow unreliable, test each configuration with the same representative content and connection. Keep the configuration that is stable and suitable for your channel, rather than choosing on a bitrate number alone.
For a playlist-based broadcast, the encoded output is what matters. A playlist may contain source videos with different resolutions, frame rates, or compression, but the encoder still creates the live output it sends to YouTube. If you are deciding how to build a loop before encoding it, the OBS and VLC comparison for a playlist-based radio station may help you think through the playback side separately from this ingest setting.
Set the encoder to CBR
YouTube recommends constant bitrate (CBR) encoding. Set the encoder’s rate control to CBR, then enter the video bitrate from the appropriate codec row. A setting labelled “target bitrate” or “average bitrate” may instead describe a variable rate, so check the encoder’s own help if its labels are not clear.
CBR is intended to keep the video output near the configured rate rather than letting it vary widely with the scene. That makes the stream’s output more predictable for ingest. It does not make an unreliable internet connection reliable, and it does not remove the need to test. A CBR stream set above what your connection can sustain can still drop frames or lose connection.
Keep audio separate in your thinking. YouTube’s listed figures above are for video. If you change an encoder’s total output setting rather than its video setting, you could inadvertently leave less capacity for video than intended or misunderstand what is being transmitted. Confirm the video field and audio field independently, and review the encoder’s output summary if it provides one.
On a playlist channel, test the parts that are most demanding as well as the quiet sections. A static devotional image may use the available bitrate differently from a clip with camera movement, transitions, animated text, or a fast-changing background. That is a reason to test representative content, not a reason to invent a different official rate. YouTube’s streaming tips also advise choosing a quality that fits the available connection and testing before the event.
If you cannot maintain the recommended rate, first check whether another device or upload is using the connection, whether your encoder is producing the expected resolution and frame rate, and whether you have selected the intended codec. Then test a lower output setting only if needed. The aim is a stable input to YouTube, not the largest number your settings panel will accept.
Choose protocol and keyframe interval
YouTube lists RTMP/RTMPS as live ingest protocols and recommends a keyframe interval of 2 seconds, with intervals no longer than 4 seconds. Set the protocol using the ingest option provided by your streaming workflow, and set the keyframe interval in the encoder if it exposes that control.
A keyframe is a reference frame from which later frames can be reconstructed. The interval determines how often one is sent. YouTube’s recommended two-second interval gives you a direct setting to use; if your encoder expresses the interval in frames rather than seconds, make sure the value corresponds to two seconds at the output frame rate. At 60 fps, that conversion is 120 frames. This is a calculation from the interval and frame rate, not a separate bitrate recommendation.
Do not confuse the ingest protocol with the word “playlist” in the title. The Google for Developers documentation on HLS live ingestion uses “Media Playlist” for a technical manifest in an HLS workflow. It describes particular media and segment requirements; that is not the same thing as a viewer-facing playlist of YouTube videos. The available official guidance does not establish a special 720p60 bitrate adjustment for looping a collection of videos.
For most readers asking about a playlist stream, the practical question is which software or workflow plays the files and sends the encoded output to YouTube. Do not switch to HLS or change your bitrate just because the word “playlist” appears in a technical document. Use the protocol supported by your actual setup and follow the configuration guidance for it. If your goal is to run a scheduled sequence rather than one looping file, the article on scheduling different video playlists on a YouTube livestream addresses that operational distinction.
Check frame rate and stream output
Select 720p as the output resolution and 60 fps as the frame rate only if that is the output you intend to send. The source videos do not all need to have been recorded at 60 fps for the encoder to produce 60 fps, but converting lower-frame-rate material does not create new motion detail. A mostly static image may not benefit visibly from higher frame rate, while movement can make a frame-rate difference more apparent.
YouTube lists frame rates up to 60 fps for live streaming. Confirm the frame rate in the encoder’s stream output settings and, where possible, in its status or statistics panel after the stream starts. The source file’s properties alone do not tell you what the encoder is transmitting. Similarly, a 720p source can be resized or combined with overlays before transmission, so verify the final output dimensions rather than assuming they match the source file.
Before a long broadcast, run a private or otherwise suitable test with audio and motion similar to the planned stream. Look at YouTube’s stream health and any incoming warning messages, and check that audio remains in sync and the encoder is not reporting dropped frames. YouTube’s encoder setup guidance explains how to create a stream with an encoder and monitor its setup; the official setup page is worth checking against your current interface.
For a channel that runs overnight, testing should include the actual file transitions or loop behaviour. Confirm that the output does not go black, freeze, or pause at the point where one item ends and another begins. Leave the test running long enough to observe the parts of the workflow that might fail after launch, including the computer’s power settings and whether the connection remains available. A successful short preview is useful, but it cannot establish that every future session will run without interruption.
If your channel depends on a local computer staying on, account for power, heat, updates, and home internet interruptions as well as encoding settings. An always-on setup may use a small PC or another workflow, but the operating effort is part of the decision; see the cost of running a 24/7 stream with a used Lenovo Tiny PC for one practical angle. The bitrate table remains the same regardless of where the encoding task runs.
What YouTube does after ingest
The bitrate you set is the input rate your encoder sends to YouTube. YouTube says it transcodes live streams into multiple output formats for viewers. That means the setting does not determine that every viewer receives a 720p60 rendition at precisely the input bitrate; playback formats and conditions can differ.
This distinction matters when you troubleshoot. If a viewer says the stream looks soft, the cause may not be that their player is receiving the exact bitrate shown in your encoder. Check your outgoing resolution and frame rate, the selected codec and video rate, and YouTube’s stream health first. Then inspect the available playback quality separately. Do not try to solve a viewer’s network or device issue by changing your ingest rate without evidence that the input itself is the problem.
It also explains why uploaded-video bitrate advice is not a substitute for the live encoder table. An uploaded file is processed through a different route than an encoder’s real-time stream. For this question, use the live ingest settings and test the result in the live control room rather than borrowing numbers from a guide about preparing a video upload.
For an all-night devotional stream or local news loop, make the ingest decision once, then observe it under the conditions in which you actually broadcast. If the stream remains healthy but a particular viewer reports buffering, distinguish that viewer’s playback experience from the encoder-to-YouTube connection. If YouTube reports a problem, use its current guidance and the messages in the live control room to narrow down whether the issue is bitrate, connection, codec, or output configuration.
The aim is not to make your own bitrate equal every viewer’s playback rate. It is to send YouTube a stable, correctly configured input at the appropriate rate for your codec, then let YouTube’s live processing provide the available viewer outputs. Keep those two parts separate when documenting settings or asking for support.
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 720p and 60 fps?
Use 8 Mbps for H.264, or 6 Mbps for AV1 or H.265/HEVC, as the recommended video ingest rate listed by YouTube. The minimums are 3 Mbps for H.264 and 2 Mbps for AV1 or H.265. Confirm the codec your encoder actually sends before choosing a row.
Is 6 Mbps enough for every 720p60 stream?
No. YouTube lists 6 Mbps as the recommended rate for AV1 and H.265/HEVC, while its H.264 recommendation is 8 Mbps. The rates refer to video input to YouTube, not the bitrate each viewer necessarily receives.
Does a YouTube playlist need a different bitrate?
The official guidance cited here does not specify a different 720p60 bitrate for a viewer-facing playlist of videos. The encoder’s codec and output settings determine which bitrate row applies. “Media Playlist” in YouTube’s HLS documentation is a technical manifest and should not be confused with a collection of videos to loop.
What other encoder settings should I check?
Use CBR, RTMP or RTMPS as supported by your workflow, and a 2-second keyframe interval that does not exceed 4 seconds. Verify the outgoing resolution, frame rate, and codec, then test with representative content and monitor YouTube’s stream health before relying on the setup.