Your crosshair feels like it is dragging through mud. Your average frame rate looks fine, but the game does not respond when you flick. That gap between your hand and the screen is input delay, and it is almost never fixed by buying a better graphics card.

This guide walks through every layer that adds delay, in the order that actually matters, starting with the changes that take a minute and ending with the ones most people never touch.

The 60 second fix

If you only have a minute before your next match, do these four things.

Step 1) Set your monitor to its highest refresh rate. Right click the desktop, Display settings, Advanced display, and pick the top value. A surprising number of people run a 144Hz or 240Hz panel at 60Hz because Windows defaulted there and never said anything.

Step 2) Turn your game to Fullscreen, not Borderless. Borderless routes your frames through the Windows compositor, which adds a frame of delay on most setups.

Step 3) Turn V-Sync off in the game. V-Sync holds finished frames back to match your monitor, and holding frames back is the definition of input delay.

Step 4) Switch your Windows power plan to High performance. Search “power plan” in the Start menu. On a laptop, plug it in first, because most laptops throttle hard on battery no matter what the plan says.

Those four alone remove the most common causes. Everything below is the deeper work.

What actually causes input delay

Input delay is not one thing. It is a chain, and every link adds a few milliseconds:

Your mouse. How often it reports its position to the PC, measured in Hz. A 125Hz mouse reports every 8ms. A 1000Hz mouse reports every 1ms.

The USB and driver layer. How quickly Windows accepts that report and passes it on. Power saving features can put USB ports to sleep between reports.

The CPU queue. Whether your processor is free to handle the game right now, or busy with a background task. This is the layer almost everyone ignores, and it is usually the worst offender.

The render pipeline. How many frames your GPU is allowed to prepare in advance. More queued frames means smoother numbers and worse responsiveness.

The display path. Whether frames go straight to your monitor or through the Windows compositor first.

The monitor itself. Its refresh rate, its response time, and whether any built in processing is enabled.

A fast graphics card only helps with one of those six. That is why people upgrade and feel no difference.

Fix the hardware layer first

Set your polling rate to 1000Hz. Open your mouse software and look for polling rate, report rate or Hz. Anything below 1000 is leaving easy responsiveness on the table. Going above 1000 helps far less than the marketing suggests, and on some systems it costs CPU.

Stop Windows suspending your USB ports. Device Manager, expand Universal Serial Bus controllers, and for each USB Root Hub open Properties, Power Management, and untick “Allow the computer to turn off this device to save power”. Do the same under Human Interface Devices for your mouse.

Turn off Enhance pointer precision. Search “mouse settings”, open Additional mouse options, Pointer Options tab, and untick it. It is mouse acceleration under a friendlier name, and it means identical hand movements produce different in game results.

Plug into the right port. Use a port directly on the motherboard rather than a front panel or a hub, and avoid sharing a controller with a busy device like an external drive.

Check your monitor’s own settings. Most gaming monitors have an overdrive or response time setting, and many have a low latency or game mode that bypasses internal image processing. Turn the processing off.

The Windows layer, where most of the delay hides

This is the part that matters most and the part people skip, because it is buried.

Turn on Hardware accelerated GPU scheduling. Display settings, Graphics, Change default graphics settings. It lets the GPU manage its own frame queue instead of waiting on the CPU.

Turn off Game Bar and background recording. Settings, Gaming. Background capture keeps an encoder running constantly for footage you will almost never use.

Deal with core parking and power throttling. Windows parks CPU cores to save power and wakes them on demand. Waking a parked core takes time, and that time lands as a stutter exactly when the action starts. High performance helps, but the deeper settings are not exposed in the normal Windows interface.

Check Virtualization Based Security. On Windows 11 this is often on by default. It sits between your game and your hardware and can cost real frame stability. Search “Core isolation” to see whether Memory integrity is on.

Cut the background load. Launchers, chat apps, browser tabs, RGB software and manufacturer utilities all take CPU time. Every one of them is a chance for your game to wait its turn.

GPU control panel settings that matter

Low latency mode. On NVIDIA this is Low Latency Mode, set to Ultra. On AMD it is Anti-Lag. Both limit how many frames the CPU prepares ahead, which is a direct trade of a little smoothness for a lot of responsiveness.

Power management mode. Set it to prefer maximum performance so the card does not downclock between bursts.

Cap your frame rate slightly below your refresh rate. If your GPU runs flat out at 100 percent it starts queueing frames. A cap a few frames under your monitor’s refresh keeps headroom and keeps latency low.

In game settings

Turn off motion blur, film grain, depth of field and chromatic aberration. They cost frames and hide information you need.

Set the render resolution to 100 percent. Some games ship with dynamic resolution on, which changes how the game feels as the load shifts.

Reflex or its equivalent, on. If your game offers a latency reduction option, use it. It coordinates the CPU and GPU better than any external setting can.

Lower shadows and effects before you lower textures. Shadows are usually the most expensive setting relative to what they add.

Why doing all this by hand goes wrong

Everything above is real and it works. The problem is keeping it that way.

Windows updates undo it. Feature updates reset power settings, re-enable services and occasionally reset graphics defaults. Work you did in March is often gone by May.

Registry edits are unforgiving. The deeper settings are not in the Settings app, and a copied command with one wrong value is genuinely difficult to unpick later.

Random scripts are a real risk. A lot of free “debloaters” passed around on forums do more than they claim, and you have no way to check before you run them.

You cannot easily tell what helped. Change twenty things at once and you learn nothing about which one mattered.

The automated route

This is the problem RIP Tweaks was built for. It applies the same categories of change described above, but as reversible toggles rather than commands you paste into a terminal.

Every change is undoable. Each tweak is a switch you can turn back off, and the app can create a restore point before you start so the whole system can go back.

It survives updates. You reapply from the app rather than rediscovering what you did months ago.

It only shows what applies to you. Tweaks are matched to your actual hardware rather than a generic list.

It never touches your games. RIP Tweaks is an optimizer, not a cheat. It only changes legitimate Windows and driver settings and never touches game files, memory or any running process. There is nothing in it that interacts with anti-cheat. Thousands of players use it daily alongside Valorant, Fortnite, CS2 and Apex.

Most people see a real improvement, and on older or bloated systems it is often the biggest jump. How much you gain depends on your hardware, your game and how your PC was set up before, so we do not quote a fixed number. There is a free version, so you can find out on your own machine before paying anything.

Your checklist

Monitor. Highest refresh rate selected, game mode on, internal processing off.

Mouse. 1000Hz polling, Enhance pointer precision off, USB power saving disabled.

Windows. High performance power plan, Game Bar off, hardware accelerated GPU scheduling on, background apps closed.

GPU. Low latency mode on, maximum performance power mode, frame cap just under refresh rate.

Game. Fullscreen, V-Sync off, motion blur off, latency reduction on, 100 percent render scale.

Frequently asked questions

Does more FPS always mean less input delay? Not always. Frame rate and latency are related but separate. A game running at 200 frames per second with four frames queued ahead can feel worse than one running at 140 with none.

Is a 1000Hz mouse enough? For almost everyone, yes. The jump from 125Hz to 1000Hz is large and obvious. The jump from 1000Hz to 4000Hz is small and costs CPU.

Will this help on an older PC? Usually more than on a new one, because older systems have accumulated more background software and more leftover settings.

Does any of this risk a ban? No. Every change described here is a Windows, driver or in game setting. Nothing here touches a game file or a running process.

What if it does not feel different? Change fewer things at a time and test in the same place in the same game. If your PC was already well maintained there is simply less to reclaim. There is a full walkthrough in Why did my FPS not increase.

More detail on the individual layers: input lag and mouse polling, lowering your ping, and the full FAQ.