What is input lag and why it matters more than FPS

Something feels off, but you can't tell what

Your FPS are high, your game isn't obviously stuttering, but something isn't quite right. You move the mouse and the crosshair arrives late. You jump and the action takes a beat longer than it should. It's not a stutter, it's a disconnect between what you do and what you see.

That's input lag: the total time between your physical action (moving the mouse, pressing a key) and the moment the result appears on screen. And it's one of the things that affects the gaming experience most, especially in competitive titles.

Input lag is not the same as ping

Ping measures the round-trip time between your PC and the game server. It's network latency. But the total latency you experience includes much more:

1. The time your mouse or keyboard takes to send the signal to the PC.
2. The time Windows takes to deliver it to the game.
3. The time the game takes to process it and calculate the result.
4. The time the CPU takes to prepare the frame and the GPU to render it.
5. The time your monitor takes to display the image.

Ping is just one of those pieces. A 20 ms ping with 80 ms of input lag feels slow. A 40 ms ping with 30 ms of input lag feels fast. What you notice is the sum.

Why FPS don't tell the full story

More FPS generally means less input lag, because each frame takes less time to produce. At 60 FPS, the GPU alone needs 16.6 ms per frame. At 240 FPS, it's 4.1 ms.

But FPS measure frame production, not the time between your input and the result on screen. You can have 240 FPS and high input lag if the pipeline between your mouse and the screen has unnecessary stops.

A real example: two PCs with the same GPU and the same 200 FPS in the same game can have very different input lags. The difference is in how each one handles drivers, the frame queue, power plan, and system interrupts.

Where input lag builds up on a Windows PC

Input lag doesn't have a single cause. It accumulates at several points in the system:

• Mouse polling rate: a mouse at 125 Hz adds up to 8 ms of latency just in reading the input. At 1000 Hz, that drops to 1 ms.
• Frame queue (render queue): by default, the graphics driver can buffer several frames ahead. Each extra frame in the queue is one frame of delay between your input and what you see.
• V-Sync: syncing frames to the monitor's refresh eliminates tearing, but can add a full frame of latency (16.6 ms at 60 Hz).
• DPC latency: poorly optimized audio, network, or USB drivers can block the processor for critical microseconds right when the game needs to process your input.
• Desktop Window Manager (DWM): in Windows 10 and 11, the DWM processes all frames before sending them to the monitor, even in exclusive fullscreen mode.

Each of these points adds milliseconds. The sum can be the difference between "feels fast" and "something's slow".

What you can do (and what you can't)

Some input lag factors are within your control without changing hardware: setting your mouse to its maximum polling rate, disabling V-Sync if your monitor allows it, adjusting the frame queue in the graphics driver panel.

Other factors require a deeper diagnosis: measuring DPC latency for each driver, analyzing how the Windows scheduler handles interrupts, and verifying that your power plan isn't introducing unnecessary latency by scaling frequencies.

What you can't do is reduce input lag to zero. There will always be a physical minimum — the time the signal takes to travel through the cable, the monitor panel's response time, the game's processing time. The goal isn't to eliminate it, but to make sure your system isn't adding latency that shouldn't exist.

Measuring input lag isn't easy, but it's possible

Unlike FPS or frametimes, total input lag can't be seen with a simple overlay. Measuring the full path from input to screen requires specialized tools or an indirect analysis combining several metrics: frametimes, DPC latency, frame queue depth, and polling rate.

What you can observe yourself is the difference: if you change a setting and the crosshair feels more responsive, you've reduced input lag. But to know exactly how much and where, you need to measure.

It's the first thing we evaluate in a LATENT diagnosis: not just how many FPS your PC produces, but how much time passes between what you do and what the screen gives back.