Frame Time to FPS Calculator: Milliseconds, Refresh Budgets & Pacing

FPS and frame time are the same number seen from two sides: 1000 ÷ FPS = milliseconds per frame. This tool converts both directions instantly and plots your frame time against the refresh budgets that matter — 16.67ms for 60Hz, 6.94ms for 144Hz, 4.17ms for 240Hz, 2.78ms for 360Hz.

This page covers frame time to fps calculator scenarios — including fps to milliseconds converter, frame time calculator — using the same estimation engine as the main FPS calculator. Prefer the wide view? Browse every tool in display, upscaling & frame-math tools.

FPS ↔ Frame Time Converter & Pacing Analyzer

Frames per Second

Frame Time (ms)

1000 ÷ FPS = ms · 1000 ÷ ms = FPS

60Hz budget16.67 ms — —

144Hz budget6.94 ms — —

240Hz budget4.17 ms — —

360Hz budget2.78 ms — —

Pacing Verdict

At 120 FPS (8.33ms), you clear the 60Hz and 144Hz budgets with room to spare — frames present the instant they finish with VRR, and every frame fits inside the 16.67ms and 6.94ms windows.

Remember: averages hide pacing. A 1% low of 45 FPS is a 22.2ms frame — more than three 144Hz budgets stacked.

Frame Time Reference Table — FPS, Milliseconds and Refresh Budgets

Frame Time Reference Table — FPS, Milliseconds and Refresh Budgets
FPS	Frame Time (ms)	Fits 60Hz (16.67ms)	Fits 144Hz (6.94ms)	Fits 240Hz (4.17ms)
24	41.67	—	—	—
30	33.33	—	—	—
45	22.22	—	—	—
60	16.67	✓	—	—
90	11.11	✓	—	—
120	8.33	✓	—	—
144	6.94	✓	✓	—
165	6.06	✓	✓	—
240	4.17	✓	✓	✓
360	2.78	✓	✓	✓

A frame "fits" a refresh budget when its frame time is at or below the budget. Over-budget frames are either dropped (tearing without V-Sync) or delayed (queued with V-Sync).

Frame Time to FPS Calculator: The Engineering Detail

Why Frame Time Tells the Truth That FPS Hides

Averages conceal pacing. Two systems at "60 FPS" are different machines if one renders every 16.7ms like clockwork and the other alternates 8ms and 25ms frames — the second visibly stutters despite the identical counter. Frame time is where consistency lives, which is why every serious benchmarking tool plots milliseconds, not FPS.

Variance matters more than the mean: ±2ms around 8ms feels flawless; ±2ms around 14ms feels broken.
1% lows are just frame-time percentiles — the worst 1% of frame times, averaged.
Stutter is a frame-time spike pattern: a single 40ms frame among 8ms frames is visible even at 120 FPS.
CapframeX, PresentMon and RTSS all graph ms — learn to read the spikes, ignore the FPS counter.

Pro tip: convert your game’s 1% low to frame time and compare it to the refresh budget — if your worst frames exceed the 16.67ms budget at 60Hz, you now know exactly why it "feels" under 60.

Refresh Budgets: The 16.67 / 6.94 / 4.17 / 2.78 Millisecond Club

Every display refresh defines a frame budget: 60Hz gives you 16.67ms, 144Hz gives 6.94ms, 240Hz gives 4.17ms, 360Hz gives 2.78ms. Missing the budget doesn’t just lower FPS — with V-Sync it doubles your present delay (the frame waits a full extra refresh), which is why a 55 FPS average on a 60Hz V-Sync display presents like 30.

Budget misses are cliff events, not slopes: 6.95ms at 144Hz V-Sync presents at 13.9ms, not 6.95ms.
VRR (G-Sync/FreeSync) turns cliffs into ramps — the panel refreshes when the frame is ready.
FPS caps exist to stay under budget with headroom: 141 cap on 144Hz absorbs spikes without queuing.
The last 10% of FPS (141 vs 155) matters less than never missing the budget.

Pro tip: set your cap 3–5 FPS under refresh (141/144) with VRR on — spikes land in the VRR window instead of the V-Sync cliff, and pacing stays flat.

Using the Converter: Latency Chains and Percentile Math

Frame time composes into latency chains: render frame time + display scanout + peripheral/driver overhead ≈ click-to-photon. The converter is the arithmetic backbone for those chains — and for reading benchmark logs, where percentiles are stored in milliseconds and headlines are printed in FPS.

Scanout at 240Hz adds ~4.2ms worst-case; average click-to-photon adds half that.
A 1% low of 45 FPS = 22.2ms — convert it and compare to your budget to quantify the "feel".
0.1% lows (the worst 1 in 1,000 frames) explain "random" hitching that averages never show.
Frame-time deltas between systems matter more than FPS deltas when comparing upgrades.

Pro tip: when comparing two GPUs from reviews, diff their frametime graphs at the spikes — a card with equal average but shallower spikes is the smoother machine, full stop.

Frame Time to FPS Calculator — FAQs

How many milliseconds is 60 FPS?

16.67ms per frame (1000 ÷ 60). That’s also the 60Hz refresh budget: any frame taking longer than 16.67ms either tears or waits for the next refresh cycle. 30 FPS is 33.3ms, 120 FPS is 8.33ms, and 240 FPS is 4.17ms.

How do I convert frame time to FPS?

Divide 1000 by the frame time in milliseconds: FPS = 1000 ÷ ms. For example, 8.5ms ≈ 118 FPS, and 22ms ≈ 45 FPS. The converter above runs both directions — enter either number and the other updates instantly.

Why does my game stutter even at high FPS?

Stutter is frame-time variance, not average throughput. A single 35ms spike between 5ms frames is visible as a hitch even at 150 FPS. Common causes: shader compilation, VRAM residency swaps, background processes, and CPU-thread contention — all visible as spikes on a frametime graph.

What frame time do I need for 144Hz?

6.94ms per frame (1000 ÷ 144). To hold 144Hz with VRR headroom, your worst frames should land near 6.9ms — which is why the 1% low equivalent (roughly 130+ FPS) matters more than the average when judging whether a system truly "runs 144Hz".

Is frame time more important than FPS?

For feel, yes — frame time (and its variance) is what your eyes and hands actually experience; FPS is just a summary statistic. Two systems with identical averages but different frame-time consistency are genuinely different gaming experiences. Always compare frametime graphs when the stakes are real.

More in Display, Upscaling & Frame-Math Tools

1080p vs 1440p vs 4K FPS CalculatorComparisonFour-way resolution matrix with pixel multipliers, % drops and VRAM pressure per tier.DLSS vs FSR FPS CalculatorComparisonNative-to-Ultra-Performance upscaling ladder with internal resolutions and FG multipliers.Monitor Refresh Rate to FPS CalculatorToolFPS-range to Hz-tier matching with VRR windows and DP/HDMI bandwidth verdicts.PSU Wattage Calculator for Gaming PCToolTransient-aware PSU sizing with ATX 3.1 / 12V-2x6 cable requirements per GPU tier.

Next step — cross-silo

FPS targets by gaming genre →

Once you can read frame budgets, match them to the frame rates your favorite genres actually demand.

Guide

Back to the hub

Done here? The main FPS calculator covers every game, resolution and preset in one place — with the pre-built combo matrix and full benchmark tables.

Open the main FPS calculator ↗