For a 1080p YouTube Live loop, use the bitrate recommendation that matches the video’s actual frame rate and the codec your encoder sends. YouTube’s guidance does not set a separate bitrate for looping; the stream uses the same encoder settings as any other live video at that resolution and frame rate.
At 1080p30, YouTube recommends 10 Mbps for AV1 or H.265 and 14 Mbps for H.264. At 1080p60, it recommends 12 Mbps for AV1 or H.265 and 17 Mbps for H.264. These are recommendations, not minimum connection speeds or guarantees that an encoder or internet connection will remain stable.
Choose the resolution and frame rate you are actually sending
“1080p” describes the image dimensions, not how many frames are sent each second. A source may be 1080p30 or 1080p60, and YouTube’s bitrate table gives different recommendations for those two cases. Identify the output your encoder will send rather than choosing a row based on the source file’s label alone.
For example, if a 1080p file contains 30 frames per second and your encoder outputs 30 fps, use the 1080p30 row. Selecting the 60 fps row simply because it sounds like a higher-quality option does not turn a 30 fps source into true 60 fps motion. It can also add encoding work without giving viewers additional source detail.
Check both the video file and the encoder’s output settings. Some software detects resolution and frame rate automatically; other workflows let you set them explicitly. YouTube says automatic detection is the default, and its encoder settings guidance explains the stream-key options for manually selecting settings. If you are unsure what your playback software is sending, look at its output or streaming settings and confirm the values in YouTube Live Control Room before starting.
A loop changes the programme sequence, not the meaning of the video settings. If you rotate several clips, transitions, or a still image between videos, make a representative test that includes those changes. A mostly static devotional image can have less motion than a news or gaming loop, but the table’s recommended values are still keyed to codec and frame rate, not to whether the programme repeats.
Identify the ingestion codec
The codec is the format in which your encoder sends video to YouTube. It is not necessarily the codec used inside the file you uploaded or opened. An encoder may decode a source file and then send a different format, so choose a bitrate row using the codec in the outgoing stream settings.
YouTube’s table distinguishes H.264 from AV1 and H.265/HEVC. For the same resolution and frame rate, its recommended bitrate is lower for AV1 or H.265 than for H.264. That difference is a stated encoder recommendation; it does not mean that every computer can encode each format equally well or that changing codecs alone will solve a weak connection.
If your software only offers H.264, use the H.264 column. If it offers AV1 or H.265 and you intend to send one of those, confirm that the encoder actually supports and is configured for it. Avoid choosing a codec by guesswork. For a practical overview of the gear in a recording setup, see what you need to record YouTube videos; for a continuously repeated programme, adding multiple videos to a continuous stream covers the playlist side rather than changing the bitrate rule.
1080p at 30 fps: use the matching recommendation
For 1080p30, YouTube’s current live-encoder table recommends 10 Mbps for AV1 or H.265/HEVC and 14 Mbps for H.264. In encoder fields labelled in kilobits per second, those values are 10,000 kbps and 14,000 kbps respectively. Match the figure to the codec you are sending, not to the codec someone else’s setup happens to use.
| 1080p30 ingestion codec | YouTube listed minimum | YouTube recommended |
|---|---|---|
| AV1 or H.265/HEVC | 4 Mbps | 10 Mbps |
| H.264 | 5 Mbps | 14 Mbps |
The table’s minimum column and recommended column have different jobs. A listed minimum is not the target to choose when you are trying to follow YouTube’s recommendation. Conversely, the recommended number is not a claim that every connection at that nominal upload speed will carry the stream reliably. Network variation, other devices using the connection, and the encoder’s behaviour still matter.
Suppose your encoder sends H.264 at 1080p30. The relevant recommendation is 14 Mbps, or 14,000 kbps. If the encoder sends AV1 at the same frame rate, use the AV1/H.265 recommendation of 10 Mbps. These are video ingestion bitrates; do not add audio bitrate to the video field or reduce the video setting to compensate for a separate audio configuration.
1080p at 60 fps: do not reuse the 30 fps figure
For 1080p60, YouTube recommends 12 Mbps for AV1 or H.265/HEVC and 17 Mbps for H.264. In kilobits per second, that is 12,000 kbps or 17,000 kbps. A 60 fps stream sends more frames each second than a 30 fps stream, so use the 60 fps row only when that is the frame rate your encoder is actually sending.
| 1080p60 ingestion codec | YouTube listed minimum | YouTube recommended |
|---|---|---|
| AV1 or H.265/HEVC | 4 Mbps | 12 Mbps |
| H.264 | 6 Mbps | 17 Mbps |
A common question is whether 6,000 kbps is enough for 1080p60. It is above the listed H.264 minimum, but it is below YouTube’s 17 Mbps H.264 recommendation. For AV1 or H.265, it is also below the listed 12 Mbps recommendation. That comparison does not by itself tell you whether a particular broadcast will look acceptable or remain stable; it simply distinguishes the values in YouTube’s table.
If your source is 1080p30, do not select 1080p60 to try to improve it. If the source is 60 fps and smooth movement matters, then use the appropriate 60 fps recommendation and test whether your encoder and connection can handle it. The guide to running retro gaming footage on repeat is a useful example of a loop where movement may make the frame-rate choice especially visible.
Minimums, recommendations and what they do not promise
YouTube lists a minimum and a recommended video bitrate for each of these combinations. They are not interchangeable labels. The minimum is the lower figure in the official table; the recommendation is the setting YouTube advises for that resolution, frame rate and codec. Use the recommended figure as the starting point when your encoder and connection can sustain it.
| Format and codec | Listed minimum | Recommended |
|---|---|---|
| 1080p30, AV1 or H.265 | 4 Mbps | 10 Mbps |
| 1080p30, H.264 | 5 Mbps | 14 Mbps |
| 1080p60, AV1 or H.265 | 4 Mbps | 12 Mbps |
| 1080p60, H.264 | 6 Mbps | 17 Mbps |
These figures are YouTube’s published encoder settings, not an approval threshold, a visual-quality guarantee, or a promise of uninterrupted delivery. Meeting a listed minimum does not establish that a stream will be stable. A connection can fluctuate, become congested, or be shared with other activity; an encoder can also struggle to keep pace. YouTube’s live streaming troubleshooting guidance advises checking stream health and connection conditions rather than treating one bitrate number as a cure for every issue.
For a long-running channel, an occasional successful test is useful but does not remove the need to monitor the live stream. A short test can show whether audio, motion, and encoding settings work together under the conditions at that moment. It cannot guarantee that the same conditions will hold overnight or when the household or workplace network is busier.
Set constant bitrate and the other encoder basics
Set video bitrate mode to constant bitrate, usually labelled CBR, and enter the recommendation that matches the outgoing codec and frame rate. YouTube also recommends a two-second keyframe interval and says not to exceed four seconds. These settings are separate from the loop itself: replaying a file does not call for a special loop bitrate or a different keyframe rule.
In YouTube Studio, open Go Live in Live Control Room and create or select the stream. Copy the stream URL and stream key into the encoder. YouTube documents both software and standalone hardware encoder workflows in its streaming help. Keep the key private, since it is what lets an encoder send video to the selected stream.
For SDR video, YouTube lists Rec. 709 and 8-bit among its settings. Its other advanced recommendations include square pixels, progressive scan, two B-frames, one reference frame, and CABAC. Do not change every advanced setting without a reason, particularly if the encoder’s default profile has been working. The bitrate choice is the main decision for this article; the rest of the settings should be checked for sensible compatibility with your source and encoder.
Audio has its own settings. YouTube lists AAC or MP3, and for stereo it lists 44.1 kHz and 128 kbps. Match audio to the production and make sure that speech, music, or ambience sounds right in a test. Raising or lowering video bitrate is not a substitute for correcting an audio setting.
If your channel depends on keeping a loop on air while your personal computer is off, StreamNeo removes the need to leave your own computer encoding the repeated file, while leaving the codec, frame-rate and bitrate choice yours to make. The stream still needs the correct YouTube settings and sensible monitoring; no setup turns the listed recommendation into a guarantee.
Check whether the connection can sustain the target
The bitrate field controls the amount of video data the encoder tries to send. Your available upload capacity must have room for that data, plus audio and the variability that comes with a real connection. A speed-test result is a useful check of present upload capacity, but it is not proof that the same speed will be consistently available to the encoder during a long broadcast.
YouTube advises choosing a reliable quality for the connection available and recommends an upload-speed test. Do a test on the connection and at the location you plan to stream from. If other people or devices share the line, test under representative conditions rather than only when nothing else is using it. For a channel that must run from a local setup, compare the network requirement with the practicalities of the device as well; using a mini PC for a continuous stream in India addresses that broader operating choice.
Before a real broadcast, send a private or unlisted test if that suits your workflow, then watch the preview and the stream-health messages in Live Control Room. Include audio and motion similar to the actual programme, as YouTube recommends. A still image alone may not reveal how a moving section behaves, and an audio-only check will not show dropped or uneven video.
If the stream reports issues, work through the causes rather than immediately lowering every setting. Check whether the encoder is overloaded, whether another upload is using bandwidth, whether the connection is fluctuating, and whether the output codec and frame rate match the settings you intended. If you need to lower the target because the connection cannot sustain it reliably, treat that as a compromise and test the resulting picture and health again. A nominally higher target is not useful if it produces an unstable broadcast.
For a 24/7 channel, the test should reflect the hours and content you expect to run. A sequence containing fades, slides, music, speech, and motion gives a more representative result than a single frame. Once live, check the health indicators periodically, especially after changing the source, encoder, network, or output settings. No short test can promise continuous uptime.
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 a 1080p YouTube Live stream?
Choose by the codec and actual frame rate being sent. YouTube recommends 10 Mbps for 1080p30 AV1 or H.265, 14 Mbps for 1080p30 H.264, 12 Mbps for 1080p60 AV1 or H.265, and 17 Mbps for 1080p60 H.264. These are recommendations, not guarantees of a stable stream.
Is 6,000 kbps enough for 1080p60?
It is above YouTube’s listed 1080p60 minimums, but below its recommendations for both codec groups. The outcome depends on the encoder, connection, source and conditions during the stream, so test the actual setup and monitor stream health rather than relying on the comparison alone.
Does a looping stream need a different bitrate?
No separate loop bitrate appears in YouTube’s encoder guidance. Use the normal recommendation for the stream’s resolution, frame rate and ingestion codec, then test representative portions of the loop.
Should I choose the minimum to avoid connection problems?
The minimum is not a connection-stability guarantee. Start from the recommendation if the connection can sustain it; if it cannot, test a lower setting as a trade-off and check both picture quality and stream health. YouTube’s current help page is the authority for its listed values and may change, so check it again before configuring a new stream.