FPS Counter Shows One Number But the Game Still Feels Choppy

You glance at your FPS counter. It says 100. Then 105. Then 98. Solid numbers, honestly.

And yet... the game still feels off. Little hitches here and there. Nothing you can point to exactly, but you notice it, especially when you're turning the camera fast or something's happening on screen.

So what's going on? Your FPS is fine. Your PC isn't struggling. But it doesn't feel fine.

Here's the thing nobody tells you when you first start caring about FPS: the number you're staring at is an average. And averages, by their nature, hide the ugly parts.

FPS is just a rate, not the full story

Let's slow down for a second, because this part actually matters.

FPS means "frames per second." It's counting how many frames got drawn in the last second, and giving you a total. That's it. That's all it's doing.

But think about what that actually leaves out:

It doesn't tell you when each frame arrived
It doesn't tell you if frames came in evenly, or in bursts
It doesn't tell you if one frame took twice as long as the rest

Two completely different gaming sessions can report the exact same 60 FPS. One feels buttery. The other feels like it's stuttering every couple of seconds. Same number. Wildly different experience.

Meet frame time - the number that actually matters

If FPS is the yearly average temperature, frame time is the daily weather. Way more useful when you're trying to figure out what's actually happening.

Frame time is just how long a single frame takes to render, measured in milliseconds.

Quick reference:

At 60 FPS, each frame should take around 16.7ms
At 100 FPS, around 10ms
At 144 FPS, around 6.9ms

Now here's where it gets interesting. Say you're averaging 100 FPS. Ideally, every single frame takes close to that 10ms. But what if, every once in a while, one frame decides to take 40ms instead?

That one frame is a stutter. You'll feel it. And here's the annoying part, your average FPS barely moves. One slow frame out of a hundred doesn't drag the average down much at all. But your eyes definitely noticed it.

This is why "1% lows" exist

Gamers and reviewers started using something called 1% lows specifically because average FPS was hiding this problem.

Here's the idea, and it's simpler than it sounds:

Take every single frame from a gaming session
Line them up from fastest to slowest
Look at the slowest 1% of them
That's your 1% low

So if your 1% low is 45, that means during the worst moments, you were basically playing at 45 FPS, even if your average said 100. There's also something called 0.1% lows, which zooms in even further, catching the really nasty individual hitches.

The gap between your average and your 1% low tells you a lot:

Small gap - frames are arriving evenly, game feels smooth
Big gap - something's causing occasional slow frames, and you're feeling every one of them

Honestly, once you understand this, you start looking at benchmarks completely differently. A game averaging 120 FPS with a 1% low of 40 will usually feel worse than a steady, locked 60. Higher number, worse experience. Weird, but true.

A simple way to picture it

Imagine you're on a video call. If the connection is stable, even if it's not the fastest connection in the world, the conversation flows fine.

Now imagine the same call, but every so often the video freezes for half a second before catching back up. Even if the "average" speed of that call was technically higher, you'd say the call was choppy. Nobody would disagree with you.

That's basically what's happening with your frames. It's not about how fast things go on average. It's about whether they show up on time, consistently, every single time.

So what actually causes this kind of stutter?

A few usual suspects show up again and again. Let's go through them.

1. CPU bottlenecks

If your CPU occasionally can't keep up maybe there's a lot happening on screen, or the game briefly needs more processing than usual it can cause a short spike in frame time. Your GPU sits there for a moment waiting on instructions, and that wait shows up as a stutter.

2. Background apps quietly eating CPU time

Recording software, overlays, browser tabs, chat apps, even some launcher processes running in the background. Individually small, but they can nibble away at CPU time your game needed right at that moment.

3. Shader compilation stutters

This one's common in newer games, especially right after launch or right after a graphics driver update. The game has to compile shaders the first time it sees a new visual effect. That compiling can cause a noticeable, repeatable hitch the first time you see something new, like a specific weapon effect or a new area.

4. VRAM running out

If your graphics card's memory fills up, especially at higher texture settings, the system starts having to shuffle data around more aggressively. That shuffling isn't instant, and it shows up as stutter.

5. Storage and loading hitches

Open-world games streaming in new areas as you move can cause brief hitches if your storage isn't fast enough to keep up, especially on older hard drives instead of SSDs.

6. Poor frame pacing at the game engine level

Sometimes it's genuinely not your hardware's fault at all. Some games just don't distribute their frames evenly, even when your PC could easily handle a smoother delivery. This is a software issue, baked into how the game itself was built.

A quick numbers example

Let's make this concrete for a second, because numbers help.

Say you run a benchmark and it reports 90 FPS average. Sounds solid, right?

Now picture two different sessions that both hit that exact same 90 average:

Session A: every frame takes almost exactly 11ms. Rock steady. Feels smooth the whole time.
Session B: most frames take around 9ms, but every second or two, one frame spikes to 45ms before things settle back down.

Both sessions average out to roughly the same 90 FPS. But Session B is the one where you'd swear something's wrong with your PC, even though the number on screen looks identical to Session A. That gap between "looks fine on paper" and "feels wrong in practice" is exactly what 1% lows are trying to catch.

This is also why two different PCs, or even the same PC with a driver update, can report similar average FPS but feel completely different to actually play. The average was never measuring the thing you actually noticed.

Why this matters more the higher your refresh rate goes

Here's a detail that catches people off guard once they get into higher refresh rate monitors.

At 60Hz, your eyes and brain are somewhat forgiving of small timing hiccups, mostly because everything is already a bit slower to begin with. At 144Hz or 240Hz, the ideal time between frames is much shorter, so any spike stands out a lot more by comparison.

That's part of why someone can upgrade from a 60Hz to a 144Hz monitor, keep the same PC, and suddenly become way more aware of stutters they never noticed before. It's not that the stutters are new. It's that the higher refresh rate made the inconsistency more obvious, since there's less room for error between frames.

How to actually check what's happening on your machine

You don't need to become a benchmarking nerd to figure this out. Try this:

Run our FPS Test during a calm moment and again during a busy, chaotic moment. Compare the two. A big drop during busy scenes is a clue.
Pay attention to when it happens. Is it random, or does it happen at the same spot every time (like turning a corner, or a specific ability)? Repeatable stutters usually point to shader compiling or asset loading, not a hardware limit.
Try closing background apps one at a time, and see if anything changes. Recording software is the usual suspect here.
If you can, check your GPU's VRAM usage in Task Manager or a monitoring tool. If it's maxed out, that's worth noting.
Update your graphics drivers, since shader-related stutters are sometimes fixed in later driver updates specifically for that game.

What actually helps once you know the cause

CPU bottleneck: close background apps, lower CPU-heavy settings like draw distance or NPC density, if the game allows it
Background software: disable overlays you're not using, and check what's launching automatically with your PC
Shader stutter: many newer games have a "pre-compile shaders" step at launch, let it finish instead of skipping it, and keep drivers updated
VRAM limits: lower texture quality one notch, this usually has a big impact on VRAM use without hurting visuals much
Storage stutter: if you're still on a hard drive, moving your most-played games to an SSD helps a lot here
Engine-level pacing issues: unfortunately, sometimes this really is just the game, and a patch or update is the only real fix

Frequently asked questions

Is a small gap between average FPS and 1% lows normal? Yes, completely. Some variation always exists. It only becomes a real problem when the gap is large enough that you can actually feel it while playing.

Does a higher refresh rate monitor fix this kind of stutter? Not on its own. A stutter caused by an uneven frame delivery will still be there on a 240Hz monitor if the frames themselves aren't arriving consistently. The monitor can only display what it's given.

Can V-Sync or G-Sync fix inconsistent frame times? They help with a related but different problem, screen tearing, and G-Sync in particular can smooth out how frames are displayed. But neither one can fix frames that were slow to begin with; they just handle the display side of things.

Why does this happen more in some games than others? It comes down to how the game is built and what it's doing behind the scenes. Some games are just better optimized for consistent frame delivery than others, even at similar visual quality.

Should I care about 0.1% lows too, or is 1% low enough? For everyday checking, 1% low is usually plenty. 0.1% lows are more useful if you're specifically chasing down rare, severe hitches that 1% lows might average out slightly.

The simple version

Average FPS tells you how fast things went overall, not how smooth it actually felt
Frame time tells you how long each individual frame took, which is where stutter really lives
1% lows show you your worst moments, not just your best average
A big gap between average and 1% low usually means something (CPU load, background apps, shader compiling, VRAM, storage) is causing occasional slow frames
Once you know what's actually causing the gap, fixing it is usually a lot more specific than just "get a better GPU"

Next time a game feels choppy despite a good FPS number, don't assume you're imagining it. Your eyes are picking up on something real, the average number just isn't built to show it to you.