Nintendo Switch Pro Controller Test

Test a Switch Pro Controller and the first thing you notice is that the buttons are wrong. Press A and something reports B. Press X and you get Y. Nothing is broken, and this page explains exactly why it happens and confirms it on your own controller with a short guided check. It also tests every input using Nintendo's own labels, reads both sticks for drift, and is upfront about the parts a browser cannot reach, which on this controller includes the motion sensors, the amiibo reader and the rumble detail that makes HD Rumble worth having.

Test Your Pro Controller

Results

Input checklist

Report

Why Your A Button Reports as B

The same swap applies to the other pair. Nintendo puts X at the top and Y on the left. Xbox puts Y at the top and X on the left. So pressing X on a Pro Controller usually reports as Y, and pressing Y reports as X.

This is why so many PC games show the wrong prompts with a Pro Controller attached, and why a button test that only knows Xbox labels looks like it is malfunctioning.

Confirm it on your own controller

Run the A and B check from the setup panel. It asks you to press each of the four face buttons in turn, by the letter printed on the plastic, and records which index your browser received. At the end it tells you plainly whether your controller is reporting in the positional order or in Nintendo's lettered order, and gives you the exact mapping table.

That matters because it is not always the same. It depends on how you connected the controller and what software sits in between, which is the next section.

If you want to watch the raw indices change live while you press things rather than run a guided check, the controller mapping tool prints every index your pad sends and the gamepad viewer shows the values moving in real time.

Three Ways to Connect, and They Do Not Behave the Same

This is the part that catches people out. A Switch Pro Controller does not present itself identically over every connection, so the answer to what is wrong with my controller often turns out to be nothing, you just changed how it is plugged in.

Bluetooth

Hold the small round pairing button on the top edge next to the USB-C port until the four lights start running back and forth, then pair from your device. This is usually the most reliable route for a browser, because the controller appears as a gamepad without needing anything installed. Expect the positional button order described above.

USB-C cable

Works, but historically this has been the fussier route on Windows without something to interpret the controller. If you plug it in and nothing appears, that is a known quirk rather than a broken port or a broken pad. Try Bluetooth before you conclude anything, and if the cable works elsewhere then the cable is fine.

Through Steam

Steam has proper Switch Pro support including motion, and it can present your controller to everything else on the system as a completely different device. That is useful in games and confusing in a test page, because what your browser receives is Steam's version rather than the controller itself. For an honest reading of the hardware, close Steam and connect over Bluetooth. Then reopen it if you want to see what Steam is doing differently.

One practical note that applies to all three. If your controller connects but nothing at all registers, confirm the browser can see the device before assuming a fault, which the controller checker answers in a single screen.

Step by Step, Start to Finish

Step one, connect and wake it

Pair over Bluetooth or plug in a USB-C cable, then press any button on the pad. Browsers hide gamepads until they see a real input, so nothing appears before you do that.

Step two, tell the tool how it is connected

Pick USB, Bluetooth or Steam from the dropdown. It does not change the measurements, but it does change the notes you get at the end, because the same symptom means different things on different connections.

Step three, run the A and B check first

Do this before the main test. It takes about fifteen seconds and it means every result afterward makes sense. The tool names one face button at a time by its printed letter and records what arrives.

Step four, press Start and work around the pad

All four face buttons, both shoulders, both ZL and ZR, all four D-pad directions, both sticks in a full circle, both stick clicks, Minus and Plus. Each one turns green and the counter climbs toward eighteen.

Step five, let both sticks rest

Take your thumbs off completely and leave the controller alone for a few seconds. The two rest readings fill in underneath. That pair of numbers is your drift check and it is the most important thing on the page for a controller with any age on it.

Step six, try the rumble

Run the light and heavy tests. Expect it to feel coarse compared with a Switch game, for reasons covered further down.

Step seven, read and save

Read the verdict, then the notes, then the checklist for anything still grey. Copy or download the report. A measurement you can compare against in six months is worth far more than one taken in isolation.

ZL and ZR Are Not Analog, and That Is Normal

Worth stating clearly, because people coming from an Xbox or PlayStation pad expect a travel meter here and there is nothing to measure.

On a Switch Pro Controller, ZL and ZR are digital switches. They are either pressed or they are not. There is no pressure reading, no partial travel and no analog value, which is why this page shows them as ordinary buttons rather than as meters like the ones on our trigger pressure test.

That has real consequences in games. Racing titles on Switch cannot give you fine throttle control from the triggers the way they can on other consoles, which is why many of them use a stick for acceleration or simply accept on and off. If you have been trying to work out why your Switch racing games feel less precise than the same games elsewhere, this is why, and no setting will change it.

What can still go wrong with them is mechanical. A ZL or ZR that needs a firmer press than it used to, feels mushy, or only registers when pressed at one end has a worn switch or a lever that is no longer transferring the press cleanly. The checklist on this page catches a dead one, and if you suspect a button is double firing rather than dying, the button test checks every button on the pad for that specific behaviour.

What a Browser Cannot Reach on This Controller

The Pro Controller has more inside it than the standard gamepad interface exposes, and it is better to know that up front than to conclude something has failed.

• Motion sensing. There is a gyroscope and an accelerometer in there, and neither comes through the interface a browser uses for controllers. Gyro aiming works on a Switch and in Steam because both talk to the controller at a lower level. Our gyro test covers what is possible on controllers that do expose motion data.
• HD Rumble detail. Covered properly in the next section.
• The amiibo reader. The NFC hardware sits near the left stick and is completely invisible to anything except a Switch.
• Battery percentage. Not part of the standard interface on any controller. If you want to track charge behaviour, the battery health test works from observed behaviour rather than a reported number, though the Pro Controller is famously the last pad you will need it for.
• The player indicator lights. Cannot be read or set.

None of that means anything is faulty. It means the browser has no route to it.

HD Rumble Through a Browser

The Pro Controller does not use the spinning weight motors that most controllers do. It uses linear actuators, which move a mass back and forth along a driven waveform. That is what lets a Switch game make you feel individual ice cubes in a glass rather than a general buzz.

The catch is that the standard gamepad interface only knows how to ask for old fashioned rumble. It sends a weak value, a strong value and a duration. Your controller receives that and approximates it, which means the rumble test on this page is a working check rather than a demonstration.

So read it this way. If you feel something, the actuators are alive and connected. If it feels coarse and characterless compared with a Switch game, that is expected and it is not a fault. For a longer workout across patterns and intensities on any controller, the vibration test runs sequences rather than single bursts.

What Actually Breaks on a Pro Controller

Stick drift, by a distance

The Pro Controller uses the same style of contact based potentiometer sticks that caused the well documented Joy-Con problem, and they wear the same way. The resting value creeps away from centre and your character starts moving on its own. On this page it shows in the two rest readings under the diagram, and past about 0.08 it is worth acting on.

For a proper measurement rather than a quick check, the stick drift test turns the offset into a starting deadzone value, and the joystick deadzone test covers the trade you make when you raise that number. If you also own newer Nintendo hardware and want to know whether the situation improved, our Joy-Con 2 drift test goes through what Nintendo changed and what it did not.

The D-pad

Generally one of the better parts of this controller, but it is still a single rocking cross rather than four separate buttons, so it can develop the usual faults. Diagonals that will not register, inputs dropping out during a roll, and phantom directions all come from the same place. The D-pad test has a roll mode built specifically to catch the dropouts a press by press check will miss.

The shell separating

A known cosmetic and structural issue where the two halves of the grip start to part. It rarely affects inputs, but it does get worse and it makes a used controller worth less. Worth checking by hand rather than by software.

The USB-C port

Soldered to the board and it takes the strain every time somebody plays while charging. Less common than on older controllers because the connector is sturdier, but still the part most likely to end a long serving pad.

Battery, which is genuinely not a problem

Worth saying because it stands out. The Pro Controller gets roughly forty hours from a charge, which is several times what a DualSense manages. If yours suddenly does not, that is unusual enough to be worth investigating rather than accepting.

Reading Your Results

Inputs confirmed

Eighteen inputs are counted. Home and Capture sit outside that number because many systems intercept them before a browser sees them, so a grey Home panel is not a fault. Anything else still grey at the end is either broken, mapped somewhere unexpected, or not pressed yet.

Stick rest readings

Under 0.02 is clean. Between 0.02 and 0.08 is minor and hidden by most games' own deadzones. Past 0.08 you will feel it, and it tends to worsen rather than settle.

If the rest readings look fine but a stick still feels wrong, the fault is elsewhere. A stick that will not reach the edges belongs to the analog stick range test. One that traces an uneven shape at full travel belongs to the circularity test. One that will not sit still belongs to the stick jitter test, and one that flicks the wrong way when you release it belongs to the snapback test.

Face button layout

Whether your controller reported in positional order, which is the usual result, or in Nintendo's lettered order. Either is normal. Knowing which you have is what stops you chasing a fault that does not exist.

Rumble

Whether the browser accepted the instruction. You still have to judge whether you felt it, since the tool can only report that the request went out.

Method and Honest Limits

Mapping is not guaranteed

Nintendo controllers are the most likely of any mainstream pad to report through a non standard path, particularly over a cable on Windows. If the mapping status does not say standard, treat the labels on the diagram as a starting point and trust the A and B check instead.

Steam changes what you are testing

If Steam Input is active, you are testing Steam's virtual controller rather than your Pro Controller. That is a genuine measurement of what your games receive, but it is not a measurement of the hardware. Close it for a hardware reading.

Sampling

Inputs are read in step with your display refresh, roughly once every seventeen milliseconds on a sixty hertz screen. Plenty for confirming a button works and reading a resting stick, not precise enough to call anything here a timing measurement. If input delay is what you are chasing, the latency test and the polling rate test are the right pages.

Wireless adds variables

A dropped packet looks the same as a dropped input from inside a browser. If results differ between sessions, test on a cable, and if the drops only happen wirelessly the connection stability test watches for them over a longer run.

Everything stays on your device

The controller is read in the page, the maths happens in the page, and the exports are files your own browser writes.

Questions People Actually Ask

Why does pressing A show up as B?

Because software identifies buttons by position, and Nintendo puts A where Xbox puts B. Nothing is broken. Run the A and B check on this page and it will show you the exact mapping your browser is receiving.

Can I fix the swapped buttons?

Not from a web page, but you can in most games and in Steam, which has a setting to use Nintendo button layout so prompts match your controller. Some games detect it automatically.

My Pro Controller works over Bluetooth but not over USB.

That is a known quirk rather than a fault. The cable connection has historically been the fussier one on Windows without something interpreting the controller. Use Bluetooth for testing and do not assume your port or cable has failed.

Why can I not test the gyro here?

Motion data is not part of the standard gamepad interface. Your Switch and Steam can both read it because they talk to the controller at a lower level than a browser is allowed to.

Why do ZL and ZR have no pressure reading?

Because they are digital switches on this controller rather than analog triggers. There is no travel to measure. That is a design choice rather than a limitation of this page.

How much stick drift is too much?

Under 0.02 at rest is clean and under 0.08 is usually hidden by a game's own deadzone. Past that you will notice it in menus and in play, and on Nintendo hardware it tends to progress rather than plateau.

Is the rumble supposed to feel this weak?

Through a browser, yes. The interface can only request plain rumble, and your controller approximates it using hardware built for something far more detailed. Feeling anything at all means the actuators work.

Does this page work with a Switch 2 Pro Controller?

If your system can see it as a gamepad, the inputs will read, though the newer controller is much harder to connect to a PC. The stick measurements and the guidance here still apply.