Nintendo redesigned the sticks for the Switch 2 and then confirmed the thing nobody wanted to hear, which is that they still are not the magnetic kind that cannot wear out. So the drift question is not settled, it is just postponed, and checking your controller every so often is a sensible habit rather than paranoia. This page reads everything a browser can reach on a Joy Con 2 or a Pro Controller 2, measures where the sticks actually rest and how far they reach, and includes a check for the new mouse sensor on the right Joy Con 2, which is the one genuinely new input on the whole system.
Every button and stick gets tracked separately. On a single Joy Con only its own half will appear, which is expected rather than a fault.
Identification comes from what the controller tells the browser about itself, which on Nintendo hardware is often vaguer than it is on other platforms.
If nothing appears at all, that is a pairing problem rather than a controller fault, and the controller checker is the fastest way to confirm whether the browser can see any device.
This trips people up more than the testing does, and the answer is different for each piece of hardware.
Plug it into your computer with a USB C cable and press a button. That is the whole process on most systems, and a cable removes any doubt about whether a weak wireless link is affecting your readings. It will also pair over Bluetooth if you hold the small sync button, but take your first measurement wired.
Hold the round sync button on the rail until the lights run back and forth, then add it from your computer Bluetooth settings. It connects as its own small controller with its own name, so if you want to check both halves you pair and test them one at a time. That is not a limitation of this page, it is how the hardware presents itself.
There is no browser level way to merge two separately paired Joy Con into one virtual controller. On the console the system does that for you. On a computer they stay two devices unless you install software specifically for combining them. So test them individually here, and expect each one to show only its own half of the inputs.
The most common cause is that the controller is still connected to the console. A Switch 2 in sleep will happily hold onto its controllers, so put the console fully to sleep or turn it off, then hold the sync button until the lights move. Forget the device in your Bluetooth settings and pair again if it keeps reconnecting to the wrong place.
Chrome and Edge give the most complete support for controllers in the browser, so reach for one of those if a pad refuses to show up elsewhere. If it pairs but nothing registers, check what the pad is actually sending with the controller mapping tool before assuming a fault.
This is why most people land on a page like this, so here is the honest background rather than a reassuring summary.
Before the Switch 2 launched, a lot of people hoped Nintendo would move to Hall effect sticks, the magnetic kind that have no physical contact inside and therefore cannot wear a track down. Nintendo confirmed that the Joy Con 2 and the Pro Controller 2 do not use that technology. What the company said instead is that the sticks were redesigned from the ground up for larger, smoother movement, and teardowns have supported that. The new modules are a genuinely refined version of the old design, with cleaner travel and better sealing against dust, but the sensing method underneath is still the type that physically wears with use.
What that means in plain terms is that drift remains physically possible over the life of the controller, because the part that caused it on the original Switch has been improved rather than replaced. The encouraging half of the picture is that the flood of complaints that hit the first Switch has not repeated at anything like the same volume, which suggests the redesign genuinely helped. The cautious half is that wear takes time to appear, so the real test is a year of play rather than the first week.
Which leads to the practical advice this page exists for. Measure your controller while it still feels perfect and save the number. Drift creeps in slowly enough that your expectations creep with it, and by the time something feels wrong you will have nothing to compare against. A reading from six months ago is what turns a suspicion into evidence, and it is what makes a warranty conversation short.
Recalibrate on the console first. Open System Settings, go to Controllers, and choose the option to calibrate the control sticks, then follow the prompts. Recalibration clears a surprising number of early complaints because it teaches the console where true centre now sits, and our guide to controller calibration explained covers why that works. If the drift comes back quickly after calibrating, that points at physical wear rather than a software offset, and it is worth contacting Nintendo while the controller is still covered.
For a closer look at a single stick on its own, our dedicated stick drift test goes further than the reading here, and the wider guide on controller stick drift explains what is happening inside the module.
The right Joy Con 2 has an optical sensor on the flat edge that lets you slide it across a desk like a mouse. It is the only genuinely new input on the whole system and it is the one thing about the Switch 2 controllers that nothing else does, so it deserves a test of its own. It also needs the most careful explanation, because what a web page can observe here is narrower than it looks.
A browser has no route to the raw optical sensor. What it can see is your system pointer. So if your operating system recognises the Joy Con 2 as a pointing device, sliding it on a desk moves your cursor, and this page can watch that cursor move and measure how far it travelled, how fast, and how smoothly. That is a real measurement of a real thing.
What it cannot do is prove which device moved the cursor. If your hand brushes a trackpad during the test, the page counts that too. So the mouse sensor mode is only meaningful if you take one precaution, which is to move nothing else. Take your hand off the mouse, keep clear of the trackpad, and slide only the Joy Con. The tool tells you what it saw and leaves the attribution to you, which is the honest way round rather than pretending to a certainty it does not have.
The other thing worth setting expectations about is support. On the console, mouse mode always works. On a computer it depends entirely on whether your operating system exposes the Joy Con 2 optical sensor as a pointing device, and that varies by system and by how up to date it is. A result of no pointer movement usually means your computer is not presenting the sensor rather than that the sensor is broken. If you want to check the pointer path itself in more depth once the cursor is moving, our mouse test is built for exactly that kind of tracking measurement.
One last note that saves confusion. The left Joy Con 2 has no optical sensor, and neither does the Pro Controller 2. If you are testing either of those, no pointer movement is the correct answer rather than a fault.
Worth its own section because it produces three separate results that look like faults and are not.
Only half the buttons appear. A left Joy Con has the directional buttons, its stick, L, ZL, minus, capture, and the two rail buttons. It does not have A, B, X, Y, and it never will, because those are physically on the other piece. A scorecard with half the rows empty on a single Joy Con is correct.
The stick may be rotated. A single Joy Con is designed to be held sideways for two player games, so the stick reports its axes relative to that sideways orientation. Push up and the tool may show the dot moving left or right. Nothing is broken. Use the stick orientation setting to rotate the reading a quarter turn and it will line up with what your thumb is doing.
Two Joy Con are two entries in the list. Each one pairs separately with its own identity, so the controller list at the top shows both and you test them one after the other. There is no browser level way to combine them, and any page that appears to do so is testing one of them and guessing about the other.
The rail buttons, the small SL and SR pair along the inside edge, are the ones people forget entirely. They only get used in sideways play, they take very little wear, and they are also the ones most likely to be missing from a mapping. If they never register here but everything else does, check with the button test before concluding anything, since a missing mapping and a dead button look identical from the outside.
Everything at once with nothing prompted. Press whatever you like and watch it light up. Inputs stay marked as seen once they have registered, so you can work through the controller at your own pace and see what is left.
The tool names each input in turn and waits for it, which stops you skipping the ones everybody forgets. On these controllers those are the stick clicks, the capture button and the rail buttons on a single Joy Con. If something genuinely will not respond, there is a button to record that rather than sitting there pressing forever.
Ten seconds with the controller flat and your hands off. It reports where each stick rests and how far it wandered while nothing was touching it. This is the measurement to save and repeat, for the reasons in the drift section above.
Roll each stick slowly around the outside of its gate a couple of times. The tool records how far it travelled in sixteen directions and draws the shape. A healthy stick reaches close to full travel all the way around. A short spot in one direction means the stick is not delivering everything the game expects there, and our circularity test goes deeper into what the shape itself tells you.
Ten seconds of watching your system pointer while you slide the right Joy Con 2 on a desk. Covered in full above, including why the result depends on you not touching anything else.
Two pulses, one on each side of the rumble, with a confirmation for each. Read the limits section before judging a poor result, because browser rumble on Nintendo hardware fails for reasons that usually have nothing to do with the controller.
How many of the inputs the tool saw, against how many that layout should have. A Pro Controller 2 has more than a single Joy Con, so the target changes with what you are holding. A low number after a casual live check usually means you did not press everything rather than that anything is wrong.
The larger of the two resting values while nothing is touching the sticks. Under 0.02 is ordinary sensor noise and every controller has some. Between 0.02 and 0.08 is mild drift, usually invisible in games because their own deadzone swallows it, but worth recording. Above 0.08 the stick is genuinely pulling and the movement is reaching your games.
How far the stick travelled in its weakest direction, on a scale where 1.00 is full travel. Above 0.95 is healthy. Between 0.85 and 0.95 is workable but measurably short. Below 0.85 means a meaningful part of your movement is missing in that direction, which shows up as a character that turns more slowly one way than the other.
Whether the page saw pointer movement during the window, and how far it travelled. Movement means your system is receiving pointing input while you slid the controller. No movement usually means your computer does not present the sensor as a pointing device, rather than that the sensor has failed.
Which of the two rumble channels you felt. Both is a working controller. Neither, on a Nintendo pad in a browser, is more often a support problem than a hardware one, so read the limits before acting on it.
| Reading | Healthy | Getting tired | Worth acting on |
|---|---|---|---|
| Stick resting value | under 0.02 | 0.02 to 0.08 | above 0.08 |
| Peak wander while resting | under 0.04 | 0.04 to 0.12 | above 0.12 |
| Shortest stick reach | above 0.95 | 0.85 to 0.95 | under 0.85 |
| Gap between the two sticks | under 0.03 | 0.03 to 0.06 | above 0.06 |
| Inputs registered | all for that layout | all with retries | any input unreachable |
| Double inputs on a button | zero | one across a session | two or more |
| ZL and ZR behaviour | jumps to full and back | not applicable | sticks on, or never reaches full |
Two pieces of context. The ZL and ZR row surprises people, so it is worth stating plainly that Nintendo shoulder inputs are on or off rather than pressure sensitive. A bar that leaps straight to full and straight back is correct behaviour and not a fault, which is the opposite of what you would want to see on an Xbox or PlayStation pad. And every figure here describes what arrives at your browser after the controller firmware and your operating system driver have both had a turn, so a comparison against your own earlier reading is worth far more than a comparison against this table.
Being straight about the gaps, because three of them come up constantly and one of them is genuinely unfixable.
The motion sensors. The gyroscope and accelerometer inside a Joy Con 2 or a Pro Controller 2 are not exposed to browsers at all. No web page can read tilt, rotation or shake from a controller, no matter how it is written. That is a limit of the interface rather than a fault in your hardware, and our gyro test explains where motion can and cannot be read.
The detailed rumble. A browser can send one simple rumble instruction with a strength number attached. The rich, textured effects the console produces travel a completely different route that a web page has no access to. So a rumble that feels basic and blunt here says nothing at all about how it feels on the console. For a fuller rumble check across any controller, our vibration test pushes the motors harder than this page does.
Battery level. Not exposed to browsers on any controller. Any page showing you a Switch controller battery percentage is inferring it rather than reading it. If your readings differ noticeably between a full charge and a nearly flat one, that is worth knowing, and the battery health test is the page for that side of things.
Which generation you are holding. Worth adding because it affects how you read your own results. Depending on your operating system and driver, a Joy Con 2 may present itself with the same generic identity as an original Joy Con. The tool takes its best guess and tells you how it got there, and the layout setting exists so you can correct it. Nobody can do better than that from inside a browser.
| What the tool shows | What is happening | What to do |
|---|---|---|
| A stick reports movement at rest | Drift. The sensor no longer reports true centre while nothing is touching it. | Recalibrate on the console through System Settings and Controllers. If it returns quickly, that is wear. |
| Drift appears immediately after pairing | Often a half finished connection rather than the stick. | Disconnect, reconnect, and measure again before assuming anything. |
| A stick is short in one direction | The module is not delivering full travel that way, or debris in the gate is stopping it early. | Blow compressed air around the stick base while working it through its range, then remeasure. |
| Half the buttons never register | Almost always a single Joy Con, which physically only has half of them. | Nothing. Check the layout line is showing a single Joy Con rather than a pair. |
| The stick moves the wrong way | A single Joy Con reporting its axes for sideways play. | Use the stick orientation setting to rotate the reading a quarter turn. |
| A button stays lit after release | Sticking contact, usually debris rather than failure. | Cleaning around the button edge frees most of these. |
| One press produces two inputs | A contact making and breaking on the way down, or a dome that has lost its snap. | Clean first. If it persists the membrane needs replacing. |
| No rumble at all | On Nintendo hardware in a browser this is very often a driver limitation rather than a dead motor. | Try a cable, try Chrome or Edge, and confirm it rumbles on the console before worrying. |
| No pointer movement in mouse mode | Your computer is probably not presenting the optical sensor as a pointing device. | Expected on many systems. It is not evidence that the sensor has failed. |
| Everything worse wirelessly than wired | The link rather than the controller. | Check it with the connection stability test and charge the controller fully. |
A light clean around the stick collar and under the button edges resolves a surprising share of sticking buttons and noisy sticks. Compressed air is the safest place to start, and it is worth doing before anything more involved. Our guide on cleaning or replacing stick sensors covers the procedure and where the risks are.
This is the part that differs from advice about older controllers. Switch 2 controllers are recent enough that most faults will still be inside a warranty period, and Nintendo has a track record of handling drift claims on Joy Con directly. Opening the controller yourself will end that cover. So on this hardware specifically, run the test, save the report, and talk to Nintendo before you reach for a screwdriver. The full guide on how to fix controller drift covers the repair route for when that is genuinely the right answer.
Sticks resting under 0.02, reaching past 0.95 in every direction, and every input registering is a healthy controller. A resting value of 0.01 is noise rather than early drift and there is nothing there to chase. And a ZL or ZR bar that jumps rather than slides is correct for this hardware rather than a fault.
Every number here describes what arrives at your browser, which has already passed through the controller firmware and your operating system driver. Both of those normalise and sometimes filter the values. That makes comparisons much more meaningful than absolutes. This controller against itself six months from now, or this controller against another one measured minutes later on the same computer, both mean something. A single figure on its own means less than it appears to.
Inputs are read in step with your display refresh, so a 60Hz screen gives about sixty looks a second. That is plenty for catching drift and missed presses. It is not precise enough to call anything here a timing measurement, and if you want to know how often the pad reports underneath that, the polling rate test shows it.
A dropped packet looks identical to a jumpy stick from up here. Where the controller allows a cable, take your reference measurement that way, and treat a wireless run as a measurement of the link as much as of the hardware.
Repeating it because it matters. The page watches the system pointer and cannot tell which device moved it. If you touch a trackpad during the window, the result is contaminated and the tool has no way to know. Move nothing but the Joy Con.
The single most useful thing you can do with this page on hardware this recent is run it while the controller still feels perfect and keep the report. Everything about diagnosing stick wear gets easier when there is an older reading sitting next to the new one.
Sign in to your account