How do I convert FPS to ms?

Divide 1000 by the frame rate: frame time (ms) = 1000 / FPS. 30 FPS = 33.33 ms, 60 FPS = 16.67 ms, 120 FPS = 8.33 ms, 144 FPS = 6.94 ms, 240 FPS = 4.17 ms. To go back, FPS = 1000 / ms, so 10 ms = 100 FPS.

How many ms is 144 Hz or 240 Hz?

One refresh at 144 Hz lasts 1000 / 144 = 6.94 ms; at 165 Hz 6.06 ms; at 240 Hz 4.17 ms; at 360 Hz 2.78 ms. This is the scan-out interval, not the full input-to-photon latency, which also includes game, render queue and panel response time.

How is 1% low FPS calculated?

Sort the frame times from a capture. The percentile method takes the 99th-percentile frame time (the time that 99% of frames beat) and converts it with 1000 / ms. The "1% low average" method used by CapFrameX averages the slowest 1% of frame times and converts that mean. The average method is always equal or lower, so state which one you report. 0.1% low uses the slowest 0.1%.

Why is my average FPS different from the average of the FPS values?

Average FPS should be frames divided by elapsed time, which equals 1000 / mean frame time. Averaging per-frame FPS values weights fast frames too heavily: 10 ms and 30 ms frames average 20 ms (50 FPS), but the mean of 100 and 33.3 FPS is 66.7 FPS.

What FPS cap should I use with G-Sync or FreeSync?

Cap a few frames below the maximum refresh so the frame rate never reaches the V-Sync ceiling. Blur Busters' G-SYNC 101 tests recommend at least 3 FPS below the refresh rate (141 FPS at 144 Hz). NVIDIA Reflex and Ultra Low Latency apply a lower automatic cap that users have measured close to Hz − Hz²/3600 (about 138 FPS at 144 Hz).

What is low framerate compensation (LFC)?

When the frame rate falls below a VRR monitor's minimum refresh (for example 48 Hz), LFC shows each frame two or more times so the panel stays inside its range: 40 FPS on a 48–144 Hz panel is shown at 80 Hz. It needs a maximum refresh at least twice the minimum; a 48–75 Hz panel cannot do it.

Why does frame time matter more than average FPS for smoothness?

Average FPS hides frame-to-frame variation. A 60 FPS average can contain frames from 5 ms to 50 ms; a single 50 ms frame is a visible hitch. Frame-time graphs, 1% lows and stutter counts show that variation.

Is monitor refresh rate the same as rendered FPS?

No. Refresh rate (Hz) is how often the display scans out an image; FPS is how often the game produces one. On a fixed-refresh display they are decoupled: frames are repeated, torn, or held by V-Sync. With VRR the display waits for each new frame while the frame rate is inside its range.

Why are CPU and GPU times compared with max() instead of added together?

The CPU prepares frame N+1 while the GPU renders frame N, so throughput is set by the slower stage: max(CPU, GPU). Adding them would describe a fully serialized pipeline, which is not how modern engines run.

Gaming FPS & Frame Time Calculator

Convert FPS to frame time in ms (1000 / FPS) and back, get 1% and 0.1% lows from a pasted frame-time log, check a G-Sync/FreeSync VRR window and FPS cap, and compare CPU vs. GPU frame budgets.

Bidirectional FPS & Frame Time Converter

Convert between frames per second (FPS) and milliseconds per frame (ms = 1000 / FPS).

Average FPS

Range: 1.0 to 1000.0 FPS

Frame Time (ms)

Range: 1.0 to 1000.0 ms

1% Low FPS (optional benchmark metric)

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

Equivalent frames per second 60.0 FPS

Equivalent frame time 16.67 ms

Theoretical frames rendered in 1000 ms 60.0

Display Refresh Interval & Alignment

Compare display scan-out intervals against application delivery rate.

Display Refresh (Hz)

Range: 24 to 500 Hz

Observed In-Game FPS

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

Rate comparison —

Fixed-refresh half-rate target 72.0 FPS (13.89 ms)

Display pipeline note Presented FPS and displayed FPS can differ based on sync mode.

VRR Window (G-Sync / FreeSync) & FPS Cap

VRR minimum (Hz)

VRR maximum (Hz)

= Display Refresh

The minimum is in the monitor spec or driver panel (often 48 Hz; 1 Hz for G-Sync module displays).

VRR window —

Low framerate compensation —

Observed FPS on this panel —

FPS cap, 3 below max (Blur Busters) —

Reflex-style cap ≈ Hz − Hz²/3600 —

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 Frame Rate (FPS)

Target budget: 1000 / Target FPS (e.g. 144 FPS = 6.94 ms)

Measured CPU Time (ms)

Game logic, physics & draw submission

Measured GPU Time (ms)

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)

CPU Stage Execution: 4.50 ms 65% of budget

GPU Stage Execution: 7.80 ms 112% of budget

FPS to ms Chart (Frame Time = 1000 / FPS)

FPS / Hz	Frame time	Where you see it
24	41.67 ms	Film cadence
30	33.33 ms	Console performance floor, 30 FPS cap
40	25.00 ms	40 FPS mode on 120 Hz TVs (3 refreshes per frame)
45	22.22 ms	Half of 90 Hz (VR reprojection)
48	20.83 ms	Common FreeSync minimum
50	20.00 ms	PAL video, 100 Hz half rate
60	16.67 ms	60 Hz monitors and TVs
75	13.33 ms	Entry high-refresh monitors
90	11.11 ms	VR headsets
100	10.00 ms	100 Hz ultrawides
120	8.33 ms	120 Hz TVs, consoles, laptops
144	6.94 ms	Most common gaming monitor
165	6.06 ms	165 Hz monitors
180	5.56 ms	180 Hz monitors
200	5.00 ms	200 Hz ultrawides
240	4.17 ms	Competitive esports monitors
280	3.57 ms	280 Hz overclocked panels
360	2.78 ms	360 Hz esports panels
480	2.08 ms	480 Hz OLED panels
500	2.00 ms	500 Hz panels
1000	1.00 ms	1 ms frame time

Pipeline note: The refresh interval is only one part of input latency. A higher frame rate can still lower latency on a fixed-refresh display because each scan-out shows a newer frame, but without sync it tears.

How 1% Lows and VRR Limits Are Calculated

Average FPS = number of frames ÷ capture seconds = 1000 ÷ mean frame time. Worked example: 99 frames at 10 ms plus one 50 ms hitch take 1,040 ms, so the average is 100 ÷ 1.04 s = 96.15 FPS.

1% low (P99) sorts frame times and takes the one at rank ⌈0.99 × n⌉, then converts it to FPS. In the example that frame is 10 ms, so the P99 low is 100 FPS: one hitch in 100 frames is not enough to move a percentile. 1% low average averages the slowest 1% of frames instead (here the single 50 ms frame) and gives 20 FPS. Use captures of at least 1,000 frames (10,000 for 0.1% lows) and report the method.

VRR window: a 48–144 Hz FreeSync panel follows any frame time between 1000/144 = 6.94 ms and 1000/48 = 20.83 ms. Below 48 FPS, LFC shows each frame ⌈48 ÷ FPS⌉ times (40 FPS → 2× → 80 Hz). LFC needs max ≥ 2 × min. Above the maximum, the display falls back to V-Sync or tearing, which is why caps sit a few FPS below the refresh rate.

Summary

A deterministic frame timing utility for gaming and real-time graphics. Convert between frames per second (FPS) and milliseconds per frame, compute average FPS, 1% lows and 0.1% lows from a pasted PresentMon / CapFrameX / MangoHud frame-time log, check whether a frame rate sits inside a variable refresh rate (VRR) window with low framerate compensation (LFC), pick an FPS cap below the refresh rate, and analyze measured CPU and GPU times against a target frame budget.

How it works

Frame time and FPS are reciprocals: frame time (ms) = 1000 / FPS, and FPS = 1000 / frame time (ms). 144 FPS = 6.94 ms; 16.67 ms = 60 FPS.
Average FPS from a log is time-weighted: frames ÷ total seconds = 1000 ÷ mean frame time. Averaging the per-frame FPS values instead overstates it.
1% low is reported two ways: the 99th-percentile frame time converted to FPS, and the mean of the slowest 1% of frames converted to FPS. 0.1% low uses the 99.9th percentile.
A VRR display (G-Sync, FreeSync, HDMI VRR) follows the frame rate between its minimum and maximum refresh. Below the minimum, LFC repeats each frame when max ≥ 2 × min.
The frame-time budget tool compares measured CPU and GPU times with max(CPU, GPU), because the two stages run in parallel on different frames.

Use cases

Convert benchmark frame rates (FPS) into exact frame durations (ms) for pacing and latency analysis.
Paste a frame-time column from PresentMon, CapFrameX, MangoHud or OCAT to get average FPS, 1% low, 0.1% low and stutter counts.
Check whether a game's frame rate stays inside a monitor's FreeSync / G-Sync range and whether LFC covers drops below it.
Choose an FPS cap a few frames below the refresh rate so VRR stays engaged and V-Sync latency is avoided.
Identify whether a rendering loop is CPU-bound or GPU-bound using measured execution times.

Frequently Asked Questions

Last updated: 2026-10-09 · Reviewed by Nham Vu

Gaming FPS & Frame Time Calculator

Bidirectional FPS & Frame Time Converter

Conversion & Pacing Output

Display Refresh Interval & Alignment

Scan-Out & Pacing Diagnostics

VRR Window (G-Sync / FreeSync) & FPS Cap

Average FPS, 1% Low & 0.1% Low from a Frame-Time Log

Log Summary

Pipelined Frame Time Budget (CPU vs. GPU)

Budget Analysis Results

FPS to ms Chart (Frame Time = 1000 / FPS)

How 1% Lows and VRR Limits Are Calculated

Summary

How it works

Use cases

Frequently Asked Questions

Gaming FPS & Frame Time Calculator

Use the Gaming FPS & Frame Time Calculator

Bidirectional FPS & Frame Time Converter

Conversion & Pacing Output

Display Refresh Interval & Alignment

Scan-Out & Pacing Diagnostics

VRR Window (G-Sync / FreeSync) & FPS Cap

Average FPS, 1% Low & 0.1% Low from a Frame-Time Log

Log Summary

Pipelined Frame Time Budget (CPU vs. GPU)

Budget Analysis Results

FPS to ms Chart (Frame Time = 1000 / FPS)

How 1% Lows and VRR Limits Are Calculated

Summary

How it works

Use cases

Frequently Asked Questions