How to Test CS2 Input Lag Before Blaming Your Aim
Your crosshair is on the head, you click, and the kill feed says you lost the duel. Not once either, three or four times a round, on a map where your trades used to land.

Your crosshair is on the head, you click, and the kill feed says you lost the duel. Not once either, three or four times a round, on a map where your trades used to land. So you buy a month of aim trainer and grind 40 minutes before every session. That was me in late September. The aim was fine. A driver update had quietly dropped my monitor back to 60Hz, and I had played eight days at 16.7 milliseconds per frame instead of 6.9.
Input lag is the hardware problem almost nobody tests, because it throws no error and shows no icon. It makes you play slightly worse than you are, which is the hardest kind of problem to spot from the inside. Here is the order I test things in now, what the numbers mean, and which fixes are worth spending money on.
Where the delay actually comes from
Total system latency is the gap between the switch under your finger closing and the pixels on the panel changing. It is a chain. The mouse samples its sensor and reports over USB. The game reads that input on the next tick it can. The GPU renders a frame. The display receives it, processes it, and lights the pixels.
What makes the chain worth thinking about is how uneven the links are. A mouse polling at 1000Hz contributes about a millisecond, which is noise. A television left in its standard picture mode can contribute 80. I once measured a cheap 1080p office panel adding 24 milliseconds of its own processing on top of its refresh time, and the player using it had just spent 90 dollars on a new mouse.
So the useful question is not how fast your gear is. It is which single link is eating the most, because that is almost always the only one worth touching.
The phone camera test that costs nothing
You do not need a monitor with a latency analyser built in. Any phone that shoots 240 frames per second in slow motion will do, and most phones sold since 2021 do.
Open a workshop map, stand still with a rifle, and prop the phone so the frame holds both your mouse hand and the lower third of the screen. Start recording, wait two seconds, then fire one shot. Scrub the clip frame by frame and count the frames between your finger visibly pressing down and the muzzle flash appearing. At 240fps each frame is 4.17 milliseconds, so eight frames is roughly 33 milliseconds of end to end latency. Fire five separate shots and take the middle result. The spread between the five tells you as much as the average does, because a setup that swings from 25 to 60 feels worse than one that sits flat at 45.
On a 144Hz panel, anything under 30 milliseconds is healthy. Between 30 and 50 you will feel it on wide peeks, where the enemy appears to shoot through your model. Above 60 you are fighting the computer as well as the opponent. During my 60Hz week I measured 71, and I had been blaming my wrist.
What the numbers mean once you have them
A total figure tells you there is a problem but not where it lives. This is the rough budget I work from when I have to split one number into parts. The ranges come from my own bench tests over the last two years, so treat them as the shape of the thing rather than gospel.
| Link in the chain | Typical contribution | How to check it in five minutes |
|---|---|---|
| Mouse polling at 1000Hz | 0.5 to 1 ms | Mouse software, or the maker's spec page |
| Frame rate held at 120fps | About 8 ms | cl_showfps 1 during a live round, not in the menu |
| Panel refresh at 60Hz | 16.7 ms | Windows display settings, advanced display |
| Panel refresh at 144Hz | 6.9 ms | Same screen, confirm it says 144 and not 60 |
| VSync left on | 20 to 50 ms | CS2 video settings and the driver control panel |
| Television in standard picture mode | 60 to 110 ms | Switch to game mode and retest with the phone |
| Monitor image processing | 2 to 25 ms | Turn off dynamic contrast, noise reduction, smoothing |
| Unpowered USB hub between mouse and PC | 1 to 5 ms, sometimes much worse | Plug straight into a rear motherboard port |
Add the numbers for your own setup and compare the total with what the phone said. If your parts add up to 35 and the camera says 70, the missing 35 is sitting in something you have not checked yet, and it is usually the display or a driver level setting.
The counter take: a faster panel is rarely the first fix
Ask about input lag in any CS2 community and the first reply will be to buy a 240Hz monitor. I review gear for a living and I still think that advice is backwards most of the time.
Going from 144Hz to 240Hz saves 2.7 milliseconds of refresh time. Turning off VSync saves 20 to 50. Taking a television out of standard picture mode saves 60 or more. Raising your one percent low frame rate from 70 to 140 saves around 7. Those three fixes are free, and together they dwarf the panel upgrade.
There is a second problem with leading on the panel. A 240Hz screen only delivers its advantage when the frame rate can feed it, and plenty of players running mid range hardware sit at 160fps in a smoke heavy retake. If your frame rate drops below your refresh rate in exactly the moments that decide rounds, the expensive panel is idling when you need it most. Sort the frame rate floor first. My guide on setting up CS2 on a laptop without overheating goes through the throttling side of that in more detail, and the same settings order applies to a warm desktop case.
The honest exception: if you are still on 60Hz, stop reading and go buy the cheapest 144Hz panel you trust. That one jump is worth more than every other fix on this page combined.
Wireless, USB ports and the hub that ate four milliseconds
I used to tell people wireless mice add lag. That stopped being true around 2019. A modern 2.4GHz dongle with its own polling rate sits under a millisecond, and in blind tests I cannot pick it out from a cable.
What does still cause trouble is everything between the dongle and the motherboard. A friend of mine ran his receiver through the USB hub built into his monitor, which routed the signal down the display cable and back. We measured four extra milliseconds and, worse, an irregular jitter that made his counter strafes land late about one shot in six. Moving the dongle to a short extension cable on the desk, plugged into a rear port on the board, cleared both.
Three habits are worth keeping. Put the receiver within 20cm of the mouse with nothing metal between them. Use rear ports wired directly to the chipset rather than front panel ports. Keep your phone charger off the same hub, because a device negotiating power on a shared controller can interrupt polling.
If your first bullet still misses after all of this, the problem has moved back to technique rather than hardware, and the drills in how to counter strafe in CS2 will do more for you than any peripheral.
What to do this week
Spend twenty minutes on the measurement before you spend anything on parts. Confirm the refresh rate in Windows and in the game, both, because they disagree more often than you would think. Turn VSync off. Open the monitor menu and disable every image enhancement it offers. Then run the phone test five times and write the number down in the same file where you keep your sensitivity, because a baseline is only useful if you can compare against it after the next driver update.
I retest mine on the first Sunday of every month. It takes four minutes and it has caught two silent refresh rate resets and one monitor firmware change that re-enabled overdrive smoothing. None of those would have shown up as anything except a vague feeling that I had got worse. More gear notes live in the gear section if you want the peripheral side of this.
FAQ
Does input lag matter if my ping is 40ms?
Yes, because they are different clocks. Ping measures the round trip to the server and affects when the server sees your shot. Input lag happens before any of that, and it shifts what you were aiming at when you decided to click. A 40ms ping with 20ms of local latency plays far cleaner than the same ping with 70ms local.
Is a 240Hz monitor worth it over 144Hz?
For refresh latency alone it buys you 2.7 milliseconds, which is small. It is more defensible for motion clarity on fast flicks. I would only buy one after the free fixes are done and the frame rate sits comfortably above 240 in your worst rounds, not your best.
Can a wireless mouse add input lag in CS2?
A current generation wireless mouse does not add anything you can feel. The receiver placement does. Put it near the mouse, plug it into a rear motherboard port, and keep it off shared hubs and monitor USB passthrough.
Why does my latency vary shot to shot?
Inconsistent frame times are the usual cause, often from background software or a CPU hitting thermal limits. A flat 45 milliseconds is easier to adapt to than a figure swinging between 25 and 60, so chase the spread before you chase the average.
More in Guides
Guides
How to Set Up CS2 on a Laptop Without Overheating
The pattern shows up in almost every laptop clip people send me.
Guides
How to Counter Strafe in CS2 and Stop Missing Shots
You peek, your crosshair is right on his head, you click, and the bullet lands a meter to the left.
Guides
How to Read the CS2 Radar Without Losing Your Crosshair
You die to a player your teammate spotted four seconds ago, and the red dot was sitting right there in the corner of your...