Overview
Gamers and developers think in frames per second and milliseconds per frame. Frame time is often more useful for spotting stutter.
Convert either way.
Worked examples
| Inputs | Result |
|---|---|
| ConvertFPS to frame timeValue144 | 144 FPS = 6.94 ms per frameFrames in a minute: 8,640 |
Show 2 more examples
| ConvertFPS to frame timeValue60 | 60 FPS = 16.67 ms per frameFrames in a minute: 3,600 |
| ConvertFrame time (ms) to FPSValue8.33 | 120.05 FPS = 8.33 ms per frameFrames in a minute: 7,203 |
Result (ms) by value
With the calculator's starting values, the result is 6.94 ms per frame. The table shows how it changes with the value.
| Value | Result (ms) |
|---|---|
| 80 | 12.5 ms per frame |
| 100 | 10 ms per frame |
| 120 | 8.33 ms per frame |
| 140 | 7.14 ms per frame |
| 144starting value | 6.94 ms per frame |
| 160 | 6.25 ms per frame |
| 180 | 5.56 ms per frame |
| 200 | 5 ms per frame |
Other inputs: Convert: FPS to frame time. Change them in the calculator above for your own numbers.
How it works
Frame time in ms = 1000 ÷ FPS.
The formula
ms = 1000 ÷ FPS
| FPS | Frames per second |
Practical tips
- 144 FPS is 6.94 ms per frame; 60 FPS is 16.67 ms.
- Going from 30 to 60 FPS saves 16.7 ms a frame, but 120 to 240 saves just 4.2 ms.
- Consistent frame times feel smoother than a higher, uneven average.
Frequently asked questions
What frame time is needed for 60 FPS?
16.67 ms or less for every frame.
Can I see above 60 FPS?
Most people notice smoother motion well above 60, with diminishing returns.