Seedance 2.5 Flash: A New Way to Create AI-Powered Videos
Content creators, marketers, and businesses are finding creating images and videos more and more effortless via AI. As…
Using your gamepad tester for the first time. I see Axis 0, Axis 1, up to Axis 5 and buttons numbered 0 to 16 or so. Which is which on my controller? And why does my cheap pad show the triggers as axes 4 and 5 but my Xbox pad shows them as buttons?
With a standard layout, axes 0 and 1 are the left stick, 2 and 3 the right stick, and buttons 0 to 3 are the face buttons, with triggers as buttons 6 and 7 that also carry analog values. Controllers without a standard layout report their own order, which is why your cheap pad shows triggers as axes.
Browsers describe controllers using a standard layout when they recognise the controller. In that layout, axis 0 is the left stick horizontal and axis 1 the left stick vertical, axis 2 and 3 are the right stick. Buttons 0 to 3 are the face buttons, bottom, right, left and top, then 4 and 5 are the bumpers, 6 and 7 the triggers, 8 and 9 the centre buttons, 10 and 11 the stick clicks, 12 to 15 the D-pad, and 16 the home button.
In that standard layout, the triggers are buttons that also carry an analog value from 0 to 1, which is how your Xbox controller appears.
When the browser does not recognise a controller, it reports the controller's own raw order instead, marked as a non-standard mapping. Many cheap pads in DirectInput mode report the triggers as extra axes, often 4 and 5, and their buttons in a different order. Nothing is wrong; it is just a different description.
A few practical notes. Vertical stick axes are usually negative when pushed up. Triggers reported as axes often rest at -1 rather than 0. And if a cheap pad has an X and D mode switch, X mode usually gives the standard layout.
Tested on: Applies to all controllers in Chrome, Edge, Firefox and Safari. Layout per the W3C Gamepad specification's standard mapping.
Checked by Arjun Mehta on . How we verify answers
Front-End Web Architect And Gamepad API Lead at Gamepad Tester
Calder is a front-end web architect working with the HTML5 Gamepad API. His focus is the part most browser testers get wrong: reading a controller often enough, and timing it well enough, that the numbers on screen match what the hardware is actually sending. He writes the polling loops that capture analog trigger tension and stick travel without dropping samples, and renders them on 2D vector layouts that hold a steady 60+ FPS on ordinary laptops. On Gamepad Tester he maintains the main tester tool, the button test and the trigger pressure test, and reviews any answer that explains how a reading on this site should be interpreted.
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.
Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.
Content creators, marketers, and businesses are finding creating images and videos more and more effortless via AI. As…
Ask ChatGPT how to check a controller for stick drift, or which pad to buy next, and the answer you get is no longer…
Plenty of controller blogs start the same way. You fix your own stick drift, write up what worked, and realize you…
The newest replies from players and the Gamepad Tester Team.