You hit the parry button on time. The game parries late. You didn’t misread the animation, and you didn’t mistime the input. Something between your thumb and the screen swallowed a few milliseconds.
That’s controller input lag. It rarely has one cause. Latency can build up at the controller, the connection, the software on your PC, the game, and the display. The fix is to find which link in that chain is slow.
This guide shows you how to measure your controller latency, cut it with seven practical steps, and use reWASD to reduce the extra delay its virtual controller layer can add. It’s written for PC players, and it matters most in shooters and fighting games, where a few milliseconds can change a round.
Quick answer: how to fix controller lag
First, measure your baseline. Then work through these seven fixes in order, stopping when the lag is gone.
Connect with a cable or a 2.4 GHz dongle.
Tidy up your Bluetooth setup.
Remove extra software layers.
Check your polling rate.
Tune your game settings.
Check Windows.
Set your display to Game Mode.
Each step is explained below, with a way to check that it worked.
Controller input lag, latency, and delay all describe the same thing: the time between a physical input and the reaction on screen.
Ping is a different problem. It’s the network delay between you and the server, and a great ping won’t fix a slow controller.
One frame at 60 fps lasts about 16.7 ms. A setup that adds even a few frames of delay will feel off in any game that rewards quick reactions.
Your input travels a long way before you see it. NVIDIA breaks system latency into four major categories: peripheral, game, render, and display latency. NVIDIA explains the full latency pipeline here. TFTCentral’s NVIDIA Reflex guide is useful as additional reading, but its breakdown is more detailed. For a controller, the same basic chain applies:
|
Where |
What it feels like |
What to try |
|
Controller and polling rate |
Inputs feel less responsive |
Check polling rate, try another mode |
|
Connection (USB, Bluetooth, dongle) |
Lag mostly when wireless |
Use a cable or dongle |
|
Software layers |
Lag after installing a new tool |
Remove overlapping tools |
|
Game settings |
Lag in one game only |
Adjust VSync, frame cap, display mode |
|
Display |
Lag in every game |
Turn on Game Mode |
The connection matters more than most players expect. In Gamepadla’s measurements, the Xbox Series controller came in at about 8 ms over a cable and about 13 ms over Bluetooth. Gamepadla notes that its data and conclusions may contain errors, so use these numbers as a guide rather than a guarantee.
Before you change anything, get a baseline. Otherwise you won’t know what helped.
Step 1: Check your polling rate.
Polling rate is how often your controller reports its state to your PC. Download the open-source Polling tool from Gamepadla, pick a stick, and rotate it smoothly until the test finishes. You’ll see your average rate and any spikes.
Step 2: Know what the test can’t show.
Gamepadla measures the time between stick updates. That’s a useful signal, but by the project’s own description it isn’t traditional input latency, which runs from button press to on-screen reaction. For that full path, you’d need a high-speed camera. NVIDIA’s Reflex Analyzer is designed for mouse input: it detects mouse clicks and measures the resulting pixel change on screen.
Step 3: Test fairly.
Change one thing at a time, run each test several times, and ignore the odd outlier. If your screen is a suspect, RTINGS explains how it measures display input lag, which is handy for comparing monitors.
A wired connection is the simplest way to lower controller latency. Plug straight into a port on your PC, not a hub or a long extension. If you want wireless, a dedicated dongle usually beats Bluetooth.
If Bluetooth is your only option, keep the controller close to the receiver and move other wireless devices out of the way. A weak adapter can add more delay than the controller itself.
Steam Input, vendor apps, overlays, and remappers can all sit between your controller and your game. Each one may add a little processing. Run only what you need, and if two tools do the same job, keep one.
Your PC can only react to what your controller sends. If your hardware supports a higher polling rate, make sure it’s switched on. If you use reWASD, there’s one more setting to check. It’s covered in the next section.
Small settings can hide a lot of delay:
Try fullscreen instead of borderless. It can often lower latency, although the difference can be small in modern games.
Turn VSync off.
Set a stable frame cap, so your GPU isn’t pinned at 100%.
Turn on NVIDIA Reflex if the game supports it and you’re using an NVIDIA GPU. On AMD GPUs, look for AMD Anti-Lag support instead.
Be careful with frame generation. It can raise your frame rate while adding delay.
In fighting games, also look for input buffer or input delay options.
Turn on Game Mode and use a performance-oriented power plan. Update your controller’s firmware and drivers, and close background apps you don’t need while you play.
Many TVs and some monitors add image processing by default. Switch to Game Mode and turn off extra picture effects. If your controller tests fine but every game still feels slow, your display is a likely suspect.
The problem: you’ve done the basics, but your controller still feels a step behind in shooters or fighters.
The solution: Device Performance in reWASD. It controls the reporting performance of the virtual controller, with Normal, High (optimized for 500 Hz), and Ultra (optimized for 1000 Hz). It lives in Output device settings.
How to turn it on:
Open the Output device settings for your selected output device.
Set Device Performance to Ultra (or High).
Run the Polling tool again to compare with your baseline.
How it works: Device Performance controls how frequently reWASD reports from the virtual controller to the game. It can reduce the extra waiting introduced by the virtual-controller layer, but it cannot make the virtual controller faster than the underlying hardware and system allow.
A few things worth knowing:
Your physical controller isn’t modified. Device Performance affects the virtual controller only. It does not change your physical controller’s firmware or reporting rate. It reduces the extra delay that reWASD itself adds; it can’t make the virtual controller faster than your hardware and system allow.
Your PC matters. For a locally emulated Xbox controller, reWASD sends reports as fast as it can. The final polling rate depends on the virtual controller type and your PC and CPU load. Ultra can increase CPU usage, so higher performance is not automatically better on every system.
Not every virtual controller benefits from Device Performance. The setting has no effect on virtual Nintendo Switch Pro or DualShock 3 devices; these always operate according to their hardware specifications.
Pick the right virtual controller. The reWASD team says virtual Xbox One is the fastest of the virtual gamepads and the best pick for minimal latency. A virtual DS4 still reports to games every 4 ms, because it has to match a real DualShock 4. More on the options in Virtual controller.
Some controllers need a specific mode. The Flydigi Vader 4 Pro, for example, is supported by reWASD in D-input mode. The reWASD team confirms this on its forum.
The result: reWASD can keep your remaps and profiles in one place while minimizing the extra delay introduced by its virtual-controller layer. The actual result depends on your hardware, CPU load, and virtual controller type.
Want to try it? Download reWASD and open the Device Performance docs.
Lag only on Bluetooth: switch to a cable or dongle first.
Lag in one game only: check that game’s VSync, display mode, and frame cap.
Lag started after installing a new tool: disable it and test again, then look for overlap with other software.
Lag in every game: check your display’s Game Mode, then your polling rate.
Fixing controller input lag is a process of elimination. Measure your polling rate, go wired or use a dongle, trim extra software, tune your game, and set your display to Game Mode. Then use Device Performance to reduce the extra delay introduced by the virtual-controller layer.
Start with step one, change one thing at a time, and test after each change. You’ll find where your latency is hiding.
Does a higher polling rate reduce controller latency?
Often, yes. Your PC gets fresher input data more often. But polling rate is only one part of the chain. A slow connection, extra software, or a laggy display can still hold you back.
Is a wired controller always faster than wireless?
Not always, but usually. A good 2.4 GHz dongle can come close to a cable, and Bluetooth often adds the most delay.
Does reWASD add controller delay?
A virtual-controller layer can add some delay between your physical controller and the game. Device Performance is designed to reduce the extra delay introduced by that layer. It does not modify your physical controller or make the virtual controller inherently faster than the hardware and system allow. The final result depends on your hardware, CPU load, and virtual controller type.
Why does my controller feel delayed in only one game?
That points to the game, not the controller. Check VSync, frame cap, display mode, and any frame generation options.

