What Is Frame Time? Why High FPS Can Still Stutter

The simplest answer of what is frame time is: this is the time that PC takes to create a single frame, measured in milliseconds (ms). Lower and more consistent frame times usually mean smoother gameplay.
While FPS shows how many frames are displayed each second, frame time shows how evenly those frames are delivered. A game with high FPS can still feel stuttery if frame times are inconsistent. For the smoothest experience, you need both high FPS and stable frame times.

Updated October 2026 — added frame time monitoring tools.

This guide explains what frame time is, why it matters more than raw FPS in many cases, and how to identify and fix frame time problems.

Frame time is the duration needed to render one frame. If a game runs at 60 FPS with perfect consistency, each frame takes exactly 16.67ms. At 144 FPS, each frame takes about 6.94ms.

The formula is simple: Frame time (ms) = 1000 / FPS

Common reference points:

• 30 FPS = 33.3ms per frame
• 60 FPS = 16.7ms per frame
• 120 FPS = 8.3ms per frame
• 144 FPS = 6.9ms per frame
• 240 FPS = 4.2ms per frame

In frame time vs FPS comparison, FPS is an average over time. If you average 60 FPS over one second, you rendered 60 frames but those frames were not necessarily evenly spaced.

Imagine two scenarios:

• Scenario A: 60 frames, each taking exactly 16.67ms — smooth, consistent motion.
• Scenario B: 60 frames, but some take 5ms and others take 40ms — same average FPS, but visibly stuttery.

Both report 60 FPS. Only frame time analysis reveals the difference. This is why frame time graphs are more informative than FPS counters for diagnosing performance issues.

Your eyes perceive motion based on the regularity of frame updates, not just the count. A game running at a consistent 50 FPS often feels smoother than one fluctuating between 40 and 100 FPS, even though the second averages higher.

Frame time spikes cause stuttering. If most frames render in 8ms but occasionally one takes 50ms, you experience a momentary hitch. These spikes are often more disruptive than sustained lower frame rates.

1% and 0.1% lows. Performance metrics often include “1% low” and “0.1% low” frame rates — these represent the performance during the slowest 1% and 0.1% of frames. Low 1% lows indicate frame time spikes that affect perceived smoothness.

Several tools display frame time graphs:

• MSI Afterburner + RivaTuner — free, highly configurable, shows frame time graph overlay in games.
• CapFrameX — captures detailed frame time data and generates reports with 1% and 0.1% lows.
• FrameView — NVIDIA’s tool for capturing frame time and power data.
• Steam’s built-in FPS counter — shows FPS but not frame time; use alongside a frame time tool.
• In-game overlays — some games and engines include built-in frame time displays.

A flat frame time graph indicates consistent performance. Spikes indicate stuttering, even if average FPS looks acceptable.

Shader compilation: Many games compile shaders during gameplay. When a new effect appears for the first time, the game pauses briefly to compile the shader, causing a spike.

Asset streaming: Loading textures or models from storage mid-game can cause hitches, especially on slower drives.

CPU bottlenecks: If the CPU cannot keep up with game logic, physics, or draw call preparation, frames are delayed irregularly.

Background processes: Antivirus scans, Windows updates, or other programs consuming CPU or disk resources cause sporadic frame time spikes.

Thermal throttling: When your CPU or GPU overheats and throttles, performance becomes inconsistent.

V-Sync on mismatched refresh rates: V-Sync on a 60Hz monitor forces either 60 FPS or drops to 30 FPS — no in-between — causing severe stuttering when the GPU cannot maintain a solid 60.

1. Cap your frame rate. Use in-game limiters or RTSS to cap FPS slightly below your system’s maximum. This creates headroom and prevents wild fluctuations.
2. Enable shader pre-compilation. Some games offer shader compilation during loading or installation. Enable it to avoid runtime compilation stutters.
3. Use an SSD. If you are on a hard drive, asset streaming stutters are common. An SSD dramatically reduces loading-related frame time spikes.
4. Close background applications. Reduce CPU and disk contention by closing unnecessary programs.
5. Check for thermal throttling. Monitor temperatures; address cooling issues if your components are throttling. See our GPU health guide for diagnostics.
6. Use variable refresh rate. G-Sync and FreeSync smooth out minor frame time variations by syncing the display to the GPU’s output rate.
7. Update drivers. GPU driver updates often include frame pacing improvements for specific games.

Frame time is the more informative metric for understanding smoothness. A game that averages 90 FPS with constant frame time spikes feels worse than one holding steady at 60 FPS. Monitor your frame times, identify the causes of spikes, and address them directly. A well-balanced system — where your CPU and GPU work together efficiently — is the foundation for consistent, smooth gameplay.