Xbox One controller is a name that covers seven years of hardware and at least five meaningfully different pads, which is why advice about them contradicts itself so often. The one that launched in 2013 has no Bluetooth and no headphone socket. The 2016 revision has both. The Series controller looks almost identical, has an extra button and a different port. They also fail in different ways. This page checks everything a browser can reach on any of them, works out which one you are actually holding, and pays particular attention to the bumpers, because a bumper that has started skipping presses is the single most common thing to go wrong with this family.
Every button, stick and trigger gets tracked separately, including the two that a quick press check almost always misses.
Model identification comes from what the controller tells the browser about itself, which is more reliable over Bluetooth than through a Windows driver.
If the controller never appears at all, that is a connection problem rather than a controller fault, and the controller checker is the quickest way to confirm whether the browser can see the device.
This matters more than it sounds, because half the advice on the internet about Xbox One controllers is correct for one revision and wrong for another. The model number is printed in tiny text on the back, usually in the battery compartment, and it is the only reliable way to know what you own.
No Bluetooth. No headphone socket. It connects by cable or through the Xbox Wireless Adapter and nothing else, so if you have been trying to pair this one over Bluetooth for an hour, you can stop. It has impulse triggers like every Xbox One controller, and a proprietary expansion port on the bottom for a headset adapter.
Same shell, still no Bluetooth, but it added the 3.5mm headphone socket on the bottom. Easy to confuse with the launch pad because they look identical from the front. If it has a headphone socket and no Bluetooth, this is what you have.
The one most people mean by Xbox One controller today. Bluetooth, a headphone socket, textured grips on the back, and a slightly smaller shell. This is the first one you can pair directly with a phone or a computer without an adapter.
Looks like a slightly refined 1708, but it has a Share button between View and Menu, a USB C port instead of micro USB, and a redesigned D-pad. It is fully compatible with Xbox One games and gets called an Xbox One controller constantly, which is why this page tests it too. If your pad has a round D-pad and an extra small button in the middle, this is the one.
The Elite Series 1 from 2015 and the Elite Series 2 from 2019. Both add four rear paddles, swappable sticks and adjustable trigger stops. The paddles are the important part for testing, because they are usually mapped to duplicate existing buttons rather than reporting as new ones, which means a browser sees a paddle press as whatever button it is mapped to. That is not a fault, it is how they work.
The tool takes its best guess from what the controller reports about itself. That guess is reliable over Bluetooth and often vague through a Windows driver, which tends to present every Xbox pad under the same generic identity. When the guess looks wrong, set it by hand in the setup panel.
If there is one signature fault on this family of controller, this is it, and it deserves a section of its own because the way it fails makes it uniquely easy to miss.
The bumpers are not simple buttons. On the Xbox One design, LB and RB sit on a long plastic arm that pivots, and that arm presses a small dome switch positioned toward the inside of the shoulder. It is a lever, and like any lever it works best near the pivot and worst at the far end. Press the bumper toward the middle of the controller and the switch gets a clean, direct push. Press it toward the outside edge, which is where a lot of people naturally rest a finger, and you are working through the longest part of the arm with the least mechanical advantage.
As the plastic wears and the dome loses its snap, the outer end of the bumper stops registering while the inner end still works perfectly. So the controller does not fail cleanly. It develops a habit. Presses go through most of the time, then one does not, and because it works when you check it deliberately, you spend weeks blaming the game.
That is exactly why the bumper stress mode exists and why it asks for twenty presses rather than one. A single press proves nothing here. Twenty presses with two misses is a diagnosis. And a general button test will tell you the bumper is fine, because it is fine, right up until the moment it is not.
Three things separate a healthy bumper from a tired one. Every deliberate press should register, which is why the tool lets you record the ones that did not. The hold times should be consistent, because a dome that has gone soft produces erratic contact durations rather than clean ones. And no press should produce two registered inputs, which is the other way a failing dome gives itself away.
This is a cheap and genuinely approachable repair. The bumper switches are common parts, they sit right at the top of the board once the shell is open, and they are among the easier components to reach. If your controller is otherwise fine, replacing a bumper switch is a far better use of money than a new controller.
Everything at once, with nothing prompted. Every input lights up as you press it and stays marked as seen, both sticks draw on the crosshairs, and both triggers fill their bars. This is the mode for confirming a suspicion quickly and for showing somebody else what your controller is doing.
The tool names each input in turn and waits for it, which stops you from accidentally skipping the ones people always forget. Those are usually the stick clicks and the Xbox button. If something genuinely will not respond, there is a button to record that rather than sitting there pressing it forever.
Twenty deliberate presses on one bumper, counting registrations, timing each hold, and flagging any press that produced two inputs. Run it on both sides. This is the mode that finds the fault described above.
Ten seconds with the controller flat and your hands off. It reports where each stick rests and how far it wandered. Xbox sticks use the same wearing sensor design as almost everything else, so drift is a matter of time rather than luck, and our dedicated stick drift test goes deeper if this one flags something.
Pull each trigger slowly to the stop and back. It records where the trigger rests, how far it reaches, and whether it returns cleanly to zero. A trigger that rests above zero reads as a permanent light pull in games, which is the cause behind a car that creeps on its own.
Four separate motors get exercised in turn. The two main rumble motors in the grips, then the two small motors inside the triggers themselves. Those trigger motors are the thing Xbox controllers have that nothing else mainstream does, and they fail independently of the main motors.
How many of the seventeen or eighteen inputs the tool saw. Eighteen means you have a Series controller with a Share button. A missing input is only meaningful once you have actually tried to press it, so a low number after a casual live check means you did not press everything rather than that anything is broken.
Registered presses against deliberate presses. Twenty of twenty is a healthy bumper. Nineteen of twenty is the beginning of the fault described above and it will get worse. Anything below that is already affecting your games whether you have noticed or not.
The larger of the two resting values, measured while nothing is touching the sticks. Under 0.02 is normal sensor noise. Between 0.02 and 0.08 is mild drift that most games will hide behind their deadzone. Above 0.08 is a stick that is actively pulling and the movement is reaching your games.
How much of the value range each trigger delivered from rest to the stop. Close to a full 1.00 is what you want. A trigger that rests above zero or never reaches full is worth investigating, and the trigger pressure test breaks that down properly.
Which of the four motors responded. Both grip motors is the minimum for a working controller. The two impulse trigger motors need a recent Chrome or Edge as well as the right hardware, so a refusal there is often the browser rather than the pad.
| Reading | Healthy | Getting tired | Worth fixing |
|---|---|---|---|
| Inputs registered | all of them | all with retries | any input unreachable |
| Bumper reliability | 20 of 20 | 19 of 20 | 18 or fewer |
| Double inputs on a bumper | zero | one across a long session | two or more |
| Stick resting value | under 0.02 | 0.02 to 0.08 | above 0.08 |
| Trigger resting value | 0.00 | up to 0.02 | above 0.03 |
| Trigger reach | 1.00 | 0.97 to 1.00 | under 0.97 |
| Grip motors responding | both | not applicable | either one silent |
| Impulse trigger motors | both, on supported hardware | refused by the browser | accepted but nothing felt |
One piece of context worth having. The impulse trigger row is the one most likely to give a confusing result, because there are two separate reasons it can fail. If the command is refused outright, that is your browser or the model. If the command is accepted and you feel nothing, that is the hardware. The tool distinguishes between those two, which is why the wording in your results is specific about which happened.
Xbox controllers reach a computer by three different routes and they are genuinely not equivalent, which explains a lot of results that otherwise look like faults.
A USB cable. The most reliable route for every model and the one to use for any measurement you plan to keep. Worth knowing that plenty of cheap cables are charge only, with no data lines connected at all, and a charge only cable produces a controller that lights up and is completely invisible to the browser. If a wired pad refuses to appear, swap the cable before anything else.
The Xbox Wireless Adapter. The small dongle that speaks the same proprietary protocol the console uses. Lower latency than Bluetooth, supports every feature including rumble properly, and works with the 1537 which cannot do Bluetooth at all. If you own one, this is the best wireless option by a clear margin.
Bluetooth. Only on the 1708 and later. Convenient, works with phones and tablets, and measurably slower and less consistent than either of the other two. Rumble support over Bluetooth also varies more by browser version than it does over a cable. If your timing or rumble results look poor wirelessly, retest wired before drawing any conclusion, and if the connection itself keeps dropping, the connection stability test is the page for that.
One more quirk specific to this family. An Xbox controller can only hold one wireless connection at a time, so a pad still paired to a console sitting in standby will fight you for it. Turn the console fully off, or hold the pairing button to force it into pairing mode, before assuming anything is broken.
| What the tool shows | What is happening | What to do |
|---|---|---|
| A bumper misses occasional presses | The classic Xbox One fault. The dome switch under the bumper arm has lost its snap, and the outer end of the lever no longer reaches it reliably. | Replace the bumper switch. Cheap part, easy to reach once the shell is open, and far better value than a new controller. |
| A stick reports movement at rest | Drift. The sensor has worn and no longer reports true centre. | Clean around the stick base with compressed air first. If it returns, the module needs replacing. |
| A trigger rests above zero | The return spring is not bringing it fully back, or the sensor zero has shifted. | Work the trigger through its range thirty times and remeasure. If it stays, open and check the spring. |
| Face button needs a hard press | The conductive pad on the rubber membrane has worn, or debris is sitting under it. | Open and clean the contacts with isopropyl alcohol. A membrane is a cheap part if cleaning does not hold. |
| D-pad diagonals will not register | Two contacts are not closing together. Usually wear at the central pivot rather than dead contacts. | Clean first. The 1914 D-pad is a different design and generally holds up better than the earlier ones. |
| Only one grip motor responds | A dead motor, or more often a cracked solder joint at the motor terminals, since they sit on a vibrating assembly. | Check and reflow the two joints before buying a motor. This fixes it more often than a replacement does. |
| Impulse triggers refused by the browser | Either the browser does not support the command or the controller does not have the motors. | Try current Chrome or Edge. If it is still refused, check your model, since only Xbox One and Series pads have them. |
| Controller not detected at all when wired | Very often a charge only cable with no data lines. | Swap the cable for one you know carries data, then try a different port. |
| Everything works wired and misbehaves wirelessly | The link rather than the controller. Interference, distance, or old controller firmware. | Update the firmware, which is the fix people forget, and check the battery. |
| Nothing registers on any input | Usually a mapping or driver problem rather than a fault. | Check what the pad is actually sending with the controller mapping tool. |
Covered above, and it is the leading cause of a controller that feels unreliable rather than broken. The design puts a lot of mechanical demand on one small switch through a long plastic arm.
The sticks use a wiper dragging along a resistive track, and the track wears where it gets used most. That produces drift, noise, or both. Nothing about the Xbox design makes this worse than average, but nothing makes it better either, and it is the second most common complaint after bumpers.
The triggers see enormous use in shooters and racing games. Springs weaken, which shows up as a resting value above zero, and the sensor track wears at the ends, which shows up as a trigger that never quite reaches full.
Specific to some revisions and purely cosmetic, but worth mentioning because it worries people. The soft coating on the back of certain models degrades into a sticky mess over years, especially in warm humid conditions. It has no effect on any input and it cleans off with isopropyl alcohol and patience.
The two sprung contacts in the battery compartment corrode and lose tension. That produces a controller that cuts out when you move it, or that reports a low battery on fresh cells. Cleaning them with a cotton bud and alcohol, then gently bending the springs out a fraction, resolves this surprisingly often. If the pad still behaves oddly on good batteries, the battery health test will help you decide whether the pack is the problem.
Everything before the 1914 uses micro USB, which is a connector that wears from repeated insertion and eventually holds the cable loosely. A wired controller that works only when you hold the cable at an angle has a worn port rather than a worn anything else.
The Xbox One controller is one of the more repairable pads. The shell comes apart with a T8 security screwdriver and one hidden screw under the sticker in the battery compartment. Bumper switches, stick modules and trigger springs are all cheap, available, and reachable once you are inside. The teardown steps and the safety notes in the controller repair guide cover the same disassembly that gets you to all of them.
Anything involving the micro USB port. Replacing it means removing the old one from a multilayer board without lifting pads, which is a genuinely difficult job and a bad first soldering project. If a worn port is your only fault, a wireless adapter is often the cheaper answer.
Every input registering, both bumpers at full marks, sticks resting near zero and both motors alive is a healthy controller. Sticky grip coating is cosmetic. And a stick resting at 0.01 is normal sensor noise rather than early drift, so there is nothing there to chase.
Xbox controllers receive firmware updates, and a surprising share of the problems people bring to a testing page turn out to be old firmware rather than worn hardware.
The updates are not cosmetic. They have fixed Bluetooth pairing failures, connection dropouts, audio problems through the headphone socket, and latency behaviour. A controller bought second hand has very often never been updated in its life, because the previous owner used it on a console that did it silently and the new owner never plugged it into anything that would.
The update comes from the Xbox Accessories app, which is free on Windows and also available on the console itself. Connect the controller with a cable, open the app, and it tells you whether an update is waiting. It takes a couple of minutes.
Worth doing before you conclude anything about a controller that behaves inconsistently over Bluetooth, because that is precisely the category of problem firmware updates have addressed most often. If the pad still drops out on current firmware, then the problem is real and worth chasing.
Buttons, both sticks, both triggers as analog values, and rumble including the impulse triggers on supported hardware. That covers essentially everything on an Xbox controller, which is not true of every pad, since Xbox controllers have no motion sensor and no touch surface to be locked out of.
Battery level is not exposed to a browser, so any page claiming to read your Xbox controller battery percentage is inferring rather than reading. Headphone socket audio is outside a page's reach entirely. Elite paddles report as whatever button they are mapped to rather than as separate inputs, so a browser cannot distinguish a paddle press from the button it duplicates.
Inputs are read in step with your display refresh, so a 60Hz screen gives about sixty looks a second. That is plenty for catching missed presses and drift, and not precise enough to call any of the timing here a proper timing measurement. If you want to know how often your pad reports underneath that, the polling rate test shows it, and if you want to measure delay from press to response, that belongs to the latency test.
The tool reads what the controller reports about itself. Over Bluetooth that is usually specific enough to name the exact revision. Through a Windows driver it is often deliberately generic, because Windows presents most Xbox pads under one identity for compatibility. A vague answer there is Windows being Windows rather than a fault, which is why you can set the model by hand.
Intermittent faults are the ones support dismisses, and a bumper that misses two presses in twenty is by definition intermittent. Two runs on separate days that agree is much stronger evidence than one run, and both reports export cleanly.
Sign in to your account