Free tool
FPS to Frame Time Calculator
Frame rate and frame time are two ways of describing the same thing. Convert between FPS and milliseconds per frame, and see why going from 60 to 120 FPS helps more than going from 200 to 260.
Common frame rates
| FPS | Frame time | Typical for |
|---|
Runs in your browser. Nothing you enter is sent to a server.
How to use it
- Type your FPS to see the frame time, or type a frame time in milliseconds to see the FPS.
- Compare with the table of common frame rates.
- Use the numbers to decide which settings are worth lowering to gain smoothness.
Why frame time matters
Frame time is the time one frame takes to draw. At 60 FPS it is 16.7 ms, at 120 FPS it is 8.3 ms and at 240 FPS it is 4.2 ms. Because the relationship is not a straight line, the same gain in FPS saves less time the higher you go. Moving from 60 to 120 FPS saves 8.3 ms per frame, while moving from 240 to 300 FPS saves only 0.8 ms.
Frame time and stutter
A game can have a high average FPS and still feel rough if some frames take much longer than others. Those spikes are felt as stutter. This is why reviewers talk about 1 percent lows: the average of the slowest frames, a better indicator of how smooth a game feels than the average alone.
Frequently asked questions
How do I convert FPS to milliseconds?
Divide 1000 by the FPS. For example 1000 divided by 144 is about 6.94 ms per frame.
What frame time is good?
A steady 16.7 ms (60 FPS) is smooth for most games. Competitive players aim for 8.3 ms (120 FPS) or lower.
Is 60 FPS to 144 FPS a big difference?
Yes. Frame time drops from 16.7 ms to 6.9 ms, which is easy to notice in motion and in aiming.
What are 1 percent lows?
They show how the slowest frames behave. Low values mean stutter even if the average FPS looks high.