Nintendo Switch Pro Controller Test
Connect a Switch Pro Controller over USB or Bluetooth and inspect the sticks, buttons and browser-reported mapping. Individual Joy-Con support varies by browser and operating system, so the page identifies those limitations instead of assuming a full two-stick layout.
Controller status
No Controller Detected
Connect your controller using USB or Bluetooth and press any button.
If you have multiple controllers connected, you can select and test each one separately.
- Browsers only reveal a pad after it sends its first input — press a face button or move a stick.
- Both USB and Bluetooth work. If nothing appears at all, reconnect the controller and press a button with this page focused.
- Some remapping tools claim the pad before the browser sees it. If nothing shows up, try closing them and reloading.
- Chrome or Edge expose the most controller features, including vibration.
Live input
Press anything — the diagram reacts instantly
Stick drift test
Timed resting measurement of both analog sticks
Connect a controller and press any button to enable this test.
Button test
Press every button once — each one lights up as the browser sees it
Connect a controller and press any button to begin.
Trigger test
Pull each trigger slowly from rest to fully pressed, several times
Connect a controller to test the triggers.
Troubleshooting
Controller not detected? Work through this checklist
Nine checks covering focus, cables, Bluetooth pairing, background software, DS4Windows virtual controllers and browser support - open it only if your controller is not showing up.
Connecting a Switch controller
A Pro Controller connects over a data USB-C cable, or over Bluetooth by holding the small sync button on the top edge until the lights run back and forth.
Joy-Cons pair individually over Bluetooth when the operating system and browser support them. Each half may appear as a separate non-standard gamepad rather than one combined controller.
Mapping quirks to expect
Nintendo's button layout swaps A/B and X/Y relative to the Xbox arrangement most browsers assume, so labels may not match the physical letters on the pad.
When the mapping is not reported as standard, this page shows raw button numbers rather than guessing which physical control each one belongs to.
Testing Pro Controller sticks and buttons
For resting drift, put the Pro Controller down, leave both sticks untouched and run the full nine-second sample. Repeat after rotating and releasing each stick so a recentring problem is less likely to be missed.
Use the button sweep to check A, B, X, Y, L, R, ZL, ZR, Plus, Minus, stick clicks, D-pad, Home and Capture only when those controls are exposed by the browser. A non-standard mapping may show button numbers instead of Nintendo names.
ZL and ZR may be reported as buttons rather than smooth analog triggers on Nintendo hardware. An immediate 0-to-1 change can therefore be a mapping characteristic rather than limited trigger travel.
Joy-Con testing limitations
A single Joy-Con has one stick, while the shared drift panel is designed around a four-axis, two-stick gamepad. Use the live raw-axis panel to confirm which axes actually move and ignore the unused stick display rather than treating zero-filled missing axes as a measurement.
Do not use the combined health score as a complete Joy-Con certificate unless the browser exposes the expected controls. Missing axes, SL/SR buttons, motion sensors, rail behaviour and pairing as a left/right set are not all represented by the standard Gamepad API.
USB, Bluetooth and browser limitations
Compare USB and Bluetooth with the same browser when possible. A different device name, button order or vibration result can reflect the platform's mapping rather than a physical change in the controller.
The page cannot test gyro, accelerometer data, NFC, the Home-button system action or Nintendo's HD Rumble behaviour through the standard browser interface. It reports only buttons, axes and optional vibration capabilities that the browser exposes.
When a result looks wrong
First check the raw mapping and axis count. Then reconnect, press a button with the page focused, and compare another browser before assuming a control has failed.
For a repeatable Pro Controller or Joy-Con issue, compare the browser reading with Nintendo's own controller calibration and support options. GamePadTestLab cannot recalibrate firmware or identify the physical cause of drift.
Frequently asked questions
- Can I test Joy-Con drift here?
- Sometimes. If the browser exposes a Joy-Con, use the raw live axes to identify its single stick. The shared two-stick drift panel fills absent axes with zero, so do not treat the unused side as a measured result.
- Why are the A and B labels swapped?
- Browsers map by position using the Xbox convention. Nintendo's physical letters sit in the opposite places, so the label may not match the print on the button.
- Does gyro or HD rumble work in a browser?
- No. Motion sensing and HD rumble are not exposed through the standard browser gamepad interface.
- Is Joy-Con drift repairable?
- Replacement stick modules are widely available and Nintendo has run repair programmes in several regions. Measure first so you know which stick is affected.
Continue testing
- Controller Stick Drift TestRun a timed resting measurement on both analog sticks. See average, median, peak and 95th percentile offset, plus a clear verdict on whether your controller is drifting.
- Controller Deadzone TestInteractive deadzone visualizer for analog sticks. Adjust the radius, see which movement gets ignored, and get a recommended minimum deadzone from your own measured resting noise.
- Controller Health CheckRun a guided full diagnostic and get a transparent controller health score with per-category results, a confidence level and a downloadable report card.
- Used Controller CheckA fast two-minute inspection for second-hand controllers. Check drift, buttons, triggers and stick range, then save the evidence as a report.
GamePadTestLab reports what your browser can see. It cannot repair stick drift, certify hardware, or read a controller's firmware. Read the testing methodology for exactly how each figure is calculated and where it stops being reliable.
Built and maintained by Joseph Sanusi
Software Developer - GamePadTestLab
Last updated: 16th October 2026