Test Xbox Series X|S, Xbox One, Xbox 360, Elite and compatible PC controllers in real time. Check every button, analog stick, trigger and supported vibration motor directly in your browser.
Connect an Xbox controller using USB or Bluetooth and press a controller button to make it visible to your browser.
Press a button or move a stick to start testing.
Track thumbstick X/Y position, resting offset, movement range and visible deadzone boundaries.
Place the controller on a steady surface, release both thumbsticks, then start the measurement. Do not touch either stick during sampling.
A drift measurement is observational. Small non-zero values do not automatically indicate a faulty controller.
Pull the triggers slowly to check whether their browser-exposed values increase smoothly and return toward zero.
Send a short vibration command if your browser and controller expose a supported actuator.
Compatibility depends on the browser and device.Inspect browser-reported axis values and button states without assuming every controller uses the same mapping.
No events recorded yet.
Most Xbox controllers can be checked in a modern browser once connected to your computer or compatible mobile device.
Older Xbox 360 wireless controllers require their compatible receiver. Xbox button, Share button and Elite paddle inputs may be handled by system software.
A healthy analog stick should return close to its centre position after you release it. Repeated resting offsets, unexpected movement or inconsistent trigger travel can justify further testing.
Browser measurements cannot determine whether a problem comes from the sensor, firmware, mapping software or a game-specific deadzone.
Check face buttons, hybrid D-pad, bumpers, triggers and thumbsticks through supported browsers. The Share button may not be exposed.
Test wired and compatible Bluetooth revisions. Earlier controllers may require a cable or Xbox Wireless Adapter.
Check standard inputs and analog travel. Rear paddles often duplicate mapped actions rather than appearing as separate browser buttons.
Test wired controllers and compatible receiver-connected wireless versions. Xbox 360 wireless controllers do not use standard Bluetooth.
Many PC-compatible controllers from other manufacturers provide Xbox-style standard mapping. Extra inputs may not appear separately.
Use an updated browser with Gamepad API support. Device permissions, operating system settings and browser restrictions may affect input availability.
Press a controller button after connecting it, keep the tab active, check your USB data cable or Bluetooth pairing and try another supported browser.
Check for button remapping, accessibility settings and applications that capture the controller. Compare the raw button list to the expected mapping.
Test the stick at rest, check your game's deadzone and ensure firmware is current. Persistent drift may need manufacturer support or a qualified repair service.
Browser vibration support is optional. A failed web vibration test does not prove motor failure; try a supported game or the manufacturer's testing software.
Connect the controller by USB or Bluetooth, press a button and use the live layout to check each input. The visualizer reads supported input data through the browser's Gamepad API.
It can measure browser-reported stick movement while the controller is resting. It cannot automatically identify which physical component is causing an observed offset.
Yes, where the operating system and browser expose the controller through the Gamepad API.
Yes. With standard gamepad mapping, the page displays analog values from 0 to 1 and stores the largest values observed during your session.
No. The browser must expose a supported vibration actuator, and the device must implement it. Some controllers or browsers do not provide this capability.
The rear paddles commonly replicate mapped button actions. A browser may therefore report the assigned button instead of a separate physical paddle.
Some third-party controllers and connection modes expose nonstandard mappings. Use the raw input list to see button and axis indices when the diagram does not correspond to the controller.
Some compatible mobile browsers can read paired gamepads. Support varies with the operating system, browser and controller model.
No. It shows controller states as delivered by the browser. True end-to-end latency requires additional measurement methods.
Yes. This widget needs no registration or installation and processes its test readings inside the browser tab.
Xbox Controller Test by Gamepad Tester · Independent browser-based utility · Not affiliated with Microsoft or Xbox.
Sign in to your account