FPS to milliseconds
Frame Time Calculator - Convert FPS to MS
Convert frames per second to milliseconds per frame, or convert frame time back to FPS. Use it to understand input latency, frame pacing, and refresh rate targets.
Formula
Frame time = 1000 / FPS
Current result
60 FPS = 16.67 ms
Why frame time matters
FPS averages can hide stutter
Frame time shows how long each frame takes to appear. Stable frame time usually feels smoother than a high FPS number with large spikes.
Example: 60 FPS is 16.67 ms per frame, while 144 FPS is 6.94 ms. Lower frame time usually means lower visual latency and smoother motion.
| FPS | Frame time | Common meaning |
|---|---|---|
| 30 FPS | 33.33 ms | Console baseline and slower motion |
| 60 FPS | 16.67 ms | Smooth general gaming target |
| 120 FPS | 8.33 ms | High refresh displays |
| 144 FPS | 6.94 ms | Popular esports monitor target |
| 240 FPS | 4.17 ms | Competitive motion clarity |
Diagnosis
Frame time explains the smoothness behind the FPS number
FPS is an average rate. Frame time is the actual wait between frames. That makes it more useful when you are trying to understand latency, stutter, browser animation timing, or why two systems with similar average FPS can feel different.
Use this calculator together with an FPS checker. First convert your target FPS to milliseconds, then compare that target with the measured frame time. If the calculator says 120 FPS should be 8.33 ms but your browser test often jumps to 20 ms or 30 ms, the issue is not just the average FPS. It is frame pacing instability.
The same timing budget is useful when reading monitor reviews, capture settings, animation budgets, and game overlays because every FPS target becomes a concrete millisecond target.
Formula
The core conversion is simple: milliseconds per frame equals 1000 divided by FPS. The reverse is 1000 divided by frame time.
Gaming
Lower frame time usually reduces visual latency. A stable 120 FPS target means frames arrive about every 8.33 ms.
Animation
Animators and frontend developers can use frame time to understand whether motion has enough frames for the intended display refresh rate.
Stutter
Micro stutter often shows up as one or two slow frames. The calculator gives you the expected baseline so those spikes are easier to spot.
FAQ
Frame time calculator questions
How do you convert FPS to milliseconds per frame?
Use the formula frame time = 1000 / FPS. For example, 60 FPS is 16.67 ms per frame, 120 FPS is 8.33 ms, and 240 FPS is 4.17 ms.
How do you convert milliseconds to FPS?
Use the reverse formula FPS = 1000 / milliseconds. For example, 16.67 ms is about 60 FPS, and 8.33 ms is about 120 FPS.
Why is frame time useful?
Frame time shows how long each frame takes. It is easier to diagnose stutter with frame time because one slow frame can be hidden by an average FPS number.
What frame time equals 144 FPS?
144 FPS is about 6.94 ms per frame. If a system often spikes above that value, motion can feel uneven even when the average stays close to 144 FPS.
Is lower frame time always better?
Lower frame time usually means lower visual latency and smoother motion, but consistency matters. Stable 8.33 ms often feels better than a higher average with frequent spikes.
Is this the same as a timecode calculator?
No. This page focuses on gaming, browser motion, animation, and display performance. Timecode calculators are for production timelines and SMPTE frame counts.
What is a good frame time for gaming?
Common targets are 16.67 ms for 60 FPS, 8.33 ms for 120 FPS, 6.94 ms for 144 FPS, and 4.17 ms for 240 FPS. The best target depends on your display refresh rate.
Can frame time explain micro stutter?
Yes. Micro stutter often appears as occasional frame time spikes. The average FPS can look fine while the frame time graph or 1% low FPS shows instability.