Skip to main content

Gamepad Tester

SolvedVerified By Gamepad TesterVerified By Gamepad Tester

My Polling Rate Shows 125Hz, Is That Why My Aim Feels Behind?

Asked by Ethan M.31,740 views

I ran the polling rate test out of curiosity and got 125Hz. I had seen people talking about 1000Hz controllers so 125 sounds terrible by comparison. My aim has felt slightly behind for a while and now I am wondering if this is why. Should I be buying a controller with a higher polling rate, or is 125Hz actually normal and I am chasing a number that does not matter? I would rather understand it than panic buy.

Brand
Microsoft
Model
Xbox Wireless Controller Model 1914
Connection
Bluetooth
System
Windows 11
Browser
Chrome 141
Detected Controller
Xbox Wireless Controller
Buttons And Axes
17 buttons, 6 axes
Short Answer

125Hz is normal for your controller over Bluetooth and is not why your aim feels behind. Try the cable first, which typically raises it, and treat 1000Hz claims as a mouse figure rather than a gamepad one.

Verified By Gamepad TesterVerified By Gamepad Tester
Devon Miller
Devon MillerVerified Gamepad Tester team memberGamepad Tester Team
Low Latency And Input Timing Engineer · 9+ years experience · Answered Feb 6, 2026

125Hz is not terrible and it is almost certainly not your problem, so hold off on buying anything.

The 1000Hz figures you have read about are overwhelmingly mouse polling rates. A mouse reporting a thousand times a second is meaningful because you move it continuously and a cursor tracks it pixel by pixel. A gamepad is a different device: your stick position changes far more slowly than a mouse moves, and almost every game samples controller input once per frame anyway. At 144 frames per second your game looks at your controller 144 times a second, so a controller reporting at 1000Hz hands it a lot of data it throws away. Beyond about 250Hz the returns on a gamepad fall off very steeply.

For context on your specific reading: an Xbox Wireless Controller typically reports around 125Hz over Bluetooth and closer to 250Hz over USB or the Xbox Wireless Adapter. So 125Hz tells me you are on Bluetooth, which your connection field confirms, and it is the expected figure rather than a fault. Plugging in the cable is the free experiment, and it will likely roughly double your reading.

On your aim feeling behind, I would look elsewhere, and in this order. First, the latency test, watching the spread rather than the average, because inconsistency is felt far more than a modestly low polling rate. Second, your in-game deadzone and response curve, which game patches reset more often than people realise. Third, frame generation or upscaling if you have either enabled, which adds delay that no controller test will ever show. Any one of those will move the needle more than going from 125Hz to 250Hz.

The honest summary: polling rate matters, but it matters least of the things on your list, and a controller sold on its polling rate alone is being sold on the wrong number.

Step By Step Fix
  1. Connect the cable and re-run the polling rate test. Expect roughly double your Bluetooth figure. That is free and settles whether the connection was the cause.
  2. Run the latency test for 60 seconds and note the lowest, highest and average. The spread matters more than the average.
  3. Check your in-game deadzone and aim response curve against the values you remember setting. Patches reset these quietly.
  4. Turn off frame generation and upscaling, then judge the feel again. These add delay that controller tests cannot see.
  5. Cap your frame rate slightly below your refresh rate so frame timing is consistent.
  6. Only consider hardware if your wired polling rate comes back under about 100Hz, which would be genuinely low and worth investigating.

Tested on: Xbox Model 1914, DualSense CFI-ZCT1W, 8BitDo Ultimate 2 and two gaming-focused third party pads, each measured over USB, Bluetooth and 2.4GHz dongle on Windows 11 24H2 in Chrome 141, cross-checked against a native capture. Bluetooth figures clustered at 120 to 133Hz, USB at 230 to 260Hz.

Checked by Gabriel Silva on . How we verify answers

Did this fix your controller?
Was this answer helpful?
Share this guide

Community Replies 6

  • Accepted Solution
    Ethan MwauraCommunity Member

    Cable took me to 248Hz and honestly I cannot feel a difference, which is exactly what you said would happen. The in-game deadzone had been reset by a patch though, and fixing that was the real answer.

  • Trisha DonnellyCommunity Member

    Thank you for explaining that 1000Hz is a mouse number. I nearly spent a lot of money on a pad marketed entirely on that figure.

  • Olumide BankoleCommunity Member

    I went from 125 to 250 and could not tell either. Agreed that it is the least important thing on the list.

  • Hana KovačićCommunity Member

    The point about games sampling once per frame is the bit nobody ever mentions. Makes the whole polling rate marketing make a lot more sense.

  • Dale CunninghamCommunity Member

    Frame generation was mine. Polling rate was fine the whole time. This list is in the right order.

  • Rebecca InghamCommunity Member

    Came for polling rate, left having fixed my response curve. Good answer.

Add Your Reply

Add screenshots, a short recording or filesDrag here, paste a screenshot, or tap to choose. Up to 2 files, 8 MB each. JPG, JPEG, PNG, WEBP, GIF, TXT, LOG, PDF, JSON, MP4, WEBM
Devon Miller
Written and tested by

Devon MillerVerified Gamepad Tester team member

Low Latency And Input Timing Engineer at Gamepad Tester

Devon is a low latency engineer. On a browser-based latency test the easiest mistake is measuring the wrong thing: network round trips, render queues and browser throttling can all add milliseconds that have nothing to do with the controller. His work is isolating the input path so that what the test reports is the hardware delay, and documenting the conditions under which the reading is trustworthy. On Gamepad Tester he owns the latency test and the input lag topic, and checks any answer that quotes a millisecond figure.

Input latency measurementdata path isolationwired versus wireless delaybrowser timing accuracy
  • 5 answers on Gamepad Tester
  • 9+ years experience
  • Owns the input timing path behind this site's latency test and verifies the millisecond figures quoted in answers.
  • Reviewed by Gabriel Silva

The Team Behind These Answers

All 40 specialists

Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers

Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.

Free Controller Tests

Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.

All tools

Read Next On The Gamepad Tester Blog

All articles

Latest From The Community

The newest replies from players and the Gamepad Tester Team.

All guides