FPS to Frame Time Calculator
Convert frames per second (FPS) to frame time in milliseconds using the simple reciprocal formula. Use it to evaluate PC performance, troubleshoot stuttering (where frame time variance matters more than average FPS), and target specific frame-time budgets for VR or competitive gaming.
Last updated: May 2026
Compare with similar
About this calculator
The formula is: frame time (ms) = 1000 ÷ FPS. The 1000 converts seconds to milliseconds, and dividing by frame rate gives the average time each frame takes to render. Common targets: 30 FPS = 33.33 ms/frame (cinema-style, console baseline); 60 FPS = 16.67 ms (typical desktop / console enhanced mode); 90 FPS = 11.11 ms (minimum recommended for comfortable VR); 120 FPS = 8.33 ms (high-refresh monitors, competitive shooter target); 144 FPS = 6.94 ms (esports standard); 240 FPS = 4.17 ms (high-end competitive); 360 FPS = 2.78 ms (top-tier esports monitors). Edge cases: zero FPS produces division by zero (no frames rendered); very high FPS (1000+) is rarely achievable and often capped by the monitor's refresh rate even when the GPU can produce more. Frame time is a more useful metric than FPS for diagnosing stuttering because average FPS hides variance — a game with 90 FPS average but frame times spiking from 11 ms to 50 ms feels worse than a steady 60 FPS at 16.67 ms. The standard quality metrics are: 1% lows (worst 1% of frames, typically the bottom 1% of frame-time samples), 0.1% lows (worst 0.1%), and frame-time variance (standard deviation of frame times). For smooth perception, you want low average frame time AND low variance. Major reviewers and benchmark sites (TechSpot, Tom's Hardware, Gamers Nexus, Digital Foundry) report all three metrics because average FPS alone can be misleading. For VR specifically, frame time must stay under 11.1 ms (90 FPS) to avoid motion sickness; for competitive gaming, lower frame time reduces input-to-display latency (the time between mouse click and visible result on screen).
How to use
Example 1 — Standard 60 FPS gaming. Your game runs at a steady 60 FPS. Enter 60 for FPS. Result: 16.67 ms frame time. Verify: 1000 / 60 = 16.667 ms. ✓ This is the standard desktop and console "smooth" target — 16.67 ms per frame is below the 20 ms human-perception threshold where most people start noticing motion choppiness. Comfortable for single-player and casual play; pro shooter players typically push higher. Example 2 — Competitive esports target. You're benchmarking a CS2 setup running at 240 FPS on a 240 Hz monitor. Enter 240. Result: 4.17 ms frame time. Verify: 1000 / 240 = 4.167 ms. ✓ At 4.17 ms per frame, each frame is delivered every 4.17 ms — the lowest input-to-display latency achievable without going to even faster panels. The diminishing returns set in around 240 FPS: dropping from 144 FPS (6.94 ms) to 240 FPS (4.17 ms) reduces frame time by 2.77 ms; going from 240 to 360 (2.78 ms) saves only 1.39 ms more. For top-1% competitive shooter play, the saving matters; for casual gaming, 60–144 FPS is plenty.
Frequently asked questions
Why is frame time better than FPS for measuring smoothness?
Because FPS is an average that hides variance. A game with 90 FPS average can have frame times oscillating between 5 ms and 50 ms — the 50 ms spikes register as visible stutters even though the average looks great. Frame time as a per-frame value lets you see the actual distribution: consistent 11 ms frames are smooth; alternating 5 ms and 17 ms frames are jittery; frequent 30+ ms spikes are stuttery. Modern reviewers report "1% lows" (worst 1% of frame times) and "0.1% lows" (worst 0.1%) because these capture the stutter experience that average FPS hides. A monitor refreshes at fixed intervals (16.67 ms for 60 Hz, 6.94 ms for 144 Hz) and any frame that takes longer than the refresh interval causes a missed frame and visible hitching. For diagnosing performance problems, frame-time graphs are essential — tools like FrameView, PresentMon, MSI Afterburner with RTSS, or built-in OS performance overlays show frame-time variance over time and reveal stutters that average FPS smooths away.
What FPS do I need for VR and competitive gaming?
For VR, the absolute minimum is 90 FPS (11.1 ms frame time) to avoid motion sickness — head movements need to be tracked and rendered fast enough that the displayed world stays aligned with your head movement. PSVR2 targets 120 FPS reprojected to 90; Meta Quest 3 targets 72–120 native. Below 90 FPS in VR, most people experience nausea within minutes. For competitive gaming, the calculus is different: 60 FPS (16.7 ms) is the comfortable minimum; 144 FPS (6.94 ms) is the esports standard and supports modern 144–165 Hz monitors; 240 FPS (4.17 ms) is high-end competitive; 360–540 FPS is for top-tier pros on the most expensive panels. Input-to-display latency improves with higher FPS, which matters for fast-twitch shooters where reaction time differences of 5–20 ms can decide gunfights. For most casual players, 60–144 FPS on a 144 Hz monitor is the sweet spot; beyond that produces diminishing returns. For single-player AAA games, 60 FPS with cinematic settings often beats 144 FPS with reduced settings, depending on the game.
Why don't I see more than 60 FPS even when my GPU can produce it?
Because your monitor's refresh rate caps the displayed frame rate. A 60 Hz monitor refreshes 60 times per second; any frames produced beyond that are either discarded (with V-Sync off, causing screen tearing) or queued (with V-Sync on, increasing latency). To benefit from higher FPS, you need a higher-refresh-rate monitor: 144 Hz, 165 Hz, 240 Hz, 360 Hz, etc. The monitor and the GPU output should match: a 144 FPS render on a 60 Hz monitor displays only 60 FPS; a 60 FPS render on a 144 Hz monitor displays 60 FPS with each frame held for ~16.7 ms then re-shown for the next refresh cycle. Adaptive sync technologies (G-Sync, FreeSync) dynamically match monitor refresh to GPU output, reducing tearing and stutter. For competitive gaming, also factor in panel response time (1 ms vs 4 ms vs 8 ms) which affects motion clarity independently of refresh rate.
What are the most common mistakes people make interpreting FPS?
The biggest is judging gaming smoothness from average FPS alone, ignoring frame-time variance — a "144 FPS average" with frequent 50 ms stutters feels worse than a steady 60 FPS. The second is benchmarking with V-Sync disabled then complaining about screen tearing; for visual smoothness, you need either V-Sync on or adaptive sync (G-Sync, FreeSync). The third is buying a 240 Hz monitor for a GPU that can't produce more than 100 FPS in your games — the monitor will only show what the GPU outputs. The fourth is comparing in-game benchmarks against real gameplay; benchmark scenes are often more or less demanding than actual play, so real-world FPS varies. The fifth is forgetting that CPU bottleneck caps FPS regardless of GPU power; high-end GPUs paired with old CPUs hit a wall well below the GPU's capability. The sixth is over-investing in 1% lows for casual single-player games where variance doesn't much matter; the metric matters most for competitive gaming and VR.
When should I not use this calculator?
Skip it for measuring real-world game performance — use in-game performance overlays (MSI Afterburner + RTSS, NVIDIA GeForce Experience, AMD Radeon Software, Intel Arc Control) or benchmark tools (FrameView, PresentMon, 3DMark, Unigine Heaven) that capture FPS, frame time, 1% lows, and frame-time variance over actual gameplay. It is the wrong tool for measuring perceived smoothness; that depends on frame-time consistency, monitor refresh rate, V-Sync settings, panel response time, and input latency — none of which this calculator addresses. Do not use it for VR refresh-rate planning without checking the headset's native refresh rate and minimum supported frame rate. For competitive gaming setup decisions (monitor purchase, GPU upgrade, settings tuning), the metric you actually care about is consistent frame-time-under-monitor-refresh-interval, not raw FPS. And for cinematic or single-player games, 60 FPS at high settings often produces a better experience than 144 FPS at low settings — frame time alone misses the visual-quality side of the tradeoff.