For a 1080p 30fps YouTube live stream, use the bitrate recommended for the codec you are actually sending: 14 Mbps for H.264, or 10 Mbps for AV1 and H.265/HEVC. Keep the encoder on CBR and set keyframes to every two seconds.
These are live-ingest settings. They describe the signal your encoder sends to YouTube during a broadcast, not the separate bitrate guidance for uploading a finished video. Your encoder, connection, audio, and YouTube's stream health messages all need checking before you rely on the setup overnight.
A compact 1080p30 settings checklist
Use this as the starting point for OBS or another encoder. The bitrate figures are not interchangeable: select the row that matches the codec configured in your encoder.
| Encoder setting | AV1 or H.265/HEVC | H.264 |
|---|---|---|
| Resolution and frame rate | 1080p at 30 fps | 1080p at 30 fps |
| Recommended video bitrate | 10 Mbps | 14 Mbps |
| Listed minimum video bitrate | 4 Mbps | 5 Mbps |
| Bitrate mode | CBR | CBR |
| Keyframe interval | 2 seconds recommended; do not exceed 4 seconds | 2 seconds recommended; do not exceed 4 seconds |
| Audio codec | AAC or MP3 | AAC or MP3 |
| Stereo audio bitrate | 128 kbps recommended | 128 kbps recommended |
| Colour space for SDR | Rec. 709 | Rec. 709 |
| Pixel and scan format | Square pixels, progressive | Square pixels, progressive |
| Protocol | RTMPS recommended; RTMP also supported | RTMPS recommended; RTMP also supported |
This table reflects YouTube Help's encoder guidance, accessed on 3 October 2026. The minimum is not a target for a demanding channel. It is better understood as a lower boundary in the published guidance, while the recommended value is the useful starting point for the relevant codec.
If your encoder offers several H.264 presets, those presets affect the work your computer does, but they do not change the need to use the H.264 bitrate guidance above. If you are building a long-running loop, also check whether your computer can maintain the selected encoder without dropped frames. The discussion in Does OBS Need a GPU for a 24/7 YouTube Loop Stream? is useful when the encoder itself is becoming the bottleneck.
Choose the bitrate for the codec you send
The codec determines which YouTube recommendation applies. At 1080p30, YouTube lists 10 Mbps as the recommended video bitrate for AV1 and H.265/HEVC, with 4 Mbps as the listed minimum. For H.264, it lists 14 Mbps as the recommended video bitrate, with 5 Mbps as the listed minimum.
Do not combine these into one generic “1080p30 bitrate”. If you select H.264 in OBS and send 10 Mbps because you saw the AV1 figure, you are not following the H.264 recommendation. Conversely, quoting 14 Mbps for an AV1 or H.265 stream makes the table less useful and can lead you to reserve more upload capacity than your selected codec requires.
The official YouTube encoder settings are the right place to check the current table before an important broadcast. YouTube's figures are recommendations for ingest. They are not a controlled comparison of image quality, hardware load, or compatibility between codecs.
Choose the codec your encoder and wider workflow support reliably. A newer codec may be available in your hardware or software, but availability alone is not enough. Confirm that the selected codec can be produced continuously, that your encoder exposes the required settings, and that your monitoring tools show a normal stream. If a production depends on older software, a capture device, or a separate automation tool, compatibility may matter more than choosing a newer codec.
For a devotional channel with mostly still artwork and gentle movement, the recommended codec bitrate is still the starting point. A local news loop with scrolling text and frequent scene changes should be tested with representative motion. Neither example changes the codec-specific figures in YouTube's table, but both can reveal problems in the actual production chain.
Set CBR and the keyframe interval
Set the video bitrate mode to constant bitrate, or CBR. With CBR, the encoder aims to send a steady stream rate rather than making large short-term changes. That gives YouTube a more predictable input and makes it easier to compare the stream's demand with the upload capacity available to you.
Set the keyframe interval to two seconds. YouTube's published guidance says the recommended keyframe frequency is two seconds and that it should not exceed four seconds. This is a timing setting, not a bitrate setting: changing it does not turn the H.264 recommendation into the AV1 or H.265 recommendation.
A keyframe is a complete reference picture from which later frames can be decoded. Between keyframes, the encoder generally sends changes rather than a complete picture each time. A regular interval gives the receiving service predictable points at which it can begin or recover playback. For this reason, do not leave the setting on an obscure automatic value if your encoder allows you to enter two seconds directly.
In OBS, the exact location of these controls depends on whether you use the simple or advanced output view and which encoder is selected. Look for the output stream settings rather than the recording settings. A recording profile can have different requirements, and copying its values into the live output can create confusion.
Do not compensate for a weak connection by switching CBR off and allowing large bitrate swings. First reduce the production's demand in a planned way, or investigate the upload path. YouTube advises leaving headroom between the total stream bitrate and the available upload capacity, so a connection that barely reaches the video figure is not a comfortable operating margin.
Select RTMPS, video encoding, and audio
YouTube supports RTMP and RTMPS for encoder connections and recommends RTMPS. RTMPS is the encrypted version of the publishing connection. When your encoder offers RTMPS as the protocol, use the stream URL and key supplied by YouTube's Live Control Room, and make sure the encoder is not silently set to a different protocol.
The protocol is separate from the codec. RTMPS does not mean H.264, AV1, or H.265 by itself. You still need to choose the video encoder and apply the bitrate table for that codec. Similarly, changing from RTMP to RTMPS does not remove the need for CBR, a suitable keyframe interval, or enough upload capacity.
For audio, YouTube's table lists AAC or MP3 and recommends 128 kbps for stereo audio. Use the sample rate and channel configuration that your encoder and production workflow support consistently. Listen to the rehearsal on headphones as well as through a phone or another ordinary playback device. A clean video signal does not help if speech is too quiet or music is clipping.
For an SDR stream, use Rec. 709, square pixels, and progressive scan. These settings describe how the picture is interpreted and displayed. They are particularly worth checking when the source passes through a capture card, a slideshow application, or a video-conversion step before it reaches the live encoder.
YouTube's encoder streaming help provides the current protocol and encoding guidance. It also explains the general encoder workflow, while your software's documentation determines where the controls appear. You do not need a hardware encoder simply because you are streaming at 1080p30; software and hardware encoders are both possible routes.
Check upload capacity before going live
The important question is not “What internet speed is needed for 1080p30?” as though there were one universal answer. The useful question is whether your available outbound capacity can carry the selected video bitrate, audio, protocol overhead, and ordinary variation on the connection while leaving room for the rest of the household or workplace network.
YouTube advises checking outbound upload bandwidth and leaving about 20% headroom. Treat that as operating room, not as a guarantee of uninterrupted service. If H.264 is configured at 14 Mbps, your connection should have more available upload capacity than that video figure alone. AV1 or H.265 at 10 Mbps has a different requirement, but it still needs headroom and a dependable route to YouTube.
Run the check at the place and time where the stream will operate. A result from a quiet office in the afternoon may not represent a shared home connection at night. Pause large uploads, cloud synchronisation, security-camera backups, and other traffic during the test, then consider what will happen when those activities resume.
A wired connection can be useful where wireless interference or distance from the access point is part of the problem, but it is not a universal remedy. Check the actual upload path first. If the connection remains marginal, a lower-demand production may be more dependable than forcing 1080p30 through a link that cannot sustain it.
Keep an eye on the encoder's outgoing bitrate and dropped-frame counters. A low upload speed can cause network-related drops, while a high encoder load can cause a different class of problem even when the network is fine. This distinction matters when diagnosing an overnight devotional loop, a study stream, or a small business information channel.
Test and monitor YouTube's stream health
Rehearse the complete path before the public broadcast. Use the same resolution, frame rate, codec, bitrate, audio, scenes, overlays, and source movement that you expect to use in the real event. A static test image will not tell you how scrolling text, a talking presenter, a music visualiser, or a changing camera view behaves.
Create or schedule the live event in YouTube Live Control Room and connect the encoder using the stream details YouTube provides. YouTube's default recommendation is to let it detect resolution and frame rate. If you need to choose those manually, YouTube says to create a custom stream key and enable manual settings under Stream Resolution.
Once the signal is connected, inspect YouTube's stream health messages rather than relying only on the preview. Check for warnings about the incoming bitrate, missing frames, audio, resolution, or connection. Compare those messages with the encoder's own statistics. The two views help separate a local encoding problem from an upload or ingest problem.
The best OBS settings for a 24/7 YouTube event replay stream can help you think through a long-running configuration, but do not copy settings blindly. The codec, source material, computer, and network still need to be tested together.
For an interactive broadcast, consider latency as a trade-off rather than selecting the lowest possible value automatically. Lower latency can make conversation feel more immediate, but YouTube notes that it may increase playback buffering. A channel that mainly plays a continuous ambience or devotional loop may value stable viewing more than rapid chat response.
DVR is another separate choice. When enabled, viewers can pause, rewind, and resume parts of a live stream. That can suit a lesson or a guided session, while a time-sensitive announcement may have different priorities. Select latency and DVR based on how viewers use the channel, then observe the result during the rehearsal.
A test can reveal a configuration problem, but it cannot guarantee that the connection or service will remain uninterrupted later. Keep the encoder logs, note the settings that worked, and check the stream health again after the broadcast begins. For reconnect behaviour in a long-running setup, see How to Restart a YouTube Live Stream Automatically When It Disconnects.
Live-ingest settings are not upload settings
A live-ingest setting controls the encoded signal sent continuously from your encoder to YouTube while the broadcast is active. Resolution, frame rate, codec, video bitrate, CBR, keyframe interval, protocol, and audio settings all describe that moving signal.
Upload encoding is different. When you upload a finished video, YouTube receives a file that can be processed before viewers watch it. Its upload guidance is not a substitute for the live encoder table. Do not take a bitrate from an upload chart and apply it to a live stream merely because both refer to 1080p.
The distinction is especially important for pre-recorded channels. A file may have been exported at a suitable upload quality, but the live encoder still needs to send a separate real-time signal. If you play the file through OBS or another application, that application may decode it and re-encode the outgoing stream according to the live settings.
For a 24/7 channel, the source file and the live output therefore deserve separate checks. Confirm that the file plays correctly, then confirm that the live encoder produces 1080p at 30 fps with the selected codec, CBR, keyframe interval, audio, and protocol. The article on OBS settings for a 24/7 ambient music YouTube stream is relevant when the source is a continuous ambience or music programme, but its settings should still be validated against the codec you actually send.
This also explains why a high-quality source file cannot rescue a poor live connection. The source may look excellent locally, while the outgoing ingest signal suffers from insufficient upload capacity, dropped frames, or an overloaded encoder. Diagnose each stage instead of treating “1080p” as a guarantee about the whole chain.
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 1080p30 YouTube live stream?
Use 14 Mbps for H.264, or 10 Mbps for AV1 and H.265/HEVC, based on YouTube's live encoder guidance accessed on 3 October 2026. The listed minimums are 5 Mbps for H.264 and 4 Mbps for AV1 or H.265, but you still need upload headroom and a stable encoder.
Should 1080p30 use CBR or variable bitrate?
Use CBR for the live output. Set the keyframe interval to two seconds, and do not exceed four seconds according to YouTube's encoder table.
How much upload speed do I need?
There is no single connection speed that guarantees a stable 1080p30 stream. Your available outbound capacity must cover the codec-specific video bitrate, audio, and connection overhead, with about 20% headroom as advised by YouTube.
Should I use RTMP or RTMPS?
YouTube recommends RTMPS, so use it when your encoder supports it and follow the stream URL and key shown in Live Control Room. RTMPS is the publishing protocol; it does not decide whether your video codec is H.264, AV1, or H.265.