DualSense Edge Controller Test | Sticks Stops And Mapping

The Edge is the only mainstream controller where you can pull the drifting stick out with your fingers and push a new one in, which changes what a test like this is even for. On any other pad, finding drift tells you whether to open the shell or buy a replacement. On this one it tells you which of two small cartridges to order for about the price of a game. So this page measures each stick module as its own thing, works out which one is actually the problem, and pays attention to the two features that quietly make every other reading wrong, which are the trigger stops and whichever custom profile you set up months ago and forgot about.

Test Your DualSense Edge

Results

Input Scorecard

Trigger Stops, Measured

Report

How To Run It Properly

1. Connect the controller with the braided USB C cable. The Edge works over Bluetooth too, but every reading here is steadier over a cable and the locking cable housing exists precisely because a wired connection is the serious option.
2. Press any button on it. Browsers keep gamepads hidden until they see one real input, so a controller you have not touched since plugging in looks like nothing at all.
3. Run the mapping check first, before anything else. It takes twenty seconds and it tells you whether a custom profile is reshaping your inputs. Skipping this step is the single easiest way to get a confusing result from every other mode.
4. Run the back button check next if you have the paddles or levers fitted. It tells you what each one is currently mapped to, which is genuinely useful information most Edge owners have forgotten.
5. Run the stick module reading with the controller flat on a table and both thumbs off it for the full fifteen seconds. This is the measurement that decides whether you order a replacement module.
6. Set both trigger locks to full travel, run the trigger stop mode, then repeat it at the middle position and again at the shortest. Three short runs and you get a real number for what each lock setting costs you.
7. Finish with the haptics mode, and read the section on what a browser can and cannot send before you judge a disappointing result.
8. Save the report. On this controller more than any other it is worth having, because a stick reading from six months ago is what turns a vague feeling into a decision about which module to replace.

If the controller never appears at all, that is a connection problem rather than a controller fault, and the controller checker is the fastest way to confirm whether the browser can see any device.

The Edge Is Three Controllers In One Shell

Testing an Edge is different from testing an ordinary pad, and it is worth understanding why before you read a single number.

A standard controller is one fixed configuration. What you measure is what it is. The Edge is deliberately not that. It has swappable stick modules, so the sticks you are measuring may not be the ones it shipped with. It has physical trigger stops, so the trigger travel you are measuring depends on where two small switches happen to be sitting. And it has onboard profiles, so the button mapping and the stick response curves you are measuring may have been changed by you, months ago, and stored inside the controller where nothing on screen reminds you about it.

That means three things can make a perfectly healthy Edge look faulty, and none of them are faults. A short trigger range is a lock position. A button reporting the wrong index is a profile. A stick behaving differently from its neighbour may simply be a newer module.

So the running order on this page is deliberate. Mapping first, because it invalidates everything else. Then back buttons, then sticks, then triggers. Work through it in that order and every number you get afterwards means what it appears to mean.

Check Your Profile Before You Check Anything Else

This is the single most useful thing on the page and it takes twenty seconds, so it goes first.

The Edge stores custom profiles on the controller itself. A profile can swap buttons around, change stick sensitivity curves, set its own deadzones, and adjust trigger ranges. All of that travels with the controller, which is the entire point of the feature, and it applies just as much on a computer as it does on a console.

The consequence is easy to miss. If a profile has cross and circle swapped, this page will show you pressing cross and lighting up circle, and you will reasonably conclude something is broken. If a profile has raised the stick deadzone, a drift reading comes back suspiciously perfect because the controller is hiding the drift before the value ever leaves it. If a profile narrowed the trigger output range, your trigger looks worn when it is doing exactly what you told it to.

The mapping check walks you through six inputs and reports which index each one actually fires. If everything lands where the standard layout says it should, you are on a clean profile and every other reading on this page can be trusted. If something lands elsewhere, the tool tells you what fired instead, and you can switch to the default profile with the function button before carrying on.

To get back to a clean state, hold the Fn button and pick the default profile. Then re measure. If you want to see the raw indices your controller is sending at any point, the controller mapping tool prints every one of them and the gamepad viewer shows them moving live while you switch profiles.

Why Back Buttons Are Invisible And What To Do About It

People expect the two rear inputs to show up as extra buttons and they do not. Understanding why makes them testable anyway.

The back buttons on the Edge are not separate inputs at the software level. The controller maps each one to an existing button and then sends that button when you press the paddle or lever. So when a browser receives a press, it receives a normal face or shoulder button and has no way of knowing whether a thumb or a rear paddle produced it. That is true of every rear button implementation on every controller, and it is not a limitation of this page.

What that gives you instead is a useful side effect. Press a back button, watch which input lights up, and you have just read out your own mapping. The back button mode does exactly that. It asks you to press each rear input in turn and reports what fired, so you end up with a plain statement of what your left and right paddles are currently doing.

That is genuinely worth knowing. Most Edge owners set up their paddles once, played for a few months, and can no longer remember what they assigned. And it is also a real test, because a paddle that fires nothing at all has either come loose in its slot or is unassigned in the current profile, and the tool distinguishes between those by telling you exactly what it saw.

One practical note. If a paddle fires the same button as one you can reach with your thumb, it is doing its job. If two paddles fire the same button as each other, that is almost always a profile you set up in a hurry rather than a fault.

Trigger Stops, And What Each One Costs You

The two small switches on the back of the Edge shorten how far L2 and R2 physically travel. Three positions, from full travel down to a very short click. Shooters benefit because a shorter pull means a faster shot. Anything analog suffers because you are compressing the range you use to modulate.

What almost nobody does is measure that trade rather than guess at it. That is what the trigger stop mode is for. You set both locks to a position, pull each trigger fully, and the tool records how far the reported value actually got. Then you move the locks and do it again. Three short runs and you have a real number for each setting on your specific controller.

The reason this is worth measuring rather than reading about is that the answer is not obvious in advance. A physical stop shortens the mechanical travel, but whether the reported value still climbs all the way to its maximum across that shorter distance, or simply stops early, depends on how the hardware and firmware handle it. Those two outcomes feel identical in the hand and are completely different in a game. If the value still reaches full, you have kept your range and merely compressed the distance. If it stops short, you have genuinely lost the top of your range and full throttle is no longer full.

Your table tells you which one your controller does. And it is worth checking rather than assuming, because it decides whether the short stop is a free win for shooters or a real cost in a racing game.

How To Read Your Three Rows

Look first at the value each position reached. Then look at the gap between positions. A shorter stop that still reaches full travel has cost you nothing in range and everything in fine control, because the same output now has to fit into less thumb movement. A shorter stop that reaches noticeably less than full has cost you both. Either way you now know, which beats guessing from a forum post about somebody else's controller.

If you want to go further into what a compressed trigger range does to modulation, the trigger pressure test measures analog travel in more detail, and the resistance side of these triggers belongs to the adaptive trigger test.

The Swappable Stick Module, Honestly Assessed

This is the Edge feature that gets both oversold and undersold, so here is a straight account.

The good part is real and significant. Stick drift is the single most common controller failure, and on almost every other pad fixing it means soldering or replacing the whole controller. On the Edge you pop the faceplate off, release a latch, pull the module out and push a new one in. No tools, no soldering, a couple of minutes. If one stick has drifted and the other is fine, you replace one small cartridge and the controller is as good as new.

The part that gets undersold is that this changes how you should test. Because the modules are independent and replaceable, comparing your two sticks against each other is far more informative than comparing either one against a general standard. Both sticks went through the same firmware, the same driver and the same cable. If one is resting at 0.005 and the other at 0.06, that difference is the module, and you know precisely which cartridge to order.

The part that gets oversold is the cost. Replacement modules are not cheap relative to the price of an ordinary controller, and the Edge itself is expensive to begin with. It is still far cheaper than replacing the whole thing, and far easier than a repair on any other pad, but it is not the free fix it sometimes gets described as.

Two more things worth knowing. A replacement module is not guaranteed to behave identically to the one it replaced, so if your numbers shift slightly after a swap that is the part rather than a problem. And a module that has just been fitted is worth measuring immediately, so you have a fresh baseline for it rather than carrying over the old one. For a deeper look at what your stick is doing once you have a suspicion, our stick drift test and stick jitter test cover the offset and the noise separately.

What Each Mode Checks

Live Check

Everything at once, nothing prompted. Press whatever you like and watch it light up, with both sticks on the crosshairs and both triggers filling their bars. Inputs stay marked as seen once they register, so you can work around the controller at your own pace.

Mapping Check

Six named inputs in turn, checking that each one fires the index the standard layout expects. This is the profile detector and it should be your first run every time.

Back Buttons

Press each rear input and the tool reports which button it currently duplicates. If nothing fires, it tells you that too, which separates an unassigned paddle from a loose one.

Stick Modules

Fifteen seconds with your hands off. It measures where each stick rests, how far it wandered, and how much the reading hisses while nothing is touching it. Then it compares the two modules and says which one, if either, is the candidate for replacement.

Trigger Stops

Pull both triggers fully at the lock position you have selected. Run it three times, once per position, and the results table builds up a picture of what each setting does to your range.

Haptics

Two rumble pulses with a confirmation for each, plus an attempt at the trigger motor command that Xbox controllers support so you can see it refused rather than wonder. Read the limits section before drawing conclusions, because a browser sends a much blunter instruction than the console does.

Reading Your Numbers

Button Mapping

Standard means every checked input fired where it should and the rest of the page can be trusted. Remapped means a profile is active and you should switch to the default before reading anything else, because a profile can change deadzones and trigger ranges as well as button positions.

Back Buttons

How many rear inputs produced a press, and what each one fired. Two is a fully assigned pair. One means the other is unassigned in this profile or not seated properly. Zero on a controller with paddles fitted is worth looking at physically.

Worst Stick Drift

The larger of the two resting values while nothing is touching the sticks. Under 0.02 is ordinary sensor noise that every analog stick has. Between 0.02 and 0.08 is mild and most games will hide it behind their own deadzone. Above 0.08 the stick is genuinely pulling and it is reaching your gameplay. On this controller that number maps directly onto a decision, which is whether to order a module.

Worst Stick Noise

How much the reading wobbles while the stick sits still, separate from where it sits. A stick can be perfectly centred and still hiss, which shows up in games as a crosshair that creeps during slow aiming. This is the measurement that catches a module going bad before the drift arrives.

Trigger Range

How far the reported value climbed at the lock position you tested. Compare the three rows rather than judging any one of them, because the whole point is the difference between settings on your controller.

Haptics

Which rumble channels you felt. Both is a working controller. Neither is worth investigating, though the limits section explains why a browser is a blunt instrument for this particular hardware.

What Counts As Normal

The row that matters most on this controller is the gap between the two modules. Every other figure here describes what arrives after the firmware and the driver have had their turn, so absolutes are soft. But both sticks travelled the identical path to reach your browser, which makes a difference between them the cleanest hardware signal you can get from a web page, and on the Edge it points straight at which cartridge to order.

What A Browser Cannot Reach On This Controller

The Edge has more features out of reach than most pads, so it is worth listing them plainly rather than letting you wonder.

Adaptive trigger resistance. The motors that push back against your finger are not vibration and there is no route to them from a web page. A browser can send a rumble instruction and nothing else. That means no page can test the resistance effects, and any that claims to is testing something else. Our adaptive trigger test goes into where the line sits.

The fine haptics. The Edge uses voice coil actuators rather than spinning weights, which is how the console produces sharp, textured effects. A browser can only send a simple strength number, which the controller translates into something its actuators can approximate. So a rumble that feels blunt here says very little about how it feels on a PlayStation. For a harder push on the motors themselves, the vibration test drives them further than this page does.

The touchpad surface. The click registers as an ordinary button and is tested here. Finger position is not part of the standard controller interface at all, so no page can read where your finger is on the pad without asking for a separate device permission.

The gyroscope. Motion sensing is not exposed to browsers on any controller. The gyro test explains where motion can and cannot be read.

Profile contents and battery level. A browser can detect the effect of a profile, which is what the mapping check does, but it cannot read the profile itself or tell you which slot is active. Battery level is not exposed either, so any page showing you an Edge battery percentage is inferring it. If the pack is your actual concern, the battery health test is the page for that.

The Failure Modes And What Each One Feels Like

Fixing It

Free Things Worth Trying First

• Switch to the default profile with the function button. On this controller that resolves more strange readings than any other single action.
• Set both trigger locks to full travel before judging trigger range.
• Reseat both stick modules. A module that is not fully latched produces intermittent readings that look like a failing sensor.
• Test with the cable rather than Bluetooth, so you know which one you are measuring.
• Close Steam and any vendor or remapping software, then reload. These commonly reshape inputs or take exclusive control of haptics.
• Charge the controller fully, since a tired pack affects both wireless stability and rumble strength.

Replacing A Stick Module

The genuine advantage of owning an Edge. Pull the faceplate off, release the latch on the module, lift it out, drop the new one in and close the latch. No tools and no soldering. Measure the new module immediately afterwards so you have a fresh baseline for it, since a replacement will not necessarily behave identically to the part it replaced.

Order one module rather than two unless both sticks are actually bad. The comparison in your results exists specifically to tell you which one, and replacing a healthy module because you were not sure is an expensive way to guess.

When The Module Is Not The Problem

If both sticks read poorly by the same amount, look at the profile and the connection before ordering anything, since a raised deadzone or a weak wireless link produces symmetrical results and worn modules almost never do. The general controller drift guide covers the causes that are not module related, most of which apply here too.

When To Leave It Alone

Both sticks resting under 0.02, quiet while still, triggers reaching full at the full travel lock, standard mapping and both paddles firing what you expect is a healthy Edge. A resting value of 0.01 is noise rather than early drift. And a short trigger range at the shortest lock position is the feature working, not the controller failing.

Method And Honest Limits

The Mapping Check Detects Effects, Not Profiles

The tool cannot read which profile is loaded or what is in it. What it can do is press six inputs and see whether they land where the standard layout says they should. That catches a remap reliably. It will not catch a profile that only changed a stick curve or a deadzone, because those change the shape of a value rather than which button it belongs to. So a standard mapping result means no remapping was detected rather than no profile is active.

Back Buttons Cannot Be Isolated

Repeating this because it is the most common misunderstanding. A browser receives the button a paddle is mapped to and has no way to know a paddle sent it. The back button mode works by asking you to press only the paddle and reporting what arrived, so the result is only as good as you following that instruction.

Trigger Stops Are Measured Through Two Layers

What you get is the value that reached the browser after the firmware and the driver both normalised it. That is the number your games get too, which makes it the useful one, but it means a short reading identifies a shortened chain rather than proving anything about the mechanism itself. Comparing your own three lock positions against each other removes that problem entirely, which is why the table is built that way.

Sampling

Inputs are read in step with your display refresh, so a 60Hz screen gives about sixty looks a second. Plenty for drift and mapping, not precise enough to call anything here a timing measurement. If you want to know how often the pad reports underneath that, the polling rate test shows it, and delay from press to response belongs to the latency test.

Measure Each Module When It Is New

More useful on this controller than on any other, because modules get replaced individually. A baseline recorded the day a module went in is what lets you judge it fairly a year later, rather than comparing a two year old stick against a two month old one and drawing the wrong conclusion.

Browser And Platform Notes

• Chrome and Edge give the most complete support. Firefox reads buttons and sticks fine. Safari is the least predictable of the three.
• Keep this tab focused. Background tabs get throttled and both input sampling and rumble stop.
• Use the cable for anything you plan to keep. Rumble support over Bluetooth varies more by browser version than it does over USB.
• Steam takes control of PlayStation controllers aggressively. If inputs look remapped and your profile is clean, close Steam before doing anything else.
• The controller may present a generic PlayStation identity rather than naming itself as an Edge, depending on your operating system. That is a driver behaviour rather than a fault.
• Onboard profiles apply on a computer exactly as they do on a console, so a remap you made for a console game will follow the controller here.
• Everything runs locally in the page. Nothing about your controller or your results leaves your device.

Questions People Actually Ask

Why do my buttons show up as the wrong ones?

Almost always a custom profile. The Edge stores remapping on the controller and applies it everywhere, including on a computer. Hold the function button, switch to the default profile, and run the mapping check again.

Why can the test not see my back buttons separately?

Because they are not separate inputs. Each rear button is mapped to an existing button and the controller sends that button when you press it, so a browser receives a normal press with no way to know a paddle produced it. The back button mode uses that to read out your mapping instead.

Which stick module should I replace?

The one with the worse reading, and the comparison in your results is built to answer exactly that. Since both sticks went through the same firmware and driver, a difference between them is genuinely about the hardware rather than anything in software.

My trigger only reaches part way. Is it worn?

Check the physical lock on the back first. The trigger stops shorten the travel deliberately, and a short reading at the middle or shortest position is the feature working rather than a fault. Set both locks to full travel and measure again.

Do the trigger stops reduce my analog range?

That is exactly what the trigger stop mode measures, and the answer is worth checking on your own controller rather than taking from a forum. Run it once at each of the three positions and the table shows you what each one reached.

Can this test the adaptive trigger resistance?

No, and neither can any other web page. The resistance motors are not vibration and there is no route to them from a browser. Only rumble can be sent, which is a different thing entirely.

Is a resting value of 0.01 drift?

No. Anything under 0.02 is ordinary sensor noise and every analog stick has some. Drift shows up as a steady offset that keeps the dot away from centre, or as movement in a game with your hands off the sticks.

My drift reading came back suspiciously perfect.

Check your profile. A raised deadzone stored in a profile hides drift before the value ever leaves the controller, which produces a flawless reading on a stick that is genuinely wandering. Switch to the default profile and measure again.

Is it worth buying replacement modules before I need them?

Only if availability worries you. Modules do not improve with age on a shelf, and measuring your sticks every few months tells you well in advance when one is heading downhill.

Both my sticks read badly. Do I need two modules?

Probably not. Two modules failing together and by the same amount is unlikely. A raised deadzone in a profile or a poor wireless link produces symmetrical results, so rule both of those out first.

Does the test work over Bluetooth?

Yes, though every reading is steadier over the cable and rumble support wirelessly varies by browser. Take your reference measurement wired and use a wireless run to see what the link is costing you.

Can it read my controller battery level?

No, and neither can any other web page. Battery level is not exposed to browsers on any controller.

A back button does nothing when I press it.

It is either unassigned in the current profile or not fully seated in its slot. Reseat it firmly first, since that is the quicker of the two to rule out, then check the assignment.

Should I test after swapping a module?

Yes, immediately. A replacement module will not necessarily behave identically to the one it replaced, so recording a fresh baseline the day it goes in is what makes every later reading meaningful.

How often should I run a DualSense Edge controller test?

Once when the controller is new, once whenever you fit a new module, and every few months after that. Stick wear is gradual enough that your expectations drift along with it, so the value is entirely in the comparison.