How to use this controller test
1. Connect the controller first
Use USB if you want the cleanest baseline. If you use Bluetooth, pair the controller with your system before opening the page, then press any button so the browser starts reporting it.
2. Test every control path
Watch the layout while you press face buttons, D-pad directions, shoulder buttons, both triggers, and both sticks. A good controller tester should make missing input obvious fast.
3. Leave sticks untouched for drift checks
When you suspect stick drift, stop touching the controller and watch whether the analog sticks rest close to center or keep drifting outside the deadzone.
How to connect your controller
Start with the simplest path. If possible, plug your controller in with USB before trying Bluetooth. A wired connection makes controller test sessions more predictable and removes a whole layer of wireless pairing issues. Xbox controllers, DualShock and DualSense pads, Switch Pro controllers, Steam Deck controllers, and many 8BitDo or generic gamepads can also work wirelessly, but the browser only sees them after the operating system already paired them correctly. That means this controller test is not the same thing as system pairing. You still need the device connected at the OS level first. After that, open the page and press any button on the controller. In many browsers the Gamepad API stays quiet until that first user input happens. If the page still says not connected, wake the controller, reconnect it, or retry in Chrome, Edge, or Firefox desktop. If you are troubleshooting a Bluetooth controller test, compare results with a wired run first. That is often the fastest way to separate browser detection issues from a real hardware problem.
What this test checks
This controller test checks the core things that matter when a gamepad feels unreliable. It shows whether the browser can see the controller at all, whether buttons register, whether triggers move through a pressure range, and whether both analog sticks report stable values. That makes it useful as a gamepad test before you blame a game, emulator, launcher, or Steam input profile. If one face button on an Xbox controller test never registers, you can narrow the issue quickly. If a DualSense test shows one trigger never reaching full range, you immediately have a better clue than a vague feeling that the pad is wrong. The same is true for Switch Pro controller test sessions, where drift or trigger inconsistency can be hard to separate from game-specific deadzones. A practical controller tester should help you answer simple questions fast: does the browser detect the controller, do the buttons react, do sticks center properly, and do triggers travel cleanly. That is the level this page is built for.
What is stick drift and how to detect it?
Stick drift is one of the biggest reasons people search for a controller test, a stick drift test, or a gamepad tester. It happens when an analog stick reports movement even though you are not touching it. In real use that can look like a character walking slowly on its own, a camera creeping to one side, menu focus drifting, or aiming never feeling stable. The clean way to detect stick drift is to leave the controller untouched and watch the stick values. If they rest close to zero, the controller is probably fine. If the values repeatedly sit outside the deadzone for several seconds without input, that is a meaningful warning. Small fluctuations are normal, and a good controller test should be honest about that. Not every tiny movement means hardware failure. But sustained off-center values can point to wear, dirt in the module, bad calibration, or a stick assembly that is simply reaching the end of its life. That is why stick drift deserves its own visual treatment and not just raw numbers hidden in a corner.
Controller deadzone explained
Deadzone is the safe area around the center of an analog stick where tiny movements are ignored. Every controller test that shows raw stick positions should also explain deadzone, because drift and deadzone are related but not the same thing. A healthy controller can still show very small non-zero values because no analog hardware is perfectly still. Games usually hide that noise by applying a deadzone. A controller deadzone test is useful because it shows how close the raw values stay to center before game logic smooths them out. A bad controller can still feel acceptable in some games when the deadzone is large, but the hardware may already be degrading. On the other hand, a very small deadzone can make a healthy controller feel too sensitive. That is why a controller deadzone test and a stick drift checker should be read together. One shows raw motion, the other shows whether that motion is likely to become a real gameplay problem.
Browser compatibility and troubleshooting
Chrome, Edge, and Firefox desktop are the best places to run a controller test or gamepad test online. Safari desktop can work, but support varies more by macOS version and controller type. iPad with a paired Bluetooth controller can work in some situations, while iPhone browser support is still limited for full game controller test flows. If your controller works in Steam or a native game but not here, that does not automatically mean the hardware is broken. Browsers use the Gamepad API, and the browser may need a real button press before it starts reporting the device. Some controllers also expose slightly different mappings, which is why a browser-based gamepad tester can behave differently from a game. The practical checklist is simple. Reconnect the controller. Press a button after the page loads. Retry in a Chromium browser. Compare USB and Bluetooth behavior. If the controller still disappears, test the same hardware in another app to decide whether the issue is with the browser layer or the controller itself.
Fixing common controller problems
A controller test is most useful when it helps you isolate the problem before you spend money. If one button never appears in the controller button test area, compare results across another browser and another app. If the same input fails everywhere, the switch may be worn out. If the trigger bars never reach high values, the trigger may be obstructed, worn, or simply calibrated low by the browser mapping. If a wireless controller test behaves badly but USB works, you may be dealing with Bluetooth interference or pairing instability rather than a true hardware defect. For stick drift, start with the easy steps first: reconnect the controller, clean around the stick modules, and test again after the controller sits untouched for a few seconds. Some pads improve after recalibration, but severe drift usually points to hardware wear. A controller tester cannot repair the pad, but it can tell you whether the problem is likely to be real, repeatable, and isolated to one control path. That is often the difference between guessing and making the right repair decision.
FAQ
How do I connect my controller to the browser?
Pair or plug in the controller at the system level first, then open the page and press any button so the browser exposes it through the Gamepad API.
My controller is not detected. What should I do?
Reconnect it, press a button again, and retry in Chrome or Edge on desktop first. Browser detection often fails until the first real input happens.
What is stick drift?
Stick drift is unwanted analog-stick movement when the stick is untouched. It usually appears as non-zero values or movement in one direction at rest.
Is stick drift fixable or do I need a new controller?
Sometimes it is fixable with cleaning, recalibration, or module replacement. Severe repeated drift often means the hardware is worn enough that repair or replacement is the realistic path.
Why does my controller work in games but not here?
Games may use different input layers than the browser. The browser also requires Gamepad API support and often a first button press before it detects the device.
Does this work on iPhone or iPad?
iPad support can work with paired Bluetooth controllers, but iPhone browser support is still limited and less reliable for full controller testing.
Can I test DualSense haptics or adaptive triggers here?
No. V1 is focused on input detection only: buttons, sticks, triggers, and drift-related signals.
What is the difference between deadzone and stick drift?
Deadzone is a software tolerance around center. Stick drift is unwanted movement from the hardware or calibration state.
Why do trigger values not reach exactly 100%?
Some controllers, browsers, and worn trigger mechanisms report slightly under full scale. That does not always mean the trigger is broken, but it can indicate wear.
Can I test PlayStation 5 or Xbox Series X controllers wirelessly?
Yes, if the controller is already paired correctly with your system and your browser exposes it through the Gamepad API. Wired testing is still the most reliable baseline.