What is Keyframe Interval?
Keyframe interval is the distance, measured in frames or time, between random-access points from which decoding can start cleanly. These points often use intra-coded pictures, but not every I-frame is necessarily an independent random-access point.
How Keyframe Interval works
The interval is an encoder and packaging constraint that shapes the group-of-pictures structure. Between random-access pictures, predictive frames reuse information across time, improving efficiency but increasing the amount a decoder must obtain before it can start cleanly. Encoders may place additional scene-cut keyframes, so a configured maximum does not necessarily create perfectly uniform spacing. Packaging then coordinates access points across renditions and segment boundaries for switching, seeking, thumbnails, and error recovery.
Key facts
- 1An intra-coded picture is not automatically a closed random-access point in every codec; leading pictures or references across the boundary can still affect clean entry.
- 2Adaptive renditions need matching random-access times, not merely the same nominal interval, or a bitrate switch can require decoding unavailable references.
- 3Expressing the setting only in frames changes its time duration when frame rate changes; time-based validation catches ladder outputs with inconsistent GOP lengths.
When Keyframe Interval matters
Longer intervals usually improve compression, while shorter intervals support faster seeking, switching, startup, and recovery. Segment boundaries may require aligned keyframes for reliable adaptive playback.
Common use cases for video
These examples cover video broadly, not specifically Keyframe Interval.
- Preparing uploaded video for web, mobile, connected-TV, social, or editorial playback.
- Creating clips, thumbnails, captions, alternate aspect ratios, and adaptive renditions.
- Normalizing camera, screen-recording, and user-generated files into predictable outputs.
Working with video
This guidance covers video broadly, not just Keyframe Interval.
A demuxer separates tracks from the container, decoders turn compressed streams into frames or samples, and filters apply spatial or temporal changes. Encoders compress the transformed tracks before a muxer writes the chosen output container.
Video compatibility is the product of codec, container, profile, level, frame rate, color, audio, and subtitles. Validate the complete output on target devices because a playable file on one decoder may fail or look different on another.
What you gain
- Standardized derivatives make diverse source files playable on target devices.
- A retained master can feed many resolutions, aspect ratios, codecs, and channels.
- Automated inspection and transformation make large upload volumes consistent.
What it costs
- More efficient codecs can lower bitrate at similar quality but usually cost more compute and may have narrower support.
- Higher resolutions and frame rates preserve more detail and motion while increasing processing and delivery requirements.
- Fast encoding settings improve throughput but can produce larger files or lower quality than slower analysis.
Before production
- 1Inspect codec, container, dimensions, frame rate, color, audio, and subtitle tracks.
- 2Test visual quality and playback support across the slowest and oldest target devices.
- 3Preserve a suitable master before applying lossy, destructive, or delivery-specific changes.