FPS to Frame Time Calculator
Converts a frames-per-second value to frame time in milliseconds, the actual time budget each frame has to render. Essential for diagnosing stutters and evaluating GPU headroom.
About this calculator
Frames per second (FPS) and frame time are two ways to express the same rendering rate, but frame time is the more technically precise metric. The formula is: frameTime (ms) = 1000 ÷ FPS. Because one second equals 1000 milliseconds, dividing 1000 by the frame rate gives the number of milliseconds available for each frame to be rendered and displayed. At 60 FPS each frame has approximately 16.67 ms; at 144 FPS each frame has about 6.94 ms. Frame time is preferred by performance analysts because FPS averages can hide spikes — a single frame that takes 50 ms causes a noticeable stutter even if the surrounding frames bring the average FPS up to an acceptable level. Monitoring frame time in addition to average FPS gives a more accurate picture of smoothness.
How to use
Suppose your game is running at 144 FPS. Enter 144 in the FPS field. The calculator computes: frameTime = 1000 ÷ 144 = 6.94 ms per frame. Now suppose your frame rate drops during a heavy scene to 45 FPS: frameTime = 1000 ÷ 45 = 22.22 ms. That jump from 6.94 ms to 22.22 ms represents a more than threefold increase in render time per frame, which your eyes will perceive as a significant stutter even if your average FPS readout still looks acceptable.
Frequently asked questions
Why is frame time a better measure of smoothness than average FPS?
Average FPS smooths out spikes by combining many frame measurements into a single number, which can mask severe stutters. For example, if 99 frames render in 6 ms but one frame takes 100 ms, the average FPS still looks reasonable, yet that 100 ms spike is a jarring freeze lasting one tenth of a second. Frame time metrics — especially 1% low and 0.1% low frame times — expose these outliers directly. Professional benchmarking tools like CapFrameX and FCAT-VR report frame times for exactly this reason.
What frame time do I need to achieve for a smooth gaming experience at common refresh rates?
At 60 Hz you need a consistent frame time at or below 16.67 ms. At 144 Hz the target drops to 6.94 ms, and at 240 Hz it is just 4.17 ms per frame. Any frame that exceeds its target time budget causes the display to repeat the previous frame, which manifests as a stutter or micro-freeze. For competitive gaming, consistency of frame time matters as much as the average — an erratic 6–14 ms range at a 144 Hz target will feel worse than a steady 8 ms, even though the averages differ.
How do I use frame time data to diagnose GPU or CPU bottlenecks?
If frame times are high and inconsistent, check whether your GPU or CPU is the limiting factor using a monitoring tool like MSI Afterburner or GPU-Z. A GPU bottleneck shows up as near-100% GPU usage with the CPU mostly idle, while a CPU bottleneck presents the reverse. Frame time spikes that coincide with specific in-game events — loading new areas, many AI agents on screen — often point to CPU stalls. Spikes that occur randomly during steady scenes more often indicate VRAM overflow or driver issues. Pairing frame time data with hardware utilization logs gives you the clearest diagnosis.