Gaming FPS & Frame Time Calculator
Convert bidirectionally between FPS and frame time in milliseconds, compare refresh rate intervals, and evaluate CPU vs. GPU frame-time budgets.
Use the Gaming FPS & Frame Time Calculator
Bidirectional FPS & Frame Time Converter
Convert between frames per second (FPS) and milliseconds per frame (ms = 1000 / FPS).
Range: 1.0 to 1000.0 FPS
Range: 1.0 to 1000.0 ms
Must be less than or equal to Average FPS.
Common Cadence Targets
Conversion & Pacing Output
Average Frame Time
16.67 ms
1000 / FPS
Average Rate
60.0 FPS
1000 / ms
1% Low Frame Time
—
1000 / 1% Low FPS
Stutter Ratio (Low FT / Avg FT)
—
1.00x = equal reported rates
Display Refresh Interval & Alignment
Compare display scan-out intervals against application delivery rate.
Range: 24 to 500 Hz
Range: 1 to 1000 FPS
Standard Display Standards
Scan-Out & Pacing Diagnostics
Display Scan Interval
6.94 ms
1000 / Refresh Rate
Rendered Frame Time
8.33 ms
1000 / Observed FPS
Pipelined Frame Time Budget (CPU vs. GPU)
Inspect measured CPU and GPU execution times. Modern graphics run concurrently in pipelined stages: effective throughput is governed by max(CPU, GPU), not their sum.
Target budget: 1000 / Target FPS (e.g. 144 FPS = 6.94 ms)
Game logic, physics & draw submission
Geometry, shading, post-processing
Bottleneck model is simplified. Pipeline overlap allows concurrency across frames, but deep render queues introduce input latency when the CPU runs ahead of a GPU-bound stage.
Budget Analysis Results
Target Budget Limit
6.94 ms
at target rate
Pipelined Frame Time
7.80 ms
max(CPU, GPU)
Frame Timing Principles & Pipeline Realities
| Cadence / Refresh | Frame Time | Reciprocal Relationship | Physical Timing Characteristic |
|---|---|---|---|
| 30 FPS / 30 Hz | 33.33 ms | 1000 / 30 = 33.33 ms | A 30 Hz refresh interval is about 33.3 ms. |
| 60 FPS / 60 Hz | 16.67 ms | 1000 / 60 = 16.67 ms | Baseline standard for 60 Hz scanning displays. |
| 120 FPS / 120 Hz | 8.33 ms | 1000 / 120 = 8.33 ms | Half the refresh interval of 60 Hz; total display latency depends on the full pipeline. |
| 144 FPS / 144 Hz | 6.94 ms | 1000 / 144 = 6.94 ms | Common gaming monitor scan interval. |
| 240 FPS / 240 Hz | 4.17 ms | 1000 / 240 = 4.17 ms | High-refresh competitive display cycle. |
| 360 FPS / 360 Hz | 2.78 ms | 1000 / 360 = 2.78 ms | A 360 FPS throughput target allows about 2.78 ms per frame. |
Pipeline Note: A higher application FPS can reduce input latency even on a fixed refresh display by presenting newer sampled game state closer to the scanout interval, though screen tearing can occur if the display lacks synchronization.
Summary
Convert bidirectionally between FPS and frame time in milliseconds, compare refresh rate intervals, and evaluate CPU vs. GPU frame-time budgets.
How it works
- Frame time and FPS are mathematical reciprocals: frame time (ms) = 1000 / FPS, and FPS = 1000 / frame time (ms).
- Comparing average FPS to 1% low FPS calculates the frame-time variance ratio, highlighting instantaneous pacing variance.
- Display refresh interval represents the hardware panel update scan duration (1000 / Hz), which is independent of application presentation rate.
- The frame-time budget tool evaluates measured CPU and GPU execution times concurrently using max(CPU, GPU) to identify the primary pipeline limiter.
Use cases
- Convert benchmark frame rates (FPS) into exact frame durations (ms) for pacing and latency analysis.
- Convert target frame times (e.g. 16.67 ms, 6.94 ms) into required presentation frame rates.
- Evaluate 1% low pacing consistency and stutter ratios from benchmark log data.
- Compare application render cadence with monitor refresh scan intervals.
- Identify whether a rendering loop is CPU-bound or GPU-bound using measured execution times.