Frame Time vs FPS: Why Smoothness Beats Peak Numbers
Learn the difference between average FPS and frame times, why consistent frame delivery beats high peak frame rates, and how to read a frame time graph.

Most players judge their system's performance by a single number: average FPS. The higher, the better, right? Not quite. Two systems can report the same average frame rate and feel completely different, because what you actually experience is not the average — it is the distribution of frame times. Understanding frame time is the key to explaining why a game feels buttery smooth on one setup and stuttery on another, even when both claim the same FPS.
What Is a Frame Time?
A frame time, also called a frame interval or ms-per-frame, is how long it takes your system to render a single frame. It is measured in milliseconds.
The relationship between frame time and FPS is simple:
- 16.7 ms per frame = 60 FPS
- 11.1 ms per frame = 90 FPS
- 6.9 ms per frame = 144 FPS
- 4.2 ms per frame = 240 FPS
To convert frame time to FPS, divide 1000 by the frame time in milliseconds. To convert FPS to frame time, divide 1000 by the FPS.
Average FPS Hides Important Information
Average FPS is just what it sounds like: the total number of frames rendered divided by the time elapsed. But averages smooth out the details, and those details are exactly what your eyes notice.
Consider two systems over a one-second window:
- System A renders 60 frames. Each one takes exactly 16.7 ms. Perfectly even.
- System B also renders 60 frames, but one frame takes 50 ms while the other 59 average about 8.5 ms each.
Both systems report "60 FPS." But System B produced one frame that lingered on screen for three times as long as the others. Your eye sees that frame hold still, registers it as a hitch or stutter, and the moment feels janky — even though the average number looks fine.
This is why frame time, not average FPS, is the metric that correlates with perceived smoothness.
The Frame Time Graph
Performance overlays like MSI Afterburner, NVIDIA Reflex, and the built-in tools in many games can display a frame time graph. Learning to read this graph is one of the most useful skills for tuning your system.
A flat, low line is ideal. It means every frame is taking roughly the same amount of time, which translates to perfectly smooth motion.
Spikes are stutters. Each spike is a frame that took much longer than the others. Even a single spike per second is usually visible.
A rising line suggests thermal throttling or gradual resource contention. As the system heats up or memory fills, frame times worsen over time.
High variance (a jagged line) means inconsistent delivery. The average may look fine, but the experience will feel uneven.
A graph that sits flat at 12 ms is better than one that bounces between 6 ms and 20 ms, even though the bouncing graph has a lower average.
Common Causes of Frame Time Spikes
If your frame time graph is full of spikes, one of these is usually responsible.
Background Processes
Operating systems constantly perform maintenance tasks — indexing files, checking for updates, syncing cloud storage. Any of these can briefly steal CPU time and cause a spike. Closing unnecessary background apps is the simplest fix.
Driver Issues
Outdated or buggy graphics drivers can produce periodic stutters, especially in newly released games. Always test with the latest "Game Ready" or equivalent driver when diagnosing.
Storage Bottlenecks
If a game streams assets from disk while you play (open-world games are notorious for this), a slow or fragmented storage device will produce stutters as the engine waits for data. Moving the game to a faster SSD often eliminates them.
Thermal Throttling
When a GPU or CPU reaches its temperature limit, it reduces its clock speed to cool down. This produces a characteristic pattern: stable frame times that gradually worsen over a few minutes, then recover, then worsen again. Improving cooling or cleaning dust from your system can help.
Memory Pressure
Running out of system RAM forces the operating system to use slower swap space on disk, which causes severe, irregular spikes. Close memory-hungry applications or add more RAM.
Engine Limitations
Some games simply have poorly optimized engines that produce stutters no matter what hardware you use. In these cases, frame rate caps, shader pre-compilation, or community mods may be the only remedies.
The 1% Low and 0.1% Low Metrics
Because averages hide problems, reviewers and serious tuners use percentile metrics to describe the worst moments.
1% low is the average frame time of the slowest 1% of frames. It represents the frame rate you experience during the worst moments of typical gameplay. If your average is 120 FPS but your 1% low is 55 FPS, you will feel regular stutters.
0.1% low is even more conservative, capturing the very worst spikes. A large gap between average and 0.1% low indicates an unstable, inconsistent experience.
When comparing hardware or settings, these numbers are often more meaningful than the average. A setup that delivers 100 FPS average with a 90 FPS 1% low will feel much smoother than one that delivers 130 FPS average with a 45 FPS 1% low.
How to Improve Frame Time Consistency
Once you understand the problem, the solutions follow logically.
- Cap your frame rate to a value your system can sustain. This prevents the GPU from swinging between easy and difficult scenes. Use the in-game limiter or your driver's frame rate cap.
- Close background apps before playing. Browsers with many tabs are a common culprit.
- Update your drivers, especially for newly released games.
- Improve cooling if you suspect thermal throttling. Monitor GPU and CPU temperatures while playing.
- Upgrade storage if stutters correlate with asset loading. An NVMe SSD is a meaningful upgrade over a SATA SSD or hard drive for asset streaming.
- Add RAM if your system is consistently near full memory usage.
Frame Time and FPS Testing
A simple FPS test will not give you a full frame time graph, but it can reveal whether your system is running at its target refresh rate consistently. If the number fluctuates wildly, your frame times are uneven, and the fixes above are worth investigating.
Final Thoughts
Average FPS is the number that gets advertised, but frame time is the number that determines how your game actually feels. A flat, consistent frame time line is the real goal, and it is achievable on a wide range of hardware with the right settings.
When you tune your system, stop chasing peak frame rates and start chasing consistency. Test your FPS, identify your weakest moments, and smooth them out. The result will feel far better than any benchmark number could suggest.