controllertest.io No paid content found Multilingual

You can test a controller online in your browser without downloading anything, as long as your browser supports the Gamepad API and your controller is connected by USB or Bluetooth. ControllerTest.io reads the raw hardware signal directly, so you can check button mapping, stick drift, trigger pressure, and vibration in one session. If the page shows "No Controller Detected," press any button on the controller once to wake the connection.

Before You Start

• Browser: Use a current version of Chrome, Edge, or Firefox. The Gamepad API is the mechanism that exposes controller input to the page.
• Connection: USB cable or Bluetooth both work. Wired is the better choice when you want to measure latency, since Bluetooth adds its own transmission delay.
• Controller: The site lists support for Xbox 360, Xbox One, PS3, PS4, PS5, Switch Pro, and other major controllers.
• Privacy: All input processing happens locally in the browser, so nothing is uploaded.

Step 1: Connect and Wake the Controller

1. Plug the controller in via USB, or pair it over Bluetooth through your operating system's settings.
2. Open the tester page.
3. If the visualizer stays idle, press any button on the controller. The site notes this explicitly: the browser may not respond until a button press activates the connection.

Expected result: The player indicator (P 1–P 4) lights up and the button/stick panels begin showing live values.

Common snag: A controller that is paired but idle can look disconnected. The button press is what triggers the Gamepad API to report it.

Step 2: Check Every Button and the ABXY Layout

Press each button one at a time and watch the visual interface. The tester highlights the button and prints "Button Pressed."

• Confirm that the physical button you pressed is the one that lights up. This is how you catch a mis-mapped ABXY layout, which is common with third-party or region-variant controllers.
• Work through the full set: face buttons, bumpers (LB/RB), triggers, D-pad, stick clicks, and any menu buttons.
• The raw data panel lists buttons as numbered indices (0–17), so you can cross-check anything the visualizer doesn't label.

Expected result: Every button registers on press and clears on release, with no button stuck "on."

Step 3: Test Stick Drift, Dead Zones, and Centering

This is the part that answers "do I need to clean or replace my sticks?"

1. Let go of both sticks completely. Do not rest a finger on them.
2. Read the Left Stick and Right Stick coordinates. At rest they should sit near +0.00, +0.00.
3. Watch the Err value. A persistent non-zero error while the stick is untouched indicates drift or a centering problem.
4. Move each stick in slow circles and watch the circularity and linearity readouts. A healthy stick traces a smooth, even circle; a worn one shows flat spots, jumps, or an offset center.

How to read the result:

The site frames this as static offset analysis, and it's the same signal you'd use to decide between cleaning the module and swapping the stick.

Step 4: Test Triggers and Vibration

Triggers: Press LT/L2 and RT/R2 gradually. The tester shows analog pressure on a 0–1 scale, so you can confirm the trigger ramps smoothly rather than jumping from 0 to 1. A trigger that only reads 0 or 1 has a failing analog sensor.

Vibration: Use the Dual Motor controls — HEAVY, LIGHT, BURST, and PULSE — to drive the left and right motors independently. If one side is silent or weak, that motor or its connection is the problem.

Expected result: Both motors respond, and each trigger produces a smooth pressure curve.

Step 5: Compare Polling Rate and Latency (Wired vs Bluetooth)

The tester measures your controller's actual polling rate and lets you compare input latency between wired and Bluetooth connections. Run the same test on both connections and compare:

• Higher polling rate + lower latency: better for competitive play.
• Noticeably worse numbers on Bluetooth: expected, and a reason to switch to USB if responsiveness matters to you.

This step is also a useful diagnostic — if latency spikes only on one connection, the issue is the link, not the controller.

What the Test Tells You

• All buttons map correctly, sticks center, triggers ramp, motors fire: the controller is healthy.
• Sticks drift but buttons are fine: cleaning or hall effect sticks are the likely fix.
• A single button or motor fails: that's a hardware fault, not a software one.
• Everything works but latency is poor on Bluetooth: use a cable.

Because the tool runs on the standard Gamepad API with no downloads, you can repeat the whole sequence after cleaning or repairing the controller and compare the numbers directly.

You can test a gamepad online without installing anything by connecting it over USB or Bluetooth and opening an HTML5 gamepad tester such as controllertest.io. The browser reads your controller through the native Gamepad API, so all input processing happens locally. This works for checking button presses, ABXY layout mapping, analog stick drift and deadzones, trigger pressure, dual-motor vibration, and polling rate. It applies to Xbox 360, Xbox One, PS3, PS4, PS5, Switch Pro, and similar controllers, and it's the right approach when you want a quick health check before deciding whether a controller needs cleaning, repair, or replacement.

Before You Start

• A controller with a working USB cable or a Bluetooth connection.
• A desktop or laptop browser that supports the Gamepad API (Chrome, Edge, and Firefox are the usual choices).
• No driver or software download is required for the test itself.

Step 1: Connect and Wake the Controller

1. Plug the controller in via USB, or pair it over Bluetooth through your operating system's Bluetooth settings.
2. Open the tester page.
3. Press any button on the controller. This is the step people most often skip. Browsers only expose a gamepad to the page after it receives an input event, so a connected-but-idle controller can still show as undetected.

Expected result: the on-screen visualizer switches from "No Controller Detected" to an active player slot (P1–P4) and starts showing live values.

Step 2: Verify Buttons and Layout Mapping

Press each button one at a time and watch the visual interface. Each press should light up the matching button, and the raw data panel should show the corresponding button index changing state.

Use this to confirm:

• Every face button, shoulder button, and stick click registers.
• The ABXY layout matches what you expect. If A and B or X and Y appear swapped, that's a mapping issue, not a dead button.
• No button is stuck on when you're not touching it.

Step 3: Check Analog Stick Drift and Deadzones

Leave both sticks completely untouched and read the stick values.

• A healthy stick at rest should sit near +0.00, +0.00 on both axes.
• A stick that reports a constant offset while untouched is drifting. The tester captures these micro-movements at rest and shows a static offset, which is the signal that you may need cleaning or hall effect sticks.
• Slowly push each stick in a full circle and watch the trace. This reveals deadzones (areas where movement isn't registered) and centering accuracy (whether the stick returns to zero when released).

Expected result: values return to roughly zero when you let go, and the circular trace is smooth rather than jumping or cutting off at the edges.

Step 4: Test Triggers

Squeeze each trigger gradually and watch the analog pressure readout, which runs from 0 to 1.

• LT/L2 and RT/R2 should climb smoothly from 0.00 to 1.00.
• A trigger that jumps straight to 1, sticks above 0 when released, or never reaches 1 has a sensor or mechanical problem.

Step 5: Test Vibration

Use the vibration test controls to fire the dual motors. The tester lets you drive the heavy and light motors independently, plus burst and pulse patterns.

Expected result: each motor produces a distinct rumble when triggered. If one side is silent or weak, the force feedback system has an issue on that motor.

Step 6: Measure Polling Rate and Latency

Run the polling rate measurement to see how often your controller reports input, then compare a wired connection against Bluetooth. Wired typically reports more frequently and with lower latency than Bluetooth, which matters if you're tuning for competitive play.

Troubleshooting "No Controller Detected"

What the Results Tell You

• Buttons all register, sticks center at zero, triggers sweep 0–1, both motors rumble: the controller is healthy.
• Sticks show a constant offset at rest: drift — clean the stick module or consider hall effect replacements.
• A button or trigger never registers or never returns to zero: likely a hardware fault worth repairing or replacing.
• High latency on Bluetooth vs wired: expected behavior, not a defect; switch to wired if it affects your play.

Because the test runs on the standard Gamepad API with all processing done locally in your browser, nothing about your input is sent anywhere, and there's no software to install or remove afterward.

You can run a full controller input test in your browser without installing anything: connect the controller by USB or Bluetooth, open an HTML5 gamepad tester such as controllertest.io, and press any button to wake the Gamepad API if the page shows "No Controller Detected." The test then reports button presses, analog stick position, trigger pressure, and vibration output, which is enough to judge whether a controller has drift, a dead button, or a failing rumble motor. This works with Xbox 360/One, PS3/PS4/PS5, Switch Pro, and other major controllers that expose a standard Gamepad API signal.

Before You Start

• A controller with a USB cable or Bluetooth connection
• A Chromium-based browser (Chrome, Edge) or Firefox — the Gamepad API is the underlying mechanism, so the tester reads hardware signals directly with no driver download
• The controller powered on and paired/plugged in

Step 1: Connect and Wake the Controller

1. Plug the controller in via USB, or pair it over Bluetooth through your OS settings.
2. Open the tester page.
3. If the visualizer still shows "No Controller Detected," press any button on the controller. Browsers only expose a gamepad to the page after a user gesture, so a button press is what triggers detection.

Expected result: the page switches from "Waiting for Input" to an active controller slot (P1–P4), and the button/axis readouts start updating.

Common snag: the controller appears in your OS but not in the browser. Re-press a button, refresh the page, and reconnect. Some controllers only register after the first input event.

Step 2: Test Buttons and Layout Mapping

Press each button one at a time and watch the visualizer.

• Each press should light the matching on-screen button and increment the "Button Pressed" indicator.
• Confirm the ABXY / face-button layout matches what you pressed — this catches swapped or mis-mapped buttons.
• Check shoulder buttons (LB/RB, L1/R1), stick clicks (L3/R3), D-pad directions, and Start/Select/Share.

Expected result: every button registers exactly once, with no ghost presses and no button that stays stuck on after release.

Common snag: a button that never lights usually means a worn contact or a broken trace; a button that stays lit after release points to a stuck membrane or debris.

Step 3: Read Analog Stick Values (Drift, Deadzone, Centering)

Leave both sticks untouched and read the live coordinates.

Then push each stick in a full circle and watch linearity, drift, and circularity:

• A clean circle with a small centering error (the "Err" value) means good calibration.
• A lopsided or squared-off circle indicates a worn or dirty potentiometer.

Expected result: sticks return to center on release and trace a smooth circle when rotated.

Common snag: a stick that reads fine but drifts only in-game is often a deadzone setting in the game, not the hardware — the tester's raw values tell you which.

Step 4: Check Trigger Pressure Range

Pull each trigger slowly from rest to fully pressed.

• The trigger readout should move smoothly from 0.00 to 1.00 (analog pressure, 0–1).
• A trigger that jumps straight to 1.00, or never reaches it, has a worn or miscalibrated sensor.

Expected result: a gradual, continuous value across the full pull on both LT/L2 and RT/R2.

Step 5: Test Dual-Motor Vibration

Use the vibration test controls (HEAVY, LIGHT, BURST, PULSE) to fire each motor independently.

• Heavy motor = low-frequency rumble (usually the larger weight)
• Light motor = high-frequency buzz (smaller weight)

Expected result: each motor produces a distinct, separate vibration. If one side is silent or weak, that motor or its wiring is failing.

Common snag: some controllers only rumble over certain connections — if vibration is dead over Bluetooth but works over USB, the issue is the connection, not the motor.

Step 6: Compare Wired vs Bluetooth Polling Rate and Latency

Run the polling rate / latency readout once over USB and once over Bluetooth.

• Higher polling rate and lower latency = more responsive input, which matters for competitive play.
• A large gap between wired and wireless tells you the wireless link is adding delay.

Expected result: wired typically shows a higher, steadier polling rate; Bluetooth may show more variance.

Deciding What to Do With the Results

FAQ

Do I need to download software? No — the tester runs on the browser's native Gamepad API, so no driver or app install is required.

Is my input data sent anywhere? On controllertest.io, all input processing happens locally in the browser, so the raw controller data stays on your machine.

My controller isn't detected at all — why? Press a button to trigger the Gamepad API, refresh the page, and confirm the controller is paired or plugged in at the OS level first.

Can I test any controller? Any controller that exposes a standard Gamepad API signal works, including Xbox, PS4/PS5, and Switch Pro.

You can test a joypad in your browser without installing anything: connect the controller by USB or Bluetooth, press any button to wake the browser's Gamepad API connection, then read the on-screen visualizer for button presses, analog stick values, trigger pressure, and vibration. This works with Xbox 360, Xbox One, PS3, PS4, PS5, Switch Pro, and other major controllers on controllertest.io, which runs entirely in the browser and processes input locally. The main condition is that your browser supports the Gamepad API and that the controller is paired or plugged in before you start pressing buttons.

Before You Start

• A controller with a working USB cable or a charged Bluetooth connection.
• A desktop or laptop browser (the Gamepad API is a browser feature, not a downloadable app).
• No driver installation is required, per the site's description of using the native Gamepad API.

Step 1: Connect and Wake the Controller

1. Plug the controller in via USB, or pair it over Bluetooth through your operating system's device settings.
2. Open the tester page.
3. Press any button on the controller. The page states that if the browser doesn't respond, pressing a button activates the connection. The visualizer shows "Waiting for Input" until a signal arrives, then displays the detected player slot (P1–P4).

Expected result: The controller appears as a connected player and the button/axis readouts stop showing "No Controller Detected."

Common snag: If nothing registers, the controller may be connected but idle — press a face button or a trigger rather than just moving a stick. Some controllers only report after a button event.

Step 2: Verify Buttons and Layout Mapping

Press each button one at a time and watch the visual interface. The tester highlights the pressed button and lists raw button indices (0–17 in the raw data panel).

• Confirm every face button, shoulder button, stick click, D-pad direction, and menu button registers.
• Check ABXY layout mapping: the visualizer shows which physical button maps to which label, which matters if you use a non-Xbox layout or a third-party pad.
• Use the raw button list to spot a button that never lights up — that points to a hardware fault rather than a mapping issue.

Step 3: Check Analog Stick Centering, Deadzones, and Drift

This is the part most people come for. The tester shows left and right stick coordinates (for example +0.00, +0.00) plus an error value.

1. Let go of both sticks and watch the resting values.
2. A healthy stick returns to near 0.00 on both axes. If it settles at a non-zero offset, that's static offset or drift.
3. Move each stick slowly in a full circle and watch the trace for linearity and circularity. A lopsided or clipped circle suggests a worn or dirty potentiometer.
4. Nudge the stick in tiny increments to find where output first changes — this reveals the deadzone size.

How to read it:

• Small resting offset that stays constant → likely static offset; the site notes this helps you decide between cleaning and hall effect sticks.
• Values that wander or jump while untouched → drift, often dust or wear in the stick module.
• A stick that won't reach full range → mechanical limit or calibration issue.

Step 4: Test Triggers

Triggers report analog pressure from 0 to 1 (shown as LT/L2 and RT/R2).

1. Squeeze each trigger slowly from rest to fully pressed.
2. Watch the value climb smoothly toward 1.00.
3. Release and confirm it returns to 0.00.

A trigger that jumps, sticks above 0 at rest, or never reaches 1.00 has a sensor or spring problem.

Step 5: Test Vibration (Dual Motor)

The tester offers independent left/right motor control with HEAVY, LIGHT, BURST, and PULSE patterns.

1. Trigger each motor separately.
2. Confirm you feel the heavy (low-frequency) and light (high-frequency) motors distinctly.
3. If one side is silent or weak, that motor or its connection is failing.

Note: vibration only works if your controller and connection support force feedback — some Bluetooth setups pass input but not rumble.

Step 6: Check Polling Rate and Latency (Optional)

The page includes a polling rate and latency readout so you can compare wired versus Bluetooth. Higher, steadier polling and lower latency favor competitive play; if Bluetooth shows noticeably worse numbers, that's your reason to switch to a cable.

Interpreting Results: What to Do Next

FAQ

Do I need to download software? No — the tester is browser-based and uses the native Gamepad API, so no driver download is required.

Is my input data sent anywhere? The site states all input processing happens locally in your browser.

Which controllers are supported? Xbox 360, Xbox One, PS3, PS4, PS5, Switch Pro, and other major controllers, per the site.

Why does nothing happen when I connect? Press a button to activate the connection — the browser often waits for an input event before reporting the device.

You can test a joystick online in your browser with no downloads by connecting your controller over USB or Bluetooth, pressing any button to wake the browser's Gamepad API, and reading the on-screen stick visualization. This works for Xbox, PS4/PS5, Switch Pro, and most other major controllers on a desktop or laptop browser. The test tells you three things: whether the stick returns to center, whether it drifts when untouched, and how much deadzone and linearity error it has. If you see movement while your hands are off the stick, you have drift — and the size and pattern of that movement tells you whether cleaning, calibration, or a stick replacement is the right next step.

What you need before you start

• A controller with an analog stick (Xbox 360/One, PS3/PS4/PS5, Switch Pro, or similar).
• A computer with a modern browser that supports the Gamepad API.
• A USB cable or a working Bluetooth connection.
• No software install — the tool runs on the browser's native Gamepad API and processes input locally.

Step-by-step: run the joystick test

1. Connect the controller

Plug in via USB or pair over Bluetooth. If the browser shows "No Controller Detected," press any button on the controller to activate the connection — the Gamepad API often stays dormant until the first input event.

2. Confirm the browser sees it

The visualizer should register the controller as a player slot (P1–P4). If nothing appears after pressing a button, try a different cable or re-pair Bluetooth before assuming the controller is broken.

3. Test the buttons first

Press each button in the visual interface and confirm the matching on-screen indicator lights up. This also verifies ABXY layout mapping, so you know the controller is reporting correctly before you judge the sticks.

4. Read the analog stick values

The tool shows live coordinates for the left and right stick, for example +0.00, +0.00, plus an error value (Err). With your hands off the stick:

• Centered and healthy: values sit at or very near 0.00, 0.00.
• Drifting: values wander away from zero on their own.

5. Watch for drift at rest

Leave the stick untouched and watch the numbers for 10–20 seconds. Any persistent non-zero reading is drift. Note whether it's a small static offset (a constant lean) or jittery movement (noisy signal) — the two point to different fixes.

6. Check deadzone and linearity

Move the stick slowly in a full circle and watch the visualization. The tool reports linearity, drift, and circularity, so you can see whether the stick reaches full range in every direction and whether the response is even or has flat spots near center.

7. Test the triggers and vibration

Triggers report analog pressure from 0 to 1, so you can confirm they ramp smoothly rather than jumping. Then run the vibration test — dual-motor control lets you fire the heavy and light motors independently (plus burst and pulse modes) to confirm force feedback still works.

8. Compare wired vs Bluetooth if latency matters

The tool measures polling rate and input latency, so you can compare a wired connection against Bluetooth. If you're chasing competitive responsiveness, this tells you which connection your setup actually delivers.

Reading the results: what each finding means

Deciding what to do about drift

Drift isn't automatically a death sentence for the controller. Use the size and character of the reading to choose:

• Clean first if the drift is small and jittery — dust or debris around the stick base is a common cause, and cleaning is free.
• Calibrate if the offset is constant and the stick otherwise tracks well — a static offset is often correctable in software.
• Replace the stick module if the stick can't reach full range, has dead spots, or drift returns immediately after cleaning. The tool itself notes that persistent drift helps you determine whether you need hall effect sticks, which don't wear out the same way potentiometer-based sticks do.
• Re-test after every change so you're comparing the same measurements, not guessing.

Common snags

• "No Controller Detected" won't clear: press a button on the controller; if that fails, swap the cable or re-pair Bluetooth.
• Wrong button mapping: the button test catches this — some third-party or remapped controllers report non-standard layouts.
• Values look frozen: make sure you're moving the correct stick and that the browser tab has focus.
• Bluetooth feels laggy: that's a real result, not a bug — compare against wired using the polling rate and latency readout.

Because the test runs on the standard Gamepad API and processes everything locally in your browser, your input data stays on your machine. That makes it a safe first stop before you spend money on repairs or a replacement controller.