Updated Oct 8, 2026· 6 min read

Key takeaways

  • Display Mode: Fullscreen. It gives the most consistent frame delivery and the lowest latency. Fullscreen Windowed has gotten closer on modern Windows but can still add delay on some systems.

  • Wait for Vertical Sync: Disabled. With V-Sync on and no frame cap, finished frames wait for the next refresh, which can add more delay than any other single setting. The exception is the G-Sync setup described below.

  • NVIDIA Reflex Low Latency: Enabled. Choose Enabled + Boost on a desktop RTX card. Boost keeps GPU clocks high when the CPU is the limit, which costs some power and heat. On a laptop running on battery or under tight power limits, plain Enabled is usually the better choice.

  • Radeon users: use the in-game AMD Anti-Lag 2 option with Adrenalin 24.6.1 or newer. CS2 was the first game to support Anti-Lag 2. Don’t use the old driver-level Anti-Lag+, which triggered VAC bans in October 2023 and was then withdrawn.

  • Multisampling Anti-Aliasing Mode: 2x or 4x MSAA on strong GPUs, None on entry-level cards. MSAA is the most expensive common setting, and dropping it raises the frame rate on GPU-limited systems.

  • Ambient Occlusion: Disabled, and Shader Detail and Particle Detail at Low or Medium. This lowers GPU load during smokes and molotovs, which is where frame times spike.

  • FidelityFX Super Resolution: Disabled unless you’re using integrated graphics or an old GPU that can’t stay above your refresh rate. Upscaling softens the image, and in CS2 a high native frame rate is worth more than the blur.

To reduce input lag in Counter-Strike 2, run Fullscreen with V-Sync off. Set NVIDIA Reflex Low Latency to Enabled, or turn on AMD Anti-Lag 2 if you have a Radeon card. Keep your frame rate well above your monitor’s refresh rate. And leave “Buffering to smooth over packet loss” at None unless telemetry shows real packet loss. Those four changes cover most of the delay you can control. Everything else is fine-tuning.

Where CS2’s input lag actually comes from

Input lag is the total of several steps added together: your mouse reporting a click, the CPU simulating it, the GPU drawing the frame, the monitor showing it, and, for anything other players see, the trip to a 64-tick server. Knowing the size of each step tells you which ones are worth chasing.

Stage Typical size What controls it
Mouse polling 1 ms at 1000 Hz; 0.25 ms at 4000 Hz Mouse software
One rendered frame 6.9 ms at 144 fps; 4.2 ms at 240 fps; 2.5 ms at 400 fps Frame rate (1000 ÷ fps)
GPU render queue Can add one or more extra frames when GPU-bound Reflex / Anti-Lag 2
Display refresh 6.9 ms at 144 Hz; 4.2 ms at 240 Hz; 2.8 ms at 360 Hz Monitor
V-Sync without a cap Can hold frames for a full refresh or more Wait for Vertical Sync
Server tick 15.625 ms per tick (64 tick) Fixed by Valve
Packet-loss buffer About +15.6 ms per buffered tick Buffering to smooth over packet loss

The table shows the priorities. A render queue or a V-Sync stall can cost more than everything else on your side put together. Going from 1000 Hz to 8000 Hz polling saves less than a millisecond.

What sub-tick does and does not change

Official CS2 servers run at 64 ticks per second, and no 128-tick option is offered for matchmaking or Premier. Sub-tick timestamps your shots and movement inputs at the exact moment they happen, so the server knows you clicked partway between two ticks. It doesn’t make the server update more often, change your ping, or remove interpolation. Valve has kept adjusting it: a November 2023 patch made the visual and audio feedback from sub-tick inputs show on the very next rendered frame, September 2025 patches targeted sub-tick shooting and movement consistency, and a January 2026 update rebuilt jumping and landing around sub-tick timing.

The practical takeaway is that your input timing is already precise, but you only see the result of it on your next frame. Higher and steadier frame rates still shorten the time between your click and seeing it land. Old launch options such as -tickrate 128 do nothing on official servers.

Step-by-step: in-game settings

  • Display Mode: Fullscreen. It gives the most consistent frame delivery and the lowest latency. Fullscreen Windowed has gotten closer on modern Windows but can still add delay on some systems.

  • Wait for Vertical Sync: Disabled. With V-Sync on and no frame cap, finished frames wait for the next refresh, which can add more delay than any other single setting. The exception is the G-Sync setup described below.

  • NVIDIA Reflex Low Latency: Enabled. Choose Enabled + Boost on a desktop RTX card. Boost keeps GPU clocks high when the CPU is the limit, which costs some power and heat. On a laptop running on battery or under tight power limits, plain Enabled is usually the better choice.

  • Radeon users: use the in-game AMD Anti-Lag 2 option with Adrenalin 24.6.1 or newer. CS2 was the first game to support Anti-Lag 2. Don’t use the old driver-level Anti-Lag+, which triggered VAC bans in October 2023 and was then withdrawn.

  • Multisampling Anti-Aliasing Mode: 2x or 4x MSAA on strong GPUs, None on entry-level cards. MSAA is the most expensive common setting, and dropping it raises the frame rate on GPU-limited systems.

  • Ambient Occlusion: Disabled, and Shader Detail and Particle Detail at Low or Medium. This lowers GPU load during smokes and molotovs, which is where frame times spike.

  • FidelityFX Super Resolution: Disabled unless you’re using integrated graphics or an old GPU that can’t stay above your refresh rate. Upscaling softens the image, and in CS2 a high native frame rate is worth more than the blur.

Frame cap: uncapped or capped?

Use the console command fps_max to set your cap (fps_max_ui sets the menu limit). There are two good setups, and the right one depends on your monitor and how much tearing bothers you.

Setup Settings Latency Trade-off
Competitive V-Sync off, Reflex on, fps_max 0 or a cap near your 1% lows Lowest Visible tearing; frame rate swings unless capped
G-Sync / FreeSync VRR on, V-Sync on in the driver, Reflex on (it caps automatically about 138 at 144 Hz, about 224 at 240 Hz) A few milliseconds higher No tearing, very even motion

If your frame rate swings widely, say between 200 and 450, a cap slightly below your usual 1% lows feels more consistent, because every frame then takes about the same time. Reflex already prevents frames from piling up when you’re GPU-bound, so a cap mostly smooths things out rather than lowering average latency.

Driver settings that matter

  • NVIDIA Low Latency Mode: has no effect once Reflex is active in CS2, so it can stay Off. Set it to On only if you’ve disabled Reflex.

  • Power management mode: Prefer maximum performance, so the GPU doesn’t drop its clocks between rounds and spike when a fight starts.

  • Vertical sync: Use the 3D application setting, unless you’re using the G-Sync setup above.

  • Don’t add the -noreflex launch option. It removes Reflex from the game completely.

Network settings that feel like input lag

Lag from your connection feels like input lag: your shots land late, or you die after getting behind cover. Go to Game, then Telemetry, and set ping and packet loss to always show. If packet loss stays at zero, set Buffering to smooth over packet loss to None (the console equivalent is cl_net_buffer_ticks 0). Each buffered tick adds about 15.6 ms, so the 2-tick setting adds roughly 31 ms on purpose. Only turn it on while you sort out a bad Wi-Fi link, then set it back to None.

  • Use wired Ethernet. Wi-Fi interference causes the kind of jitter that makes buffering look necessary.

  • Pause cloud backups, game downloads and video uploads while you play.

  • Lower the maximum acceptable matchmaking ping in the game settings so you get matched to nearby servers.

Peripherals and display

A 1000 Hz mouse is enough for most players. If you use 4000 or 8000 Hz, watch your 1% lows, because very high polling rates add CPU load and can cause frame-time spikes on older processors. On the monitor side, turn off motion smoothing or other processing, use the highest refresh rate it supports, and check that Windows is actually running at that refresh rate. Monitors set to 60 Hz after a driver reinstall are a common cause of “laggy” CS2.

Hardware That Lowers Input Lag Further

Once the settings above are dialed in, most of the remaining delay in Counter-Strike 2 comes from the monitor and mouse. A higher refresh rate and a high polling-rate mouse are the next steps.

AOC 27" Gaming Monitor QHD 260Hz Overclocked IPS NVIDIA G-SYNC Q27G41ZE

AOC 27" Gaming Monitor QHD 260Hz Overclocked IPS NVIDIA G-SYNC Q27G41ZE

Included for 'How to Reduce Input Lag in Counter-Strike 2 (CS2)' as a relevant option in this category; details come from the product listing.

View on Amazon

Logitech G PRO X Superlight 2 Wireless Gaming Mouse - Black

Logitech G PRO X Superlight 2 Wireless Gaming Mouse - Black

Included for 'How to Reduce Input Lag in Counter-Strike 2 (CS2)' because the listing specifies Black, details this guide uses to compare options.

View on Amazon

Razer Viper V3 Pro Wireless Esports Gaming Mouse, 54g Lightweight, Black

Razer Viper V3 Pro Wireless Esports Gaming Mouse, 54g Lightweight, Black

Included for 'How to Reduce Input Lag in Counter-Strike 2 (CS2)' because the listing specifies 54g Lightweight and Black, details this guide uses to compare options.

View on Amazon

J
Jack Morgan
We compare specs, materials and verified owner reviews before a product earns a spot. Rankings are never paid.

FAQ

Frame cap: uncapped or capped?
Use the console command fps_max to set your cap (fps_max_ui sets the menu limit). There are two good setups, and the right one depends on your monitor and how much tearing bothers you.
Affiliate disclosure. As an Amazon Associate we earn from qualifying purchases at no extra cost to you. Prices accurate as of the date shown.
How to Reduce Input Lag in Counter-Strike 2…Check price on Amazon