Technology

FPS to ms Frame Latency Calculator (+ Smoothness Table)

Convert FPS to frame latency in milliseconds: 60 FPS = 16.67 ms, 144 FPS = 6.94 ms, 240 FPS = 4.17 ms. Free calculator + full FPS-to-ms reference table and smoothness tiers.

Data verified · June 2026
Edited by Martín Rodríguez
Formula verified by automated tests
Private — runs on your device

Suggest an improvement

Calculator Free · Private

Edited by: Martín Rodríguez (editorial policy )

Suggest an improvement

🧮 Keep calculating

Gaming PC Budget Calculator by FPS TargetFind out how much to spend on a gaming PC in 2026. Get GPU and CPU recommendations matched to your target FPS — 60, 144, or 240 FPS — at 1080p, 1440p, or 4K.Ideal Weight for Women by Height (Devine, Robinson & Hamwi)Find your ideal weight for women by height using three evidence-based formulas (Devine, Robinson, Hamwi). Includes a reference chart from 5'0" to 6'0" and frame size adjustments.PC Power Consumption CalculatorCalculate total watts and recommended PSU for your gaming PC. CPU + GPU + components with 30% headroom. Free, instant. Calculate now.Docker Image Size Calculator (by base image + dependencies)Pick a base (Alpine, Debian slim, Ubuntu, distroless), add dependency MB, get the total — plus a base-image size table and how to shrink it.

Want to change something?Edit any field and calculate again.

Instant resultIt recalculates in your browser, no page reload.

Fast and transparent

How to use this calculator

Follow this tool’s steps, then review its formula, assumptions, and limits below.

Step by step

Enter your data

Tap the Calculate button

Check the result

This calculator converts frames per second (FPS) into frame latency — the milliseconds each frame takes on screen — using the exact formula Frame Latency (ms) = 1000 ÷ FPS. At 60 FPS each frame lasts 16.67 ms; at 144 FPS just 6.94 ms; at 240 FPS only 4.17 ms. Lower ms per frame means snappier, smoother motion and less perceived input lag. Use it to pick a monitor refresh rate (60 Hz vs 144 Hz vs 240 Hz), set an in-game FPS cap, or diagnose stutter — and read the full FPS-to-ms table below.

When to use this calculator

Choosing a monitor refresh rate (60 Hz vs 144 Hz vs 240 Hz) by matching your GPU's average FPS to the panel's native cadence to avoid tearing or wasted frames.
Setting an in-game FPS cap in titles like CS2 or Valorant so frame pacing stays even — capping at 240 FPS yields 4.17 ms/frame, matching a 240 Hz panel exactly.
Diagnosing input-lag complaints where a drop from 120 to 90 FPS raises frame latency from 8.33 ms to 11.11 ms — a gap skilled players notice.
Judging whether a GPU upgrade is worth it perceptually: 60→90 FPS saves 5.56 ms/frame, but 120→144 FPS saves only 1.39 ms/frame.

FPS to Frame Latency Reference Table

FPS	Frame Latency (ms)	Matching Refresh Rate	Smoothness Tier
24	41.67 ms	Cinema (24p)	❌ Choppy for gaming
30	33.33 ms	30 Hz	⚠️ Minimum playable
45	22.22 ms	45 Hz (VRR range)	🟡 Acceptable
60	16.67 ms	60 Hz	✅ Smooth (standard)
72	13.89 ms	72 Hz	✅ Smooth
90	11.11 ms	90 Hz	✅ Very smooth
120	8.33 ms	120 Hz	🏆 Competitive
144	6.94 ms	144 Hz	🏆 Competitive
165	6.06 ms	165 Hz	🏆 Competitive
240	4.17 ms	240 Hz	🚀 Pro / Esports
360	2.78 ms	360 Hz	🚀 Pro / Esports
480	2.08 ms	480 Hz	🚀 Bleeding edge

Fuente: Blur Busters & NVIDIA FrameView (formula: Frame Latency ms = 1000 ÷ FPS). Perceptual returns flatten for most players above ~240 FPS.

How it works

How FPS Converts to Milliseconds

The single governing formula turns a frame rate into the time budget for each frame:

Frame Latency (ms) = 1000 ÷ FPS

Example: 60 FPS → 1000 ÷ 60 = 16.67 ms/frame

This tells you how long the CPU, GPU, and display pipeline have to produce one complete image. If rendering takes longer than this budget, a frame is dropped or repeated, causing visible stutter. NVIDIA's FrameView and the FCAT methodology measure this value directly as "frame time" and flag spikes above ~1.5× the average as stutter events.

To go the other way (ms → FPS), just invert it: FPS = 1000 ÷ ms. A 5 ms frame time equals 200 FPS.

---

FPS to ms Reference Table

Perceptual returns flatten for most players above ~240 FPS; gains beyond that are marginal except for elite esports athletes.

---

ms to FPS (Reverse Lookup)

Frame Time (ms)	FPS
33.33 ms	30
16.67 ms	60
11.11 ms	90
8.33 ms	120
6.94 ms	144
4.17 ms	240
2.78 ms	360

---

Why Lower ms Feels Smoother

Smoothness is about how recent the image on screen is. At 30 FPS the newest frame is up to 33.33 ms old; at 144 FPS it is at most 6.94 ms old. Because the visual system can track motion below ~10 ms inter-frame gaps, dropping under that threshold is where the jump from "playable" to "fluid" is most obvious. Beyond pure FPS, frame pacing consistency matters: an average of 120 FPS that swings between 2 ms and 14 ms frames feels worse than a rock-steady 90 FPS at 11.11 ms.

---

Typical Use Cases with Numbers

Case 1 — Console-to-PC Transition

A player on 30 FPS console (33.33 ms/frame) upgrades to a PC delivering 144 FPS (6.94 ms/frame). Frame latency is cut by 79%, and motion reads as dramatically more fluid because the inter-frame gap drops below the ~10 ms threshold.

Case 2 — Competitive FPS Cap

A Valorant player's GPU averages 280 FPS on a 240 Hz monitor. Capping at 240 FPS (4.17 ms/frame) eliminates tearing and keeps pacing even. Running uncapped at 280 FPS (3.57 ms/frame) adds only 0.60 ms of saved latency while raising GPU heat and power draw.

Case 3 — VR Minimum

Meta recommends 90 FPS (11.11 ms/frame) as the comfortable VR minimum. Below 72 FPS (13.89 ms/frame) many users feel motion sickness because the vestibular-visual mismatch window exceeds ~15 ms.

---

Common Mistakes

1. Confusing FPS with refresh rate — A 144 Hz monitor cannot show more than 144 unique frames per second. Rendering at 200 FPS on a 144 Hz display (without V-Sync) causes tearing but does not push on-screen frame latency below 6.94 ms.

2. Trusting average FPS over frame pacing — A "120 FPS average" hides spikes. Two frames of 2 ms and 14.67 ms (instead of 8.33 ms each) feel stuttery despite a 120 FPS average.

3. Assuming all 60 FPS looks identical — 60 FPS film (24p with motion blur upscaled) looks different from 60 FPS in a sharp-rendered game. Engines add motion blur to soften fast camera pans.

4. Ignoring display lag on top of frame latency — 16.67 ms frame latency (60 FPS) plus 10 ms display input lag = 26.67 ms total. Pick monitors with ≤1 ms gray-to-gray (GTG) response to keep added latency negligible.

5. Believing the "eye only sees 60 FPS" myth — The human visual system has no fixed FPS cap; flicker can be detected well above 60 Hz. The practical gaming ceiling where returns diminish for most players is ~240 FPS, not 60.

---

Related Calculators

Aspect Ratio Calculator

Monitor Size & PPI Calculator

Internet Speed / Bandwidth Calculator

Worked Example: 60 FPS

Enter your frame rate: 60 FPS

Apply the formula: 1000 ÷ 60

Result: each frame lasts 16.67 ms

60 FPS = 16.67 ms/frame (Smooth tier)

Frequently asked questions

How many milliseconds is 60 FPS?

60 FPS equals 16.67 ms per frame, because 1000 ÷ 60 = 16.67. That means a brand-new image appears every 16.67 milliseconds. For comparison, 30 FPS is 33.33 ms (twice as slow) and 120 FPS is 8.33 ms (twice as fast).

What is the formula to convert FPS to ms?

Frame Latency (ms) = 1000 ÷ FPS. Divide 1000 by your frame rate to get the milliseconds each frame lasts. To reverse it, FPS = 1000 ÷ ms — so a 4.17 ms frame time equals 240 FPS.

Is 144 FPS much smoother than 60 FPS?

Yes. 60 FPS is 16.67 ms per frame and 144 FPS is 6.94 ms — a 58% reduction in frame latency. The on-screen image is always more recent at 144 FPS, so motion looks crisper and perceived input lag drops noticeably, especially in fast-paced shooters and competitive play.

What FPS do I need for competitive gaming?

Most pro esports players target 240 FPS (4.17 ms/frame) on 240 Hz monitors, with 144 FPS (6.94 ms/frame) the current minimum standard for ranked play in CS2, Valorant, and Apex Legends. NVIDIA and independent lab studies link the latency reductions from 60 to 240 FPS with measurable aim improvements in first-person shooters.

Why does 60 FPS feel smooth in some games but choppy in others?

Frame pacing matters as much as the average. If frames arrive every 16.67 ms like clockwork, 60 FPS feels fluid; if frame times swing between 5 ms and 30 ms (averaging ~17.5 ms), the irregularity reads as stutter. Slow-paced RPGs feel fine at 60 FPS while fast-twitch shooters expose frame-time variance more harshly. Motion blur settings also change perceived smoothness.

Is there a point where higher FPS stops making a difference?

For most players, perceptual returns flatten above 240 FPS. Going from 240 FPS (4.17 ms) to 360 FPS (2.78 ms) saves just 1.39 ms — detectable mainly by elite athletes in controlled tests. NVIDIA research found measurable aim gains up to roughly 240 FPS, with diminishing returns beyond that for average players.

What's the difference between frame latency and input lag?

Frame latency (ms/frame = 1000 ÷ FPS) is the render pipeline's per-frame time budget. Input lag is the total delay from a physical action — like a mouse click — to pixels changing on screen, and it includes frame latency plus CPU/GPU processing and the monitor's own response time (typically 1–10 ms). A 240 FPS setup has 4.17 ms frame latency; add a 1 ms GTG monitor for roughly 5–7 ms total system latency.

Should I cap my FPS, and at what value?

Capping FPS at or just below your monitor's refresh rate reduces GPU heat, power draw, and frame-time variance. A common rule is to cap at (monitor Hz − 3): for a 144 Hz panel, cap at 141 FPS (7.09 ms/frame). With G-Sync or FreeSync (VRR), cap 3–10 FPS below the panel's max to keep the variable refresh zone active and avoid tearing.

What FPS is needed for VR to avoid motion sickness?

90 FPS (11.11 ms/frame) is the comfortable VR minimum per Meta/Oculus engineering guidance. At 72 FPS (13.89 ms/frame) some users feel discomfort during fast head turns, while 120 FPS (8.33 ms/frame) is comfortable for nearly everyone. Frame rates below 60 FPS in VR cause strong vestibular-visual conflict and should be avoided.

Does V-Sync change frame latency?

V-Sync locks rendering to the display's refresh cycle, removing tearing but adding up to one full frame of latency — up to 16.67 ms on a 60 Hz monitor. NVIDIA G-Sync and AMD FreeSync use Variable Refresh Rate to sync the monitor to the GPU dynamically, eliminating tearing without that latency penalty, which is why VRR is preferred for competitive gaming.

Sources & references

Methodology & trust

Editorial

Technology calculator with its formula verified automatically against Blur Busters – frame time, refresh rate and motion clarity research, per our editorial policy and methodology.

Updates

Updated: June 2026. Parameters are verified periodically against the cited sources.

Privacy

Calculations run 100% in your browser. We do not store or transmit your data.

Limitations

Indicative results. For critical decisions, consult a professional.

📌 How to cite this calculator

Rodríguez, M. (2026). FPS to ms Frame Latency Calculator (+ Smoothness Table). Hacé Cuentas. https://hacecuentas.com/en/fps-perceived-smoothness-gaming

Content licensed under CC-BY 4.0 — reuse it citing the source with a link to Hacé Cuentas.

✉️ Report an error in this calculator