Joystick Tester

05 / Start with the signal 🎮

Free Online Joystick Tester

A Joystick Tester reads the input that your browser can see from a USB or Bluetooth device. It shows live stick movement, button changes, and every axis exposed by the Gamepad API. That makes it useful for a small console pad, a flight stick, a HOTAS rig, or a wheel with pedals. You can check a new device before a game session, or compare a worn control with a spare. Nothing needs to be installed. The page reads data in the current tab and keeps the result on your screen.

The first view gives you a clear connection state. With no pad present, the trace area stays quiet and the data panels say that they are waiting. Press a button once after you connect a device. Many browsers wait for a real user action before they expose a gamepad. Once the pad appears, the tool shows its name, button count, axis count, and current values. Those counts can differ from one driver to the next, so the page does not force every device into one fixed console layout.

What the Joystick Tester Shows

The main plots turn the first two axis pairs into a quick visual read. The primary plot uses axes 0 and 1. A second plot uses axes 2 and 3 when they exist. A moving point marks the current position, while the path keeps recent movement in view. Beside the plots, the Button Matrix uses the real index sent by the device. Raw Axis Data lists extra inputs such as a throttle, rudder, or pedal. An event log adds a short record when a button or axis changes by a clear amount.

This setup helps with fast checks. A button cell should light and change state when you press it. An axis bar should move in the same direction as your control. A stick that rests near the center should not draw a steady path while your hand is away. For a deeper center check, use the Stick Drift Test. For a shape check, continue with the Circularity Error Test.

“A live input map tells you what the game will receive, not what the label on the shell promises.”

06 / A calm first pass

How to Use the Joystick Tester

You can run a useful Joystick Tester check in a few minutes. Connect the device, wake the input, and move each control in a slow and repeatable way. A calm pass gives the browser time to catch small changes. It also makes the trace easier to compare with a second run.

1. Connect the device. Plug in over USB, or pair it over Bluetooth. Close another page that may be reading the same controller.
2. Wake the signal. Press a face button or move one stick. Wait for the status badge to change from No Controller.
3. Read the map. Press each button once. Watch the matrix and the event log. Note any button that stays dark or reports twice.
4. Move the sticks. Sweep left, right, up, and down. Then draw a slow circle near the outer stop without forcing the cap.
5. Check the rest point. Let the stick go. The pointer should return near the center and stop sending large changes.
6. Repeat the pass. Run the same motion again. A repeat pattern is more useful than one rushed or uneven sweep.

Do not judge a device from one hard flick. A fast motion can skip a part of the rim, while a light grip can stop short on one side. Keep your hand in a similar place for each run. If the trace looks different each time, slow down before you blame the hardware. If the same gap or center shift returns, save a note with the device name and connection type. That note can help when you adjust an in-game deadzone or speak with a repair shop.

A browser page can report input, but it cannot repair a worn module. Use the values as a guide. If your game still feels wrong after the page shows a stable path, check its own deadzone, sensitivity, and button map. Games can remap or filter values after the browser sees them.

07 / Built for many rigs

Works With All Your Devices

The Gamepad API uses a common browser view of controller input. That lets one Joystick Tester page serve many types of hardware. A standard pad may show four axes and a familiar set of buttons. A flight setup can expose several sticks, a throttle, a twist control, and a large button bank. The page keeps the full list rather than hiding inputs that do not fit a console shell.

Compatibility still depends on the browser and operating system. Chrome and Edge tend to offer broad Gamepad API support. Firefox can work well, though a driver or permission setting may change what appears. The page does not need a download or a plug-in. If a device stays missing, press a button, reconnect it, and check whether the operating system sees it first. You can read the browser API details in the MDN Gamepad API guide.

08 / Find the quiet zone

Joystick Deadzone Test

A deadzone is the part of a stick’s travel that produces little or no visible input. The inner deadzone sits near the center. The outer deadzone sits near the edge when the cap cannot reach the full output range. A Joystick Tester can help you estimate both zones from the values on screen, but the Gamepad API does not reveal the exact firmware setting used by a device.

To check the inner zone, let the stick rest, then move it by tiny amounts. Watch the X and Y numbers. The distance from center to the first steady change is your rough inner estimate. Test more than one direction. Wear can make the quiet zone wider on the left than on the right. A software deadzone may also hide small movement, so compare the page with the raw device settings if your driver offers them.

1. Return the stick to its natural center.
2. Move slowly along one axis until a stable change appears.
3. Repeat near the four main directions.
4. Push to the edge and check whether output reaches full scale.
5. Repeat after reconnecting if the result looks uneven.

Outer deadzone needs a different look. Push the stick to its maximum on the X axis, then the Y axis, then the corners. If the value stops well below the expected limit, the device may have a short outer range. A shell edge, a gate shape, a worn sensor, or a driver scale can cause that gap. Ease inward and see whether the value drops at once or fades over a wider span. That shape can tell you whether the limit is sharp or gradual.

A deadzone setting can hide mild drift, but it cannot restore lost range. If the center is noisy, visit the Stick Drift Test. If the edge is uneven, compare a slow path in the Circularity Error Test. Use both results with care: a deadzone estimate is a clue for setup, not a lab measurement.

09 / Control with intent

Built for Flight Simmers & Sim Racers

Sim controls punish small setup faults. A flight stick may feel centered in a menu, yet pull a nose up during a long climb. A racing wheel may look fine at the start line, then drift from center in a long turn. The Joystick Tester gives you a quick input map before you load a session.

Test the rig in the same connection mode you use for play. Bluetooth can expose a different map from USB, and some wheels need a driver profile before every axis appears. The page reports what the browser receives. It does not promise that a sim will use every input without its own setup. After the check, open the Controller Mapping Test to confirm the names that your game should bind.

10 / Read beyond the button

Advanced Joystick Tests

A Joystick Tester can show more than a button press. A slow edge sweep gives clues about circularity, central accuracy, tremor, and skipping zones. These checks work best with the same grip and motion each time. Keep the result as a comparison tool. A browser sees the signal after the device and driver have already shaped it.

A single odd path does not prove a damaged part. Your hand can press one side harder, and a physical gate can change the path near a corner. Make two or three calm runs. If the same zone appears each time, compare the output with how the device feels in a game. Hall-effect sticks can keep a clean signal for a long time, while older potentiometer modules can show wear. Both still depend on their shell, map, and driver.