Frame Time vs FPS: Why Stutter Persists

Yes, you can have high FPS and still see stuttering, and the reason is that FPS is an average while stuttering is caused by individual frame times that are much longer than the average. Measuring frame times—the time each frame takes to render—reveals the spikes and hitches that a simple FPS counter hides, and it is the first step to diagnosing and fixing the problem.

Formula

The relationship between FPS and frame time is simple: Frame time (ms) = 1000 / FPS. If a game runs at 60 FPS, the average frame time is 1000 / 60 = 16.67 milliseconds. Conversely, FPS = 1000 / frame time (ms). A 33.3 ms frame corresponds to 30 FPS, and a 8.33 ms frame corresponds to 120 FPS.

This formula is the core of the calculator above: it converts a finish time and distance into an average pace and speed, which is the same mathematical relationship as FPS and frame time, just in different units. The key is that the formula gives an average—it tells you the mean, not the distribution.

Worked Example

Using the default values from the calculator: a finish time of 50 minutes over a distance of 10 km.

1. Average pace = finish time / distance = 50 min / 10 km = 5.00 min/km.
2. Average speed = distance / (finish time / 60) = 10 km / (50 / 60) h = 10 / 0.8333 = 12.00 km/h.

The same logic applies to FPS: if you render 50 frames in 1 second, the average frame time is 1000/50 = 20 ms, but that tells you nothing about whether those frames were evenly spaced or came in bursts of 10 ms followed by a 100 ms hitch.

Why FPS Averages Hide Stuttering

An FPS counter displays the number of frames rendered in the last second, or a rolling average of the last several seconds. This is a single number that smooths out all the variation. Consider a game that renders 60 frames in one second, but does so in this pattern: 20 frames at 5 ms each (200 FPS), then a single frame that takes 200 ms, then 39 frames at 10 ms each (100 FPS). The average is 60 FPS, but the 200 ms frame is a visible freeze—a stutter. The FPS counter shows 60, but the experience is a slideshow.

Frame time graphs, on the other hand, plot the time taken for each frame. A flat line at 16.7 ms means perfectly smooth 60 FPS. A graph with spikes—a frame taking 50 ms, then 100 ms, then back to 16.7 ms—reveals the stutters. The human eye is very sensitive to these irregularities, especially when the frame time doubles or triples, because it creates a visible judder or micro-freeze.

Common Causes of Frame Time Spikes

Frame time spikes are not random; they have identifiable sources. The most common culprits include:

• Shader compilation: When a game encounters a new visual effect (a new texture, a particle effect, a character model), it must compile the shader code. This can cause a one-time hitch that lasts from a few milliseconds to over a second. Many modern games pre-compile shaders during loading screens to avoid this, but it still happens in open-world games or when you enter a new area.
• Asset streaming: Games load textures, models, and audio from disk or network as you move through the world. If the storage device is slow, or the game requests too much data at once, the game engine may pause rendering to wait for the data, causing a stutter.
• CPU bottlenecks: A frame can be delayed if the CPU cannot prepare draw calls fast enough. This often happens in CPU-intensive scenes with many objects, physics calculations, or AI. The GPU may be idle waiting for the CPU, resulting in a long frame time.
• Background processes: Windows updates, antivirus scans, or even a browser with many tabs can steal CPU time or cause GPU driver timeouts, leading to intermittent spikes.
• Thermal throttling: When a GPU or CPU heats up, it reduces its clock speed to cool down. This can cause a sustained period of higher frame times, though it usually appears as a gradual drop in FPS rather than a single spike.
• Driver issues: A poorly optimized or buggy graphics driver can cause micro-stutters that are hard to reproduce.

How to Measure Frame Times

You do not need expensive equipment to measure frame times. Several free and widely used tools can do it:

• MSI Afterburner with RivaTuner Statistics Server (RTSS): This is the most common tool. It can display an on-screen overlay with a frame time graph, not just an FPS counter. You can enable the frame time graph in the settings, and it will show a real-time line graph.
• CapFrameX: A dedicated frame time analysis tool that records a session and gives you detailed statistics, including the 1% low and 0.1% low frame times, which are the average of the worst 1% and 0.1% of frames. These are much better indicators of stutter than the average FPS.
• PresentMon: A command-line tool from Intel that captures frame timing data and can export it to a CSV file for analysis. It is the underlying engine for many other tools.
• NVIDIA FrameView: A tool from NVIDIA that measures frame times and power consumption, useful for benchmarking.

When you run a game, look for the frame time graph. A healthy graph looks like a flat horizontal line with minor fluctuations of a few milliseconds. A stuttering game shows tall spikes that reach 2-3 times the average value. You can also record a session and look at the 1% low and 0.1% low numbers: if the 1% low is 50 ms while the average is 16.7 ms, you have a stutter problem.

What to Do About Frame Time Spikes

Once you have identified that you have frame time spikes, you can address the causes. The order of actions below is a practical troubleshooting sequence:

1. Update drivers: Install the latest GPU driver. Often, driver updates include fixes for stuttering in specific games.
2. Enable or disable vsync: Vsync can help by synchronizing frame delivery with the monitor’s refresh rate, but it can also introduce stutter if your frame time fluctuates above and below the refresh rate. Try both Vsync and G-Sync/FreeSync if your monitor supports them. G-Sync/FreeSync (adaptive sync) is generally the best solution because it matches the monitor’s refresh rate to the frame rate, avoiding both tearing and stutter.
3. Limit your frame rate: If your game runs at 200 FPS but your monitor is 60 Hz, you are wasting GPU power and may be causing micro-stutters. Cap the frame rate slightly below your monitor’s refresh rate (e.g., 58 FPS on a 60 Hz monitor) using the game’s built-in limiter or RTSS. This gives the GPU headroom to avoid spikes.
4. Disable background applications: Close browsers, chat apps, and other software that might be using CPU or GPU resources. Use the Task Manager to find any process using significant CPU or disk.
5. Check storage speed: If the game is installed on a mechanical hard drive, move it to an SSD. Asset streaming is a common cause of stutter, and an SSD dramatically reduces loading times and streaming hitches.
6. Lower graphics settings: Reduce settings that stress the CPU or GPU, such as shadow quality, draw distance, and anti-aliasing. Sometimes a setting like “Ultra” texture quality can exceed your GPU’s VRAM, causing constant swapping and stutter.
7. Reinstall the game: If you have mods or a corrupted game file, a clean install can fix it.

Frame Time vs. 1% Low vs. Average FPS

When reading benchmarks, you will see three numbers: average FPS, 1% low, and 0.1% low. The average FPS is the mean frame rate. The 1% low is the average frame time of the worst 1% of frames, converted back to FPS. The 0.1% low is the average of the worst 0.1% of frames. For example, a game might have an average of 100 FPS, a 1% low of 60 FPS, and a 0.1% low of 30 FPS. This means that 1% of the time, the frame rate dips to 60 FPS or below, and 0.1% of the time it drops to 30 FPS, which is a noticeable stutter.

A good rule of thumb: the higher the 1% low and 0.1% low relative to the average, the smoother the game feels. If the 1% low is less than half of the average, you will likely perceive stutter. For example, a game with an average of 100 FPS and a 1% low of 90 FPS is smooth, while one with an average of 100 FPS and a 1% low of 40 FPS is stuttery.

Frequently Asked Questions

Why does my game stutter when FPS is high?

High FPS means the average frame time is low, but stutter is caused by individual frame time spikes. For example, if you have 200 FPS average but every few seconds a frame takes 100 ms, you will see a noticeable hitch. The FPS counter smooths over these spikes, so it shows a high number even though the experience is not smooth.

What is a good frame time?

A good frame time depends on your target refresh rate. For 60 Hz, a frame time of 16.7 ms is ideal; for 144 Hz, 6.9 ms; for 240 Hz, 4.2 ms. The frame time should be as close to these values as possible, with minimal variation. Fluctuations of a few milliseconds are normal, but spikes that double the frame time are visible.

How do I fix micro-stutter?

Micro-stutter is often caused by inconsistent frame times. Start by capping your frame rate to a value your system can maintain consistently, enabling G-Sync/FreeSync if available, and closing background apps. If the stutter persists, check the frame time graph to see if the spikes correlate with loading new areas, which points to asset streaming, or with specific actions, which might point to shader compilation.

Is VSync good or bad for stuttering?

VSync can both help and hurt. It eliminates screen tearing, but if your frame time fluctuates above and below the refresh rate, VSync will cause the frame rate to drop to half (e.g., from 60 to 30 FPS) to maintain sync, which is a large stutter. Adaptive sync (G-Sync/FreeSync) is better because it adjusts the monitor’s refresh rate to the frame rate, avoiding both tearing and the VSync half-rate drop.

What is a 1% low?

The 1% low is the average frame time of the worst 1% of frames, expressed as an FPS value. It is a better indicator of stutter than the average FPS because it focuses on the slowest frames. A low 1% low (e.g., 30 FPS when the average is 100 FPS) indicates noticeable hitches.

Related

• Circuit Calculator: Voltage and Current Explained
• Voltage to Current Calculator: Ohm’s Law Explained
• Amps to kW Calculator: Convert Electrical Power

in t | Finish time | min | 50 | 0
in d | Distance | km | 10 | 0 | 100000
out pace | Average pace | min/km | t / d | 2
out speed | Average speed | km/h | d / (t / 60) | 2