Frame pacing describes how evenly frames are delivered over time. A game can report a high frame rate (FPS) and still feel uneven if individual frames arrive at inconsistent intervals. Smoothness comes from consistent timing between frames, not just a high average number.
This is why frame pacing is usually explained using frametime rather than FPS. Frametime measures how long each frame takes to appear, typically in milliseconds. At 60 FPS, the ideal frametime is about 16.7ms per frame. When pacing is stable, each frame lands close to that interval. When frametimes fluctuate widely, the result is visible judder or micro-stutter, especially during camera movement.
FPS counters can be misleading because they often show an average over time. A game might alternate between very fast frames and much slower ones, still averaging out to a respectable number. The problem is that players experience each frame individually. Large swings in frametime create uneven motion even when the average FPS looks fine.
Poor frame pacing usually appears as stutter or micro-stutter. These feel like brief hitches or tiny pauses that interrupt motion. On a frametime graph, smooth pacing looks like a mostly flat line with small variation, while stutter shows up as spikes where individual frames take much longer than the surrounding ones.
It is also important to separate frame pacing from other, similar issues. Low FPS means consistently long frametimes, which can feel slow but still smooth. Screen tearing is a presentation artefact where parts of multiple frames appear in a single refresh. Frame pacing problems are about inconsistency between frames, not incomplete frames being shown.
Frame pacing can be affected by both the game and the system. Anything that causes uneven work from one frame to the next can disrupt pacing, including CPU simulation spikes, asset streaming, shader compilation, or background tasks. These issues change how long individual frames take, even if overall performance seems stable.
Because pacing is about when frames appear, it intersects with presentation control. V-Sync synchronises frame presentation to the display’s refresh rate, which can reduce tearing but may introduce stutter if the system cannot meet the refresh target consistently. Variable refresh rate (VRR) technologies approach the same problem by adjusting the display’s refresh timing to better match frame delivery when performance fluctuates.
From my own experience, frame pacing issues are most obvious during slow camera pans, where motion should look continuous but instead feels slightly uneven even though the FPS counter barely moves.
Understanding frame pacing helps explain why two games running at the same FPS can feel completely different in motion. It shifts the focus from raw performance numbers to consistency, which is often what players notice first when something feels “off” during play.