Buried in your encoder settings is a field called keyframe interval, and almost every platform tells you to set it to 2. Most people obey without knowing why, then wonder why their stream misbehaves when they leave it on auto. Here is what a keyframe actually is and why the number matters.
What a keyframe is
Video does not send a full picture every frame. It sends occasional complete frames, called keyframes (I-frames), then describes the changes in between with much smaller frames. The keyframe interval is how often a full picture is sent. A 2-second interval at 60 fps means a fresh keyframe roughly every 120 frames.
Why platforms want 2 seconds
| Interval | Effect on viewers | Effect on bitrate |
|---|---|---|
| 1 second | Fast joins/seeks | Higher (more full frames) |
| 2 seconds | Platform standard | Balanced |
| 4+ seconds | Slow seeks, playback errors | Lower |
| Auto/0 | Unpredictable | Can break DVR/latency |
What goes wrong without it
Platforms slice your stream into short segments that must begin on a keyframe. If your keyframes are irregular (auto mode) or too far apart, the platform cannot cut clean segments, which causes playback stalls, broken low-latency mode, and viewers who cannot seek in the VOD. Setting a fixed 2-second interval gives the platform a predictable cut point and fixes a surprising number of “my stream is laggy” reports.
Does it hurt quality?
Slightly and rarely. Keyframes are larger than the in-between frames, so more frequent keyframes spend a bit more of your bitrate on repetition. At a 2-second interval on a 6,000 kbps stream the cost is negligible, and the compatibility payoff is worth it. Only extremely bitrate-starved setups benefit from stretching the interval, and even then the platform errors usually are not worth it.
Where to set it
In OBS the field is in Output settings under your encoder as “Keyframe Interval,” measured in seconds. Set it to 2. Leave it at 2 for Twitch, YouTube, and Kick unless a specific platform’s guide tells you otherwise. If you use low-latency mode, keeping a fixed short interval is what makes that mode stable.
How keyframes interact with low-latency mode
Keyframes matter even more when you turn on a platform’s low-latency mode, which shrinks the delay between you and your viewers to a couple of seconds so chat feels conversational. That mode relies on cutting the stream into very short segments, and every segment must start on a keyframe. An irregular or long interval starves the platform of clean cut points, so low-latency mode either falls back to normal latency or stutters. A fixed two-second interval is what keeps it stable.
This is also why “auto” keyframe mode causes such odd, hard-to-diagnose problems. On auto, the encoder places keyframes based on scene changes, so a static menu might go many seconds without one while a busy scene spams them. Viewers then experience uneven seeking, broken clip creation, and playback hiccups that look like a network issue but are really an encoder setting. Fixing it is free: set the interval to two seconds, confirm it stuck, and a whole cluster of vague complaints tends to disappear at once.
FAQ
Is auto keyframe ever fine?
For local recording, yes, since there is no platform segmenting your file. For live streaming, always set a fixed 2-second interval to avoid playback and latency problems.
Should I use 1 second for low latency?
Two seconds already supports low-latency mode on major platforms. Only drop to 1 if a platform explicitly recommends it, since it raises bitrate overhead.
Bottom line
Set your keyframe interval to a fixed 2 seconds and stop thinking about it. It costs almost no quality, keeps low-latency mode stable, and prevents the segment-boundary errors that make an otherwise fine stream feel broken. Auto mode is only safe for local recordings.
