Input Lag vs FPS — How Frame Rate Affects Latency
The relationship between FPS and input lag is real and measurable — but it's only one component of your total end-to-end latency. Understanding which part of the latency chain FPS actually controls prevents both over-investing and under-investing in frame rate.
Frame Delivery Latency
Games sample input state at the beginning of each frame. If you click between two consecutive frame reads, your click isn't registered until the next sample — introducing a wait of 0 to one full frame period. This is called frame delivery latency or sampling latency.
This delay is random within [0, frame_period]. On average, you wait half a frame period. At 60 FPS, that's an average of 8.3 ms added purely from frame sampling. At 240 FPS, it drops to 2.1 ms average.
The Math
Frame period = 1000 ms ÷ FPS. Average sampling delay = frame_period ÷ 2.
- 30 FPS → 33.3 ms frame period
- ~16.7 ms avg sampling delay
- 60 FPS → 16.7 ms frame period
- ~8.3 ms avg sampling delay
- 120 FPS → 8.3 ms frame period
- ~4.2 ms avg sampling delay
- 240 FPS → 4.2 ms frame period
- ~2.1 ms avg sampling delay
- 360 FPS → 2.8 ms frame period
- ~1.4 ms avg sampling delay
INPUTLAG FOR WINDOWS
Doing this by hand?
See your system’s optimization status, try three free starter optimizations, and review supported changes before applying them. Advanced tools are available on paid plans.
Windows 10 / 11 · Free starter tools · No card requiredWhat Frame Rate Doesn't Fix
Even at uncapped framerates, you still have: peripheral polling latency (0–8 ms at 125 Hz), OS scheduler delay (varies with timer resolution), GPU render queue depth (1–3 frames at default settings), and display processing delay (1–4 ms). A 400 FPS game with V-Sync enabled adds back the full frame-wait penalty anyway.
The most common mistake is targeting extreme framerates while leaving V-Sync on or GPU pre-rendered frames at 3. These settings undo the sampling latency gains entirely.
Diminishing Returns
The gains from increasing frame rate follow a curve of diminishing returns. 60→144 FPS is a large jump — 4 ms saved. 144→240 FPS is noticeable — 2 ms saved. 240→360 FPS is detectable in controlled tests but not perceptually significant for most players.
The more impactful optimization is removing latency from other parts of the chain — particularly OS-level settings and GPU driver configuration — before chasing the last few FPS.
Frequently asked questions
Does matching my monitor's refresh rate cap FPS?
You can run higher FPS than your monitor's refresh rate. Doing so reduces sampling latency even though frames beyond the refresh rate never appear. Many competitive players run uncapped or cap far above monitor refresh (e.g., 500 FPS on a 240 Hz monitor) specifically for this reason.
Is there input lag at the start of each frame or end?
Most engines sample input at the start of the frame update cycle — before physics, animation, and rendering. This means your input from just before frame start is processed in the same frame, but input that arrives just after the sample point waits a full frame.
Does DLSS or FSR affect input lag?
Frame generation (DLSS 3 Frame Gen, FSR 3) inserts synthetic frames between real frames. This doubles effective display refresh rate but adds 1 real frame of latency — making it a net negative for competitive play. Standard quality DLSS and FSR upscaling have minimal direct impact on input lag.