Stutter is a visible hitch or jerk in a game’s motion caused by frames that arrive at irregular intervals, usually when a single frame takes much longer to produce than the frames around it. In gaming performance, stutter is distinct from a low frame rate: a game can report a high average fps and still stutter badly, because the problem lies in the consistency of frame delivery rather than in its average speed.
Players describe stutter as micro-freezes, hitching or judder. Technically, it shows up as spikes in frame time, the number of milliseconds each frame takes, and it is the main reason why reviewers measure 1% lows and frame time graphs in addition to average frame rates.
How stutter appears in frame time
Smooth motion requires frames to arrive at even intervals. At 60 fps, each frame should take about 16.7 milliseconds; at 120 fps, about 8.3 milliseconds. When one frame suddenly takes 50 or 100 milliseconds, the image freezes briefly and then jumps forward, and the eye perceives that jump as stutter.
Averages hide this effect. A game that renders 59 frames in 10 milliseconds each and one frame in 410 milliseconds still averages 60 fps over that second, yet the player sees a clear freeze. That is why frame time graphs and percentile metrics describe smoothness far better than an fps counter.
| Target frame rate | Frame time budget | Spike that feels like stutter |
|---|---|---|
| 30 fps | 33.3 ms | Above roughly 60 ms |
| 60 fps | 16.7 ms | Above roughly 30 ms |
| 120 fps | 8.3 ms | Above roughly 20 ms |
| 144 fps | 6.9 ms | Above roughly 15 ms |
The thresholds in the last column are rough guides, not a standard. Sensitivity to spikes varies between people and depends on how fast the camera is moving, since fast panning makes hitches far more visible than a static scene.
Common causes of stutter
Stutter almost always means that some piece of work blocked the frame for longer than the budget allowed. The cause can sit in the game engine, the driver, the operating system or the hardware, which is why diagnosing stutter requires looking beyond the GPU alone.
| Cause | Mechanism | Typical pattern |
|---|---|---|
| Shader compilation | Shaders compiled the first time an effect appears | Hitches on new effects, fewer on later runs |
| Asset streaming | Textures or geometry loaded while moving | Hitches when entering new areas |
| Traversal stutter | World sections loaded or unloaded at boundaries | Hitch at the same spots every time |
| VRAM overflow | Data swapped between GPU and system memory | Frequent spikes at high texture settings |
| CPU bottleneck | Game logic or draw calls exceed the budget | Spikes in busy scenes and crowds |
| Background tasks | Updates, scans or overlays steal CPU time | Random spikes unrelated to the scene |
On PC, shader compilation stutter is one of the most discussed problems, because consoles can ship precompiled shaders for one fixed GPU while PC games must compile them for many different GPUs and drivers. A shader cache reduces the problem on later runs, but driver updates can invalidate it.
Stutter compared with related performance problems
Stutter is often confused with neighboring problems that feel similar but have different causes. Separating them matters, because each one needs a different fix.
| Problem | What the player notices | Root cause |
|---|---|---|
| Stutter | Occasional freezes or jumps | Individual long frames |
| Poor frame pacing | Constant uneven motion despite good fps | Frames delivered at alternating intervals |
| Low frame rate | Consistently choppy motion | Every frame is too slow |
| Screen tearing | Horizontal split in the image | Frame shown mid-refresh without sync |
| Input lag | Delayed response to controls | Long pipeline between input and display |
| Network lag | Players or objects teleporting | Netcode and connection delay |
Frame pacing problems are the closest relative. A 30 fps game that alternates between 16 and 50 millisecond frames looks worse than one that delivers a steady 33 milliseconds, even though both average 30 fps.
Measuring and reducing stutter
The reliable way to confirm stutter is a frame time overlay or capture tool that records every frame. A flat line indicates smooth delivery; tall isolated spikes indicate stutter. The 1% low and 0.1% low values summarize how slow the worst frames are, and a large gap between the average and the 1% low points to inconsistency.
Fixes depend on the cause, but several measures help in many situations.
- Use a frame rate cap slightly below what the system can sustain, so the GPU and CPU keep spare time for heavy frames.
- Enable VRR with G-SYNC or FreeSync, which hides small timing variations by adjusting the display’s refresh rate.
- Lower texture quality when VRAM usage approaches the card’s capacity.
- Install games on an SSD, since streaming from a hard drive causes far more hitches.
- Let shader precompilation finish before playing, when a game offers it.
Some stutter cannot be fixed by the player. Traversal and compilation stutter built into the engine need a game patch, and no amount of hardware fully removes them, which is why even very fast PCs can stutter in poorly optimized ports.
In everyday language
Stutter is when a game suddenly freezes for a split second and then jumps ahead, like a video that skips. It can happen even when the game normally runs fast.
Imagine a train that usually arrives every five minutes but sometimes takes twenty. The average may look fine on paper, but passengers remember the long waits. Smooth games depend on steady timing, not only on speed.
Seen in the real world
A player with a powerful PC installs a new open-world game and sees an average of 110 fps, yet the camera hitches every time a new enemy type or spell effect appears for the first time. A frame time overlay shows isolated spikes of 80 to 150 milliseconds, while normal frames sit around 9 milliseconds.
The pattern points to shader compilation. The player enables the game’s optional shader precompilation step in the settings, waits about ten minutes for it to finish, and caps the frame rate at 100 fps with VRR enabled on a 144 Hz monitor.
On the next session, the large spikes almost disappear, the 1% low rises from about 40 fps to around 85 fps, and the remaining small hitches occur only when crossing into new regions of the map.