For YouTube Live, set the keyframe interval to 2 seconds in OBS. YouTube recommends that frequency and says not to exceed 4 seconds; at 30 frames per second, a two-second interval is 60 frames.
A keyframe interval is the time, or corresponding number of frames, between complete reference frames in the encoded video. In OBS, where you find and enter it depends on the output mode and encoder, so check whether the field expects seconds or frames before changing it.
YouTube’s recommended keyframe interval
YouTube’s live encoder guidance recommends a keyframe frequency of two seconds and sets four seconds as the upper limit. For an OBS stream going to YouTube, use two seconds as the target. The recommendation is specific to YouTube’s published live settings; do not assume that another platform’s requirements apply here.
YouTube publishes a wider set of encoder guidance alongside the interval. Its current RTMP/RTMPS settings list H.264, H.265 (HEVC) and AV1 video, frame rates up to 60 fps, constant bitrate encoding, and AAC or MP3 audio. It recommends RTMPS for encrypted transport. These are YouTube’s published options, not a guarantee that every codec is available in your OBS encoder or on your computer. Check YouTube’s live encoder settings and confirm what your selected OBS encoder actually supports.
The interval is not a quality preset by itself. It works with frame rate, codec and the rest of the encoder configuration. A two-second interval does not tell you what resolution or bitrate to choose, and changing it will not fix an overloaded encoder or an unstable internet connection. For those decisions, use YouTube’s guidance and your own stream-health results rather than copying settings intended for another platform.
If you are new to broadcasting, first confirm that your channel can go live and that YouTube Studio recognises the stream. Our guide to enabling YouTube live streaming for the first time covers that separate prerequisite. Once the channel and ingest are ready, the keyframe setting is one item to verify in the encoder.
Why keyframes matter to a stream
A video encoder does not need to store every frame as a wholly independent image. It can encode changes in relation to other frames, while a keyframe provides a more complete reference point from which later frames can be decoded. The interval describes how often those reference points are sent.
That timing matters to a live platform receiving and processing an encoded stream. YouTube’s guidance gives you a concrete target: keyframes every two seconds, with no more than four seconds between them. The practical aim is to match that requirement consistently, not to pursue the shortest possible interval without regard to the rest of your setup.
Think of the interval as one part of the outgoing video format. If the stream is otherwise configured correctly but the actual keyframes arrive less often than YouTube expects, YouTube may report a keyframe-frequency problem. Conversely, changing the interval is not a general repair for dropped frames, an upload connection that cannot sustain the selected bitrate, or audio problems. Diagnose the warning you see rather than treating every stream-health message as the same fault.
For a 24/7 channel, a small configuration mismatch can be easy to miss during a brief test and then persist after you leave the computer. The useful habit is to verify the setting and inspect YouTube’s stream health after the encoder connects. If the stream is part of a larger continuous setup, this guide to measuring live-stream quality of experience can help you distinguish an encoder issue from other delivery problems.
Find the keyframe setting in OBS
In OBS, look in the output settings for the encoder used for streaming. The location and available controls depend on whether Output Mode is Simple or Advanced, which encoder is selected, and the OBS version. In Advanced mode, the relevant control is commonly in the Streaming section of Output settings, but treat that as a place to inspect rather than a promise that every OBS installation has the same field or label.
The general route to check is Settings > Output. If the interface offers an Output Mode selector, inspect the streaming controls for the chosen mode and encoder. A field called Keyframe Interval or similar may be displayed in seconds. Some encoder configurations instead expose codec parameters, where a keyframe interval is expressed as a frame count. Do not infer the input format from the field name alone; read its units or encoder documentation.
OBS Project forum guidance discusses the distinction between an Advanced Output interval expressed in seconds and custom x264 keyint parameters expressed as frames. The forum discussion is useful for understanding the units, but it is not a current universal OBS manual. Controls can change, and service-specific configurations may affect what OBS displays. If your interface differs, consult the documentation for your OBS version and selected encoder.
An AWS guide to setting up OBS for Amazon IVS also illustrates a path through Advanced Output to a streaming keyframe field. That example is for IVS, not YouTube, so it can corroborate where a control may appear without establishing YouTube’s requirement. Use YouTube’s two-second recommendation as the target, not another service’s guide.
Before editing, note the current mode, encoder and value. If you switch modes or encoders, check the interval again; a setting shown in one configuration may not describe the output produced by another. This is especially important if you are using a custom encoder parameter rather than a dedicated OBS field.
Set a two-second interval
If the OBS streaming control explicitly asks for seconds, enter 2. Do not enter 2 into a field that asks for frames: that would mean two frames, not two seconds. At a frame rate of 30 fps, enter 60 only when the encoder parameter is a frame count and its documentation confirms that interpretation.
After changing the value, apply the settings and make a test broadcast to YouTube before relying on it for a long session. Confirm the stream is being received in YouTube Studio and inspect its health information. YouTube recommends testing with audio and movement similar to the real event, then monitoring stream health while live. A quiet test image may not reveal issues that show up when your usual content moves or changes.
If you already have an established OBS profile, keep the rest of the encoder setup stable while checking the interval. Changing several variables together makes it harder to tell which change helped or caused a new warning. Record the selected frame rate and the interval units so that you can restore a known configuration if needed.
A continuous broadcast also needs to survive more than a successful short test. If your channel relies on a playlist or a machine that must remain running, consider how the broader setup behaves when your computer, connection or encoder stops. StreamNeo can remove the need to keep your own computer running for a file-based 24/7 YouTube broadcast, so you do not have to maintain an OBS session solely to keep that uploaded video on air.
Convert seconds to frames when needed
The conversion is straightforward when an encoder parameter requires a frame count: multiply the frame rate by the interval in seconds. For YouTube’s two-second target, the calculation is frame rate × 2. At 30 fps, that is 30 × 2 = 60 frames. YouTube’s troubleshooting guidance uses this same 30 fps, 60-frame example.
| Frame rate | YouTube target interval | Frame-count equivalent |
|---|---|---|
| 24 fps | 2 seconds | 48 frames |
| 30 fps | 2 seconds | 60 frames |
| 60 fps | 2 seconds | 120 frames |
The table shows the arithmetic for common frame rates, not a recommendation to use any particular frame rate. Choose a frame rate that suits your content, equipment and available connection, then calculate the frame count only if the control genuinely requires it. If OBS asks for seconds, use seconds instead of converting.
For example, at 30 fps, a keyint value of 60 corresponds to two seconds. At 60 fps, the same value corresponds to one second, not two. If the frame rate changes, recalculate rather than carrying a frame-count value across unchanged. A seconds-based setting avoids that particular conversion, but you still need to confirm that the outgoing encoder honours it.
Do not mix up keyframe interval with bitrate, frame rate or the number of frames in a video file. They describe different parts of the stream. If you are using a custom parameter, verify the parameter’s meaning with the encoder documentation; the fact that a field accepts a number does not tell you whether that number represents frames, seconds or something else.
Check YouTube’s stream and troubleshoot warnings
Once OBS is sending video, check YouTube Studio’s stream preview and health notices. A displayed OBS value is evidence of your intended configuration, but it does not by itself prove that the stream arriving at YouTube has the expected GOP size. YouTube’s live-stream error guidance says that incorrect GOP sizes can also arise from ingestion errors, so a persistent warning calls for checking the outgoing stream as well as the UI.
If YouTube reports an incorrect keyframe frequency, first confirm that the selected streaming encoder is configured for two seconds. Check the units, the active OBS profile and the frame rate. For a frame-count parameter, recalculate it from the actual frame rate. If you have more than one OBS scene collection or profile, make sure you are checking the one used for the live broadcast.
YouTube’s troubleshooting advice is direct: “Change so that keyframes are sent every 2 seconds.” If the warning remains after you have checked the configuration, investigate whether the encoder is applying the change and whether the ingest itself is producing the reported GOP problem. Avoid repeatedly changing unrelated settings without evidence. The YouTube live-stream error messages page is the right place to check current official troubleshooting steps.
Also separate a keyframe warning from other health issues. A warning about bitrate, dropped frames or connection stability may need a different response. YouTube recommends selecting a quality that is reliable for the available upload connection. Testing with representative audio and movement, then observing health while the stream runs, gives you more useful evidence than assuming a single encoder setting accounts for every interruption.
For an always-on broadcast, keep a short record of the profile, encoder, frame rate and keyframe units that passed your test. If you later update OBS, change encoders or alter the frame rate, verify the interval again. If you use an automated playlist or script, include the active encoder settings in your checks; this guide to running an FFmpeg playlist at boot for YouTube Live covers a different workflow, but the same principle applies: verify the output, not only the saved configuration.
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 should my keyframe interval be for YouTube Live in OBS?
Set it to 2 seconds. YouTube recommends keyframes every two seconds and says the frequency should not exceed four seconds. Check whether your OBS control expects seconds or a frame count before entering the value.
Is a keyframe interval of 2 the same as 2 frames?
Only if the specific encoder field says it measures frames. A seconds-based OBS field uses 2 to mean two seconds; a frame-count parameter uses a number of frames. At 30 fps, two seconds is 60 frames.
Why does YouTube still show a keyframe warning after I set it to 2?
The value shown in OBS may not reflect the GOP size actually reaching YouTube, and YouTube notes that ingestion errors can cause incorrect GOP sizes. Check the active encoder and units, then inspect YouTube’s current troubleshooting guidance if the warning continues.
Does this setting control video quality or stability by itself?
No. It is one encoder setting among several and does not replace a suitable bitrate, frame rate or reliable connection. Test with content like your real broadcast and monitor YouTube stream health.