Connect a DualShock 4 and this page reads every input your browser can see, using the labels actually printed on the controller rather than generic button numbers. Both sticks, the analog travel on L2 and R2, all four face buttons, the D-pad, the touchpad click, Share, Options and PS, plus a rumble test for both motors. It also tells you plainly which parts of a DS4 a browser cannot reach, because the gyro, the touchpad surface, the light bar and the battery level are not part of the standard gamepad interface and any page claiming otherwise is guessing.
Every input turns green once the browser has seen it move. Anything still grey at the end is either broken or mapped somewhere unexpected.
If a button never lights up, that is not always a fault. Try a cable instead of Bluetooth first, and check the raw indices with the controller mapping tool, because DualShock 4 mapping shifts between operating systems more than most pads.
This is worth setting out before anything else, because the DualShock 4 has more hardware in it than the standard gamepad interface exposes, and plenty of pages quietly pretend otherwise.
None of that means your controller is faulty if this page cannot show it. It means the browser has no route to it. Worth knowing before you conclude your gyro is dead.
There are two versions and telling them apart takes two seconds. Look at the top edge of the touchpad. If there is a thin strip of the light bar glowing through the plastic, you have the second version, model number CUH-ZCT2, sold from late 2016 onward. If the touchpad is solid with no light showing through, you have the original CUH-ZCT1 from the 2013 launch.
The model number is also printed on the label on the back, under the shoulder buttons.
Why it matters for testing. The second version has a slightly larger battery, which affects how long it holds a charge before the pack itself becomes the problem. The first version is now over a decade old, so anything you buy used at this point has almost certainly had its sticks worn in by somebody. And the rubber on the original version's stick caps and grips is the part that has aged worst, which is a physical inspection rather than anything a test page can measure.
Neither version behaves differently as far as the browser is concerned. The buttons, the sticks and the triggers report identically.
After more than a decade in circulation, DualShock 4 failures are well documented and they cluster into a short list. Here is what each one looks like in this test.
The sticks report movement when nobody is touching them. On this page it shows in the two rest readings under the controller. Anything past about 0.08 is worth acting on. The DualShock 4 uses contact based potentiometers, they wear, and after three or four years of regular use a large share of them develop some drift. It is common enough that it has been the subject of consumer complaints and legal action in several countries.
If your rest readings look bad, the stick drift test measures it properly and turns the number into a starting deadzone, and the controller drift repair guide covers cleaning and module replacement.
This is the DualShock 4 fault that surprises people, because it is mechanical rather than electrical. Inside each shoulder button is a small plastic tab that transfers your press onto the switch on the board. That tab snaps. When it does, the button either feels mushy and spongy or stops registering entirely, while every other input on the controller keeps working perfectly.
On this page it shows as L1 or R1 never turning green while everything around them does. There is no software fix. The tab is a physical part and it needs replacing, though the part itself is cheap and the repair does not require soldering.
The textured rubber on the thumbsticks wears smooth and eventually splits, exposing the plastic underneath. This does not affect any reading on this page at all, which is exactly why it is worth mentioning. It is a comfort and grip problem, it makes precise movement harder, and replacement caps cost almost nothing.
The small springs that return the triggers lose tension or break outright. The symptom is a trigger that feels loose, rattles, or does not spring back cleanly. On this page it shows in the trigger meters as a resting value that does not sit at zero, or as travel that does not reach the top. If the meters look wrong, the trigger pressure test goes deeper into analog travel, dead zones and uneven range.
The port is soldered to the board and it takes the strain every time somebody yanks a cable or plays while charging. A wobbly connection, charging that only works at a certain angle, or a port that has stopped working entirely is a common end of life for a DualShock 4. If the pad works over Bluetooth but not wired, this is almost always why.
Nineteen inputs get tracked. Everything green means every button and axis the browser can see is registering. Something still grey at the end means one of three things. The input is genuinely broken. It is mapped to a different index than expected, which happens on some Bluetooth setups. Or you simply have not pressed it yet.
Where each stick sits when you let go. Under 0.02 is clean. Between 0.02 and 0.08 is minor and usually invisible behind a normal deadzone. Past 0.08 is drift you will notice in games with a tight deadzone, and it tends to get worse rather than settle.
The lowest and highest values L2 and R2 reported. A healthy trigger rests at 0.00 and reaches 1.00. A trigger resting at 0.06 is not returning fully. A trigger topping out at 0.92 is not travelling fully. Either one points at the spring or at debris in the mechanism.
Whether the browser could send a vibration effect and whether you felt it. This one needs your judgement, because the tool can only report that it sent the instruction. If nothing happened, try a cable, since rumble over Bluetooth is inconsistent across browsers. The vibration test drives the motors through patterns and intensities if you want to check each one separately.
Plug it in with a micro USB cable that carries data rather than power only. This is the most reliable route and the one to use for any measurement you plan to keep, because it removes the wireless link from the equation entirely. If the pad charges but nothing appears, the cable is a charge only cable, which is a very common false alarm.
With the controller off, hold Share and the PS button together for about five seconds until the light bar starts double flashing. It will then appear in your Bluetooth device list as a wireless controller. Pairing is straightforward, but expect slightly less consistent reporting than a cable gives you, and expect rumble support to vary by browser.
Both sit between the controller and everything else, and both can change what a browser receives. Steam Input in particular can present the DualShock 4 as a completely different device. For an honest test, close them and test the pad on its own first, then turn them back on if you want to see what they are doing. The gamepad viewer makes that comparison easy because you can watch the values change as you toggle a setting.
Work through it in this order. Press a button on the pad. Try a different cable. Try a different port. Try a different browser, since Chrome and Edge are the most consistent. Then confirm whether the browser can see the device at all with the controller checker before assuming the controller is dead.
This page is a broad check. It tells you which input is misbehaving rather than exactly how, so here is where each result leads.
A stick that rests off zero goes to the stick drift test for the measurement and the joystick deadzone test for the setting that hides it.
A stick that will not reach the edges goes to the analog stick range test, which measures how far it travels in each direction and how evenly the two ends of each axis match.
A stick that feels rough or uneven when you roll it goes to the circularity test, which draws the actual shape your stick traces at full travel.
A stick that jumps or wanders while you hold it still goes to the stick jitter test, and one that flicks the wrong way when you let go goes to the snapback test.
A D-pad that misses diagonals or drops inputs mid roll goes to the D-pad test, which tests the cross the way a rocker actually gets used rather than one direction at a time.
Inputs that feel late rather than wrong belong to the latency test and the polling rate test, and inputs that drop out only over Bluetooth belong to the connection stability test.
For a general sweep across any controller rather than a DualShock 4 specifically, the controller tester and the button test cover the same ground with generic labels.
Honest answer, and it depends on which fault you have.
Worth fixing. Shoulder button tabs, stick caps and trigger springs are cheap parts, need no soldering, and the repair takes under an hour with a screwdriver and some patience. A drifting stick module is a soldering job, so it is worth it if you already own an iron or know somebody who does.
Think harder. A broken USB port means removing the board and doing fine soldering on a connector that takes mechanical stress. Possible, but it is the repair most likely to end in a controller that is worse than when you started.
Probably not. Multiple faults on an original 2013 model. At that point you are rebuilding a pad that is worth less than the parts and the afternoon.
One thing worth doing either way. If you are buying a used DualShock 4, run this page on it before money changes hands. Rest readings on both sticks and a full press of every button takes about ninety seconds, and it catches exactly the faults a seller is least likely to mention.
The button numbering used here is the standard gamepad mapping, which is what Chrome and Edge use for a DualShock 4 over a cable on most systems. Bluetooth on some operating systems, and older browsers, can present a different layout, which is why the mapping status is shown in the controls panel. If it does not say standard, treat the labels on the diagram as a best guess rather than a fact.
Inputs are read in step with your display refresh, so a 60Hz screen means one look every sixteen milliseconds or so. That is fine for confirming a button works and for reading a resting stick. It is not precise enough to call anything a timing measurement.
On most setups the touchpad click arrives as an extra button beyond the standard sixteen. On some it does not appear at all. If your touchpad panel stays grey but the click feels normal, that is a mapping limitation rather than a fault.
Vibration works most reliably over a cable in Chrome and Edge. Over Bluetooth, and in other browsers, it is inconsistent. A silent motor here does not prove a dead motor.
Sign in to your account