Convert Frames per Second into Milliseconds per Frame
Conversion: Convert a frame-rate target into the millisecond budget available to prepare and render each frame. Use the result to read frame-time captures, refresh-rate targets and 1% lows more accurately.
- Two-way FPS and millisecond conversion
- Common refresh targets
- Frame-time trace interpretation
Move between FPS and milliseconds
Enter either value. The other field updates immediately, so you can translate a target FPS or a measured frame-time spike without changing calculators.
The calculation runs in this browser. No frame-rate value is sent to the server.
Use the budget as a line on the graph
FPS reports throughput across an interval. Frame time reports the duration of each delivered frame. At 60 FPS the budget is 16.67 milliseconds. At 144 FPS it falls to 6.94 milliseconds. The shorter budget is why a small delay that is harmless at 60 FPS can cause a visible miss at a high refresh target.
The slow frame matters even when the average looks healthy
The example contains four frames close to a 144 FPS budget and one frame that takes about twice as long. An average can soften that event. A trace preserves it. Compare how often the line is crossed, how far a spike rises and whether the spike repeats during the same action.
Reference budgets for common refresh targets
| Target | Budget per frame | Useful interpretation |
|---|---|---|
| 30 FPS | 33.33 ms | Common for visually heavy workloads where responsiveness is secondary. |
| 60 FPS | 16.67 ms | A widely used baseline for smooth real-time delivery. |
| 120 FPS | 8.33 ms | Requires both rendering speed and faster CPU-side frame preparation. |
| 144 FPS | 6.94 ms | A one millisecond delay consumes more than fourteen percent of the budget. |
| 240 FPS | 4.17 ms | Small scheduling, simulation and input delays become much more important. |
The CPU and GPU do not receive separate full budgets
CPU preparation and GPU rendering can overlap, queue and wait on synchronization. Do not add two timing values blindly or assume each stage may use the entire displayed budget. Compare measurements from the same capture and understand how the monitoring tool defines CPU time and GPU time.
Turn the conversion into a controlled test
- Choose the frame-rate target that matters for the display and game.
- Mark the calculated millisecond budget on a repeatable frame-time capture.
- Repeat the same scene after changing one graphics, CPU, memory or background-work variable.
- Keep the explanation only if the frame-time distribution responds as predicted.
Refresh rate, FPS, frame time and 1% lows answer different questions. Record frame caps, V-Sync, variable refresh rate, frame generation and the sample duration beside the result.
Take the budget to a real capture
Start with the Frame Time and 1% Lows to read slow frames, then use the PC Bottleneck Checklist to preserve the target and baseline.
