A keyframe is commonly used to describe a coded video picture that provides an important decoding access point. Many compressed pictures depend on other pictures, so starting at an arbitrary timestamp may require the decoder to begin earlier and reconstruct those dependencies. The precise meaning depends on codec and picture structure: an intra-coded picture and a clean random-access point are not always identical concepts. Keyframe placement affects channel startup, seeking and recovery after missing data. It differs from frame rate, which describes how many pictures are presented over time, and from segment duration, which describes a delivery container's time span.
Keyframe and Every frame
Many compressed pictures depend on other pictures and are not independent starting points.
Seeking needs a decodable starting point
A viewer can request a position between access points. The player may fetch an earlier portion, decode forward and display the requested moment, or land near an available access point according to its seeking mode. This is one reason a seek can take time even when the network is fast. The index, container and player implementation also affect how accurately the requested position is found.
More frequent access points have tradeoffs
Frequent clean access points can help random access and error recovery, but they can change compression efficiency and encoding choices. A longer interval can reduce opportunities to start decoding independently. Those are source-encoding decisions rather than settings every player can alter. Raising a display refresh rate or reinstalling an app does not insert new access points into an already encoded stream.
Use the symptom to locate the layer
If playback is smooth after startup but each seek pauses at predictable intervals, access-point spacing and indexing are useful topics for the publisher or operator. Constant stutter during normal playback has a broader set of causes. Record the requested position, actual landing point, source and player version. Avoid claiming a stream's keyframe interval without inspecting media metadata or receiving that information from its operator.
An illustrative example
A viewer seeks to 12:13 in a video whose suitable access points are spaced several seconds apart. The player begins decoding from an earlier point and advances to the requested scene. A short delay can arise from that reconstruction work, even though the selected time is valid and network downloads remain healthy.
Practical actions
- Record requested and actual seek positions for repeatable seeking problems.
- Keep keyframe interval separate from frame rate and segment duration.
- Ask the operator or publisher to inspect access points and indexing when evidence fits.