Why does a game stutter when the FPS looks fine? Frame time and 1% lows explained

FPS is an average, and averages hide things

Your game says 60 FPS, yet it feels choppy. That is not your imagination. FPS (frames per second) counts how many pictures your PC drew in the last second. It says nothing about when in that second they arrived. Sixty frames can show up like a metronome, or they can bunch together and then leave a gap. Both add up to 60.

The gap is what you feel. Your eyes follow a moving object and expect it to shift a little each frame. When one frame takes far too long, the object freezes and then jumps. That jump is stutter.

Frame time: how long each picture takes

Frame time is the number of milliseconds (ms) between one frame and the next. It is the same information as FPS, turned upside down: divide 1000 by the FPS. A smooth 60 FPS means a new frame every 16.7 ms, again and again.

Frame time shows what an FPS counter smooths away. If most frames take 14 ms and one takes 80 ms, the counter still reads a healthy number, but you saw a freeze nearly five frames long.

Try it: the same FPS, a very different feel

Both lanes below average the same frame rate. The top lane delivers frames evenly. In the bottom lane, drag the slider to add occasional slow frames. The dot in each lane moves at the same speed, and it only updates when a new frame arrives, just like a game does. Watch the bottom dot hitch while the average number barely moves.

What 1% lows tell you

Many reviewers and overlay tools report 1% lows next to the average. The idea is to take the slowest 1% of frames and convert them into an FPS number. If the average is 60 but the 1% low is 25, those worst moments felt like 25 FPS. A small gap between the two numbers means steady pacing. A large gap means stutter, even when the average looks fine.

Tools calculate this slightly differently, so only compare 1% lows measured the same way. Use them as a warning light, not a precise score.

What causes stutter

Stutter happens when something makes a single frame wait. The common culprits:

Running out of VRAM. When the graphics card's memory is full, data has to be swapped in from slower memory, and frames stall. Lower texture quality is the usual fix.

Slow loading from storage. Open-world games stream the world in as you move. Installing on an SSD instead of a hard drive helps a lot.

Shader compilation. Some games prepare graphics code the first time an effect appears, which can freeze a frame. It often calms down after the first play session.

Background programs and heat. A browser, an update, or a hot, throttling processor can steal time from the game at random moments.

What to look for

You do not need to buy anything to start. Try these in order: close background programs, make sure the game is on an SSD, update your graphics driver, then lower texture quality if your VRAM is nearly full. Capping your FPS slightly below what your PC can hold steadily also keeps frame times even, because the game stops swinging between fast and slow.

Then judge smoothness by feel and by frame time, not by the FPS number alone. If a game says 60 and feels like 40, trust your eyes and look at the worst frames, not the average.