For a 1080p60 YouTube live stream, use 17 Mbps with H.264 or 12 Mbps with AV1 or H.265. YouTube lists lower minimums of 6 Mbps for H.264 and 4 Mbps for AV1 or H.265, but the recommended rate depends on the codec you actually send.
Set the encoder to CBR, use a two-second keyframe interval, choose RTMPS, and use AAC or MP3 audio. These settings are a starting point, not a guarantee that a stream will remain stable: test the real connection and monitor YouTube's stream health before relying on it overnight.
Quick settings checklist for 1080p60
Use this as a first-pass checklist when creating an encoder profile for YouTube Live:
| Encoder setting | H.264 | AV1 or H.265 |
|---|---|---|
| Resolution and frame rate | 1920 × 1080 at 60 fps | 1920 × 1080 at 60 fps |
| Recommended video bitrate | 17 Mbps | 12 Mbps |
| Listed minimum video bitrate | 6 Mbps | 4 Mbps |
| Bitrate mode | CBR | CBR |
| Keyframe interval | 2 seconds | 2 seconds |
| Maximum keyframe interval | Do not exceed 4 seconds | Do not exceed 4 seconds |
| Ingestion protocol | RTMPS recommended | RTMPS recommended |
| Audio codec | AAC or MP3 | AAC or MP3 |
| SDR colour space | Rec. 709 | Rec. 709 |
The figures in the table are for live encoder ingestion, not for uploading a finished video file. YouTube gives separate upload guidance, so do not copy an upload bitrate into a live encoder profile simply because both use 1080p60.
If your software shows separate fields for output resolution and canvas resolution, the output sent to YouTube should be 1920 × 1080. The source can be different, but scaling it to 1080p does not turn a lower-resolution recording into genuine 1080p detail.
YouTube can detect resolution and frame rate automatically. If you need to set them manually, YouTube's Help guidance says to create a custom stream key and enable manual settings under Stream Resolution. Check the official YouTube encoder settings if the names in your encoder or Live Control Room differ.
Choose bitrate by codec
The first decision is the codec, because the recommended bitrate is not codec-independent. For H.264, YouTube's current live guidance recommends 17 Mbps at 1080p60. For AV1 or H.265, it recommends 12 Mbps. Sending one universal number for every codec hides an important part of the configuration.
YouTube lists 6 Mbps as the minimum for H.264 and 4 Mbps as the minimum for AV1 or H.265 in this 1080p60 context. A listed minimum is not the same as the recommended operating point. It may be useful when diagnosing a constrained connection, but dropping to the minimum changes the trade-off between available bandwidth and picture detail.
The codec choice should follow what your encoder and computer can support reliably. A newer codec is not automatically the right choice if your software cannot encode it consistently, your hardware has limited support, or the resulting stream is difficult to test. Compare the encoder's actual codec support with YouTube's codec-specific figures rather than selecting a codec because its name appears in a settings menu.
H.264 remains a practical choice when compatibility across encoding software and hardware matters. AV1 or H.265 may be suitable when your equipment supports them and you have tested the complete path. YouTube identifies H.265 as its recommended HDR codec and says AV1 is not supported for HDR, so an HDR workflow requires a separate check of the colour and dynamic-range requirements.
For ordinary SDR 1080p60, use Rec. 709 as the colour space listed in YouTube's guidance. Colour-space settings are separate from bitrate. A higher bitrate will not correct a source that is incorrectly tagged or converted.
Do not confuse the video bitrate with the total traffic used by the stream. Audio and protocol overhead also use some upload capacity. YouTube's published table gives the video bitrate figures, but it does not provide a universal extra upload-speed margin for every connection. Test the complete setup instead of adding an invented safety percentage.
Set CBR and a two-second keyframe interval
Set bitrate encoding to constant bitrate, usually shown as CBR. This tells the encoder to aim for a steady video rate rather than allowing large swings based on how complex each moment is. A steady output is useful for a platform ingesting a continuous live feed, particularly when the stream is expected to run for many hours.
Set the keyframe frequency to two seconds. The keyframe interval controls how often the encoder places a complete reference frame into the stream. Other frames can refer back to that data, so the interval affects how the platform can process and recover the incoming video.
YouTube says not to exceed a four-second keyframe interval. If your encoder asks for a keyframe value in frames rather than seconds, the conversion depends on the frame rate. At 60 fps, two seconds corresponds to 120 frames and four seconds corresponds to 240 frames. Check whether the field expects seconds or frames before entering a number.
A common mistake is setting the video to 60 fps but leaving a keyframe value that was intended for 30 fps. The resulting interval can be twice as long as expected. Another is selecting variable bitrate because it produced a smaller file in a local recording. Live ingestion has different priorities from storing a finished file, so use the live guidance and then test the output.
These settings still need to be applied to the encoder profile that is actually running. It is possible to change one profile while the live job uses another, or to alter the canvas without altering the stream output. After saving the profile, inspect the active output fields before starting the test.
Choose RTMPS and configure audio
YouTube lists RTMP and RTMPS as ingestion protocols and recommends RTMPS. If your encoder offers both, select the secure RTMPS option and copy the server URL supplied by YouTube rather than typing an address from memory.
Your stream key works as a credential for the encoder. Treat it like a password and do not publish it in a screenshot, tutorial, chat message or public configuration file. If you believe it has been exposed, YouTube provides a reset workflow in Live Control Room; after resetting it, update the encoder with the new key. The YouTube guide to managing live stream settings covers the relevant controls.
For audio, YouTube supports AAC or MP3 for the live stream. Pick the option your encoder handles cleanly and confirm that the audio is present in the actual output, not only in the local preview. A devotional loop, local news bulletin or study stream can appear visually healthy while sending silence, the wrong input or a delayed channel.
Keep the audio path simple during the first test. Use the same source, mixing, sample-rate configuration and processing that you intend to use during the real broadcast. If you plan to add a microphone, background music or scheduled segments later, test the combinations that matter rather than testing a silent video and assuming the live mix will behave the same way.
AAC or MP3 is a codec choice, not a recommendation to use a particular microphone or sound card. YouTube describes software and standalone hardware encoders as options, and external cameras and audio equipment are production choices rather than prerequisites for 1080p60. If your channel is a looping visual with a soundtrack, a reliable audio file and correct levels may matter more than buying additional equipment.
For a channel built around repeated material, technical settings are only one part of the publishing decision. You should also read the guidance on reused content and 24/7 loops before assuming that a technically valid stream is suitable for your channel.
Check upload capacity and encoder output
A 17 Mbps H.264 video output needs a connection that can sustain that live upload, while a 12 Mbps AV1 or H.265 output has a different requirement. The practical question is not whether a speed test once displayed a high figure. It is whether the connection can carry the selected stream consistently while other traffic, Wi-Fi variation and the rest of the encoder's output are present.
YouTube recommends checking available upload bitrate with a speed test and choosing a quality the connection can sustain. Run the test in the place where the encoder will operate and at a time that resembles the intended use. A home broadband result taken beside the router may not represent the connection available to a computer in another room, a VPS, a shop or a small office.
Do not treat a speed-test result as proof that the encoder is configured correctly. Check the encoder's output statistics as well. Look for the selected resolution, frame rate, codec, bitrate mode and keyframe interval. If the encoder reports dropped frames, rendering delays or overloaded output, determine whether the cause is the connection, the machine or the source before changing the YouTube bitrate.
For a pre-recorded video used as a live loop, play a representative section during testing. Include the busiest visual movement, the loudest or most complex audio passage and any transitions. A static devotional image and a fast-moving music visual can place different demands on the encoder even when both are labelled 1080p60.
Software encoding can work with an existing computer, while a standalone hardware encoder may suit a production setup that needs a separate device. YouTube lists both approaches and does not require a particular one for 1080p60. The right choice depends on the equipment you already have and whether that equipment can produce the selected output continuously.
If you use a computer-based workflow, avoid changing operating-system updates, power settings or background applications immediately before an overnight broadcast. If you use a hosted workflow, verify the actual output and connection from that environment. The place that stores your video is not necessarily the place sending the live stream.
For a workflow that uses local software to repeat a file, the OBS and FFmpeg comparison can help you think through the operational differences. It does not replace checking the codec, bitrate and keyframe fields in the encoder you finally choose.
Test the real broadcast before relying on it
YouTube's advice is to test before starting the live stream, including audio and movement similar to what you will use. That is more useful than checking only that the encoder connects. A connection test can pass while the real video has silent audio, a changing frame rate or an overloaded encoder.
Create a test that resembles the planned broadcast in the ways that affect delivery:
- Use the same 1920 × 1080, 60 fps output.
- Use the same codec and codec-specific bitrate.
- Keep CBR enabled and set the two-second keyframe interval.
- Send the same audio codec and source.
- Use RTMPS and the stream key that will be used for the channel, or a separate test key where appropriate.
- Include motion, transitions and audio rather than testing a blank screen.
- Leave the setup running long enough to observe more than the initial connection.
The final point is not a request for a particular duration. There is no universal test length that proves an overnight stream will be stable. The purpose is to expose problems before the audience depends on the channel, then to repeat the test after changing a material setting.
Review the viewer-facing result as well as the encoder's own statistics. Watch for buffering, missing audio, judder, incorrect aspect ratio and a picture that is not actually 1080p60. If the preview looks fine on the production computer but not on another connection, investigate both the source output and playback conditions.
Keep a short record of what worked: codec, bitrate, keyframe setting, protocol, audio source and the connection used. This makes troubleshooting more orderly when a later change causes a problem. It also prevents repeatedly testing different variables at once.
Monitor stream health while live
Once the stream is running, watch YouTube's stream health messages in Live Control Room. YouTube recommends monitoring the health of the stream and reviewing any messages. A green-looking local encoder does not necessarily show every issue YouTube is seeing at ingestion.
Check the stream health at the beginning and after any change to the source, network or encoder. For a 24/7 channel, arrange a practical way to notice warnings when you are not sitting beside the computer. The exact arrangement depends on your workflow, but it should not rely on discovering a problem only after viewers report it.
When a warning appears, change one relevant thing at a time and observe the result. If the upload cannot sustain the selected output, compare the codec-specific bitrate options and the source quality you genuinely need. If the encoder is overloaded, inspect the machine and encoding method. If the audio is missing, follow the audio path from the source to the active output rather than changing the video bitrate.
A long-running channel also has an operational choice between keeping an encoder computer running and using a workflow that removes that particular overnight dependency. StreamNeo removes the need to leave your own computer running by letting you upload the video, provide the YouTube stream key and have the channel run while the broadcast is monitored and restarted automatically if it drops. It remains your responsibility to choose suitable source material, confirm the settings and monitor the YouTube channel.
If you are considering a hosted workflow, the guide to running a 24/7 stream without OBS explains the wider operational question. The settings in this article still apply to the output being sent to YouTube, regardless of where the encoder runs.
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 1080p60?
Use 17 Mbps when sending H.264, or 12 Mbps when sending AV1 or H.265, based on YouTube's current live encoder guidance. YouTube lists lower minimums of 6 Mbps for H.264 and 4 Mbps for AV1 or H.265, but those figures do not replace testing the connection and the complete encoder output.
Should YouTube Live use CBR or VBR?
Use CBR for this 1080p60 live configuration. Also set the keyframe interval to two seconds and do not exceed four seconds, then confirm that the active encoder profile is using those values.
Is RTMPS required for 1080p60?
YouTube lists both RTMP and RTMPS ingestion, and recommends RTMPS. Select RTMPS when your encoder supports it, keep the stream key private, and test the actual connection before relying on the stream.
Can I run 1080p60 with software encoding?
Yes. YouTube describes both software and standalone hardware encoders as options; it does not require a particular type for 1080p60. Choose based on the equipment you already have, then check that it can maintain the selected codec, bitrate, frame rate and audio output during a representative test.