어떤 FPS든 밀리초 단위 프레임 타임으로 변환하고, 각 주사율(30 / 60 / 144 / 240 / 360 Hz)이 실제로 얼마나 이득인지 나란히 비교하세요.
| FPS | 프레임 시간 (ms) | 프레임 시간 (μs) | 일반적인 입력 지연 (≈1.5프레임) |
|---|
프레임 시간(ms) = 1000 / FPS. 60FPS는 프레임당 16.67ms, 144FPS는 6.94ms가 걸리며, 프레임당 약 9.7ms를 절약합니다.
대부분의 엔진에서 전체 입력 지연은 약 1.5프레임(샘플링, 렌더링, 스캔아웃) 정도이므로, FPS가 높아질수록 이 과정 전체가 짧아집니다. 실제 입력 지연은 모니터 스캔아웃, USB 폴링, 게임 엔진 파이프라이닝에도 영향을 받습니다.
Frame time is simply 1000 ÷ FPS, expressed in milliseconds. The calculator runs that on two values at once and reports the gap between them: 60 FPS is 16.67 ms per frame and 144 FPS is 6.94 ms, so moving between them saves 9.72 ms on every frame. The reference table repeats the maths for eleven common rates from 24 up to 480, giving each in milliseconds, in microseconds, and as an estimated input lag of roughly 1.5 frames.
FPS A defaults to 60, described as your current refresh rate or FPS cap, and FPS B defaults to 144, the upgrade you are weighing up; both accept anything from 1 to 1000. The preset buttons of 30, 60, 75, 120, 144, 165, 240 and 360 FPS fill FPS A only, so type FPS B yourself. Rows matching either value are highlighted in the table, which makes the diminishing returns easy to read.
The input-lag column is a rule of thumb rather than a measurement: it multiplies frame time by 1.5 to approximate sampling, rendering and scan-out, and the page says as much. Real end-to-end latency also depends on monitor scan-out rate, USB polling interval, engine pipelining, frame buffering and driver settings, none of which are modelled here. The tool also assumes a steady frame rate, so it says nothing about frame-time variance, stutter or 1% lows.
16.67 ms, from 1000 ÷ 60, which the table also gives as 16667 microseconds. At 30 FPS a frame lasts 33.33 ms and at 240 FPS only 4.17 ms, so the curve flattens sharply as the frame rate climbs higher.
Enter 144 and 240 and the saving is 2.78 ms per frame, against the 9.72 ms you gain going from 60 to 144. Each step up returns less than the last, which is why the jump away from 60 Hz feels so much larger than anything above 144.
It estimates the chain from mouse movement to photons — sampling, rendering, then scanning out — as about one and a half frame times. At 60 FPS that is 25.00 ms and at 240 FPS 6.25 ms. It is an approximation, not a measured latency figure.
This tool does not answer that directly, since it only converts rates into frame times. It does let you put a capped and an uncapped figure side by side, which shows exactly how much frame time you would give up by capping below your panel's ceiling.
The buttons cover eight common panel rates from 30 through 360, while the reference table lists eleven values and adds 24, 90 and 480 for context. Either input field will accept any number between 1 and 1000 if you type it in manually.
Mouse Sensitivity Converter (Valorant, CS2, Apex, Fortnite)
Convert mouse sensitivity between games at matched DPI — Valorant, CS2, Apex, Overwatch, Fortnite, Rainbow Six.
Streaming Bitrate Calculator (Twitch, YouTube, Kick)
Recommended bitrate, resolution and encoder settings for Twitch, YouTube Live, Kick and TikTok Live.
Twitch Subs, Bits & Revenue Calculator
Estimate streamer payout from subs (tier 1/2/3), bits and ads, with split, currency and tax breakdown.
