CS2 Input Lag: How to Cut the Delay Between Mouse and Screen

In CS2 the gap between winning and losing a duel fits inside a few milliseconds. When your aim seems to arrive half a beat behind your hand, you lose trades your aim would have won — and it feels like the problem is you.

Often it is not. Input lag has concrete causes, and most of them cost nothing to fix.

The biggest gain is not what you would guess

Before any mouse setting: FPS is the largest source of input lag there is.

Every frame is an opportunity to show the result of your movement. At 100 FPS a new frame arrives every 10 milliseconds. At 300, every 3.3. Just waiting for the next frame costs three times more in the first case.

That is why raising your baseline FPS in CS2 reduces delay without touching a single peripheral. And why fixing delay while FPS stays low rarely feels different.

VSync off

If there is one thing to take from this guide, it is this.

VSync holds finished frames back until the monitor is ready to display them. Holding a frame is literally adding delay, and it is one of the largest avoidable sources there is.

If screen tearing bothers you, the alternative is your monitor's adaptive sync, which matches refresh rate to the game rather than holding frames.

About Reflex in CS2

Here I need to be honest about an uncertainty, because the information in circulation contradicts itself.

There are reports that CS2 offers a Reflex option in its video settings, and reports that it does not. There are also recent player reports saying that, where present, it has not been behaving well in CS2 — unlike other games, where it works very well.

I cannot confirm the state on your version, so the practical guidance is:

• Open the game's video settings and look. If the option is there, test it on and off and keep whatever feels better
• If it is not there, use the driver equivalent: in the NVIDIA panel, create a profile for CS2 and enable low latency mode. AMD cards have an equivalent

Testing is more reliable than following a video's recommendation, because this changes between game and driver versions.

Monitor refresh rate

Worth checking even though it seems obvious, because the mistake is extremely common: a high refresh monitor running at 60 Hz because nobody changed the Windows setting after buying it.

At 60 Hz you wait up to 16.7 ms on the display alone, and no optimization compensates for that.

Mouse polling rate

At 125 Hz a mouse reports position every 8 milliseconds. At 1000 Hz, every 1.

If yours is at 125, fixing it is a real gain. If it is already at 1000 — as nearly every gaming mouse of the last few years is — going higher returns fractions of a millisecond, and your time is better spent on the items above.

Frame cap and consistency

Swinging FPS feels worse than a lower steady number, because the time between frames keeps changing.

In CS2 this shows up a lot, because smoke and grenades genuinely cost performance and pull the number down exactly when the fight starts.

Worth considering capping at a value the machine sustains through those moments, rather than leaving it uncapped and living with the jolt.

Underneath the game

Once the settings above are done and delay remains, what is left is in the system:

• Power plan in saving mode, holding back CPU frequency
• Background processes competing for the primary core, which CS2 uses heavily
• High interrupt latency from a badly configured driver — producing micro-stutter and delay even with seemingly good FPS

That last one is the most technical and least known. It explains the cases of people with high FPS, correct settings, and a game that still feels stiff.

The order

1. Monitor refresh rate in Windows
2. VSync off
3. Low latency mode — the game's if it exists, the driver's if not
4. Raise baseline FPS
5. Mouse at 1000 Hz
6. Power plan and processes
7. Interrupt latency

The first four are free and take minutes. People who feel delay usually have at least one of them wrong — and never find out, because they went straight to buying a new mouse.

If you also play Valorant, the reasoning is the same, with that game's own specifics.