If you are sending a finished video file through a live encoder to YouTube Live at 4K/30fps, YouTube’s recommended bitrate depends on the codec: 42 Mbps for H.264, or 30 Mbps for H.265/HEVC and AV1. Those are live-ingest recommendations, not a promise of identical picture quality across codecs.
In OBS, set the streaming keyframe interval to two seconds and use constant bitrate (CBR). OBS labels and available controls vary by version and encoder, so verify the actual control in your installed build rather than relying on an old screenshot. This guide covers where to look, how to test the result, and why a normal video upload uses a different bitrate recommendation.
Open OBS Output settings
Start by checking the output controls in OBS rather than changing the video resolution or frame rate first. Open Settings, then select Output. The streaming options are usually presented separately from recording options, but their arrangement and wording can vary between OBS versions.
Make sure you are looking at the streaming controls. A keyframe setting under recording may not affect the live broadcast. This distinction matters if OBS is also configured to save a local copy: recording and streaming can use different encoders and settings. Check the heading or tab for the streaming section before adjusting anything.
If you have been following a guide that shows a different layout, treat its directions as a clue, not proof that your build has the same control. OBS changes over time, and encoder plugins or platform-specific packages can add their own options. The goal is not to reproduce a screenshot; it is to find and confirm the setting that controls keyframes for the stream encoder.
If you are putting a video file into an OBS scene, make a short test with that same source before relying on a long playlist. For other ways to send a finished video through OBS, see this guide to streaming a Telugu podcast playlist from a laptop. It is useful context for the media-source workflow, while the encoder controls discussed here apply to the outgoing live signal.
Switch to Advanced output mode if needed
OBS output settings commonly provide a simpler mode and an advanced mode. The simpler view can hide individual streaming encoder controls. If you do not see a keyframe interval, look for the Output Mode selector near the top of the Output settings and choose Advanced, then return to the streaming section.
Do not assume the selector appears in the same location in every release. If the labels differ, consult the help or documentation for your installed OBS version, or inspect the streaming settings carefully for an equivalent advanced view. Avoid changing several options just to make the screen resemble a tutorial: switching the view should reveal controls, not silently select a different delivery setup.
After changing output mode, check whether the encoder selection has changed or whether new controls have appeared. Advanced mode may expose rate control, bitrate, keyframe interval and other options that the simple mode abstracts away. The presence of more controls does not mean each one needs adjustment. For this task, identify the live encoder and its keyframe interval, then review bitrate and rate control against YouTube’s guidance.
If you also troubleshoot audio in OBS, keep that as a separate check. A changed video encoder setting will not normally correct an audio timing issue; this guide on fixing audio out of sync in an OBS pre-recorded stream addresses that separate problem.
Find the streaming encoder controls
Within Output, select the streaming section or tab and locate the encoder used for streaming. Depending on the version and chosen encoder, the interface may expose the keyframe control directly, put it among encoder-specific options, or use different wording. Look for Keyframe Interval, Keyframe Interval (seconds), or an equivalent control that explicitly concerns keyframes for the stream.
The key is to distinguish a real encoder setting from a setting that only affects recording, a scene source, or a video filter. Confirm you are in the live streaming output path and that the selected encoder is the one that will send video to YouTube. If the control is absent, do not infer that it is already set correctly. Check whether the current output mode is simple, whether the encoder offers advanced options, and whether your OBS version or encoder supports exposing this parameter.
YouTube’s live encoder guidance recommends a two-second keyframe interval and says not to exceed four seconds. Use two seconds when the encoder provides a configurable interval. Do not set a longer interval based on an outdated forum post or a screenshot from a different encoder. If your chosen encoder does not show a keyframe control, verify its documented behaviour or select a compatible encoder that lets you configure the stream as required.
YouTube’s live encoder settings also list RTMP/RTMPS as ingest protocols and H.264, H.265/HEVC and AV1 as video codecs. Those available choices depend on your encoder and sending route; the codec in the finished source file does not by itself establish which codec OBS sends to YouTube.
Set Keyframe Interval to 2 seconds
When you have found the streaming encoder’s keyframe control, enter 2 if the field is expressed in seconds. If the field is expressed in frames, do not type “2” without checking the meaning: the corresponding number of frames depends on the frame rate. At 30 fps, two seconds is 60 frames, but encoder interfaces do not all present this control in the same units. Confirm the unit in the label or the encoder’s documentation.
Apply the change, close or leave Settings as required by your OBS build, then return to the streaming section and verify that the displayed value remains two seconds, or the equivalent frame count. Some encoders expose a preset or an automatic setting rather than a numeric field. In that case, check the encoder documentation to determine what it sends; do not treat “automatic” as confirmation of a two-second interval unless that behaviour is documented.
Keyframes are reference frames that help a decoder begin or recover video without relying on earlier frames. A regular interval is useful to the receiving service and viewers joining a stream part-way through. The setting is not a way to improve source detail: it does not turn a low-resolution file into 4K or compensate for insufficient bitrate. It is one part of a stream configuration that should agree with the platform’s ingest recommendations.
For an ongoing loop, you can also review how the source is arranged and restarted in a guide to restreaming old videos. The source loop and the encoder’s keyframe cadence are different things: a clean playlist transition does not replace the outgoing stream setting.
Check the selected encoder and service settings
Once the keyframe interval is set, confirm the encoder and its rate-control mode. YouTube recommends CBR for live ingest. In the same YouTube table, the 4K/2160p at 30 fps recommendation is 42 Mbps for H.264, with a listed minimum of 11 Mbps; for H.265/HEVC or AV1, it is 30 Mbps, with a listed minimum of 8 Mbps. These figures refer to the codec YouTube receives, not necessarily the codec used to create your original file.
| Live ingest codec at 2160p/30 | YouTube recommended bitrate | Listed minimum |
|---|---|---|
| H.264 | 42 Mbps | 11 Mbps |
| H.265/HEVC | 30 Mbps | 8 Mbps |
| AV1 | 30 Mbps | 8 Mbps |
Choose the row for the actual outgoing encoder. H.264 is a broadly supported live workflow, while HEVC or AV1 may be available only with particular encoder and ingest combinations. The lower recommendation for those codecs is not a claim that either codec is universally better, or that every OBS installation can use them. Check the selected encoder, service configuration and YouTube’s current guidance before planning around them.
For SDR, YouTube’s settings list Rec. 709 and 8-bit. For HDR, the cited guidance identifies H.265/HEVC and 10-bit, and notes that AV1 is not supported for HDR in those described settings. If you are not deliberately producing HDR, do not switch colour settings casually; the colour workflow needs to match the content and encoder. YouTube also says low-latency mode is unavailable for 4K/2160, so those streams use normal latency under the documented settings.
A finished video sent as a live stream is not the same workflow as uploading that file as an ordinary video. For a standard 4K/2160p upload at 24, 25 or 30 fps, YouTube’s separate recommended upload encoding settings list 35–45 Mbps. Do not use that upload range as the live-ingest answer, or use the live table as a blanket recommendation for a regular upload.
Plan upload capacity around the stream
The bitrate configured in OBS has to fit within reliable outbound upload capacity. An advertised download speed is not the figure to use. Run an upload speed test on the connection and device that will carry the stream, and consider other traffic on the same connection, such as cloud backups, video calls or household use.
YouTube’s streaming tips recommend leaving 20% headroom above the total stream bitrate. As an illustration of the arithmetic, 20% above a 42 Mbps video setting is about 50.4 Mbps, before adding audio, other network use or fluctuations. That calculation applies YouTube’s margin to the video setting; it is not a separate YouTube speed threshold and should not be mistaken for a guarantee that a connection will hold the stream.
The relevant question is whether the upload remains steady during a sustained test, not whether a speed test briefly reports a high peak. Shared networks, wireless interference and background transfers can reduce the capacity available to OBS. If the connection cannot reliably sustain the intended stream, consider reducing the output bitrate or using a more stable connection rather than assuming YouTube will repair inconsistent delivery.
For a channel that needs to keep broadcasting while the operator’s computer is off, a file-based cloud workflow can remove the need to leave OBS running locally; StreamNeo addresses that specific always-on computer burden. It remains important to prepare the file, confirm the YouTube channel and stream key, and choose settings appropriate to the outgoing codec and available connection.
Verify the result in a test stream
Before an important broadcast, test privately or unlisted with the same file, OBS scene, encoder and network conditions you intend to use. Include motion and audio rather than testing only a static image. A few minutes of a quiet still frame may not expose the same delivery issues as a moving video with music or speech.
Check the encoder output settings again before starting. Confirm the stream uses the intended codec, CBR, the selected bitrate and a two-second keyframe interval or documented equivalent. Then monitor YouTube Studio’s stream health while the test is running. YouTube recommends testing before going live and monitoring stream health during the event; a successful local preview alone does not confirm the ingest is healthy.
If health warnings appear, change one thing at a time and test again. First check whether available upload capacity is being shared or fluctuating. Then verify that the encoder is using the codec and bitrate you intended, and that the live output is not accidentally using recording settings. If the problem is tied to the 4K setting, remember that YouTube’s documented 4K live guidance uses normal latency; changing latency expectations will not create a low-latency 4K mode.
A test is a check of your present setup, not a permanent guarantee. Recheck after changing OBS versions, encoder options, the network, or the source format. A guide written for a previous interface can still help you navigate, but the controls visible in your own build and the result shown in stream health are the evidence to act on.
Prepare the channel and keep a recovery note
Write down the working settings that matter: output resolution and frame rate, streaming encoder, rate control, bitrate, keyframe interval and service configuration. Keep a note of where the controls appear in your own OBS version. If an update changes the layout, this record helps you re-verify the output without assuming that a remembered screenshot still matches.
For a continuous channel, decide what you will do if the local computer, connection or source file fails. A short recovery checklist might include checking the active broadcast in YouTube Studio, confirming OBS is still sending, and checking whether another application has taken upload capacity. For a playlist or music channel, make sure the next source item behaves as intended and that transitions do not leave a silent or blank interval. The guide to a continuous YouTube stream on an AWS Lightsail VPS discusses a different operating approach; choose a workflow according to how much you want to maintain yourself.
Use the settings as a starting point, then base decisions on a test of your actual outgoing stream. The right bitrate is codec-specific, and a stable connection plus a verified encoder configuration matters more than blindly copying an isolated number.
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
Is 42 Mbps enough for a 4K 30fps YouTube Live stream?
For H.264 live ingest, YouTube recommends 42 Mbps at 2160p/30 and lists 11 Mbps as the minimum. For HEVC or AV1, the recommendation is 30 Mbps, so first confirm which codec your encoder sends. A recommended bitrate does not guarantee that your connection can sustain it.
Should I use the upload bitrate for a pre-recorded live stream?
No. If you send the file through a live encoder, follow YouTube’s live-ingest settings for the outgoing codec. YouTube gives a separate 35–45 Mbps recommendation for ordinary 4K uploads at 24, 25 or 30 fps.
Where is Keyframe Interval in OBS?
Open Settings → Output, switch to Advanced output mode if needed, then inspect the streaming encoder controls. The exact label and location vary by OBS version and encoder; make sure you are not changing the recording path instead.
Can I use a keyframe interval longer than four seconds?
YouTube says not to exceed four seconds and recommends two seconds. Set two seconds where the encoder allows it, and verify the control or documented behaviour rather than following a historical forum screenshot that may describe a different interface.