For 4K/2160p at 60 fps, YouTube’s recommended ingest bitrate is 50 Mbps for H.264 and 35 Mbps for H.265; its listed minimums are 14 Mbps and 10 Mbps respectively. Use constant bitrate (CBR), set a two-second keyframe interval, and choose the codec and colour depth to match SDR or HDR.
For HDR, YouTube lists H.265/HEVC at 10-bit. For SDR, it lists Rec. 709 at 8-bit. These are ingest settings, not a promise of picture quality or successful delivery: you still need to test the complete stream and watch its health before relying on it for an event or an overnight channel.
Choose H.264 or H.265 for the workflow
Start with the material you intend to send. If the stream is SDR, either H.264 or H.265 is listed by YouTube for live video. If it is HDR, YouTube’s guidance identifies H.265 as the HDR video codec and specifies 10-bit depth. Do not select a codec just because its name sounds newer; confirm that your encoder can produce the codec and colour format you actually need.
For 4K60 SDR, the difference most directly useful for setting up the stream is the recommended ingest rate: YouTube lists 50 Mbps for H.264 and 35 Mbps for H.265. The listed minimums are 14 Mbps for H.264 and 10 Mbps for H.265. A minimum is not the recommended target, and reaching either figure does not mean that a connection will be reliable in every moment or that viewers will see a particular result.
| Workflow | Codec and colour | YouTube-recommended 4K60 video bitrate | Listed minimum |
|---|---|---|---|
| SDR | H.264, Rec. 709, 8-bit | 50 Mbps | 14 Mbps |
| SDR | H.265/HEVC, Rec. 709, 8-bit | 35 Mbps | 10 Mbps |
| HDR | H.265/HEVC, 10-bit | Use the applicable current YouTube guidance and encoder workflow | Check the current guidance |
The HDR row needs a little care: do not carry the SDR comparison across as if it established every HDR bitrate choice. Consult the current YouTube Live encoder settings and check what your encoder can send. The official guidance establishes YouTube’s codec and bit-depth requirements for HDR, but it does not establish a universal best-looking setting for every scene or device.
If your encoder offers both codecs, use the one that fits the intended output and the available, stable upload capacity. If it only offers H.264, it may suit an SDR broadcast; it is not the HDR path described in YouTube’s guidance. If you are working out the broader data-rate implications, the resolution and frame-rate bitrate calculator is a useful companion, but treat YouTube’s current live ingest table as the authority for the platform targets.
Set 4K60 resolution and frame rate
The target format is 4K, also labelled 2160p, at 60 frames per second. These are separate settings: resolution describes the frame dimensions, while frame rate describes how frequently frames are sent. Confirm both in the encoder output, rather than assuming that a 4K source file guarantees a 4K60 live signal.
YouTube recommends automatic resolution and frame-rate detection by default. If you need to select a fixed output, YouTube’s guidance says to create a custom stream key and enable manual settings under “Stream Resolution”. This gives you a way to specify the intended format, but it does not make the encoder or connection capable of delivering it. Check that the actual outgoing stream reports the expected resolution and frame rate.
For a pre-recorded loop, also check the source file and the encoder’s handling of it. A file may contain a different frame rate or colour format from the live output you intend. Decide whether you want the encoder to convert it, and verify the resulting stream rather than relying on the file’s label alone. If you are building an always-on channel from a video loop, the practical concerns in running a 24/7 YouTube stream from a VPS in India provide relevant context for keeping a continuous broadcast in mind while setting format.
A 4K stream has a latency trade-off worth knowing before scheduling a live event. YouTube’s guidance says the option to improve for low latency is not available for 4K/2160 streams; they are optimised for quality and use normal latency. If near-real-time interaction matters more than 4K, reconsider the output resolution rather than expecting a latency toggle to change that constraint.
Enter the codec-specific bitrate
For the 4K60 live ingest figures in YouTube’s guide, keep the codec and rate paired correctly. H.264 is 50 Mbps recommended and 14 Mbps minimum. H.265/HEVC is 35 Mbps recommended and 10 Mbps minimum. Do not swap the rows, and do not describe the minimum as the recommendation.
The table is about video bitrate sent to YouTube, not a complete upload-speed specification for your internet service. Your connection also carries audio and other traffic, and its available upstream rate can vary. YouTube advises testing upload bitrate and selecting a quality that is reliable for the connection. In practice, the important question is not just whether a speed test once showed enough capacity, but whether the whole live path can sustain the chosen output under the conditions in which you will use it.
Set the video bitrate in the encoder’s live output profile. If the encoder has separate fields for target rate, maximum rate, or rate control, make sure you know which field controls the transmitted video rate; do not assume a field label has the same meaning in every application. Use the current documentation for the encoder itself when those controls are unclear. This article does not establish settings for a particular application or hardware model.
A stable bitrate alone does not guarantee a clean picture. Fast movement, fine detail, source quality, encoding behaviour, dropped frames, and delivery conditions can all affect what arrives and what viewers see. If the image is blocky despite a seemingly stable rate, work through the checks in YouTube Live blocky-artifact troubleshooting rather than immediately raising the bitrate beyond what the connection can sustain.
Use CBR and configure keyframes
Set bitrate encoding to CBR, or constant bitrate. YouTube lists CBR in its live encoder guidance. The aim is to send a controlled rate rather than letting the video rate vary freely; this makes the selected bitrate a more useful reference for planning the ingest stream. CBR does not remove variation in network conditions or guarantee that every frame will arrive on time.
Set the keyframe interval to two seconds. YouTube recommends two seconds and says not to exceed four seconds. A keyframe is a reference frame that can be decoded without relying on preceding frames in the same way as intervening frames. The interval is a distinct control from frame rate and bitrate: set it explicitly if your encoder exposes it, then confirm that the outgoing profile uses that value.
YouTube’s advanced recommendations also include progressive scan, square pixel aspect ratio, two B-frames, one reference frame, and CABAC for applicable H.264 settings. These additional fields can be useful when your encoder exposes them, but do not let a long list of advanced controls distract from the essentials: correct codec, resolution, frame rate, rate control, keyframes, and colour format. If a control is not available or its meaning is uncertain, check the encoder’s documentation rather than guessing.
Audio deserves a separate check because an otherwise correct video profile can still produce an unusable broadcast. YouTube lists AAC or MP3 for audio; it lists 44.1 kHz and 128 Kbps for stereo, and 48 kHz and 384 Kbps for 5.1 audio. For 5.1 over RTMP/RTMPS, the listed supported audio codec is AAC. Use the format that matches the programme and verify that audio is present and synchronised during the test.
Configure SDR colour settings
For an SDR stream, use Rec. 709 colour space and 8-bit depth, as listed in YouTube’s live settings. Check both the encoder’s output settings and any source or project settings that can alter the colour handling. A 4K label does not tell you whether the stream is SDR or HDR, and frame rate does not determine colour space.
Make a conscious choice between SDR and HDR at the beginning of the workflow. If the original material is SDR, selecting an HDR output mode does not create genuine HDR detail. It can instead introduce mismatches between the source, encoder metadata, and viewer playback. Keep the path consistent: SDR source and output should remain SDR unless you have a deliberate conversion workflow and can validate it.
During the test, inspect a range of content that resembles the real channel: dark scenes, bright areas, skin tones if present, and any saturated graphics or text. This is not a substitute for a calibrated monitoring environment, but it can catch obvious errors such as washed-out levels or unexpected colour shifts before viewers encounter them. If the channel is a long-running devotional or ambience stream, test the actual loop and overlays, not just a short colour-bar clip.
Configure HDR with H.265 and 10-bit
For HDR, YouTube lists H.265/HEVC and 10-bit video. Its guidance does not identify H.264 as the recommended HDR path, so do not reuse an H.264 SDR preset and label it HDR. Confirm that the encoder can send H.265 with the required 10-bit format and that the source is genuinely prepared for HDR.
HDR is a chain, not a single switch. The source, encoder output, stream metadata, ingest path, and viewer display all matter. A mismatch can make a stream look different from the intended grade, even if the stream is accepted. For this reason, check the encoder’s HDR controls and YouTube’s current requirements together; do not invent a colour-space or transfer-function selection based on a menu label alone.
YouTube recommends H.265 over RTMP(S) for HDR. Its guidance says HLS can be considered if the encoder does not yet support the relevant capabilities over RTMP. That is a workflow distinction, not a reason to assume every encoder supports HDR over every protocol. Verify the exact combination in your encoder and test it on the channel before relying on it for a scheduled broadcast.
Keep SDR and HDR profiles separate if you use both. Name them clearly, record the codec, bit depth, resolution, frame rate, bitrate, and keyframe interval, and test each profile independently. This avoids accidentally sending an SDR programme through the HDR path or changing one setting in a profile that was already validated for another programme.
Use RTMPS when available and test the stream
YouTube lists RTMP and RTMPS as supported protocols and recommends RTMPS. Select it where your encoder and connection support it. Enter the stream key carefully and keep it private; it authorises the encoder to send to your channel. You can consult Google’s YouTube Live streaming documentation for platform context, and use YouTube Help for the current ingest settings.
Test the complete stream before an event. YouTube Help explicitly advises creators to test before starting a live stream. Run the same encoder, output profile, network connection, audio path, source material, and overlays that you plan to use. A test that uses a different codec or only sends a static image does not tell you how the real stream will behave with movement, audio, and the intended duration.
Watch the live control room’s stream health and read any messages it presents. Check for dropped frames or warnings, confirm the reported resolution and frame rate, listen for audio, and inspect the picture on a playback device. A technically accepted signal can still fail your practical needs if it is too delayed, too soft, wrongly coloured, or inconsistent. Testing tells you about the actual setup; a settings table cannot guarantee the result.
For an always-on channel, include recovery in the test. Confirm that the broadcast can be resumed if the encoder or connection stops, and decide who will notice and respond to a warning overnight. StreamNeo can remove the need to leave your own computer running for a file-based 24/7 YouTube stream, which addresses the specific burden of keeping a local machine on continuously; it does not replace checking the codec settings, source rights, stream health, or the platform’s current requirements.
If your test cannot sustain the chosen 4K60 profile, do not treat the minimum bitrate as an automatic fix. Recheck the upload path, encoder output, and whether 4K60 is necessary for the programme. A lower output format that remains stable may serve viewers better than a nominally higher-quality profile that repeatedly drops frames. Make the decision from a complete test, then repeat the test after material changes to the encoder, network, or source.
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 4K60 YouTube Live?
YouTube recommends 50 Mbps for H.264 and 35 Mbps for H.265/HEVC at 4K60. Its listed minimums are 14 Mbps for H.264 and 10 Mbps for H.265; these are minimums, not recommended targets, and neither figure guarantees a reliable stream.
Can I use H.264 for HDR?
YouTube’s live guidance lists H.265/HEVC as its HDR video codec and specifies 10-bit depth. Do not describe an H.264 configuration as YouTube’s recommended HDR path based on that guidance; check the current official requirements and your encoder’s capabilities.
What keyframe interval and rate control should I set?
Use CBR and a two-second keyframe interval. YouTube says not to exceed four seconds, so check the encoder output if you are unsure whether it is applying the interval you selected.
Does the recommended bitrate guarantee good picture quality?
No. The figures are YouTube’s ingest recommendations, not a guarantee of quality, successful ingest, or uninterrupted delivery. Test the complete stream with representative motion and audio, then monitor stream health and make adjustments based on what the actual setup reports.