How the Switch Pro controller test maps each button
The Switch Pro controller test uses the standard browser Gamepad layout by physical position. On the Switch-style face cluster, B is the bottom button, A is the right button, Y is the left button, and X is the top button. In the browser's standard index order, those positions are 0, 1, 2, and 3. That is why a Switch Pro controller test may show different labels from an Xbox-style tester even when the physical button is working correctly.
The Switch Pro controller test also separates L and R from ZL and ZR. L and R are the upper shoulder buttons at indexes 4 and 5. ZL and ZR are the larger rear triggers at indexes 6 and 7. On many Switch Pro compatible pads those triggers behave as digital buttons, so the value may jump from 0 to 1 instead of moving smoothly like an analog racing trigger.
- B, A, Y, and X light up by their physical Nintendo-style positions.
- D-pad Up, Down, Left, and Right use standard button indexes 12 through 15.
- Left stick press and right stick press are checked as L3 and R3.
- Home and Capture are shown separately because browser support can vary.
When to run a Switch Pro controller test
Run a Switch Pro controller test after pairing the controller with a PC, changing from Bluetooth to USB, using an adapter, buying a used pad, or troubleshooting a game that shows the wrong button prompts. A Switch Pro controller test is designed to answer a practical question: does the browser see the same physical control you are pressing?
If the Switch Pro controller test shows a clean response but a game behaves differently, check Steam Input, emulator profiles, in-game remapping, operating system drivers, or adapter modes. A Switch Pro controller test gives useful browser evidence, but the game may apply another input layer after the controller reaches the browser.
- Use USB first when you need the simplest connection baseline.
- Repeat the Switch Pro controller test over Bluetooth when wireless play is the real use case.
- Keep the raw input panel visible when an adapter changes button indexes.
- Generate a local report only after you can reproduce the symptom.
Stick, D-pad, vibration, and motion limits
The Switch Pro controller test checks the inputs that browsers commonly expose through the Gamepad API: buttons, stick axes, trigger values, raw indexes, and sometimes vibration. Move each stick slowly to the edge, press each stick down, roll the D-pad in four directions, then press the face buttons one at a time. If a stick rests away from center, use the drift and deadzone modules before assuming the controller is broken.
Motion control, NFC, console pairing behavior, player LEDs, firmware functions, and wake-from-console features are not reliable browser signals. The Switch Pro controller test does not write firmware, change calibration, or access console-only features. A Switch Pro controller test focuses on local browser readings that are safe to observe.
Local testing and privacy boundaries
Gamepad input is read by the browser and rendered on the page. The site does not upload button values, axis values, controller names, microphone audio, or generated reports to a server. For Switch Pro Controller Test, treat that limit as part of Switch Pro controller test guidance rather than as a separate verdict.
Microphone recording starts only after you press the recording button and grant browser permission. Playback and deletion happen locally in the browser. On this Switch Pro Controller Test page, compare that note with the live module that matches device-specific mapping behavior, connection method differences, input symptoms, and feature exposure.
Browser and hardware limits
Gamepad API support, haptic feedback, MediaRecorder, and WebHID are exposed differently across Chrome, Edge, Firefox, Safari, Linux, mobile browsers, USB, Bluetooth, and third-party drivers. For Switch Pro Controller Test, treat that limit as part of Switch Pro controller test guidance rather than as a separate verdict.
A missing feature in the browser does not prove that the controller is damaged. Use the live readings as diagnostic hints and compare results across connection methods when possible. On this Switch Pro Controller Test page, compare that note with the live module that matches device-specific mapping behavior, connection method differences, input symptoms, and feature exposure.