What's the difference between average FPS and 1% low?

Average FPS is the mean frame rate over time, the headline number, telling you typical performance but smoothing over variance. 1% low is the average of your worst 1% of frames, capturing how bad your dips are. A game can have a great average FPS while its 1% low is poor, meaning it stutters badly, because the average hides the worst frames. Average tells you typical performance; 1% low reveals the inconsistency players feel.

Why does 1% low matter for game performance?

Because players feel consistency more than average frame rate, the dips are what register as stutter and jank. The 1% low captures how bad your worst frames are, so it reveals inconsistency that average FPS hides. A game with a high average but a low 1% low feels choppy despite the good average, while a steady game with a high 1% low feels smooth. So 1% low often matters as much as or more than average FPS for perceived smoothness.

Can a game have a good average FPS but still feel choppy?

Yes, this is common. Average FPS smooths over variance, so a game can average a great 60 FPS while regularly dipping to 20, and those dips, captured by the 1% low, are what players feel as stutter. The average looks fine, but the worst frames ruin the experience. That's why you should look at 1% low (and frame times) alongside average FPS: the average tells you typical performance, but consistency, revealed by 1% low, is what determines whether the game feels smooth.

Average FPS vs 1% Low

Quick answer: Average FPS is the mean frame rate over time; 1% low is the average of your worst 1% of frames, capturing the dips. Average looks good even with bad stutter, while 1% low reveals the inconsistency players feel.

Average FPS and 1% low are two performance metrics that tell very different stories, one about typical performance, the other about the worst moments. The difference is why a game can benchmark well yet feel choppy. Here's the comparison.

What Average FPS Measures

Average FPS is the mean frame rate over a period, the headline number most people cite. It tells you typical performance, but it's a single smoothed figure that hides variance. A game can average a great 60 FPS while regularly dipping to 20, and the average alone won't reveal those dips.

Average FPS is useful for a rough sense of performance and for comparing builds at a high level. But its weakness is exactly that it averages, it conceals the worst frames, which are what players feel as stutter. A good average doesn't mean a smooth experience.

What 1% Low Measures

1% low is the average of your worst 1% of frames, it captures how bad your dips are. It's a consistency metric: a game with a high average but a low 1% low has bad stutter, because its worst frames are far slower than typical. The 1% low exposes the inconsistency the average hides.

Bugnet's frame-time data lets you see the worst frames, the basis of metrics like 1% low. The 1% low (and the related 0.1% low) is what reveals whether your frame delivery is consistent, which is what players actually perceive as smoothness, far better than the average.

Why 1% Low Matters for Smoothness

Players feel consistency more than average, the dips are what register as stutter, so 1% low often matters as much as or more than average FPS for perceived smoothness. A steady game with a high 1% low feels better than a higher-average game that constantly dips. Optimizing for 1% low means smoothing the worst frames.

Bugnet captures frame-time spikes so you can target the worst frames dragging down your 1% low. So don't judge performance by average FPS alone, look at 1% low to understand consistency, and optimize the worst frames, since a high average with a poor 1% low is a stuttery experience players will feel.

Average FPS is the mean (looks good even with stutter); 1% low is the average of your worst frames (reveals the dips players feel). For smoothness, 1% low matters as much as or more than average FPS.