GEARCHECK LABPress a physical controller button and label the browser index that responds. This records the mapping exposed by the browser rather than changing your controller firmware.
READY — choose an action below
No measurement yet.
Browser button indices are not always the printed labels on the controller. Standard mapping follows the browser’s standard gamepad layout; an empty mapping value means that guarantee is absent. The table retains the largest value seen for each index during this run so analog triggers can be compared too. A pressed indicator reflects the active browser value. Labels are your own observations and can be edited after stopping. Exported mappings are reports, not profiles that reconfigure a game.
The browser cannot force firmware remapping or see inputs reserved by drivers. Some controllers appear only after a button press. Multiple devices can change index assignment; stop and select the intended device before comparing runs. Polling pauses when the page is hidden and no vibration or output command is sent.
Device previews, recordings, selected files and report notes stay in your browser. Downloaded files remain on your device. The call check sends small HTTP probes to GearCheck Lab. The WebRTC test exchanges temporary connection descriptions through our server and contacts the disclosed STUN service only after you create or join a session. Ordinary page requests and usage measurement are described in our privacy policy.