A gaming computer setup

1% Lows Explained: Why Average FPS Can Mislead You

You look at two graphics card reviews. Both cards average 100 frames per second in the same game. One feels smooth, and the other feels like it is skipping. The average cannot explain the difference, but another number can: the 1 percent low.

This guide explains what the 1 percent low is, why the average hides stutter, how different tools calculate it, and how to read the number without being fooled.

Why the average is not enough

Average FPS is the total number of frames divided by the total time. It describes overall speed, and it says nothing about how evenly the frames arrive. Imagine a game that runs at a perfect 100 FPS for most of a minute and then freezes for half a second. The average barely moves, but you notice that freeze immediately.

What your eyes notice is the time between frames, called frame time. A steady game delivers frames at regular intervals. A stuttering game delivers some frames late, and those late frames are the ones that ruin the feel. The 1 percent low is a way to put a number on the late ones.

What a 1 percent low is

The simplest definition is the average FPS of the slowest 1 percent of frames. If you capture 60 FPS for ten minutes, you have about 36,000 frames, and the slowest 1 percent is about 360 frames. The 1 percent low is the FPS those 360 frames would average. The 0.1 percent low does the same for the slowest 0.1 percent, about 36 frames, so it focuses on the very worst moments.

If your average is 100 and your 1 percent low is 90, almost every frame is close to the average, and the game is consistent. If your average is 100 and your 1 percent low is 40, the game has regular hitches even though the headline number looks excellent.

Why different tools give different numbers

This is the part that causes confusion. There is no single official formula, and tools use different methods. CapFrameX, a popular analysis tool, documents several of them:

  • Percentile. The value that 99 percent of frames beat, which is the 1st percentile of FPS (or the 99th percentile of frame time). It counts frames and ignores how bad the outliers beyond the cutoff are.
  • Average of the lowest frames. The average of the slowest x percent of frames. Because every outlier is included, the result is always lower than the percentile.
  • Time-based (integral). Frame times are sorted slowest first and added up until they reach x percent of the total time. This weights long frames more heavily, and it better reflects how long a stutter lasts.

The practical lesson is that you can compare 1 percent lows only when they come from the same tool and the same method. A number from one review does not match a number from another.

How many frames you need

A 1 percent low from a short capture is shaky. With only 1,000 frames, the 1 percent low is the average of just 10 values, so one bad frame can change it a lot. Capture at least a minute of the same scene, and repeat the run two or three times to see if the result holds. Test the same repeatable section each time so you compare like with like.

How to read the gap

  1. Close to the average (within about 20 percent). Smooth, consistent frame delivery.
  2. Noticeably below (roughly 50 to 80 percent of the average). You may feel occasional hitches.
  3. Far below. Expect visible stutter, even if the average looks high.

These cutoffs are rules of thumb, not standards. What matters is the trend when you change a setting. If a change raises the average but drops the 1 percent low, the game may look faster on paper and feel worse.

What usually causes bad lows

  • Not enough memory. When the system runs out of RAM, it swaps data to the drive, and frames stall. Our guide on why computers slow down over time covers this.
  • Heat. A hot processor or graphics card lowers its own speed. The same idea explains why a phone gets warm while charging.
  • Background programs. Updaters, overlays, and browsers can wake up in the middle of a game.
  • Shader compilation. The first time a game shows an effect, it can stall for a moment. The spike often disappears on a second run.
  • A slow network. In online games, lag can feel like stutter even when frame times are fine. See why Wi-Fi gets slower with distance.

Measure it yourself

You can log frame times with PresentMon or tools built on it, such as CapFrameX, then paste the numbers into our FPS and frame time calculator. It shows average FPS, 1 percent and 0.1 percent lows, the worst frame, and a count of stutter frames, and it runs in your browser without uploading anything. Our calculator uses the average of the slowest frames, so its numbers can differ slightly from tools that use the percentile method.

Quick answers

Is a higher 1 percent low always better?

Yes, for the same method and the same scene. A higher low means the slowest frames are less slow, which usually feels smoother.

What is a good 1 percent low?

There is no universal number. A useful target is a low that stays close to your average and above the refresh rate you care about, such as 60 FPS on a 60 Hz screen.

Why does my game stutter with a high average?

The average hides the late frames. Check the lows, the worst frame time, and the count of frames that took much longer than the median.

The short version

  • Average FPS describes speed, and the 1 percent low describes smoothness.
  • The 1 percent low is the average FPS of the slowest 1 percent of frames, though tools define it in different ways.
  • Compare lows only from the same tool and method, and capture at least a minute.
  • A big gap between the average and the low means stutter, even if the average looks great.

Sources

Related reading

Similar Posts