Tester
Hardware
GameGamepad Tester
Test gamepad controllers (PS4, PS5, Xbox) for stuck buttons, analog drift, and trigger response. Real-time button mapping and deadzone detection.
No gamepad connected. Press any button on your controller to connect.
Controller Preview
L1
L2
↑
←
→
↓
R1
R2
Press any button on your controller to start testing
Controller Information
Name: -
Raw ID: -
Index: -
Buttons: -
Axes: -
Buttons
Analog Sticks
Left Stick (L3)
X: 0.00 Y: 0.00
Right Stick (R3)
X: 0.00 Y: 0.00
Triggers
Left Trigger (L2)
0.00
Right Trigger (R2)
0.00
D-Pad
↑
←
→
↓
Note: Press any button on your controller to connect. This tool works with PS4, PS5, Xbox, and most USB/Bluetooth game controllers.
Have feedback? Report bugs, suggest features, or share your thoughts — we read them allFrequently Asked Questions
How do I test my gamepad controller?
Simply connect your controller to your computer via USB or Bluetooth, then press any button. The tool will automatically detect your gamepad and display all button presses, analog stick movements, and trigger values in real-time.
What controllers are supported?
This tool supports all standard gamepad controllers including PlayStation (PS4, PS5, DualShock, DualSense), Xbox (Xbox One, Xbox Series X/S), Nintendo Switch Pro Controller, and generic USB/Bluetooth game controllers that follow the standard Gamepad API.
How can I test for analog stick drift?
When your controller is connected, look at the analog stick visualizations. Without touching the sticks, they should stay centered. If the dot moves on its own, you have analog drift. The tool also displays precise X/Y values to detect minor drift.
Can I test wireless controllers?
Yes! Both USB-connected and Bluetooth-connected controllers work. For Bluetooth, make sure your controller is paired with your computer first, then press any button to wake it up and connect to the tool.
Why is my controller not detected?
Make sure your controller is properly connected (USB plugged in or Bluetooth paired). Try pressing different buttons to wake it up. Some controllers require specific drivers. Also ensure you're using a modern browser (Chrome, Edge, Firefox) that supports the Gamepad API.
What is a Gamepad Tester?
A gamepad tester is an online diagnostic tool that helps you verify the functionality of your game controllers. Whether you're using a PlayStation DualShock, Xbox controller, or any standard USB/Bluetooth gamepad, this tool provides real-time feedback on button presses, analog stick positions, trigger pressure, and D-pad inputs. It's essential for identifying hardware issues like stuck buttons, analog drift, or unresponsive triggers before they affect your gaming experience.
Key Features
- Real-time button press detection for all 17 standard gamepad buttons
- Analog stick visualization with precise X/Y coordinates
- Analog drift detection to identify faulty joysticks
- Trigger pressure monitoring (L2/R2 or LT/RT)
- D-pad directional testing
- Support for PS4, PS5, Xbox One, Xbox Series X/S, and Switch Pro controllers
- Works with both wired (USB) and wireless (Bluetooth) connections
- No installation required - runs directly in your browser
How to Use the Gamepad Tester
- Connect your controller to your computer via USB cable or Bluetooth
- Open this tool in a modern browser (Chrome, Edge, or Firefox recommended)
- Press any button on your controller to activate it
- The tool will automatically detect and display your controller's name
- Test each button by pressing it - you'll see visual feedback immediately
- Move analog sticks to check for drift or dead zones
- Press triggers to verify smooth pressure response
- Check the D-pad by pressing all four directions
Common Controller Issues & Solutions
- Analog stick drift: If the stick position shows movement without touching it, your controller has drift. Try recalibrating or consider replacement.
- Stuck buttons: If a button shows as pressed when you're not touching it, there may be debris inside. Try cleaning around the button.
- Controller not detected: Ensure proper connection, try a different USB port, check Bluetooth pairing, or press the controller's sync button.
- Delayed response: For wireless controllers, check battery level and reduce distance from the receiver. For USB, try a different cable.
- Trigger not reaching 100%: This indicates trigger wear or obstruction. Clean the trigger mechanism or consider professional repair.
Frequently Asked Questions
The tool uses the browser's Gamepad API to enumerate connected controllers and exposes everything the operating system makes available: digital buttons (face buttons, shoulder buttons, system buttons, D-pad), analog axes (left and right thumbsticks with X/Y values from −1.0 to 1.0), pressure-sensitive triggers (L2/R2 or LT/RT with values 0.0 to 1.0), and on supported controllers also rumble motors and haptic feedback. It reports the controller's id string (which usually includes the vendor and product), the standard mapping name when applicable, and the raw button and axis index numbers. It does not read battery level, motion sensors (gyroscope/accelerometer in PS5 DualSense), or touchpad input, because those are not exposed by the standard Gamepad API.
Controllers are mechanical devices that wear out — analog sticks develop drift after 100–500 hours of use, buttons gradually lose tactile click, triggers stick from dirt accumulation, and wireless modules can suffer interference issues. Testing before a tournament, competitive ranked match, or long single-player session helps you avoid losing because of hardware rather than skill. For new controllers, testing verifies that all buttons map correctly before you start a return window, and for used controllers it confirms whether the seller was honest about wear. Streamers and content creators test routinely to avoid losing live segments to controller failure. Even unused controllers stored long-term can develop issues from capacitor aging or rubber dome decay.
A healthy controller shows: thumbsticks resting at (0.00, 0.00) ± 0.05 when untouched (this is the natural deadzone of the sensor), triggers at exactly 0.00 when released and reaching exactly 1.00 when fully pressed, buttons that register only when pressed and release cleanly, and a consistent identifier in the id string. Premium controllers like Xbox Elite Series 2, PS5 DualSense, and 8BitDo Ultimate have tight tolerances and very small deadzones. Budget third-party controllers may show resting values of (0.05, 0.10) which forces games to compensate with larger deadzones. If you see thumbstick resting values above 0.15 in any direction, you have measurable drift that will affect gameplay precision.
Analog stick drift is the most common failure mode of modern game controllers. The Hall-effect or potentiometer sensors inside the thumbstick assembly wear unevenly, causing the stick to report movement even when at rest. To detect it: release both sticks completely, do not touch the controller, and watch the X/Y values for several seconds. Any consistent value above ±0.05 indicates drift; values above ±0.15 will cause unwanted character movement in most games. Drift often gets worse over months and may temporarily improve after cleaning around the stick base with compressed air. Permanent fixes require replacing the sensor module or the entire controller. Hall-effect aftermarket replacements (used in 8BitDo Ultimate, GuliKit) are immune to drift and last much longer than original Sony/Microsoft sensors.
The Gamepad API has a "standard mapping" specification that maps physical buttons to consistent indices across controllers, but compliance varies. Xbox controllers tend to follow standard mapping cleanly on Windows. PlayStation controllers use a different physical layout (X/O/Square/Triangle vs A/B/X/Y) that may report under nonstandard mapping depending on the driver. Chrome and Firefox have slightly different implementations — Firefox historically required restart after connecting a new controller, while Chrome auto-detects. On Linux, controller drivers may have different button orderings. The "id" string the tester displays helps reveal which mapping is active. For game developers, always read both standard and raw mappings, and never assume a specific button index corresponds to a specific physical button.
All three work in modern browsers, but with different feature exposure. Xbox Wireless Controller (Series X/S generation) follows the standard mapping closely on Windows and works seamlessly via USB or Bluetooth. PS5 DualSense exposes its standard buttons and sticks fine, but the adaptive triggers, haptic feedback, accelerometer, gyroscope, touchpad, and microphone are not accessible through the Gamepad API — only Sony's native PS5 console and some recent games on PC via Steam Input use them. Switch Pro Controller works via USB and Bluetooth on PC, though its A/B and X/Y labels are physically inverted from Xbox convention which can confuse standard mapping. None of these expose battery state through the web API. For full feature access on PC, native drivers like Steam Input remain necessary.
USB HID (Human Interface Device) is the protocol class defined in USB-IF's HID 1.11 specification for input devices. Game controllers declare themselves as HID class 0x03 with a usage page of Generic Desktop (0x01) and usage of Joystick (0x04) or Game Pad (0x05). The HID Report Descriptor (a small data structure inside the device firmware) tells the operating system the layout of button bits and axis bytes in each input report. The browser receives polled HID reports through the OS and reformats them into the Gamepad API shape. This means quality of detection depends on three layers: the controller firmware's HID descriptor, the OS HID driver, and the browser's Gamepad API implementation. Most issues come from non-compliant descriptors in cheap clone controllers.
The Gamepad API exposes the controller id string which often includes vendor name and product (e.g. "Xbox Wireless Controller (STANDARD GAMEPAD)") plus an internal index number. This is a potential fingerprinting signal but a weak one — millions of users have identical Xbox or PlayStation controllers, so it adds maybe 5–10 bits of entropy. The API only returns data while controller input is being polled, and browsers gate it behind user interaction (a button must be pressed once to "connect"). Sites cannot read controller state without an active page and cannot infer keyboard or mouse input through the controller. Privacy-conscious users can disable Gamepad API in browser settings, but doing so breaks legitimate cloud gaming and browser games. The risk is roughly equivalent to revealing screen resolution.
DIAGNOSTICS11
WUTOOLS