Frame Time Explained: The Real Measure of Smoothness
Frame time measures how long each individual frame takes to render, expressed in milliseconds. At 60 FPS, each frame should take 16.7ms. At 120 FPS, 8.3ms. Unlike FPS averages, frame time reveals the smoothness problems FPS hides — a game can average 120 FPS while individual frames spike to 50ms, causing visible stuttering that FPS counters won't show.
Understanding frame time is essential for diagnosing stuttering. When your 1% lows (the worst 1% of frame times) are far below your average FPS, that gap is what you feel as micro-stutters and hitches.
Got frame time spikes? Upload your HWiNFO log and our free analyzer pinpoints what's spiking your frames — thermal, power, or CPU — in seconds.
Find my spike cause freeWhat Is a Good Frame Time?
A good frame time is the per-frame interval that matches your target FPS — and stays consistent. At 60 FPS each frame should take 16.7 ms, at 120 FPS 8.3 ms, and at 144 FPS 6.9 ms. A steady frame time feels smoother than a high FPS average that hides spikes.
| Target FPS | Frame Time |
|---|---|
| 60 FPS | 16.7 ms |
| 120 FPS | 8.3 ms |
| 144 FPS | 6.9 ms |
Why High FPS Can Still Feel Choppy
FPS (Frames Per Second) only tells you the average number of frames rendered per second. But here's the problem:
Smooth 60 FPS
16.6ms, 16.6ms, 16.6ms, 16.6ms...
Each frame takes equal time
Stuttery "60 FPS"
8ms, 8ms, 50ms, 8ms, 8ms...
One long frame = visible stutter!
Both scenarios average 60 FPS, but one feels terrible. Frame time reveals the truth. If your frame time graph shows frequent spikes, our FPS stuttering diagnosis guide can help you track down the cause.
Understanding the Metrics
FPS (Frames Per Second)
What it is: Average number of frames rendered per second
Formula: FPS = 1000 / Frame Time (ms)
Limitation: Hides stutters and inconsistencies
Frame Time (ms)
What it is: Time to render each individual frame in milliseconds
Why it matters: Shows the actual smoothness of each frame
What to look for: Spikes indicate stutters
1% Lows (and 0.1% Lows)
What it is: The worst 1% of frame times, converted to FPS
Why it matters: Shows how bad the worst stutters are
Healthy ratio: 1% lows should be at least 60-70% of average FPS
120 FPS / 90 1% Low
120 FPS / 60 1% Low
120 FPS / 30 1% Low
Frame Pacing
What it is: How evenly spaced frames are delivered
Perfect pacing: Each frame displays for exactly the same duration
Bad pacing: Frames display for varying durations, causing judder — which can feel like stuttering or lag even though they are different problems
Tools to Measure Frame Time
CapFrameX
Best for: Detailed analysis & comparisons
- Records frame times to CSV
- Creates beautiful graphs
- Compares multiple sessions
- Free & open source
RTSS (RivaTuner)
Best for: In-game overlay
- Real-time frame time graph
- Works with any game
- Frame rate limiter built-in
- Comes with MSI Afterburner
In-Game Options
Best for: Quick checks
- Steam: Settings → In-Game → FPS Counter
- NVIDIA: Alt+R for performance overlay
- AMD: Alt+R for metrics overlay
- Many games have built-in options
How to Interpret Frame Time Graphs
Healthy Graph
- Flat, consistent line
- No major spikes
- Frame times close to target (16.6ms for 60 FPS)
Signs of Problems
- Regular spikes: Could be background process, driver, or V-Sync issue
- Gradual increase: Memory leak or thermal throttling
- Random large spikes: Shader compilation, asset loading, or GPU utilization drops
- Constantly unstable: Often points to a CPU bottleneck or badly optimized game
Not sure this is actually your issue?
Upload your HWiNFO log — if frame time issues is the cause, the analyzer confirms it in under a minute with your real sensor data.
Frequently Asked Questions
What is a good frame time for gaming?
A good frame time depends on your target FPS: 16.7ms at 60 FPS, 8.3ms at 120 FPS, and 6.9ms at 144 FPS. More importantly, frame time should be consistent — a steady 16.7ms feels smoother than frames alternating between 8ms and 35ms even though the latter averages higher FPS. Check your 1% lows: they should be within 30% of your average.
Is frame time more important than FPS?
Yes, frame time is more important than FPS for perceived smoothness. FPS is just an average — it hides stuttering. A game running at '60 FPS' could deliver perfectly smooth 16.7ms frames or wildly inconsistent frames averaging 16.7ms. Frame time graphs reveal the truth. Professional benchmarks like Digital Foundry always analyze frame time, not just FPS.
What causes frame time spikes?
Frame time spikes are caused by: CPU bottlenecks (single-thread saturation), shader compilation (first-time rendering of new effects), thermal throttling (heat-induced clock drops), storage stuttering (slow asset loading from HDD/SSD), VRAM overflow (textures swapping to system RAM), and driver issues (DPC latency). Use HWiNFO logs during gameplay to identify which component spikes correlate with frame time drops.
How do I read a frame time graph?
A healthy frame time graph shows a flat, consistent line near your target (e.g., 16.7ms for 60 FPS). Spikes above the line are stutters — the taller the spike, the worse the hitch. Regular periodic spikes suggest thermal throttling or background processes. Random tall spikes suggest shader compilation or asset loading. A gradually rising baseline means thermal degradation over time.
What's the difference between FPS and frame time?
FPS is how many frames per second (average). Frame time is how long each individual frame takes. FPS hides spikes — a single 50ms frame in a sea of 8ms frames barely changes average FPS but is very noticeable as stutter.
What are 1% lows and why do they matter?
1% lows represent the slowest 1% of frames. If your average is 120 FPS but 1% lows are 30 FPS, you'll feel regular stutters. Ideally, 1% lows should be at least 60-70% of your average FPS.
How do I measure frame time?
Use tools like CapFrameX, RTSS (RivaTuner), or in-game overlays. Enable the frame time graph, not just FPS counter. The graph shows spikes that the FPS number hides.
Why does my game feel choppy at 60 FPS but smooth at 144 FPS?
Higher FPS means shorter frame times (6.9ms vs 16.6ms), which gives more headroom for occasional spikes without them being noticeable. A spike from 6.9ms to 15ms at 144 FPS is barely visible, but 16.6ms to 33ms at 60 FPS is very obvious.