Choose the Joy-Con mode before reading results
A Joy-Con test is different from a full-size controller check because Joy-Con can appear as one combined controller, two separate controllers, or a remapped adapter profile. This Joy-Con test is built for the common paired layout where the browser receives one standard gamepad. In that mode B is the bottom face button at index 0, A is right at index 1, Y is left at index 2, and X is top at index 3.
The left Joy-Con side of the Joy-Con test watches the directional buttons at indexes 12 through 15, the left stick press at index 10, the - button at index 8, Capture at index 17, L at index 4, and ZL at index 6. The right Joy-Con side watches the right stick press at index 11, + at index 9, Home at index 16, R at index 5, and ZR at index 7.
- Use the Joy-Con test as a paired Joy-Con baseline before checking single-side modes.
- Keep the raw panel open if a Bluetooth driver or USB adapter changes indexes.
- Treat SL/SR as optional rail buttons because browsers do not standardize them.
- Compare visual highlights with raw data before changing emulator or launcher mappings.
A practical Joy-Con test routine
Start the Joy-Con test with both Joy-Con resting flat. Before touching either stick, confirm that the two analog dots stay near center. Then press the left directional buttons one at a time, followed by B, A, Y, and X on the right Joy-Con. Move next to -/+, Capture, Home, L/R, and ZL/ZR. Finish by clicking each stick and slowly rotating both sticks to the outer edge.
If one side fails during the Joy-Con test, do not assume the whole pair is defective. A single Joy-Con may have low battery, weak Bluetooth signal, worn rail contacts, a sticky button membrane, or a mode mismatch from an adapter. Run the Joy-Con test again after reconnecting, then compare paired mode with the mode you actually use in your game.
- Check stick center first; drift is easier to see before button testing.
- Press one Joy-Con button at a time to catch double-fire or missed presses.
- Use USB or an adapter when Bluetooth pairing creates inconsistent results.
- Repeat the Joy-Con test after changing grip, rail, or sideways play mode.
What this browser Joy-Con test can show
The Joy-Con test can show browser-visible button states, stick axes, raw indexes, timestamps, vibration exposure, and trigger-style values for ZL/ZR when a driver reports them that way. The Joy-Con test can reveal a left stick that leans while untouched, a right stick that does not reach the edge, a sticky A button, or a shoulder input that appears only after heavy pressure.
The Joy-Con test cannot validate every Nintendo hardware feature. Motion controls, accelerometer and gyro data, HD rumble detail, NFC, the right Joy-Con IR camera, console pairing, player LEDs, wake behavior, and firmware functions are not reliable Gamepad API signals. The Joy-Con test does not write firmware or change calibration; it only reads what the browser exposes locally.
SL/SR deserve special care. On a single sideways Joy-Con those rail buttons may act like primary shoulder buttons, but in a paired Joy-Con test they may be hidden or reported as extra indexes. This page displays SL/SR as optional extended inputs and keeps the raw button grid visible so you can confirm what your browser actually receives.
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 Joy-Con Test, treat that limit as part of Joy-Con 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 Joy-Con 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 Joy-Con Test, treat that limit as part of Joy-Con 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 Joy-Con Test page, compare that note with the live module that matches device-specific mapping behavior, connection method differences, input symptoms, and feature exposure.