For a 720p60 YouTube Live stream, set the video bitrate to 8 Mbps with H.264 or 6 Mbps with AV1 or H.265. These are YouTube’s recommended live ingest targets; the corresponding minimums are lower, but they are not the targets to aim for when your connection can sustain the recommendation.
A playlist of gaming highlights does not change the encoder bitrate table. It does change what you should test: scenes with fast movement, game audio, transitions between clips, and any live commentary should all be represented in a sustained test. Your actual outbound upload capacity and its stability determine whether a target is usable.
Set the output to 1280×720 at 60 fps
Choose 1280×720 progressive output and 60 frames per second in the encoder. YouTube’s live bitrate table calls this mode 720p at 60 fps; 1280×720 is the conventional pixel size for that resolution. Progressive output avoids configuring an interlaced mode where the encoder offers one.
The 60 fps setting is useful when your highlights include quick camera turns, movement, or other action that benefits from smoother motion. It also means the encoder has more frames to handle than a 30 fps output. Do not borrow a 720p30 rate simply because the resolution is the same: the requested frame rate is part of the mode, and YouTube publishes a distinct recommendation for 720p60.
Make sure the game capture and the encoder output agree where possible. If the game capture is 60 fps but the encoder is set to 30 fps, the live output will not preserve 60 frames each second. Conversely, changing the output setting to 60 does not create detail absent from a lower-frame-rate source. Start with the actual source and the mode you intend to broadcast, then test it.
If you are still deciding how much resolution your channel needs, the trade-offs in choosing a YouTube livestream resolution are a useful companion. For this configuration, keep the scope narrow: 720p60 output, codec selection, bitrate and a real connection test.
Choose a codec your encoder can sustain
The bitrate recommendation depends on the codec used for ingest. For the same 720p60 mode, YouTube lists one target for H.264 and another for AV1/H.265. The encoder, operating system, graphics hardware and chosen workflow affect which codecs are available, so select from what your actual setup supports rather than assuming that a newer codec is automatically usable.
| 720p60 ingest codec | YouTube recommended video bitrate | YouTube minimum video bitrate |
|---|---|---|
| H.264 | 8 Mbps | 3 Mbps |
| AV1 or H.265 | 6 Mbps | 2 Mbps |
The figures are video bitrate, not the total upload rate for everything your stream sends. Audio and any separate primary or backup stream also consume upload capacity. YouTube’s live encoder settings guidance provides the codec-specific table and general encoder requirements.
H.264 is a practical choice when it is the codec your encoder reliably supports. AV1 or H.265 may be available in a newer encoder or hardware workflow, but a lower recommended bitrate does not by itself prove that your computer can encode it smoothly or that your connection is stable. Check encoder load and stream health during testing. If your machine struggles, use a supported codec and profile that it can maintain rather than forcing a setting it cannot handle.
The audience’s playback conditions are another part of the picture. YouTube processes incoming live streams for viewing on different devices and networks, but that does not remove the need for a clean ingest from your encoder. Treat the table as a way to configure the source sent to YouTube, not a promise that every viewer receives identical quality.
Use the recommended bitrate as the target
For H.264 at 720p60, set 8 Mbps as the target video bitrate. For AV1 or H.265 at the same mode, set 6 Mbps. These are YouTube’s recommended live ingest rates, not interchangeable numbers and not rates for 720p30. If your encoder exposes a video bitrate field and separate audio controls, apply the matching figure to video and account for audio separately when planning the connection.
Do not lower the target just because a highlights playlist contains prerecorded clips. When those clips are being sent as a live stream, the encoder still has to deliver a live ingest at the configured resolution and frame rate. Likewise, do not use the rate YouTube recommends for an uploaded video as if it were a live ingest rate. The upload and live-streaming paths are different workflows; the research notes, for example, distinguish 720p high-frame-rate H.264 upload guidance from the live 720p60 ingest recommendation.
A rate setting is not a substitute for capacity. YouTube advises leaving upload headroom rather than using the entire measured outbound capacity for the stream. Its bandwidth guidance recommends 20% room and says to check upload rather than download speed. Apply that advice to the bitrate you plan to send, including audio and a backup stream if you use one.
For example, if you choose the H.264 target, assess whether the connection can carry that video rate plus the rest of the stream while retaining the recommended headroom. If it cannot, the target may not be usable on that connection at that time. Try a more stable connection, an available supported codec with its own matching target, or a different output plan, then test again. Do not assume a short speed test settles the matter.
Keep minimums separate from recommendations
A minimum is not the rate to recommend for ordinary operation merely because it is permitted by the table. YouTube lists 3 Mbps as the H.264 minimum for 720p60 and 2 Mbps as the AV1/H.265 minimum. The recommendations remain 8 Mbps and 6 Mbps respectively. Use the recommendation when your connection can sustain it; regard the minimum as a lower bound in the published guidance, not proof that a stream at that rate will look or behave well for your material.
This distinction matters for gaming highlights. A quiet menu screen may send less visible movement than a fast action sequence, but a brief low-motion sample does not tell you whether your full playlist will remain clean. If you set a lower rate, test representative gameplay rather than judging from a static scene. Watch for stream-health warnings and visual degradation while the encoder is actually sending the programme.
A lower video rate can be a sensible compromise when you cannot sustain a recommended target, but it comes with less room for the video. It is not a way to claim the recommended 720p60 configuration at a different rate. Be explicit about the trade-off in your own setup notes, and revisit it after testing under the conditions in which you intend to go live.
Configure CBR and the keyframe interval
Set the encoder to constant bitrate (CBR), then set a keyframe interval of two seconds. YouTube’s general encoder guidance recommends CBR and a two-second keyframe interval, with four seconds as the maximum. These controls do not increase your upload capacity; they make the encoder output conform to the guidance for the live ingest.
Encoder interfaces label these fields differently. Look for rate control or bitrate mode for CBR, and keyframe interval, keyframe distance or GOP length for the keyframe setting. If the software asks for frames rather than seconds, use its documentation to translate the interval for the selected frame rate instead of guessing. The intended result is a keyframe every two seconds, not an interval longer than YouTube’s stated maximum.
Avoid changing several settings at once during troubleshooting. If the stream is unstable, first establish whether the connection has enough sustained outbound capacity and whether the encoder is keeping up. Then make one controlled adjustment and test the same content again. A good setting on a test clip is only useful if the machine and connection can repeat it through the longer playlist session.
Use RTMPS where your encoder supports it
Choose RTMPS as the stream transport where it is available in your encoder. YouTube recommends RTMPS for secure transport. Check the encoder’s own connection options and YouTube’s current encoder setup guidance for the supported details relevant to your workflow.
Transport and bitrate solve different problems. Selecting RTMPS does not compensate for inadequate upload capacity, an overloaded encoder, or an incorrectly configured stream key. Equally, a stable connection does not make the bitrate table irrelevant. Configure the transport, codec, output mode and bitrate as separate parts of the setup, and verify that the encoder reports a healthy connection when you test.
Treat your stream key as a credential. Paste it into the encoder or approved workflow you are using, avoid displaying it in a screen recording or public support post, and follow YouTube’s current account and stream setup steps. If you are running a playlist continuously and do not want to keep a personal computer switched on, StreamNeo addresses that specific operational burden by taking an uploaded video and running it as a YouTube live stream after you supply the stream key; it does not change the codec or bitrate choices described here.
Test the playlist and leave headroom
Before broadcasting to viewers, run a sustained test using the same encoder, network, output settings and type of content you will use live. Include fast gameplay, quieter sections, clip changes, audio and commentary if applicable. A speed test is a useful check of outbound capacity, but it is not a sustained test of the complete live path. Watch the encoder and YouTube stream-health indicators while the test is running.
If the stream drops frames or reports a connection problem, do not conclude that the published bitrate is wrong. Check whether outbound upload is fluctuating, whether other devices or applications are using the connection, and whether the computer can encode the selected codec at the chosen output. If you send both a primary and a backup stream, include both in the bandwidth calculation. YouTube’s headroom recommendation applies to the total you send, not just the video field on the encoder screen.
For a playlist, also test the transitions. A gap, frozen frame or unexpected pause between videos is a programme issue as well as a bitrate issue; bitrate changes alone may not fix it. If your looping setup has trouble at clip boundaries, see how to prevent a frozen frame between videos. If you are arranging a fixed sequence to repeat, planning a YouTube playlist stream in a fixed order covers the scheduling side rather than the encoder settings.
A highlights workflow can begin while you are live. Use stream markers to note good moments, then create and trim highlights in YouTube Studio and add the finished videos to a playlist. A solo streamer can mark a moment while playing and edit later; a team can divide those jobs. The bitrate settings make the live source; they do not automatically create, trim or organise highlight videos.
Plan for an archive as well as the playlist. YouTube’s live archive guidance says streams under 12 hours can be automatically archived, while a stream longer than 12 hours may not be captured. Keep a local recording as a backup if the session matters to you, and check YouTube’s current guidance before relying on automatic archiving. The archive is not a substitute for the separately edited highlights you want to organise in a playlist.
When your output, connection and highlight workflow are ready, decide whether you want to operate the broadcast locally or hand off the always-on running task.
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 720p 60fps on YouTube Live?
Use 8 Mbps for H.264 or 6 Mbps for AV1/H.265 as the recommended video ingest target. The correct choice depends on your supported codec and whether your outbound connection can sustain the rate with headroom. Test the actual stream before relying on it.
Is 6 Mbps enough for 720p60 streaming?
It is YouTube’s recommended video bitrate for 720p60 when ingesting AV1 or H.265. It is not the H.264 recommendation, which is 8 Mbps, and it does not guarantee a stable connection. Account for audio and other streams, then test the complete setup.
Do I need 8 Mbps for 720p60 gaming?
YouTube recommends 8 Mbps for H.264 at 720p60; for AV1 or H.265, it recommends 6 Mbps. Use the target for the codec you have selected, if your connection can sustain it. The H.264 minimum is 3 Mbps, but a minimum should not be mistaken for the recommended target.
How do I save gaming highlights from a YouTube livestream?
Mark useful moments during the stream, then use YouTube Studio to create and trim highlights, add titles and details, and place the videos in a playlist. Keep a local recording if you need a dependable backup, and check YouTube’s current archive guidance for long streams. A live bitrate setting alone does not save or organise highlights.