01 / Live controller lab ๐ŸŽฎ

Controller Input Test

Full Controller Input Test for button-by-button and axis-by-axis inspection. Check buttons, D-pad, triggers, joystick axes, and raw browser values without downloading an app.

Use this page for a complete input audit. For a faster overview of the main signals, start with the Quick Controller Scan.

No controller connected Connect by USB or Bluetooth, then press any button.
Controller slot

LIVE SIGNAL MAP

Press any control to light the map

LOCAL ONLY
Active signal Live stick position Analog trigger value

AXES 0โ€“1

Left stick
0% range
X +0.00 Y +0.00

AXES 2โ€“3

Right stick
0% range
X +0.00 Y +0.00

ANALOG INPUT

Trigger travel
LT / RT
LT / L2 0.00
RT / R2 0.00
Button states See press and release signals as they happen.
Trigger range Watch analog pull depth from rest to full press.
Joystick axes Check both sticks, center return, and movement range.
D-pad input Verify directions and combined inputs without delay.
Show raw browser values

AXES

0 +0.00 1 +0.00 2 +0.00 3 +0.00

BUTTONS

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Browser-local Gamepad API No account ยท no upload ยท no install

How to Test Controller Input Online with Controller Input Test

A good online controller check starts with a live signal, not a guess. Connect your pad, wake it with one press, then use the map above to check each control. The tool reads the browser's Gamepad API in real time. It can show a pressed button, a trigger value, and the current path of each stick without asking you to install an app. That makes it useful after a new setup, after a cable swap, or when a game feels slow and you need to learn if the fault starts in the pad or in the game.

Controller Input Test checks at a glance

Start with a direct USB link when you can. A wired test removes one more variable from the chain. Bluetooth can work well too, but a low battery, a weak link, or a sleeping pad can hide an input for a few seconds. Keep the controller still while the page wakes. Then press one control at a time. A clear result has a simple shape: the matching button lights up, the value rises when a trigger is pulled, and the stick point moves in the same direction as your thumb.

  1. 1
    Connect the pad. Use USB or pair it by Bluetooth with your PC, Mac, tablet, or phone.
  2. 2
    Wake the input. Press a face button or Home if the browser still shows the waiting state.
  3. 3
    Check every button. Tap ABXY, shoulder keys, menus, stick clicks, D-pad directions, and Home.
  4. 4
    Move both sticks. Sweep up, down, left, right, and through both diagonals. Let each cap return to center.
  5. 5
    Pull both triggers. A trigger should move from 0.00 near rest to about 1.00 at full travel.
Quick read: a control passes when the right map item reacts at once, returns to rest, and does not fire while your hand is still. ๐ŸŽฎ

If one signal feels late, repeat the same check with another port and another browser. Watch the live value, not only the graphic. A button may light while a trigger stays near zero, or a stick may move but fail to settle at its center. Those details point to different fixes. Use the Stick Drift Test when the stick moves while you are not touching it. Use the Controller Mapping Test when a game sees the wrong index. For a wider axis view, the Joystick Tester can show every axis your device exposes.

What this Controller Input Test covers

This page checks the main signals that a standard gamepad sends to a browser. A digital button is either quiet or pressed. An analog input has a value between two limits, so it can show partial trigger travel or a stick that sits a little off center. Seeing those types together helps you tell a dead button from a value that is present but mapped in an unexpected place.

The controller drawing is a map, not a claim that every pad has the same shell. Xbox, PlayStation, Switch, arcade, and compact PC pads can use different names or layouts. The browser still reports a set of indexes. This tool keeps the common indexes in one view so you can tap through them fast. It also keeps the current stick values visible next to the art, which is helpful when a cap looks centered but its X or Y value is not near zero.

Signal groupWhat you can seeUseful clue
ButtonsPress state and live valueA missed light can point to a map or hardware fault.
TriggersTravel from 0.00 to 1.00A flat value can mean a stuck, blocked, or digital trigger.
SticksX, Y, center return, and rangeA resting value away from zero may show drift or poor calibration.
D-padFour directions and fast tapsOne missing direction can be a switch or mapping issue.

The current tab does not need to send a command back to a game. It reads what the browser already receives and paints the result. That makes this page a safe first pass before you change a profile. If you use a remap tool, close it for one run, since an overlay can change button order or hide a raw signal. Test the same pad in its normal mode and, when available, its XInput or DInput mode. Different modes can expose different button counts.

A short table cannot replace feel. A stick may report a neat center but still feel rough at the edge. A trigger may reach 1.00 yet have a broken spring on release. Use the visual state, the number, and the physical feel as three parts of one check. If a fault repeats across two browsers and two connection types, note the pattern before you adjust any game setting. That record makes the next fix much quicker.

Frequently Asked Questions about Controller Input Test

1

What does this controller input test check?

It reads standard browser gamepad data for buttons, triggers, D-pad directions, and four common stick axes. The live drawing gives you a quick visual check, while the small readouts show the values behind each movement.

2

Do I need to install a driver or app?

No extra app is needed for a browser that supports the Gamepad API. Connect the pad, open this page, and press one control to wake the browser. A driver may still be needed by your operating system for a very old or unusual device.

3

Will this work with Xbox, PlayStation, and third-party pads?

Most modern USB and Bluetooth pads work when the browser exposes them as a gamepad. Xbox pads often use the standard layout. PlayStation and third-party pads may report different labels, but their button indexes and live values can still be checked.

4

Does the page send my controller data anywhere?

No. The page reads input in the current tab and updates the screen in your browser. The tool does not need an account, a file upload, or a server request to display the readings. Closing the tab clears the live session.

5

Why is the tool still waiting after I plug in the pad?

Press a face button or the Home button once. Some browsers expose a gamepad only after the first user input. If the status stays idle, try a direct USB port, wake the pad, close a remap layer, and reload the page.

6

Why do my buttons look different from the drawing?

The drawing is a clear reference map, not a photo of every controller. A Switch pad, arcade stick, or compact third-party pad can place controls in a different spot. The API index and value still tell you which signal reached the browser.

7

What if one button never lights up?

Test that control more than once, then try a wired link and another browser. If the rest of the pad works, the cause may be a custom mapping, a missing standard index, or a hardware fault. Compare the result with the controller maker's own test page.

8

Can I use this page on a phone or tablet?

The layout adapts to small screens, but mobile Gamepad API support is less steady than desktop support. A phone may need a special cable, a paired pad, or a browser with a compatible input path. For a clear diagnosis, a desktop browser and a direct USB link are safer first steps.