Hardware explained
Frametime vs FPS: What Actually Makes Games Feel Smooth
Reviewed July 2026
High FPS does not guarantee a smooth experience. Frametime — how long each individual frame takes — is what separates smooth 90 FPS from choppy 90 FPS. Here is what 1% lows are, why consistency beats average, and how to diagnose and fix spikes.
What makes a game feel smooth?
01 FPS vs frametime: two numbers measuring different things
FPS (frames per second) is the average number of frames your GPU produces each second. Frametime is how long each individual frame takes in milliseconds. At 60 FPS, every frame should take 16.6 ms. At 144 FPS, every frame should take 6.9 ms. The problem with average FPS is that it is exactly that — an average. A game could report 60 FPS while some frames take 5 ms and others take 40 ms, creating an uneven cadence that feels choppy even though the number reads 60. Frametime measures that consistency.
02 Why frametime matters more for feeling smooth
The human eye and brain are highly sensitive to sudden changes in frame cadence. A game locked at 60 FPS where every frame takes exactly 16.6 ms feels smooth and fluid. A game that averages 90 FPS but where every few frames one takes 60 ms produces jolts — those long frames stand out as hitches or stutters. Real smoothness does not live in the average: it lives in consistency. That is why experienced gamers pay more attention to frametime than to average FPS.
03 What 1% lows are and why they matter
1% lows (sometimes 0.1% lows) represent the slowest 1% of frames during a session or benchmark. If your average FPS is 120 but your 1% lows are 30, you will feel that 30 FPS as periodic jolts even though the big number looks good. 1% lows matter because they capture exactly the worst frames — the ones that ruin the experience. A high and stable 1% low is the difference between a game feeling smooth and feeling like it stutters even when the average is high.
04 Why your game feels choppy even at high FPS
If you have a high average FPS but the experience feels jerky, it is almost always a frametime consistency problem, not an average FPS problem. Common causes: a background task waking up and stealing CPU time during one frame, shader compilation hitching on a new effect, thermal throttling briefly dropping clocks, RAM bandwidth saturation producing a spike in one frame, or a slow drive stalling to load a texture. Each of these shows up as a frametime spike — a single long frame in a sea of short ones — that the eye catches immediately.
05 Common causes of bad frametime consistency
The most frequent culprits: background processes activating at bad moments (Windows indexer, antivirus scanning, updaters, cloud sync apps), shader compilation in UE5 or similar modern engines (the first frame with a new effect is slower), thermal throttling where GPU or CPU drop clocks when running too hot, insufficient RAM forcing use of the on-disk pagefile, and video capture overlays or hooks that add variable overhead to the renderer. A real-time frametime graph tells you which one is guilty: look for the tall spikes and correlate them with what is happening on the system at that moment.
06 How to see your frametime while gaming
The most useful free tools are CapFrameX (open-source, saves frametime CSV logs for post-session analysis) and RTSS with MSI Afterburner (shows a live frametime graph overlay on screen). NVIDIA's in-game overlay also shows 1% lows. Some games like CS2 or Valorant have built-in FPS counters but rarely frametime graphs — third-party overlays are more useful for real diagnosis.
07 The relationship between frametime and variable refresh rates
Monitors with G-Sync or FreeSync sync their refresh to your actual frametime — eliminating tearing without adding the input lag of classic VSync. This makes variable frametimes look and feel much better on a VRR monitor than on a fixed one. With a fixed 60Hz monitor, frametime variance between 8ms and 20ms produces tearing and micro-stutters. With FreeSync/G-Sync, the monitor simply waits for the next frame instead of showing a partial one. If you have a VRR monitor and still feel micro-stutters, the source is deeper — look at the software.
08 How to improve frametime consistency
The most effective improvements: close background apps that consume CPU and RAM during your session, keep GPU drivers current (many updates fix frametime issues), check your temperatures — thermal throttling is a frequent cause of spikes, apply a framerate cap a few FPS below your monitor maximum to keep the GPU stable rather than spiking, and for UE5 or similar games accept that the first-frame hitch of a new effect (shader cache) is normal and goes away.
09 Where Neon helps with frametime
Neon reduces the background CPU and RAM pressure that causes frametime spikes when OS tasks activate at the wrong moment — trimming startup programs, background services, and notification-heavy apps that tend to interrupt the GPU's work. It will not fix shader compilation spikes (that is the game engine) or hardware limits, but it removes a common class of software-caused spikes. Every change is reversible and logged.
Frametime quick reference
| Target FPS | Ideal frametime | Feel |
|---|---|---|
| 30 FPS | 33.3 ms | Limit for casual games |
| 60 FPS | 16.6 ms | Smooth for most |
| 144 FPS | 6.9 ms | Fluid and responsive |
| 240 FPS | 4.2 ms | Competitive ceiling |
Common questions
- What is frametime and how is it different from FPS?
- FPS (frames per second) is the average number of frames your GPU produces each second. Frametime is the time each individual frame takes to render, measured in milliseconds. At 60 FPS, every frame should take 16.6 ms. At 144 FPS, every frame should take 6.9 ms. The difference is that FPS is an average — a game could report 60 FPS while some frames take 5 ms and others take 40 ms, creating an uneven cadence that feels choppy. Frametime measures that consistency.
- What are 1% lows and why do they matter more than average FPS?
- 1% lows (sometimes written as 0.1% lows) represent the slowest 1% of frames during a benchmark or session. If your average FPS is 120 but your 1% lows are 30, you will feel that 30 FPS as periodic jolts even though the 'average' looks great. 1% lows matter because the human eye and brain are very sensitive to sudden drops in frame cadence. Smooth 60 FPS with solid 1% lows often feels better than average 90 FPS with bad 1% lows.
- Why does my game feel choppy even when FPS is high?
- Choppy feel at high average FPS is almost always a frametime consistency problem, not an average FPS problem. Common causes: a background task waking up and stealing CPU time for one frame, shader compilation hitching on a new effect, thermal throttling causing a brief clock drop, RAM bandwidth saturation spiking one frame, or a slow drive causing a texture streaming stall. Each of these shows up as a frametime spike — a single long frame in a sea of short ones — that the eye catches immediately.
- How do I see my frametimes while gaming?
- The most common free tools are CapFrameX (open-source, saves frametime CSV logs you can analyze) and RTSS with MSI Afterburner (shows a live frametime graph overlay). NVIDIA's in-game overlay also shows 1% lows. In-game options in some titles (like CS2 or Valorant) show FPS counters but rarely frametime graphs — the third-party overlays are more useful for diagnostics.
- Can Neon help improve frametime consistency?
- Yes, within the limits of what Windows-side optimization can do. Neon reduces the background CPU and RAM pressure that causes frametime spikes from OS tasks waking at the wrong moment — trimming startup programs, background services, and notification-heavy apps that tend to interrupt the GPU's work. It will not fix frametime spikes from shader compilation (that is a game engine issue) or from actual hardware limits, but it removes a common class of software-caused spikes.
Want to fix the choppiness? See how to fix FPS drops and stutter and shader compilation stutter.