Frame Time Calculator
Convert frames per second to milliseconds per frame. Compare frame durations at common rates without confusing frame time with total input latency.
Time per frame
Average frame time does not describe frame pacing or input latency.
Formula checked · NumberSwift · Review process
FPS to milliseconds reference table
Frame duration is 1,000 divided by FPS. These rounded values describe a steady frame rate, not total input latency or stutter.
| Frame rate | Time per frame |
|---|---|
| 30 FPS | 33.33 ms |
| 60 FPS | 16.67 ms |
| 90 FPS | 11.11 ms |
| 120 FPS | 8.33 ms |
| 144 FPS | 6.94 ms |
| 165 FPS | 6.06 ms |
| 240 FPS | 4.17 ms |
| 360 FPS | 2.78 ms |
How this calculator works
Frame time makes the difference between refresh rates easier to compare. Moving from 60 to 120 FPS reduces average frame duration from about 16.67 to 8.33 ms; moving from 120 to 240 FPS saves about 4.17 ms more. Individual frames may take longer or shorter than the average.
Formula
milliseconds per frame = 1,000 / FPS
Assumptions & limitations
Average frame time does not describe frame pacing or input latency.
Worked example
144 FPS corresponds to 6.9444 ms per frame.
To compare two measured frame durations, the Percentage Change Calculator expresses the relative reduction; this does not measure input latency.
Our approach to calculations ↗Common questions
Is frame time the same as input latency?
No. Input, simulation, rendering, display scanout and buffering all affect latency. Frame duration describes only one part.
Why do FPS gains have diminishing time savings?
Frame duration is 1,000 divided by FPS. Doubling 60 to 120 saves about 8.33 ms, while doubling 120 to 240 saves about 4.17 ms.
Does average FPS capture stutter?
No. Individual frame times and percentile metrics are needed to describe uneven frame pacing.