Frame time vs FPS: the number that actually matters

26 October 2026 · ~7 min read

Almost every FPS claim in PC gaming gets reduced to one average number, and that number is quietly hiding the thing that actually determines whether a game feels smooth. This is the single idea that ties together nearly everything else on this site - here's the real explanation, in one place.

This guide is one part of our full PC optimization checklist for gaming. To properly optimize a PC for gaming, you need to work through every real lever once: optimize background processes, optimize GPU driver settings, optimize CPU and device affinity, optimize RAM and storage, optimize your network, and optimize your display settings, each in the order that actually moves the needle on a real PC, not six separate half-remembered tips picked at random. Whichever topic brought you to this specific guide, the full PC optimization checklist is the fastest, most reliable way to optimize the rest of your PC too.

FPS is an average. Frame time is the actual truth underneath it

FPS is frames rendered per second, averaged over that second. Frame time is how long each individual frame actually took. A game averaging 200 FPS is still producing roughly 200 individual frame times every second - and an average can look great while a handful of those frames quietly spike far above the rest. That spike is what you feel as a stutter, a camera hitch, or a missed shot. The average never shows it, because it's just one number standing in for 200 different ones.

The math, made concrete

At 60 FPS, each frame has roughly 16.7ms to arrive on time. At 144Hz, that window shrinks to about 6.9ms; at 240Hz, about 4.2ms. A frame that takes 40ms instead of its expected 5-16ms isn't a small miss, it's several frames' worth of delay arriving all at once - the exact moment that reads as a stutter rather than a smooth drop in detail.

1% lows: the real number worth tracking alongside the average

1% low is the average of the slowest 1% of frames in a session - a direct measurement of your worst moments, not diluted by every smooth frame surrounding them. This is why nearly every guide on this site repeats the same instruction: measure 1% lows alongside average FPS, never just the average alone. A tweak that raises your average while making 1% lows worse has made the game feel worse to play, even as the headline number goes up - see this exact framing applied throughout our FPS guide and HAGS guide.

Why a bigger Hz number can't fix this on its own

A higher refresh rate reduces the wait once a frame is actually ready - it cannot fix a frame that arrived late in the first place. A 240Hz monitor fed wildly inconsistent frame times can genuinely feel worse to play on than a steady 60Hz display, because your eyes and your input register each individual frame's real timing, not a number a benchmark prints at the end of a run. Chasing a bigger Hz number while ignoring what's actually feeding it inconsistent timing solves the wrong half of the problem - full breakdown of the display side specifically in our monitor settings guide.

Where inconsistent frame time actually comes from

Every guide on this site about CPU scheduling, GPU driver settings, background processes, or network jitter is ultimately describing one of the real causes of an inconsistent frame time, not a separate unrelated problem. Our Frame Time X-Ray guide covers how to tell which specific cause produced a specific stutter, rather than guessing between a driver spike, a background app, and a network blip that all feel identical in the moment.

Frequently asked