Frametimes vs FPS: why FPS lie to you

Your game shows 60 FPS, but something feels off

Your game shows 60 FPS in the corner of the screen. Benchmarks say your hardware should handle it fine. But you can feel it: a slight hitch here, a micro-stutter there, a nagging sense that something isn't quite right.

You're not imagining things. The problem is that you're looking at the wrong number.

What FPS measure (and what they miss)

FPS (frames per second) count how many frames your GPU rendered in the last second. If you see "60 FPS", it means your GPU produced 60 frames during that second.

But that number tells you nothing about how those 60 frames were distributed within that second. Imagine two scenarios, both showing 60 FPS:

• Scenario A: each frame takes exactly 16.6 ms to render. 60 frames, one every 16.6 ms, like a metronome.
• Scenario B: some frames take 8 ms, others 40 ms, others 12 ms. The total is still 60 frames in one second, but the distribution is chaotic.

The FPS counter says "60" in both cases. Your brain spots the difference instantly.

What is frametime

Frametime is how long it takes to render a single frame. It's measured in milliseconds (ms). At 60 FPS, the ideal frametime is 16.6 ms (1000 ms ÷ 60). At 144 FPS, it's 6.9 ms. At 240 FPS, it's 4.1 ms.

But what matters isn't the average frametime — it's the variation. A game with an average frametime of 16.6 ms but spikes to 40 ms and dips to 8 ms feels worse than a game running at a steady 50 FPS with a stable 20 ms frametime.

Frametime variation is the real cause of stuttering, micro-hitches, and that lack-of-smoothness feeling that FPS don't capture.

Why frametimes vary on Windows

Your GPU can render frames with perfect cadence, but between your GPU and what you see on screen sits an entire operating system with hundreds of processes competing for CPU, memory, and disk access.

• Background processes: antivirus, Windows telemetry, updates, search indexing — they all interrupt the rendering pipeline.
• High DPC latency: Deferred Procedure Calls are kernel-level tasks prioritized over your game. Poorly optimized audio, network, or USB drivers can spike them.
• CPU scheduling: Windows doesn't know your game needs priority. It gives it the same importance as Cortana or the print spooler.
• Power plan: the "Balanced" mode dynamically scales CPU frequency, introducing microseconds of latency on every change.
• Default GPU drivers: a standard driver installation is not the same as one optimized for your specific hardware.

None of these causes show up in your FPS counter. All of them show up in your frametimes.

How to see your frametimes right now

You don't need to buy anything. These free tools show frametimes in real time:

• CapFrameX: the go-to tool for frametime analysis. Free, open source, with detailed graphs and percentiles (1% low, 0.1% low).
• MSI Afterburner + RTSS: the classic combo. Configure the overlay to show frametime in ms alongside FPS.
• FrameView: by NVIDIA, but works with any GPU. Measures frametimes, power, and performance.

What you're looking for isn't the average frametime — it's the variation. If your frametime jumps between 8 ms and 35 ms while FPS show 60, that's your problem.

Measuring is the first step

FPS are a useful summary, but a summary that hides the detail that matters most: consistency.

When someone says "my PC runs smoothly at 60 FPS", they may be right — or they may be seeing 60 FPS with frametime variations their eyes notice but their counter doesn't. Measuring frametimes is the first step to understanding what's actually happening. It's the first thing we do in every LATENT session: before changing anything, we measure. Before adjusting anything, we know what to change and why.