🛒 Best Price Today on Amazon
Prime members get fast, free shipping on everything above, plus member-only deals. New members get a 30-day free trial — cancel anytime.
- The latency chain from click to pixel
- Diagnostic matrix: symptom versus likely cause
- Display settings that matter most
- Graphics driver, frame caps and synchronization
- Windows settings and background load
- USB bus and peripheral choices
- Wireless, Bluetooth and cable considerations
- A worked example with stated assumptions
- System verification checklist
- Related guides
- Frequently asked questions
To reduce input lag on a PC, work through the chain in order: your display’s settings first, then the frame cap and graphics driver options, then Windows, and finally the USB devices. The display and the way frames are queued usually account for the largest share of delay, so they come first. Peripheral tweaks come last because they tend to shave off the smallest amounts.
The guidance below draws on published documentation from display, GPU and operating system makers plus general PC knowledge. Every number below is an illustration built on stated assumptions, so confirm any single change with your own repeatable comparison.
The latency chain from click to pixel
Input lag is the total of several small delays. A click leaves the mouse, travels over USB to the PC, is read by the game, is turned into a frame by the CPU and GPU, waits in a queue, and finally appears on the screen after the display processes it. A fix only helps if it targets a stage that is actually slow on your system.
A useful reference point is the frame interval, the time between frames at a given frame rate. At 60 FPS each frame lasts about 16.7 ms, at 144 FPS about 6.9 ms, and at 240 FPS about 4.2 ms. If the game queues two or three frames before showing them, the delay multiplies accordingly, which is why a high frame rate can still feel sluggish when buffering is deep.
Diagnostic matrix: symptom versus likely cause
| Symptom | Likely stage | Where to look |
|---|---|---|
| Everything feels floaty, even at high FPS | Display processing | TV or monitor game mode, motion smoothing |
| Delay worse when GPU is at 99% usage | Render queue | Frame cap, GPU latency option |
| Tearing gone but response heavy | V-Sync buffering | VRR with a frame cap |
| Occasional delayed clicks | USB or background load | Port choice, hub, overlays |
| Fine on wired, laggy on wireless | Wireless link | Receiver placement, battery, interference |
| Fine in one game only | Game settings | In-game buffering and render options |
Display settings that matter most
Start with the screen. TVs and some monitors run image processing such as motion smoothing, noise reduction and sharpening, which can add noticeable delay. Switch the input to Game Mode or PC Mode, which usually disables most of that processing. Name and menu layouts vary by brand, so check the manual.
Set the display to its highest supported refresh rate in Windows display settings, since many monitors default to 60 Hz after first connection. Confirm the cable and port can carry that rate; an older HDMI or DisplayPort version may cap resolution or refresh rate, and the spec sheet will list the supported modes. If your monitor supports variable refresh rate, enable it on the monitor and in the graphics driver. Overdrive settings change pixel response; an aggressive level can create overshoot artifacts, so choose the middle setting unless your display’s documentation says otherwise.
Graphics driver, frame caps and synchronization
When the GPU is running flat out, frames queue up and delay grows. Capping the frame rate a few frames under your refresh rate, for example 141 FPS on a 144 Hz display, keeps the GPU slightly below saturation so the queue stays short. The exact offset that works best varies, so treat it as a starting point.
Graphics vendors offer latency-reduction features in supported games, such as NVIDIA Reflex or AMD Anti-Lag. These reduce the render queue, but they only work in titles that support them, and availability depends on your GPU generation, so consult the vendor documentation. Driver-level low latency modes exist too; the benefit is typically larger when the GPU is the bottleneck than when the CPU is.
For synchronization, the common options are classic V-Sync (smooth but adds buffering), VRR such as G-SYNC or FreeSync (avoids tearing without the same hold-back), and sync off (lowest latency, visible tearing). A common balance is VRR on, V-Sync enabled in the driver only as a limit, and a frame cap just under the maximum refresh. Try each option in your own titles, since behavior differs.
If your problem is uneven frame delivery rather than steady delay, our guide to reducing stuttering in PC gaming covers that separate topic, and our walkthrough of Rocket League input lag shows how the same ideas apply to one game.
Windows settings and background load
Windows Game Mode is generally worth keeping on, as it tells the system to prioritize the game. Close overlays, recording tools and browsers with hardware acceleration while you play, because they compete for GPU time. In the graphics settings page, hardware-accelerated GPU scheduling is an option that may help or hurt depending on hardware and driver, so toggle it, restart, and compare rather than assuming.
Set the power plan to a balanced or high-performance profile so the CPU does not drop clocks between bursts of activity. For games that offer it, try exclusive fullscreen or the borderless mode your driver documentation recommends; modern Windows versions handle borderless windows efficiently in many cases, but the better choice differs per game.
USB bus and peripheral choices
Plug the mouse and keyboard directly into ports on the motherboard’s rear panel, not into a crowded front hub or a daisy chain. Separate high-bandwidth devices such as webcams, capture cards and external drives from your mouse where you can, because they share bandwidth on some controllers. Set the mouse polling rate to the highest stable option the maker supports, commonly 1000 Hz, and keep wireless receivers close with a clear line to the mouse.
Wireless, Bluetooth and cable considerations
Wireless peripherals come in two broad kinds. Models that use a dedicated USB receiver are usually built for gaming and their makers publish claims about responsiveness on the spec page. Bluetooth-only devices tend to be tuned for battery life and convenience, and they generally add more delay. If you play competitive shooters, a receiver-based or wired device is the safer choice; for casual games, the difference may never matter to you.
Keep the receiver close to the mouse, ideally on a short extension cable on the desk rather than behind the tower, because walls of metal and other wireless gear can interfere. Replace low batteries early, since weak batteries can cause dropped reports on some devices. Cables matter too: a worn or damaged video cable can force the display into a lower mode, so if a monitor suddenly feels worse, confirm in Windows display settings that it still shows the refresh rate you chose.
It is also worth checking the monitor’s on-screen menu for an input lag or response time setting that resets after power cuts or firmware updates. Some displays quietly return to defaults, and a setting you configured last month may no longer be active.
A worked example with stated assumptions
Assume a player on a 144 Hz monitor, a game running uncapped at around 230 FPS with the GPU at full load, and a TV-style input mode with processing on. The table shows where changes might help; the delays are illustrative guesses, not measurements.
| Change | Stage affected | Illustrative effect |
|---|---|---|
| Enable monitor game mode | Display processing | Often the largest single drop |
| Cap at 141 FPS with VRR | Render queue | Shorter queue, steadier pacing |
| Turn on the game’s GPU latency option | Render queue | Further reduction where supported |
| Raise mouse polling to 1000 Hz | Peripheral | Roughly 1 ms report interval |
| Move to a rear motherboard USB port | Bus | Small, mostly consistency |
System verification checklist
- Display on its highest refresh rate, Game Mode on, smoothing features off.
- VRR enabled on both display and driver, frame cap just under refresh.
- Game’s own latency option on, if offered.
- Overlays and recording tools closed while playing.
- Mouse and keyboard on rear motherboard ports, polling rate set.
- One change at a time, same practice scenario before and after.
If delay remains obvious after all of this, suspect a failing cable, a very old display, or a CPU bottleneck, and consult the maker’s support pages before buying anything.
Related guides
- Gaming Chairs For Back Pain With Lumbar Support
- Gaming Keyboards For Fps With Rapid Trigger
- How To Fix Gaming Mouse Double Click Issue
Frequently asked questions
Is input lag the same as low FPS or stutter?
No. Frame rate describes how many images are drawn per second, stutter describes uneven frame delivery, and input lag describes the delay between your action and the result on screen. They overlap, because a higher frame rate shortens each frame interval, but a game can run at a high frame rate and still feel delayed if buffering, a slow display mode or a queued render path adds latency.
Should I turn V-Sync off to cut latency?
In many games, turning classic V-Sync off lowers latency because frames are not held back to match the refresh. The trade-off is visible screen tearing. A variable refresh rate display paired with a frame cap slightly under the maximum refresh gives a good balance for many players. Results depend on the game and display, so change one setting at a time and compare how it feels.
Does a higher polling rate mouse really help?
A higher polling rate shortens the interval at which the mouse reports its position to the PC, for example about 1 ms at 1000 Hz. That can make cursor movement feel slightly more immediate, but the gain is small compared with the display and GPU stages. Very high rates also use more CPU time, so check the mouse maker’s documentation and keep the setting if it feels smooth.
Is wireless always worse than wired?
Not always. Many current wireless gaming mice and keyboards that use a dedicated USB receiver are designed to match wired responsiveness, and their makers say so on their spec pages. Bluetooth connections generally add more delay than a dedicated receiver. If you are chasing every millisecond, a wired connection removes one variable, but treat it as a late-stage change, not a first step.
How do I know if my changes helped?
Trust repeatable comparisons, not memory. Play the same practice map or training mode for the same duration before and after each change, and note how aiming or flicking feels. Overlays that report frame time show whether the frame rate is steady. Some GPU vendors offer latency overlays in supported games; if yours does, check the vendor’s documentation for how to read it.