For a 720p60 YouTube Live stream, use a video bitrate of 8 Mbps with H.264, or 6 Mbps with AV1 or H.265/HEVC, as YouTube’s recommended starting points. The same general live-ingest table applies to a gameplay playlist stream: YouTube does not publish a separate bitrate table for playlists.
Those figures are for encoded video, not the complete amount of upload capacity your connection needs. Set the encoder to CBR and a 2-second keyframe interval, then test the stream on the actual connection and leave room for audio, any backup feed and network variation.
YouTube’s 720p60 bitrate recommendations
YouTube’s live encoder settings table gives the following figures for 720p at 60 frames per second. The minimum is a lower listed value, not the recommended target for a new setup.
| Ingest video codec | Listed minimum video bitrate | YouTube recommended video bitrate |
|---|---|---|
| H.264 | 3 Mbps | 8 Mbps |
| AV1 | 2 Mbps | 6 Mbps |
| H.265 / HEVC | 2 Mbps | 6 Mbps |
These are YouTube’s published live-encoder settings, accessed on 3 October 2026. Check the current YouTube encoder settings table before going live, in case its guidance has changed. The table is keyed to ingest resolution, frame rate and codec. If you choose 720p60 and H.264, the recommended video setting is 8 Mbps; changing to AV1 or H.265 changes the recommendation to 6 Mbps.
A listed minimum can be useful when diagnosing a constraint, but it should not be mistaken for the recommended operating target. At a minimum setting, fast gameplay movement or detailed scenes may be harder to represent cleanly. Start from the recommendation for the codec you actually send, then assess the picture and stream health rather than assuming the minimum is enough.
The recommendation concerns the stream sent to YouTube for live ingest. Do not substitute YouTube’s separate bitrate recommendations for uploading prerecorded videos: those refer to a different process. Nor does the presentation format change the row. A playlist of gameplay clips sent as one live broadcast still uses the general row matching its resolution, frame rate and codec. That is an interpretation of the published general table, not a special YouTube playlist rule.
H.264, AV1 and H.265 compared
Codec choice affects which bitrate row applies, as well as what your encoder and playback workflow can support. H.264’s 720p60 recommendation is 8 Mbps; YouTube lists 6 Mbps for AV1 and H.265/HEVC. That does not mean you should select a codec solely because its recommended number is lower. The encoder has to be able to produce it reliably, and the workflow must be compatible with the video you intend to send.
H.264 is a familiar choice and may be the straightforward option when your encoder or hardware does not offer AV1 or H.265. Its higher recommended video bitrate means you should plan more network capacity than for the other two choices at the same resolution and frame rate. If your tool presents a choice between software and hardware encoding, check what it can sustain during actual gameplay or while reading the playlist. A setting that overloads the encoder can cause trouble even when the internet connection is adequate.
AV1 and H.265/HEVC share the 6 Mbps recommendation for 720p60 in YouTube’s table. You still need to confirm that your encoder exposes the intended codec and that the stream reaches YouTube in that format. Do not infer from a label in an editing or capture programme that the ingest codec has changed; verify the live encoder output settings.
| If your priority is… | A reasonable starting point | What to check |
|---|---|---|
| Broad compatibility in your existing setup | H.264 at 8 Mbps video | Whether the encoder stays stable and the connection has headroom |
| Using AV1 or H.265/HEVC where your workflow supports it | 6 Mbps video | Whether the encoder and delivery path are actually configured for that codec |
| Understanding a lower limit during troubleshooting | YouTube’s listed codec-specific minimum | Whether the lower setting resolves the constraint without unacceptable picture quality |
These choices are not a quality ranking. The table gives YouTube’s recommended video bitrates, not a promise that every encoder, game or network will look or behave identically at those values. If you are deciding on an encoder layout as well as a bitrate, the OBS settings guide for 24/7 YouTube playlist streaming in India can help you think through the broader configuration.
Video bitrate is not upload capacity
The encoder’s video bitrate is only one part of what the network carries. Audio also uses bandwidth, and a primary stream plus a backup stream requires capacity for both. You need enough available upload bandwidth for the complete outgoing stream, not just a speed-test result that matches the video figure.
YouTube recommends leaving 20% upload bandwidth headroom. In practical terms, treat the stream’s total outgoing bitrate as the amount to fit beneath the available upload capacity, with extra room beyond it. For instance, an 8 Mbps video setting does not mean that an 8 Mbps upload service is sufficient: audio adds to the stream, and a backup feed adds another load if you use one. A connection can also vary or be shared with other devices and people.
Use a speed test that reports outbound upload, not only download. Run it under conditions close to the time you expect to broadcast: another person on a video call, cloud backups or other household traffic can reduce the capacity available to your encoder. A test at a quiet moment is useful, but it does not establish that the same capacity will always be available.
If the measured upload is tight, there are several trade-offs to consider. You can reduce the video bitrate, choose a codec whose recommendation is lower if your workflow supports it, avoid sending a backup feed, or improve the connection conditions. Lowering the bitrate can affect picture detail, and removing redundancy changes how you recover from a failure. Do not solve a capacity issue by raising the stream setting or by treating the video value as the whole network load.
A wired connection is an optional way to reduce reliance on a variable Wi-Fi link between the encoder and router. It does not increase the upload capacity supplied by your internet provider, and it is not a YouTube requirement. The useful test is whether your available outbound capacity remains sufficient while the stream and other normal network use are active.
Set CBR and a 2-second keyframe interval
For live ingest, YouTube lists constant bitrate (CBR) and recommends a 2-second keyframe frequency, with a maximum interval of 4 seconds. Use those values as the initial encoder configuration unless you have a specific reason and verified guidance to do otherwise. The YouTube live encoder settings also identify RTMP/RTMPS as supported protocols and list H.264, H.265/HEVC and AV1 as video codecs.
CBR aims to keep the outgoing bitrate steady around the target rather than letting it fluctuate widely with scene complexity. A constant rate makes it easier to budget the stream against upload capacity. It does not guarantee an unchanging picture: a busy game scene can still be more demanding to encode than a static menu, and the encoder may have to make different quality compromises to maintain the target.
Keyframes provide points from which playback can be decoded more independently. A 2-second interval is YouTube’s recommended setting. Longer intervals are not necessarily a useful way to save bandwidth; keep within YouTube’s stated maximum of 4 seconds and check your encoder’s keyframe setting rather than assuming its default matches.
The rest of the video configuration still matters. YouTube’s table supports frame rates up to 60 fps; choose 60 only if the material and encoder can sustain it. For SDR, YouTube lists Rec. 709 and 8-bit depth in its advanced settings. If you are sending a standard SDR gameplay playlist, avoid changing colour settings without a reason, and verify the resulting image in the live preview.
For a playlist assembled from prerecorded files, keep transitions and output format consistent. A change in the source clip’s frame rate or resolution does not itself justify changing the live ingest target mid-broadcast; check how your encoder scales and encodes each item. If the stream has black gaps or reconnect issues between files, that is a playlist-handling problem rather than evidence that the 720p60 bitrate table has changed. See the guide to fixing a black screen between videos in a 24/7 stream for that separate class of issue.
Leave upload bandwidth headroom
YouTube’s 20% headroom recommendation is a planning margin, not a new video bitrate. First account for the complete outgoing stream, including audio and any backup feed; then leave room above that total for variation and other network use. The YouTube streaming tips page advises using a reliable network and checking upload capacity. The connection’s actual available bandwidth matters more than the headline speed printed on a broadband plan.
A practical check is to observe the network while the stream is running at the intended settings. If upload use sits close to the available capacity, another device can push it over the limit. Pause non-essential uploads, avoid scheduling large cloud syncs during the broadcast, and arrange household use where possible. In India, this can matter when the connection is shared across a home or shop, or when performance changes at busy times. Test at the time and location you plan to stream, rather than assuming a daytime result represents an overnight run.
If you need a backup stream, budget for its traffic as well. A backup is useful only if the network can carry the extra load and the failover arrangement is configured correctly. If capacity is limited, a single well-tested feed may be more dependable than two feeds competing for the same upload connection.
Do not treat a single speed-test result as a guarantee. Repeat the test at relevant times, check for dropped frames and YouTube’s stream-health warnings, and note whether network activity elsewhere coincides with problems. If results vary, lower the load or improve the connection before relying on the stream unattended. A checklist for keeping a 24/7 church stream live when OBS crashes covers the related question of what happens when the local encoder stops; bitrate headroom cannot by itself address an encoder crash.
Test a gameplay playlist stream
The numbers above are starting points from YouTube’s general live-ingestion table. The official guidance reviewed does not give gameplay playlists their own bitrate values. Apply the row for the codec, resolution and frame rate you are sending, then test with representative content. This is particularly useful for a playlist because its clips may not all stress the encoder in the same way.
Build a short test around material that resembles the planned stream: fast camera movement, detailed scenes, menus, transitions and any overlays. Watch the YouTube preview and the local encoder’s status while these play. Check whether the image remains acceptable during movement, whether the encoder reports dropped frames, and whether YouTube reports connection or ingest problems. A still image or quiet menu alone is not a meaningful test of a fast gameplay sequence.
If the test is unstable, identify which part is constrained before changing several settings at once. Encoder overload points to the computer or encoding choice; network warnings or dropped frames can point to insufficient or inconsistent upload; a poor-looking image without transmission problems may call for a different bitrate or codec. Change one relevant setting, repeat the same test segment, and record what improved or worsened. That gives you a useful comparison rather than a guess based on how the stream looked once.
For a playlist, also let the test cross a clip boundary. Confirm that the next file starts, audio behaves as expected, and overlays or captions do not disappear. If you use a local encoder, keep in mind that it depends on the computer and its network staying available for the broadcast. If the specific pain is keeping a prerecorded file on air without leaving a computer running, StreamNeo removes that local-computer requirement by taking an uploaded video and running it as a YouTube live stream; it does not change YouTube’s bitrate recommendations or replace checking the stream’s output.
For more on choosing and scheduling playlist material, see how to schedule YouTube playlist rotation with cron in IST on Debian. The scheduling mechanism and the bitrate are separate concerns: a correct rotation does not ensure a healthy ingest, while a good ingest setting does not ensure the playlist advances correctly.
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 720p60 YouTube Live?
For video, YouTube recommends 8 Mbps with H.264 and 6 Mbps with AV1 or H.265/HEVC. Its listed minimums are 3 Mbps for H.264 and 2 Mbps for AV1 or H.265, but those are not the recommended targets. Allow additional upload capacity for audio, any backup stream and headroom.
Is 6 Mbps enough for a 720p60 stream?
It is YouTube’s recommended video bitrate for 720p60 when the ingest codec is AV1 or H.265/HEVC. It is not the recommended H.264 video bitrate, which is 8 Mbps, and 6 Mbps does not include audio or a backup feed. Check total upload capacity and test with representative gameplay.
Does a gameplay playlist need a different bitrate table?
YouTube’s published guidance reviewed here does not set a separate bitrate table for playlist streams. Use the general live-ingest recommendation matching your codec, resolution and frame rate. Treat that application to a playlist as an inference from the general table, then verify the stream in a test.
What should I change first if the stream drops frames?
Check whether the encoder reports dropped frames or whether YouTube reports a connection issue, since those point to different constraints. Confirm the outgoing bitrate, upload headroom and other network use before lowering picture quality. Change one setting at a time and repeat the same test so you can identify the effect.