A high average frame rate does not automatically make a game feel smooth. Two PCs can both report 100 FPS while one delivers steady motion and the other produces obvious hitches. The difference lies in how long individual frames take to render and how severe the occasional slowdowns are. That is why a useful benchmark includes 1% lows alongside the headline average.
What average FPS tells you
Average FPS is the number of rendered frames divided by the duration of the test. It is a convenient broad measure of performance: it helps you judge whether a graphics card suits a resolution and how much faster one configuration is than another.
The average also hides what happened during the run. A game might sit near 120 FPS most of the time and fall to 35 FPS for several seconds in a demanding area, yet still finish with an attractive result. The player will notice the slowdown immediately. Average FPS is valuable when the scene, settings, game version and test duration are identical, but it cannot describe consistency on its own.
What a 1% low means
To calculate a 1% low, frame times are sorted and the slowest one percent are examined. Those frame times are then expressed as an FPS value. In plain terms, the metric represents performance during noticeable slow periods that occur often enough to matter, without letting one isolated event dominate the result.
The closer the 1% low is to the average, the more consistent the experience tends to be. A result of 110 FPS average and 85 FPS at the 1% low will usually feel better than 120 and 48 FPS. The second machine has the higher headline number, but its larger gap points to stutter. CPU limits, memory, asset streaming, shader compilation, background tasks and the chosen scene can all affect the lower figure.
A 0.1% low focuses on even rarer frames. It can expose severe pauses, but it is also more sensitive to one-off events such as a notification, a first visit to an area or a background process. Treat it as a diagnostic alongside a frame-time graph, not as a standalone ranking.
How to compare results fairly
Only compare tests that use the same resolution, graphics preset, game version and benchmark route. Check whether ray tracing, dynamic resolution and upscalers such as DLSS, FSR or XeSS are enabled. A sound test lasts long enough to include representative gameplay, is repeated, and lists the full PC configuration, including the processor and memory setup.
Do not overinterpret a difference of two or three frames; it is often within normal run-to-run variance. A repeatable advantage and the relationship between the average and the 1% low matter more. Competitive players should also consider refresh rate and input latency, while single-player games often benefit most from a stable frame-rate cap.
What counts as a good result
There is no universal threshold. A consistent 30 FPS can be acceptable for a slower controller-based game when frame pacing is even. Stable 60 FPS remains a sensible target for most games, while fast competitive titles benefit from 120 FPS or more. In every case, the 1% low should stay reasonably close to the target rather than being hidden by a very high average.
A useful rule is to choose your target first, examine the 1% low and frame-time graph next, and read the average last. That turns a benchmark from an impressive number into an answer to the question that matters: how consistently will the game feel on your PC?