Keyframe Interval Explained: OBS, Streaming & FFmpeg Guide

Is your stream buffering every few seconds? Or maybe you've tried to edit a recording and found that cutting between scenes leaves a frozen, ghosted mess on your timeline? The culprit might be a single setting you've never touched: the keyframe interval.

I've lost count of how many times I've seen streamers tear their hair out over playback issues, only to discover that OBS had defaulted their keyframe interval to 8 seconds. That's an eternity in streaming terms. The good news? Fixing it takes about ten seconds once you understand what's happening under the hood.

This guide walks through everything you need to know about keyframe intervals—what they are, how they affect your video encoding, and the exact settings you should use for streaming, recording, and even FFmpeg command-line work.

What is a Keyframe Interval? (And Why It Matters in Video Encoding)

Let's start with the basics. A keyframe interval is the frequency at which full frames (called I-frames or keyframes) appear in your video stream. Think of it as the heartbeat of your video—every so often, the encoder sends a complete picture, and between those beats, it only sends the changes.

Keyframes vs. Predictive Frames: The Basics

To understand keyframe intervals, you need to know about the different frame types in video compression. Video encoders like H.264 don't store every single frame as a full image—that would be insanely inefficient. Instead, they use three frame types:

• I-frames (keyframes): These store the complete image. They're your reference points.
• P-frames (predictive frames): These store only the changes from the previous frame.
• B-frames (bi-directional frames): These store changes by looking at both past and future frames.

Here's a simple analogy: a keyframe is like a map of a city, while P-frames and B-frames are like turn-by-turn directions. The map gives you the full picture. The directions just tell you "turn left here" or "continue straight"—they only make sense if you have a starting point.

The collection of frames between two keyframes is called a GOP (Group of Pictures) . The keyframe interval essentially determines the length of your GOP. A 2-second interval at 30 FPS means a new keyframe every 60 frames, so your GOP length is 60.

How Keyframe Interval Affects File Size, Quality, and Seekability

The interval you choose creates a trade-off triangle: file size, error recovery, and editability.

Shorter intervals (more keyframes):

• Larger file sizes (keyframes are data-heavy)
• Easier seeking—you can jump to any point quickly
• Better error recovery—if a frame gets corrupted, the player doesn't have to wait long for the next keyframe
• Smoother editing experience

Longer intervals (fewer keyframes):

• Smaller file sizes
• Better compression efficiency
• Risk of corruption spreading across more frames
• Painful editing—more on this later

Here's a rough comparison I put together from my own tests with a 1080p, 30-second test clip at 10 Mbps:

Best Keyframe Interval for Streaming: OBS, Twitch, and YouTube Settings

When it comes to live streaming, the best keyframe interval for streaming isn't really up for debate—it's 2 seconds. Full stop. Here's why.

The 2-Second Rule: Why Twitch and YouTube Recommend It

Twitch, YouTube, Facebook Live, and Kick all recommend a 2-second keyframe interval. This isn't arbitrary. It's the sweet spot that balances:

• Latency: Shorter intervals mean players can join mid-stream faster.
• Error recovery: If a viewer's connection hiccups, the player needs a keyframe to resync. Two seconds is short enough that the recovery is seamless.
• Bandwidth: Keyframes are expensive in terms of data. Every keyframe is a full frame, so sending them too frequently wastes bandwidth.

At 30 FPS, 2 seconds equals 60 frames. At 60 FPS, it's 120 frames. Most encoders express this as a frame count, so you'll need to do the math based on your frame rate.

Here's a quick reference table for platform requirements:

Keyframe Interval 2 vs 4: What's the Real Difference?

So what happens if you set your keyframe interval to 4 seconds instead of 2? In my testing, the visual quality difference is negligible for most content. The problems show up in other ways.

With a 4-second interval, viewers who join your stream mid-broadcast might wait up to 4 seconds before seeing anything. On low-end devices, seeking becomes sluggish. And if a network packet gets lost, the player has to wait longer for the next keyframe to recover.

That said, there are scenarios where 4 seconds is acceptable. If you're streaming a static scene—a talking head with minimal movement, a slideshow, a desktop with no motion—the longer interval won't hurt you. The encoder is already producing tiny P-frames because nothing is changing.

But here's the warning I give everyone: do not use 0 (auto) in OBS. The auto setting defaults to approximately 8 seconds, which is terrible for streaming. I've seen this cause buffering issues on Twitch more times than I can count. The platform's ingest servers expect keyframes at regular intervals, and 8 seconds is too sparse.

How to Set Keyframe Interval in OBS Studio (Step-by-Step)

Setting this in OBS takes less than a minute:

1. Open OBS Studio and go to Settings > Output.
2. Switch the Output Mode to Advanced if it isn't already.
3. Under the Streaming tab, find the Keyframe Interval field.
4. Enter 2 (this means 2 seconds, regardless of your frame rate).
5. Click Apply and OK.

One thing to note: if you're using a hardware encoder like NVENC, the keyframe interval setting works the same way. The encoder respects the value you enter. With x264 (software encoding), you get more granular control, but the 2-second rule still applies.

For recording, you'll want to set the keyframe interval in the Recording tab separately. I'll cover the recommended recording values in the next section.

Keyframe Interval for Recording: Optimizing for Editing and 60FPS

Streaming and recording have different priorities. When you're live, you're optimizing for bandwidth and latency. When you're recording, you're optimizing for editability. This is where the keyframe interval for YouTube upload 1080p content becomes relevant.

Best Keyframe Interval for 60FPS Recording

For recording, I recommend a 1-second keyframe interval. At 60 FPS, that means a keyframe every 60 frames. At 30 FPS, it's every 30 frames.

Why so aggressive? Because video editors need keyframes to cut and scrub efficiently. When you're editing a 60 FPS recording, you want to be able to jump to any point in the timeline and see an accurate preview. With a 2-second interval, your editor has to decode up to 120 frames of P-frames before showing you the frame you clicked on. That's slow.

The file size trade-off is real, but manageable. A 1-second interval at 60 FPS with a higher bitrate (say, 20 Mbps for 1080p) will give you excellent quality and smooth editing. Storage is cheap; your time isn't.

Why a High Keyframe Interval Ruins Video Editing

Here's the scenario I run into with clients all the time: they record a gaming session with the default OBS settings (8-second keyframe interval), then try to edit it in Premiere Pro or DaVinci Resolve. The result? When they cut between clips, the preview freezes or shows ghosting artifacts. The timeline scrubbing feels like wading through molasses.

This happens because most NLEs (non-linear editors) struggle with GOPs longer than 4 seconds. When you make a cut, the editor needs to decode from the nearest keyframe to the exact frame you want. With an 8-second interval, that means decoding up to 240 frames (at 30 FPS) just to show you one frame.

The rule of thumb I give everyone: 1 second for recording, 2 seconds for streaming. If you're doing both simultaneously (streaming while recording), set the streaming interval to 2 and the recording interval to 1. OBS handles these independently.

Advanced: Setting Keyframe Interval with FFmpeg and Hardware Encoders

For the command-line crowd, FFmpeg gives you precise control over keyframe placement. This is where the keyframe interval ffmpeg workflow comes into play.

FFmpeg Command for Keyframe Interval Every 2 Seconds

The key parameter in FFmpeg is -g, which sets the GOP size (the number of frames between keyframes). To get a 2-second interval at 30 FPS, you'd use -g 60. At 60 FPS, it's -g 120.

Here's a complete example for H.264 encoding:

ffmpeg -i input.mp4 \
  -c:v libx264 \
  -g 60 \
  -keyint_min 60 \
  -sc_threshold 0 \
  -c:a aac \
  output.mp4

Let me break down what each flag does:

• -g 60: Sets the GOP size to 60 frames (2 seconds at 30 FPS).
• -keyint_min 60: Ensures the minimum keyframe interval is also 60 frames. Without this, the encoder might insert extra keyframes when it detects scene changes.
• -sc_threshold 0: Disables scene change detection. This forces the encoder to stick strictly to your GOP size. If you want the encoder to add keyframes on scene changes (which can be useful), remove this flag.

For H.265 (HEVC), the same flags apply:

ffmpeg -i input.mp4 \
  -c:v libx265 \
  -g 60 \
  -keyint_min 60 \
  -sc_threshold 0 \
  -c:a aac \
  output.mp4

NVENC vs x264: Does the Encoder Change the Ideal Interval?

The short answer: no, the 2-second rule still applies regardless of encoder. But there are differences in how encoders handle keyframes.

NVENC (hardware encoding):

• Faster encoding with minimal CPU usage
• Less control over GOP structure
• Keyframe placement is generally reliable but less flexible
• Ideal for live streaming where latency matters

x264 (software encoding):

• Slower but better compression efficiency
• Full control over GOP structure, B-frame placement, and scene detection
• Better quality at the same bitrate
• Ideal for recording where quality is the priority

In my experience, NVENC's keyframe handling is perfectly fine for streaming. The quality difference between NVENC and x264 has narrowed significantly in recent generations of GPUs. For recording, I still prefer x264 for maximum quality, but NVENC with a higher bitrate is a perfectly viable alternative.

Keyframe Interval vs Keyframe: Clearing Up the Confusion

This is one of the most common points of confusion I see in forums and comment sections. People use "keyframe" and "keyframe interval" interchangeably, but they're not the same thing.

What is a Keyframe?

A keyframe (or I-frame) is a single frame in your video that contains the complete image data. It's a reference point that doesn't depend on any other frame. When you're scrubbing through a video, these are the frames your player can jump to instantly.

Why the Distinction Matters for Your Settings

The keyframe interval vs keyframe distinction comes down to this: a keyframe is a single frame, while the interval is the distance between keyframes.

Think of it like bus stops. A bus stop is a specific location (the keyframe). The distance between bus stops is the interval. You can't say "I want more bus stops" without also deciding how far apart they should be.

When you set "keyframe every 1 second" in OBS, you're not choosing a type of keyframe—you're choosing how frequently they appear. This distinction matters because it affects everything we've discussed: file size, seekability, and editing performance.

Troubleshooting: Symptoms of a Bad Keyframe Interval

Sometimes you don't know your keyframe interval is wrong until something breaks. Here's how to diagnose the most common symptoms.

Buffering, Stuttering, and Playback Issues

If your stream or recording exhibits any of these symptoms, your keyframe interval might be the culprit:

How to Test Your Keyframe Interval Setting

If you're not sure what your current keyframe interval is, you can check it with ffprobe. Here's a command that lists all keyframes in a video:

ffprobe -select_streams v -show_frames -show_entries frame=pict_type -of csv input.mp4

The output will show a line for every frame with its type (I, P, or B). Count the frames between I-frames to determine your actual keyframe interval.

For a more concise view, you can use:

ffprobe -select_streams v -show_frames -show_entries frame=pict_type -of csv input.mp4 | grep "I" | head -20

This shows the first 20 keyframes. The frame numbers will tell you the interval. If you see I-frames at frames 0, 60, 120, etc., you have a 2-second interval at 30 FPS.

FAQ

What is a good keyframe interval for OBS?

For streaming, set it to 2 seconds. For recording, use 1 second. Avoid the "0" (auto) setting, which defaults to approximately 8 seconds and causes buffering and editing problems.

Does keyframe interval affect video quality?

Not directly. The interval doesn't change the visual quality of individual frames. However, it affects error recovery and editing. A too-high interval can cause visible artifacts after seeking or when frames are lost during transmission.

What is the difference between keyframe and keyframe interval?

A keyframe is a single full frame (I-frame) that stores complete image data. The keyframe interval is the distance between keyframes. Think of it as the difference between a bus stop and the distance between bus stops.

What happens if keyframe interval is too high?

You'll experience buffering, slow seeking, editing problems, and potential frame drops on low-end devices. The player has to wait for the next keyframe to resync, and longer intervals mean longer waits.

Conclusion

The golden rule is simple: 2 seconds for streaming, 1 second for recording. This single setting balances video quality, bandwidth usage, and editability in a way that works across platforms and use cases.

But don't just take my word for it—test your specific setup. Every encoder, GPU, and streaming platform has its quirks. Run a test stream, check your recording, and see what works best for your hardware and content type.

The keyframe interval is one of those settings that's easy to ignore but can make or break your streaming and recording experience. Now that you understand what it does and how to configure it, you can stop fighting your encoder and focus on creating great content.

Have questions about your specific setup? Drop them in the comments below—I read every one and I'm happy to help you dial in your settings.