BottleneckCalculator.biz
Check my PC
Frame pacing tool

FPS to Frame-Time Calculator

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.

Live calculation

Convert FPS into milliseconds per frame

Enter the sustained or target frame rate. The result is the total time budget shared by CPU preparation, rendering and display delivery.

FPS
6.94 msper frame

Formula: 1,000 divided by FPS.

What the frame-time result means

FPS measures throughput over an interval. Frame time measures how long an individual frame takes. A 60 FPS target allows about 16.67 milliseconds per frame, 120 FPS allows 8.33 milliseconds, 144 FPS allows 6.94 milliseconds, and 240 FPS allows only 4.17 milliseconds. The CPU and GPU do not each receive that full budget independently because their work overlaps and queues through the rendering pipeline.

Read spikes, not only the average

A stable average can hide disruptive spikes. Use the calculated budget as a reference line on a frame-time graph, then inspect the frequency and size of excursions. A short spike to 30 milliseconds is visible even when the surrounding frames keep average FPS high.

Use frame time to compare performance consistently

Keep the capture repeatable

Capture the same scene, warm-up state and settings. Compare the median or average frame time with percentile lows and the shape of the graph. If lowering resolution reduces GPU frame time and improves the distribution, the graphics path had recoverable headroom. If the result remains flat while a critical CPU thread is saturated, investigate CPU-side or engine work.

  • 60 FPS target: 16.67 ms per frame.
  • 120 FPS target: 8.33 ms per frame.
  • 144 FPS target: 6.94 ms per frame.
  • 240 FPS target: 4.17 ms per frame.

Frame time, refresh rate and 1% lows are different measurements

Combine all three views

Refresh rate describes how often the display can update. FPS describes delivered frame throughput. A frame-time trace shows consistency, while a 1% low summarizes the slower tail of the capture. Use all of them together and keep V-Sync, variable refresh rate, frame caps and frame generation documented.

Continue from the result

Use the result as a starting point. Choose the next resource that matches what you want to measure or understand.

Frame Time and 1% LowsLearn how spikes and percentile lows reveal frame-pacing problems. PC Bottleneck DiagnosticsTurn the calculated budget into a repeatable test of the whole system. CPU Bottleneck GuideConnect a short frame budget to critical-thread and game-engine pressure. PC Bottleneck ChecklistSave the target and capture a repeatable baseline before comparing hardware. All PC Performance ToolsCompare frame budgets, resolution load and CPU-GPU balance.