When you read a benchmark or watch a performance overlay, you will see more than one frame rate number: average FPS, 1% lows, and sometimes 0.1% lows. These metrics tell very different stories about how a game actually feels. Understanding them helps you spot stutter that a headline average number completely hides.

Our Top Picks

  1. ASUS TUF Gaming NVIDIA GeForce RTX 4090 OCOC Edition5.1 pounds
    Check on Amazon
  2. ASUS ROG Strix GeForce RTX 4090 OC EditionROG Strix14.1 x 5.9 x 2.8 Inches8.05 Pounds
    Check on Amazon
  3. MSI GeForce RTX 4090 Gaming X Trio 24GLarge
    Check on Amazon
  4. ASUS TUF Gaming GeForce RTX 5090 32GB GDDR7RTX5090|OC13.7 x 5.7 x 2.8 inches5 pounds
    Check on Amazon

What average FPS really tells you

Average FPS is the total frames rendered divided by the time taken. It is a useful headline figure for comparing hardware, but it is easy to be misled by it. Two systems can both average 100 FPS while one feels perfectly smooth and the other stutters badly, because the average says nothing about consistency — only the overall pace.

Why 1% lows matter more for feel

The 1% low represents the frame rate during the worst 1% of frames in a run. It captures the dips and hitches that you actually notice while playing. A game averaging 120 FPS with 1% lows of 110 feels rock solid; the same 120 average with 1% lows of 55 feels choppy despite the identical headline number. This is why experienced builders care about 1% lows as much as the average.

Metric What it measures Feels like
Average FPS Overall pace General smoothness ceiling
1% low Worst 1% of frames Noticeable dips/hitches
0.1% low Worst 0.1% of frames Sharp, rare stutters
Frame time (ms) Time per frame Consistency, pacing

0.1% lows and rare spikes

The 0.1% low zooms in even further, on the worst one-in-a-thousand frames. These correspond to the occasional sharp stutter — a shader compiling, an asset streaming in, or a background task interrupting. A big gap between your average and your 0.1% low signals infrequent but jarring hitches worth investigating, even if the game feels mostly fine.

Frame time: the underlying truth

All of these are derived from frame times, the milliseconds each frame takes to render. A flat frame time graph means smooth gameplay; spikes mean stutter. Watching the frame time line is often more informative than any single FPS number because it shows consistency directly. As a rough guide, 60 FPS is 16.7 ms per frame, 120 FPS is 8.3 ms, and 144 FPS is about 6.9 ms.

How to use these numbers when tuning

When you change a setting, do not just watch the average — check whether 1% and 0.1% lows improve. Sometimes lowering one CPU-heavy setting barely moves the average but dramatically raises the lows, transforming how the game feels. Chasing a smoother experience means closing the gap between your average and your lows, not simply maximizing the top number.

Capturing these metrics

Overlay tools and benchmark utilities report all three plus a frame time graph. Run a consistent, repeatable scene, and compare like-for-like between settings or hardware. A single pass through a busy area reveals far more than an idle menu ever will.

FAQ

Which number should I care about most?

For how a game feels, 1% lows and frame time consistency matter most. Average FPS is a good headline for comparing raw power, but smooth gameplay comes from high, stable lows.

What causes a big gap between average and 1% lows?

Usually a CPU bottleneck, insufficient VRAM, storage stutter, or background tasks. Closing the gap often means addressing the CPU, adding VRAM headroom, or reducing streaming hitches.

Bottom line

Average FPS shows the pace, but 1% and 0.1% lows reveal the stutter you actually feel, and frame times are the raw truth underneath. When benchmarking or tuning, aim for high lows and a flat frame time graph, not just a big average. That is the difference between a game that looks fast on paper and one that genuinely feels smooth.

Related guides

Browse all Uncategorized guides →