For a 1080p60 gaming loop, YouTube recommends a video bitrate of 12 Mbps when you send AV1 or H.265, and 17 Mbps with H.264. Those are the relevant published 60fps settings; YouTube does not add a separate bitrate multiplier for fast-motion gameplay.
Treat the recommendation as an encoder target, not a promise about what your connection or computer can hold steadily. Choose the row for your actual codec, resolution and frame rate, then check upload capacity and test a representative section of gameplay before starting a long broadcast.
YouTube’s published 60fps recommendations
YouTube’s live encoder settings table distinguishes incoming streams by resolution, frame rate and codec. For 60fps video, the recommended bitrates are:
| Incoming video | AV1 or H.265 (HEVC) | H.264 |
|---|---|---|
| 720p60 | 6 Mbps | 8 Mbps |
| 1080p60 | 12 Mbps | 17 Mbps |
| 1440p60 | 24 Mbps | 34 Mbps |
| 2160p60 | 35 Mbps | 50 Mbps |
These are recommended video bitrates, not total network use. The table also gives minimum settings, but a minimum is not the same as the recommended target. For example, at 1080p60 the minimum is 4 Mbps for AV1 or H.265 and 6 Mbps for H.264. At 1440p60 those minimums are 6 and 8 Mbps; at 2160p60 they are 10 and 14 Mbps. If your system cannot sustain a recommended target, lowering the output resolution or frame rate is a clearer adjustment than treating the minimum as a guarantee of acceptable gameplay quality.
The frame-rate row matters. For context, YouTube’s 1080p30 recommendation is 10 Mbps for AV1/H.265 or 14 Mbps for H.264; the 2160p30 figures are 30 and 42 Mbps. A 30fps loop should not be assigned a 60fps row merely because the game is capable of running at 60fps. Set the encoder output to the frame rate you mean to deliver, and use the corresponding recommendation.
The figures are YouTube’s published guidance, not a universal quality threshold for every title, scene or viewer. A relatively static game menu and a rapid camera pan can look different at the same setting, but YouTube’s table does not supply a special row for either. Start with the applicable published recommendation, then assess the encoded result under representative motion rather than assuming the number alone settles quality.
See YouTube’s live encoder settings and bitrate table for the current official rows. Check it again when configuring a broadcast, since platform guidance may change after this article is written.
Codec choices at 1080p60
At 1080p60, the choice between codecs changes the recommended video rate in YouTube’s table: 12 Mbps for AV1 or H.265, compared with 17 Mbps for H.264. That difference is a reason to check which codecs your encoder and streaming workflow actually support. It is not a reason to select a codec that your hardware cannot encode reliably or that your settings do not offer.
If you have a choice, compare the whole path rather than the table in isolation. Your encoder must produce the chosen codec at the intended resolution and frame rate, and the connection must carry the resulting stream consistently. If your setup only offers H.264, use its row as the reference. If it offers AV1 or H.265, confirm that the selected mode is supported and behaves properly in a test broadcast. Do not assume every computer, capture workflow or software preset exposes every format.
YouTube’s encoder guidance lists H.264, H.265/HEVC and AV1 as supported video codecs, and recommends constant bitrate encoding. It also specifies a two-second keyframe interval, with four seconds as the maximum. These settings describe how the stream is encoded and delivered to YouTube; they do not mean the incoming stream is the format every viewer will watch. YouTube transcodes incoming live video into output formats for viewers, so encoder input and playback format are distinct parts of the process.
For a practical setup, choose your codec first based on what the encoder supports, then use the corresponding row for the target resolution and frame rate. Set CBR, and use the recommended two-second keyframe interval unless your encoder presents a specific reason you need to change it. Avoid changing several variables at once during troubleshooting: if the picture breaks up, it is easier to identify whether codec, bitrate or network stability was responsible when you alter one setting and retest.
A gaming loop may be assembled from captured or rendered video rather than played live by a person. That does not change YouTube’s published table for the incoming live stream. If your channel is built from a playlist or repeated recording, the same encoding decision applies to the output you send. The workflow question is separate from the bitrate question; turning a YouTube gaming playlist into a live rerun channel concerns how a loop is organised, while the codec row determines the video target sent to YouTube.
When you move to a higher resolution
A higher resolution has a higher published recommendation at the same frame rate, and the difference between codecs remains. At 1440p60, YouTube lists 24 Mbps for AV1/H.265 and 34 Mbps for H.264. At 2160p60, it lists 35 Mbps and 50 Mbps respectively. These are substantial video targets to plan around, so do not move to a higher output resolution simply because the source game is rendered at that resolution.
Your delivered resolution depends on the encoded output, not only on the game’s internal rendering setting. A 4K game capture can still be scaled to 1080p60 before it reaches YouTube. Conversely, a 2160p60 output asks the encoder and upload connection to handle the row for that format. Decide what resolution is useful to your audience and feasible for your setup, then configure the actual outgoing stream accordingly.
| Target output | AV1/H.265 recommendation | H.264 recommendation | Practical question |
|---|---|---|---|
| 1080p60 | 12 Mbps | 17 Mbps | Can your encoder hold the chosen codec and the upload sustain the video rate with headroom? |
| 1440p60 | 24 Mbps | 34 Mbps | Is the extra resolution useful enough to justify a larger upload target? |
| 2160p60 | 35 Mbps | 50 Mbps | Can the entire encoding and network path remain stable for a long broadcast? |
The table is useful for comparing targets, not for proving a computer or connection can sustain them. An encoder may struggle with the chosen resolution, frame rate or codec even when the network has capacity. The network may also be shared with other devices, so a speed result taken at a quiet moment does not settle what happens overnight or during household use.
If you are deciding between 1080p60 and 4K60 for a continuous channel, weigh the additional detail against the higher encoding load and upload rate. The practical considerations for a long-running 4K broadcast are covered in keeping a 4K 60fps YouTube live stream running 24/7. For bitrate, use YouTube’s published 60fps row for the output you select rather than extrapolating a new number from another resolution.
Why fast motion has no separate row
It is reasonable to ask whether a racing game, shooter or rapidly scrolling game needs a special bitrate beyond the 60fps recommendation. Fast motion can make compression artefacts more noticeable because image detail changes from frame to frame. However, YouTube’s cited live settings table does not publish a “gaming” or “fast motion” uplift. Its rows are organised by codec, resolution and frame rate, so there is no official multiplier to apply to the figures above.
That distinction matters because adding an unsupported uplift can create a false sense of precision. A claim such as “add a fixed percentage for gaming” would not come from the table. Nor does the fact that a game is fast-moving guarantee that a higher rate will be sustainable or that it will fix every visible problem. Use the relevant official row as your baseline, make a representative test, and adjust resolution or other supported encoder settings if the picture or stream health requires it.
The test should contain the type of movement that is likely to expose the weakness: quick pans, scrolling, busy scenes, particle effects or sharp changes between dark and bright areas. A title screen may look clean while the actual gameplay turns into a blur or blocky image. Conversely, if the picture is already acceptable and the health indicators remain stable, there is no official gaming-specific number that requires you to raise the target simply because the content is gameplay.
If you see poor image quality, check what kind of problem you have before changing bitrate. Compression softness and blockiness during movement may point towards the quality of the encoded picture, while dropped frames or an unstable health state can indicate that the encoder or connection is not keeping up. Raising the target during a connection problem can make the network demand harder, not easier. Test one adjustment at a time and keep notes of the output settings and what you observed.
Match the target to upload capacity
The bitrate setting is for video; it is not the total bandwidth consumed by the stream. Audio and network overhead also use capacity, and other devices may share the same upload connection. YouTube’s streaming tips say the total stream bitrate should not exceed available upload bandwidth and recommend leaving 20% headroom. In practical terms, do not choose a video setting that consumes nearly all the measured upload capacity and assume the connection will remain stable.
Measure outbound upload capacity, not download speed. A plan advertised for fast downloads does not by itself tell you how much data can be sent upstream. Run a measurement from the same connection and, where possible, under conditions resembling the time the channel will run. If the connection is shared with video calls, backups, cameras or other streams, their traffic can reduce the capacity available to your broadcast. YouTube’s streaming tips discuss bandwidth and the value of leaving headroom.
For a simple planning check, begin with the video target from the table, remember that the total stream is larger than video alone, and leave the recommended reserve rather than assigning the full measured upload rate to video. If the target does not fit, step down resolution or frame rate and look up that row, or select a supported codec with a lower recommendation. Do not claim a target is safe because a speed test briefly reached a matching number; measured capacity can vary with network use and disruption.
A wired Ethernet connection can be worth trying when you are diagnosing local wireless instability, especially if the computer is far from the access point or shares a busy wireless network. It is an optional troubleshooting step, not a bitrate upgrade and not a way to increase the upload capacity provided by your internet connection. If a wired test improves consistency, that tells you something about the local path. If it does not, look at the available upload service, shared traffic and encoder load instead.
For a channel intended to run continuously, the test should include likely network conditions rather than only a short, quiet session. If the stream shares an internet connection with a household or workplace, find out what else runs during the intended broadcast hours. A local speed test is only a snapshot; watch the stream’s health messages over a meaningful trial and repeat the check if the connection or encoder configuration changes.
Configure the encoder and test the loop
Set the encoder to the output resolution and frame rate you intend to send. Select the codec the encoder can reliably produce, then set the matching YouTube recommended video bitrate. Use CBR and a two-second keyframe interval; YouTube’s guidance says the interval should not exceed four seconds. Make sure the audio is present and correctly routed, since a picture-only test will not reveal missing or distorted sound.
YouTube explicitly advises testing before going live with audio and movement similar to the planned stream. For gaming, play or replay a demanding section rather than leaving the broadcast on a static menu. Include the quick camera changes and dense action that occur in the loop. Watch the preview and stream-health messages, and check the result on another playback device if possible. The aim is to find out whether the chosen encode and connection remain stable and whether motion looks acceptable, not to demonstrate that one number works for every game.
Keep a short record of the test: codec, resolution, frame rate, video bitrate, upload conditions and any health warnings. If frames are dropped, note whether the encoder reports a processing issue or the stream health suggests a network issue. Lowering the output resolution may ease both demands, while changing the codec can alter encoder load and bitrate recommendation. Make one change at a time, retest the same gameplay section and compare what happened.
For a repeated video loop, test both the portion with the most movement and the transition back to its beginning. A loop can look fine for most of its duration but reveal a freeze, jump or brief blank interval at the join. That is a playback and editing issue rather than a reason to add a bitrate multiplier. If the source file is already degraded, encoding at a higher bitrate cannot restore detail that is not present in the source.
The encoder and connection need to remain workable for the duration you plan to broadcast. A brief successful test shows only that the settings worked for that test; it cannot promise overnight stability. Monitor stream health and messages after going live, and keep a practical fallback such as a lower-resolution preset ready. If the computer itself must remain on to encode the loop, that is another operational requirement distinct from bitrate; a 24/7 rain-sounds stream workflow illustrates the broader planning involved in keeping a channel running beyond the initial setup.
Keep quality and continuity in view
For a gaming loop, the quality target is only part of the decision. Consider whether viewers benefit more from a sharper output or from a stable, uninterrupted channel. A 1080p60 output at a sustainable setting may be more useful than a higher resolution that repeatedly drops frames or loses connection. That is not a universal preference; it is a trade-off to evaluate against the content and viewers’ likely screens.
When the test indicates a network limit, lower the demand before trying to force a larger bitrate through the same connection. When the test indicates encoder overload, inspect whether the chosen resolution, frame rate or codec is too demanding for the system. When motion looks compressed but the health remains stable, compare the current setting with YouTube’s recommendation for that exact row and retest. Keep these cases distinct, because a bitrate adjustment will not repair every failure mode.
If the aim is a continuously running loop, decide in advance how you will notice a dropped broadcast and what action you can take. Monitor health messages during setup and after launch, and confirm that the intended file repeats as expected. A cloud-run workflow can remove the need to leave your own computer encoding the loop, but it does not change YouTube’s bitrate table or remove the need to prepare the file and stream settings. StreamNeo is relevant when keeping a local computer on for a continuous broadcast is the specific operational burden you want to remove.
The resolution, codec and upload target should be settled before you plan around a long run. Check YouTube’s current settings, test the exact output, and keep a lower-demand alternative available if conditions change. Do not treat a successful short test as a guarantee for every later hour, since shared traffic, service disruption or encoder behaviour can differ over time.
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 stream at for 1080p60 gaming?
YouTube recommends 12 Mbps for AV1 or H.265 and 17 Mbps for H.264 at 1080p60. These are video bitrate recommendations, not total stream bandwidth or a guarantee that your connection and encoder can sustain them. Test with representative gameplay before starting the broadcast.
Does fast-motion gameplay need extra bitrate?
YouTube’s published table has no separate fast-motion or gaming multiplier. Use the row for your codec, resolution and frame rate, then judge the result with a test that includes the movement your loop actually contains. Do not add an invented uplift to the official recommendation.
Is H.264 or AV1/H.265 better for a 1080p60 loop?
YouTube’s table lists a lower recommended video bitrate for AV1/H.265 than for H.264 at this output. Your choice still depends on whether your encoder supports and reliably produces the codec. Compare tested stability and picture quality rather than choosing solely by the bitrate figure.
How much upload speed do I need?
Start from the video target, then account for audio, overhead and other use on the connection. YouTube recommends leaving 20% headroom and says total stream bitrate must not exceed available upload bandwidth. Measure upload under realistic conditions and test the stream; download speed alone is not a useful substitute.