Frame Time to FPS Calculator: Convert Frame Time to FPS Instantly
Convert frame time (ms) to frames per second and back β instantly see your GPU's real-world performance
Try the calculator
Math runs in your browser. No sign-up.
FPS and frame time averages hide per-frame variance. Always review the full frame-time graph from a capture tool for a complete picture of smoothness.
FPS equals 1000 divided by frame time in milliseconds; frame time equals 1000 divided by FPS. At exactly 60 FPS each frame takes 16.667 ms; at 144 FPS each takes 6.944 ms. Average FPS alone is misleading β a game can average 100 FPS while occasional 33 ms spikes cause visible stutter that only the 1% low metric reveals.
**Frame time and FPS are exact reciprocals: FPS = 1000 Γ· frame_time_ms.** At 60 FPS every frame must render in exactly 16.667 ms; at 144 FPS the budget shrinks to 6.944 ms. The number most players watch β average FPS β hides spikes: a game averaging 100 FPS but spiking to 50 ms on 1% of frames will stutter visibly even though the average looks fine. Always check your 1% low alongside the average.
What is a frame time to fps?
Frame time and frames per second are exact mathematical reciprocals: FPS = 1000 / frame_time_ms, where 1000 is the number of milliseconds in one second by SI definition. At 60 FPS every frame must render in 16.667 ms; miss that budget and the monitor repeats the previous frame, producing judder. Average FPS hides this β the 1% low frame time (99th-percentile frame time) is the metric that exposes stutter. This calculator converts in both directions and computes your 1% low FPS and stutter ratio from a single frame-time capture. The formula and all constants are sourced to the BIPM SI Brochure (9th edition, 2019).
The formula
- FPS β frames rendered per second
- t_ms β time to render one frame, in milliseconds
- 1000 β milliseconds per second (exact SI definition: 1 s = 1000 ms)
Source: Reciprocal unit conversion: FPS = 1000 / frame_time_ms, derived from the SI definition 1 s = 1000 ms.
Worked examples
160 FPS target β standard 60 Hz monitor
The most common gaming target is 60 FPS. Applying FPS = 1000 / t_ms: 1000 / 16.667 = 59.998 FPS β 60 FPS (the tiny error is rounding 16.Μ6Μ to 16.667). The inverse confirms it: t_ms = 1000 / 60 = 16.6Μ ms per frame. With a 1% low frame time of 25.0 ms the 1% low FPS = 1000 / 25.0 = 40 FPS. The stutter ratio = 25.0 / 16.667 = 1.50Γ, sitting right on the boundary between smooth and mild variance. A player on a 60 Hz monitor would notice occasional brief dips below 40 FPS, though the average frame time looks acceptable.
2144 Hz high-refresh β competitive gaming
For a 144 Hz monitor the per-frame budget is t_ms = 1000 / 144 = 6.9Μ4 ms. Rounding to three decimal places gives 6.944 ms, so FPS = 1000 / 6.944 = 144.01 FPS (rounding artifact only). With a 1% low frame time of 10.0 ms: 1% low FPS = 1000 / 10.0 = 100 FPS. Stutter ratio = 10.0 / 6.944 = 1.44Γ, comfortably below 1.5Γ. This is a smooth profile β the worst 1% of frames still deliver 100 FPS, well above the 60 FPS threshold most players consider the floor for competitive play.
330 FPS locked β console-style target
Many console and cinematic-style PC games target 30 FPS. The frame budget is t_ms = 1000 / 30 = 33.3Μ ms. Entering 33.333 gives FPS = 1000 / 33.333 = 30.00 FPS. A 1% low frame time of 50.0 ms corresponds to 1% low FPS = 1000 / 50.0 = 20 FPS and a stutter ratio of 50.0 / 33.333 = 1.50Γ. Even at a locked-30 target, spikes to 50 ms are perceptible as judder β the 33 ms frame budget leaves almost no headroom before frames cross into the next refresh cycle on a 30 Hz output.
How to use this calculator
- Frame time β The time in milliseconds your GPU takes to render one frame. Find this in tools like FrameView, MSI Afterburner/RTSS, or CapFrameX.
- Frames per second (FPS) β The average number of frames rendered per second. Leave blank if you are converting from frame time above.
- 1% low frame time β The 99th-percentile frame time (the slowest 1% of frames). Report from CapFrameX, FCAT-OC, or FrameView. Leave blank if unknown.
- Read the result. Use the worked examples below to sanity-check against a known scenario.
Common mistakes and edge cases
Treating Average FPS as the Full Story
Average FPS is the arithmetic mean of all frames in a session. If 999 frames take 7 ms and one frame takes 700 ms, the average is about 7.7 ms (β 130 FPS) β but that 700 ms spike is a 0.7-second freeze that any player would notice. Always pair the average with the 1% low or a full frame-time graph. Tools like CapFrameX export percentile data alongside averages.
Rounding Frame Time Before Dividing
Entering 16.7 ms instead of 16.667 ms gives 1000 / 16.7 = 59.88 FPS instead of exactly 60 FPS. When diagnosing whether a game is hitting a locked frame-rate target, use the full precision value your capture tool reports. The formula has no built-in error; rounding the input is the only source of discrepancy.
Confusing 1% Low FPS with Minimum FPS
The 1% low is a percentile, not the absolute minimum. A single catastrophic 2000 ms stall raises the 0.1% low but may barely move the 1% low if it happened only once in an hour-long session. Minimum FPS is the worst single frame and is dominated by outliers. The 1% low is statistically more robust and is the industry-standard stutter metric for this reason.
Assuming a Higher Average FPS Means a Higher Refresh Rate Helps
A monitor renders at its native refresh rate regardless of GPU output. If your GPU delivers 80 FPS to a 144 Hz monitor, 64 of the 144 refresh cycles per second will repeat the previous frame. The monitor does not create new frames β it only displays what the GPU provides. A higher refresh rate improves perceived smoothness only when the GPU can sustain the corresponding frame time budget.
How small changes affect your result
Because FPS = 1000 / t_ms, the relationship is non-linear: a 1 ms improvement at low frame times (high FPS) is worth far more than a 1 ms improvement at high frame times (low FPS).
Frame time budgets at common refresh-rate targets
| Target FPS | Monitor Hz | Frame time budget (ms) | 1% low target (ms) | Stutter headroom (ms) |
|---|---|---|---|---|
| 30 FPS | 30 Hz | 33.333 | 50.000 | 16.667 |
| 60 FPS | 60 Hz | 16.667 | 22.222 | 5.556 |
| 120 FPS | 120 Hz | 8.333 | 11.111 | 2.778 |
| 144 FPS | 144 Hz | 6.944 | 9.259 | 2.315 |
| 165 FPS | 165 Hz | 6.061 | 8.081 | 2.020 |
| 240 FPS | 240 Hz | 4.167 | 5.556 | 1.389 |
| 360 FPS | 360 Hz | 2.778 | 3.704 | 0.926 |
1% low target assumes a stutter ratio of 1.5Γ (the smooth threshold). Stutter headroom = 1% low target β average frame time budget. All values computed from FPS = 1000 / t_ms.
Frequently asked questions
What is the formula to convert frame time to FPS?
How do I convert FPS back to frame time in milliseconds?
Why is frame time better than FPS for measuring smoothness?
What is the 1% low FPS and why does it matter?
What frame time do I need for 60 FPS?
What frame time do I need for 144 FPS?
What is a good stutter ratio?
How do I measure frame time on my PC?
Frame Time to FPS glossary
How we built this calculator
Methodology
The relationship between frame time and FPS is a strict mathematical reciprocal derived from the SI definition of the second. One second contains exactly 1000 milliseconds (BIPM SI Brochure, 9th ed., 2019, Table 6). Therefore:
Sources & references
Every numeric assumption traces to a primary source.
- BIPM SI Brochure, 9th edition (2019) β Table 6: non-SI units accepted for use with the SI (millisecond definition)INT
- NVIDIA FrameView β frame-time capture and analysis tool documentationUSA
- CapFrameX β open-source frame-time analysis tool (percentile methodology documentation)INT
- NVIDIA FCAT-OC methodology β frame-capture analysis at display outputUSA
- VESA DisplayHDR and Adaptive Sync specifications β refresh rate and frame-pacing definitionsINT
- Numora Editorial Policy. numora.net/editorial-policy