If average FPS is the metric that misleads, frame time is the one that tells the truth. Frame time is the gap, in milliseconds, between one frame and the next — and it's the consistency of those gaps, not their average, that your eyes register as smoothness or stutter. This is why a game at 90 FPS can feel worse than one at a steady 60: uneven frame times produce microstutter the average FPS can't show. This article explains frame time, frame-time variance, and why it's the real measure of smoothness.
It's the deeper companion to what FPS is and why it misleads, and part of understanding benchmark scores properly.
Frame Time Is the Inverse of FPS — but More Honest
Mathematically, frame time and FPS are linked: 60 FPS averages about 16.7ms per frame, 120 FPS about 8.3ms. But where FPS averages over a whole second, frame time can be measured frame by frame — exposing the variance the average hides. A run that averages 90 FPS might deliver frames at 8ms, 9ms, 8ms, then a sudden 40ms — and that one long frame is a visible hitch, even though the average still looks great.
Why Variance Causes Stutter
- Your eyes track consistency: a steady cadence of frames reads as smooth; an irregular one reads as juddery, even at a high average rate.
- Microstutter: small, frequent frame-time spikes produce a subtle unevenness that's hard to name but easy to feel — and invisible on an FPS counter.
- The 90-can-feel-worse-than-60 effect: a steady 60 FPS (consistent ~16.7ms frames) often feels smoother than a 90 FPS average riddled with spikes.
This is exactly the kind of problem behind games that stutter despite a good FPS number, and a common gaming PC issue.
How Frame Time Connects to 1% Lows
Percentile "lows" — the 1% and 0.1% lows you see in good reviews — are really frame-time measurements in disguise. The 1% low is roughly the frame rate of your worst 1% of frame times; the 0.1% low, the worst 0.1%. They quantify the spikes frame time exposes, which is why they predict felt smoothness far better than the average. When a reviewer reports them, they're telling you about consistency, not just throughput.
The Nigeria-Specific Note
Frame-time consistency can degrade as a system heat-soaks — thermal throttling under a warm Nigerian ambient introduces exactly the kind of irregular slowdowns that spike frame times. A build that holds steady frame times when warm (good cooling, no throttling) feels smoother than one with a higher cool-bench average that wobbles once it heats up. See how to check your temperatures.
Frequently Asked Questions
What is frame time? Frame time is the gap, in milliseconds, between consecutive frames. It's the inverse of FPS (60 FPS ≈ 16.7ms) but measured frame by frame, so it exposes the variance and spikes that an averaged FPS number hides — and it's that consistency you actually feel.
Why can 90 FPS feel worse than 60 FPS? Because smoothness comes from consistent frame times, not the average. A 90 FPS average with frequent frame-time spikes (sudden long frames) produces visible hitches, while a steady 60 FPS delivers frames evenly and feels smoother.
How do 1% lows relate to frame time? They're frame-time measurements expressed as a frame rate — the 1% low reflects your worst 1% of frame times. They quantify the spikes that frame time reveals, which is why they predict felt smoothness much better than the average FPS.
The One Thing to Remember
Smoothness is a frame-time story, not an FPS one: it's the consistency of the millisecond gaps between frames that your eyes read as smooth or juddery. Uneven frame times cause microstutter the average FPS can't show, which is why a steady 60 can beat a spiky 90 — and why 1%/0.1% lows matter. In Nigeria, prioritise a build that holds steady frame times when heat-soaked, not just a high cool-bench average.
Want consistently smooth gameplay? Configure a gaming PC online → or talk to our team → and we'll build for steady frame times that stay smooth under real, warm conditions.