Quick answer: Frame time is how many milliseconds pass between frames (roughly 1000 / FPS when pacing is even). Smooth play needs consistent frame times — not only a high average FPS. Spikes in frame time are the hitching you feel; that is why 1% lows matter on PC reviews.
You will see frame-time graphs in benchmark overlays and serious GPU reviews. Product pages still shout average FPS; smoothness lives in the ms chart.
This explainer is based on how frame time is used in consumer PC gaming discussions. Gadget Clash does not bench-test frame pacing. Confirm review methodology when comparing GPUs or laptops.
Frame time at a glance
| Question | Short answer |
|---|---|
| What it is | Milliseconds from one frame to the next |
| Feels smooth when | Times stay steady near your FPS target |
| Feels bad when | Occasional spikes (hitch / stutter) |
| Care most if | You compare GPUs, laptops, or dig into stutter |
| Related | FPS, 1% lows, shader stutter |
What frame time actually is
At a steady 60 FPS, each frame ideally takes about 16.7 ms; at 144 FPS, about 6.9 ms. If most frames are 7 ms but every second one jumps to 40 ms, average FPS can still look “fine” while motion judders. Frame-time plots make those spikes obvious.
1% lows summarize the slowest common frames as an FPS-like number. Other hitch sources include shader compilation stutter, storage hitches, thermal throttling, and CPU vs GPU bottlenecks. Average FPS alone cannot tell that story.
Why it shows up on product pages
- Review culture: good GPU coverage includes frame-time or 1% low charts
- Marketing gap: ads still lead with average FPS banners
- Laptop / cooling: thin chassis may hold averages while spikes grow as heat builds
Buyer takeaway: When two cards have similar averages, prefer steadier lows in the games you play.
Choose it if / Skip it if
Watch frame time / 1% lows if you are picky about stutter or choosing between similar GPUs. Ignore deep charts if a console mode already feels locked and fine at 30/60.
Frame time vs related terms
| Term | What it means |
|---|---|
| FPS | Frames per second — averages can hide spikes |
| 1% lows | How bad the worst common frames get |
| Input lag | Delay to response — helped by high, steady FPS |
| VRR | Helps track varying FPS; does not erase huge hitches |
Practical checklist
- Use an overlay that can show frame time or 1% lows, not only average FPS
- Compare reviews that publish lows for your resolution
- Investigate spikes: shaders, background apps, thermals, settings
- Pair steady FPS with VRR when possible — Hz vs FPS
Frequently asked questions
Is lower frame time always better?
Yes for smoothness — up to what your display can show. Chasing tiny ms on a 60 Hz TV wastes headroom.
Why does my FPS counter look fine but the game hitch?
Averages hide rare slow frames. Check frame-time spikes or 1% lows.
Does frame generation fix frame time?
It can raise the FPS number while changing pacing and latency — see frame generation.
What frame time is “good”?
Steady near your target (e.g. ~16.7 ms for 60, ~8.3 ms for 120). Consistency beats a flashy average.
Related terms
Editorial note: Frame-time tools and review methods differ. Compare like with like. Part of the Gadget Clash Knowledge Base (Gaming).