Controller Touchpad Test | Surface Tracking And Click Check

The touchpad is the part of a PlayStation controller that nobody tests until something odd happens. It opens the map, it works as a mouse in Steam, it scrubs through menus, and in a handful of games it does something clever with a swipe. Then one day the top half stops clicking, or a strip across the middle stops tracking, and there is no obvious way to prove it. This page reads the two halves of the touchpad separately, because a touchpad is a sensing surface sitting on top of a single mechanical switch, and those two parts fail independently. You can have a perfect click on a dead surface, or a flawless surface on a switch that only responds at the bottom.

Test Your Controller Touchpad

Results

Signal Breakdown

Coverage By Region

Report

The CSV holds every touch reading with its timestamp and finger slot, which is what you want if you plan to plot the path yourself. The JSON holds the finished numbers.

How To Run It Properly

1. Plug the controller in with a USB cable. Everything here works over Bluetooth too, but a cable removes any doubt about whether a gap in the data came from the pad or from the radio link.
2. Press any button on the controller. Browsers keep gamepads hidden until they see one real input, so a pad that has not been touched since you plugged it in looks like nothing at all.
3. Run the click drill first. It needs no permission and it works in every browser that can see the controller. The tool names six spots on the pad in turn and waits for a click at each one.
4. Press Connect touch surface and pick your controller from the browser list. This is the step that unlocks finger position, and the section below explains exactly why it needs a separate permission.
5. Follow the short locate routine. Slide one finger slowly from the left edge to the right edge and back. The tool works out where the touch data sits in the report and locks onto it.
6. Run the surface map. Cover the whole pad in a slow snake pattern, edge to edge and corner to corner, until the coverage grid fills in. Twenty seconds is plenty at a sensible pace.
7. Run tracking quality with a single slow straight drag across the pad, three times. This is the mode that catches stutters that a coverage map completely misses.
8. Finish with the two finger mode. Rest two fingers on the pad, apart from each other, and check that both slots report their own position.

If the controller does not appear at all in step two, that is a connection problem rather than a touchpad problem, and the controller checker is the fastest way to confirm whether the browser can see the pad in the first place.

Why This Test Asks For A Permission

Worth explaining properly, because it is the single thing that makes this page different from every other touchpad tester, and because a permission prompt out of nowhere makes people suspicious for good reason.

Browsers read controllers through an interface that was designed around a fairly standard gamepad. Buttons, analog sticks, triggers, and a vibration motor. Everything on that list is exposed to any web page without asking you for anything. The touchpad click is on that list, because as far as the browser is concerned the click is just another button. So a page can count your touchpad clicks with no permission at all.

Finger position is not on that list. There is no place in the standard gamepad interface for a pair of touch coordinates, so no matter how carefully a page reads your controller through that route, the surface stays invisible. This is not a limitation somebody forgot to fix. The interface simply has no field for it.

The data does exist. It is sitting in the raw report your controller sends to the computer many times a second, a few dozen bytes along from the stick positions. Reading that raw report requires a different browser interface, one that hands a page direct access to a specific device, and direct device access is exactly the sort of thing a browser should ask you about first. So it does. You pick your controller from a list the browser controls, and the page can then read that one device and nothing else.

The practical consequence is worth stating plainly. Any touchpad tester that shows you finger movement without ever asking permission is not reading your controller touchpad. It is reading your system pointer, which is a different thing that happens to move when some setups let the touchpad act as a mouse. That measurement is real but it is measuring the software layer, not the pad.

What Happens To The Data

The permission covers reading input reports from the device you chose. Everything the tool does with those reports happens inside the page. Nothing is uploaded, nothing is stored between visits, and closing the tab ends the access. The exports are files your own browser writes when you ask for them.

How The Tool Finds Your Touch Data

Different controllers pack their raw reports differently, and the same controller packs it differently over a cable than over Bluetooth. Rather than assume a fixed position and fail silently on anything unusual, the tool searches for the data.

During the locate routine you slide one finger across the pad while the tool captures a few hundred raw reports. It then walks through every possible position in those reports and decodes each one as if touch data started there. Almost all of them produce nonsense: coordinates far outside any plausible range, values that leap by a thousand between one reading and the next, a contact flag that never changes. One position produces a number that starts low, climbs smoothly, and ends high, exactly matching the finger you just moved. That is the one it locks onto.

Two consequences worth knowing. The first is that the locate step genuinely needs you to move, so a still finger or no finger at all will fail, and the tool will say so rather than pretend. The second is that this approach is not limited to controllers anybody has written a profile for. If a pad reports touch in the common four byte format, the search finds it, whether or not the tool has ever seen that model before.

If the search comes back empty, the honest answer is usually that the device does not report touch coordinates at all, which covers every Xbox controller and every Nintendo controller, since neither platform has ever shipped a touchpad.

A Touchpad Is Two Devices Stacked

This is the mental model that makes every symptom on this page make sense, and almost nobody has it.

The top layer is a capacitive sensing surface. It has no moving parts. It detects the electrical presence of your finger across a grid and reports a coordinate. It fails through contamination, through damage to the sensing layer, or through a ribbon connector working loose. When it fails you get dead patches, jumpy tracking, or nothing at all, and none of that has anything to do with pressing.

Underneath it is a single mechanical switch. One switch, for the whole pad. The pad is hinged along its top edge and the switch sits under the bottom edge, which is why a click at the bottom of the pad feels crisp and a click at the top feels stiff and vague. You are working a lever, and the further up the pad you press, the worse your leverage is.

That geometry is the reason for the most common complaint on the entire component. As the switch wears or the hinge loosens, the bottom of the pad keeps clicking perfectly while the top stops registering. Nothing has gone wrong with the surface. Nothing has gone wrong with the electronics. You have simply run out of the leverage margin that was hiding the wear.

This is also why the click drill in this tool names six specific spots instead of just counting clicks. Counting clicks tells you the switch works. Clicking at the top left corner tells you whether it still works where it is hardest, which is where it fails first and where a general button test will never look, because to a button test the touchpad click is one button and one button either works or does not.

What Each Mode Catches

Click Drill

The tool names six positions in turn, from the easy bottom centre out to the awkward top corners, and waits for a click at each. If the surface is connected it also checks where you actually clicked, so a click recorded far from the target gets flagged. If a spot genuinely will not respond, press the button that says so and the tool records it as a failure rather than waiting forever. This is the mode that finds hinge and switch wear.

Surface Map

Sixty cells across the whole pad, filled in as your finger passes over them. Snake up and down or side to side until you have covered everything. A cell that stays empty after you have deliberately dragged through it is a dead patch in the sensing layer. This is the mode that finds contamination and sensor damage.

Tracking Quality

One slow straight drag, three times. The tool measures how often your controller reports, how large the steps between readings are, and whether the contact ever breaks in the middle of a drag that your finger never lifted from. This is the mode that finds the stutter people describe as the cursor sticking, and it is invisible on a coverage map because a stuttering pad still eventually covers every cell.

Two Finger

PlayStation touchpads track two fingers independently, with a separate slot for each. Rest two fingers on the pad, well apart, and the tool checks that both slots report and that they report different positions. A pad that only ever fills one slot cannot do pinch or two finger gestures, whatever the game claims to support.

Reading Your Numbers

Surface Coverage

How many of the sixty cells registered a touch. This number is only meaningful if you genuinely tried to cover everything, so it measures your thoroughness as much as the pad until you have swept properly. Once you have, an empty cell in the middle of a filled area is a real finding. Empty cells right at the outer border are usually normal, and the edge reach number below explains why.

Report Rate

How many times a second your controller sends a report while you are touching the pad. Over a cable this is usually high and very steady. Over Bluetooth it is lower and more variable. This is the ceiling on how smoothly anything can track, and it is the same underlying figure the polling rate test measures from the button and stick side.

Tracking Gaps

Two things counted together. A contact break is the pad reporting your finger as lifted for a moment during a drag you never interrupted. A jump is the reported position moving further between two consecutive readings than a finger physically could. Both feel identical in use, which is why they share a counter, but the fixes differ and the notes under your results tell you which one you have.

Click Reliability

How many of the six drill positions produced a click. Six out of six is a healthy switch and a healthy hinge. Anything less, and which positions failed matters far more than how many, because failures clustered at the top are the classic wear pattern while a failure at the bottom centre points at the switch itself.

Fingers At Once

The highest number of separate contacts reported simultaneously. Two is correct on a PlayStation touchpad. One means either you never put two fingers down or the second slot is not reporting.

Edge Reach

How much of the full coordinate range your readings actually spanned. A touchpad has a small border where the sensing grid stops before the plastic does, so nobody reaches a perfect hundred percent. Values in the nineties are normal. A noticeably low number on one axis means the sensing layer is not reading near one edge, which shows up in use as a swipe that stops responding just before you finish it.

What Counts As Normal

Two pieces of context. Report rate figures vary a lot between controllers and between operating systems, so treat the bands as a starting point and trust a comparison against your own earlier reading far more than against the table. And a single tracking gap in a fast drag is usually you moving faster than the pad reports rather than a fault, which is exactly why the tracking mode asks for a slow one.

The Failure Modes And What Each One Feels Like

Why Touchpads Fail

The Switch Is A Consumable

It is one small tactile switch rated for a finite number of presses, and on a controller used for years it will get a lot of them. This is ordinary wear rather than a defect, and it is the single most common touchpad fault by a wide margin.

Skin Oil On The Surface

A capacitive sensor reads the electrical presence of your finger, and a film of oil and grime sitting between the two makes that reading less reliable. This is why the first thing to try on a patchy surface is a proper clean, and why it works more often than people expect.

Liquid

A touchpad is a wide flat surface sitting on the top face of the controller, which makes it the first thing a spilled drink reaches. Liquid under the sensing layer leaves permanent dead patches, and the coverage map is the clearest way to see the shape of the damage.

The Ribbon Connector

The touchpad board connects to the main board with a fine ribbon cable in a small clip. That connection loosens over time, and it loosens faster on a controller that has been dropped or opened before. It produces intermittent faults rather than dead ones, which is why it usually shows up as tracking gaps rather than as missing coverage.

Previous Repairs

Worth mentioning because it is easy to miss. If your touchpad started misbehaving right after a stick replacement or a shell swap, the ribbon connector is almost certainly the cause, since it sits right where your hands were and it is easy to knock loose or seat badly on the way back together. That is good news, because it is the easiest fault on this list to fix.

Fixing It

Free Things Worth Trying First

• Clean the surface with a slightly damp cloth and let it dry fully. Not a wipe with your sleeve, an actual clean. This alone fixes a surprising share of patchy tracking.
• Test over a cable rather than Bluetooth and compare. If the gaps disappear, the pad was never the problem.
• Close anything sitting between the controller and the browser. Steam Input in particular takes the touchpad over and turns it into a mouse, which changes what everything downstream sees.
• Try the click at the very bottom edge of the pad. If that works and the top does not, you have your answer without opening anything.

Reseating The Ribbon

If tracking gaps are your main symptom, this is the fix worth attempting. Open the controller, find the small ribbon running to the touchpad board, release the retaining clip, reseat the ribbon squarely and close the clip again. It requires no soldering and no parts. The teardown steps and the safety notes in the controller repair guide cover the same disassembly, since getting to the touchpad means the same shell removal as getting to a stick.

Replacing The Switch

The real fix for a worn click. The switch is a common part, it costs very little, and the job is two solder joints. It is a step up from reseating a ribbon but it is well within reach if you have soldered anything before. If you have not, this is a reasonable first project because there is very little around it to damage.

When To Leave It Alone

A pad that clicks everywhere, covers the full surface, and drags without gaps is healthy, and chasing the last few percent of edge reach is not worth opening a controller for. Equally, if the click works fine at the bottom and you only ever press it there, a top corner that has gone stiff is an annoyance rather than a fault, and it is entirely reasonable to note it and carry on.

What The Touchpad Actually Does In Games

Worth knowing before you decide how much a fault matters, because the answer varies enormously by what you play.

As a button. The overwhelming majority of use. Map screen, inventory, scoreboard, journal. Only the click matters here, and only at wherever your thumb naturally lands, which is usually the middle or the bottom. A dead top corner will never once come up.

As a mouse in Steam. Steam turns the touchpad into a pointer, and here the surface matters completely. Dead patches make the cursor stall. Tracking gaps make it jitter. If you use your controller to navigate a desktop or a launcher, a surface fault is a daily irritation rather than an occasional one.

As a gesture surface. A small number of games read swipes and a smaller number read two fingers. When these break, the game usually gives you no feedback at all, so a gesture that silently never fires is easy to blame on yourself.

As a wheel or a slider. A handful of racing and simulation titles map a drag along the pad to a continuous value. This is the use that is most sensitive to tracking gaps, because a gap in the middle of a drag reads as a sudden jump in the value rather than as a pause.

If your complaint is that inputs feel unreliable in general rather than specifically on the touchpad, the pad may not be the culprit. The full controller tester covers every input in one pass and is a faster way to find out where the problem actually lives.

Method And Honest Limits

The Click And The Surface Come From Different Places

The click is read through the standard gamepad interface and the surface is read from the raw device report. They are two separate streams arriving by two separate routes, and the tool lines them up by timestamp rather than by anything the controller guarantees. Click positions are therefore accurate to within one report, which at normal report rates is a few milliseconds and a few pixels of finger travel. Good enough to tell a top corner from a bottom corner, not good enough to call it precision.

Coordinates Are Raw

The numbers the pad reports are its own, in its own units, and this page does not rescale them into anything else. The advantage is that nothing is being smoothed or filtered on the way to you. The cost is that the absolute numbers only mean something relative to that model of controller, so compare your pad against itself over time rather than against somebody else's screenshot.

Report Rate Is Measured At The Browser

The rate shown here is how often reports arrive at this page, which is a fair reflection of the link and the device but is not a measurement taken at the controller. If a browser is busy, some of that shows up here. Keep the tab focused and close heavy work in other tabs before you take a reading you plan to keep.

Coverage Depends On You

The tool cannot tell the difference between a cell you never touched and a cell that failed to register. It can only report what came back. So sweep deliberately, and read a low coverage number as a prompt to sweep again before treating it as a fault.

Run It Twice

Intermittent faults are the ones that get dismissed by support, and one clean run does not disprove a fault you have felt for weeks. Two runs that agree are worth far more than one, and a run saved today next to a run from six months ago is worth more still.

Browser And Platform Notes

• Chrome and Edge support both halves of this test. Firefox and Safari can read the touchpad click through the standard gamepad interface but cannot read the surface, so the surface modes will tell you plainly that they are unavailable rather than failing quietly.
• The page must be served over a secure connection for the surface permission to be offered at all.
• On some setups the controller is claimed by other software before the browser sees it. Steam is the usual culprit. Close it, or turn off its controller support, and reconnect.
• A wired connection reports faster and more evenly than Bluetooth on every controller tested, so take your baseline measurement wired.
• Xbox and Nintendo controllers have no touchpad, so the click drill will find no button and the locate routine will find no touch data. That is expected rather than a fault.
• If the click button index does not match, press Learn and click the pad once. If you want to see every index your pad sends, the controller mapping tool prints them and the gamepad viewer shows them moving live.
• Everything runs locally in the page. Nothing about your controller or your results leaves your device.

Questions People Actually Ask

Why does the surface test need permission when the click test does not?

Because they use different routes. The click arrives through the standard gamepad interface, which every page can read. Finger position is not part of that interface at all, so reading it means direct access to the device, and browsers ask before granting that.

My touchpad clicks at the bottom but not at the top. Is it broken?

It is worn rather than broken. The pad is hinged at the top and the switch sits under the bottom edge, so pressing at the top gives you the worst leverage. That is where wear shows first, and it is a switch replacement rather than anything you can fix in software.

Can I test the touchpad on an Xbox or Switch controller?

There is nothing to test. Neither platform has ever shipped a controller with a touchpad. If you are checking a general input problem on one of those pads, the controller tester covers what they do have.

Does this work over Bluetooth?

Yes, both halves work wirelessly. The report rate will be lower and less even than over a cable, so take your reference measurement wired and use the wireless run to see what the link is costing you.

The coverage map has holes but I definitely swiped there.

Then you have found a dead patch. Clean the surface properly and run it again, since a film of oil is a genuine cause. If the same cells stay empty after a clean, the sensing layer is damaged in that spot.

What is a tracking gap exactly?

Either the pad reporting your finger as lifted during a drag you never interrupted, or the position leaping further between two readings than a finger could physically move. Both feel like the cursor sticking, and both usually point at the ribbon connector rather than the pad surface.

Why does my report rate look low?

Bluetooth, a busy browser tab, or a controller that simply reports less often than average. Test wired with other tabs closed before drawing a conclusion, and compare against the polling rate test which measures the same thing from the button side.

Two fingers only register as one.

Put them further apart and try again. Contacts close together read as a single larger contact on most capacitive surfaces, which is normal behaviour rather than a fault.

Is this different from a laptop trackpad test?

Completely. A laptop trackpad is a system pointer device and a browser reads it as mouse movement. This reads the controller's own raw touch report, which is why it needs a permission and why it can show you two separate fingers rather than one cursor.

Steam is doing something to my touchpad. Does that matter?

Yes. Steam Input takes the touchpad over and remaps it, usually into a mouse, which changes what everything downstream sees. Close Steam or turn off its controller support before measuring.

Can I use this to prove a fault for a warranty claim?

The report is designed for exactly that. It names the controller, lists which click positions failed, gives coverage and gap figures, and timestamps everything. Run it twice on separate days and attach both, since an intermittent fault documented once is easy to dismiss.

Will cleaning actually fix anything?

For patchy surface tracking, often yes, because a capacitive sensor is reading through whatever is sitting on top of it. For a click that has stopped working, no. Those are two different parts and only one of them cares about a clean surface.

The tool could not find my touch data.

Run the locate routine again and slide one finger slowly and deliberately from one edge to the other. It needs real movement to work. If it fails a second time on a controller that definitely has a touchpad, try a cable rather than Bluetooth, since the report layout differs between the two.

Does any of this leave my computer?

No. Every reading is processed inside the page, nothing is uploaded, and the permission ends when you close the tab. The export files are written by your own browser only when you ask for them.

How often should I run a controller touchpad test?

Once when the controller is new so you have a baseline, then any time the click starts feeling stiff or the cursor starts sticking. Click wear is gradual, so a reading from six months ago is what turns today's reading into evidence.

Related Tests On Gpadtester

This page covers the pad on the top face. These cover everything around it, and two pages agreeing on a fault is far stronger than one page suggesting it.

Buttons And Surfaces

Analog Sticks

Whole Controller And Connection

Read Next

How to fix controller drift covers the teardown, the safety notes and the part replacement steps. The same disassembly gets you to the touchpad ribbon and the click switch.

Other Hardware

Away from the controller: keyboard test, mouse test, mic test, frame rate test and refresh rate test.