FLXCode Gamepad Tester

FLXCode apps

Appearance

Gamepad Tester

Connect a controller and press a button. Buttons and sticks show live. Nothing is sent.

Connect a controller, then press any button on it. Browsers only show a controller after its first button press.

No ads. No account. Controller input stays on your device. Check it. We count page events with a daily code.

Problem or idea? Email us

Quick start

  1. Connect the controller by USB or Bluetooth.
  2. Press any button on it. The browser shows a controller only after that first press.
  3. Press every button and push both sticks around. Each one should light up or move on screen.
  4. Squeeze the triggers slowly. The fill grows with how far you press.
  5. Put the controller down and press Check stick drift.

Stick drift and deadzone

The check records both sticks for 3 seconds while you do not touch them and reports how far each one wandered from the centre, on a scale where 1 is full tilt. Under 0.03 counts as no drift. Between 0.03 and 0.15 is small drift that a deadzone hides. Above 0.15 the stick is worn or dirty, and a deadzone alone will cost you precision. The suggested deadzone sits a little above the value measured. It is a starting point for your game's settings, not a fix for the hardware.

Controller not showing?

  • Press a button. Browsers list a controller only after the first press.
  • Click the page first, then press the button. Some browsers need the tab focused.
  • Try another USB port or cable. Charge-only cables carry no data.
  • Bluetooth: pair the controller in the system settings first, then press a button here.
  • Close games and Steam. Some apps take control of the controller, and the browser then sees nothing.
  • An unusual controller may report in a non-standard order. The buttons then show by number.

Accuracy and limits

The page reads the controller once per screen refresh, so it can miss a press shorter than one frame. It shows what the browser receives, which may differ from what a game or the system driver sees. The page does not measure the controller's own update rate.

How it works

The page uses the browser's Gamepad API and reads the state of buttons and axes on every frame while a controller is connected. Vibration uses the browser's haptics call, only when you press Vibrate. We count events without cookies and never the controller name or input (details). Keyboard next? Try the keyboard tester.

FAQ

Is my controller input sent anywhere?

No. The page reads buttons and sticks in this tab and shows them here. Nothing is stored or sent, and the controller name stays on your screen. We only count events, like "drift check started".

Why does the page say nothing is connected?

Browsers hide a controller until you press a button on it. Connect it by USB or Bluetooth, click the page, then press any button. If it still does not show, try another USB port or cable, or reconnect it.

What does stick drift mean?

A stick that is not touched should read zero on both axes. Drift is when it reads a little more, so a game sees small movement by itself. The check watches the sticks rest for 3 seconds and reports the farthest they wandered from the centre.

What is a deadzone and what number should I use?

A deadzone makes a game ignore stick values below a threshold. The suggested number is a little above the largest value seen at rest, in steps of 0.01, never below 0.05. Many games have a deadzone setting in their controls menu. Treat the number as a starting point.

What do "Standard" and "Not standard" mapping mean?

Standard means the browser knows your controller's layout, so buttons have names like A, B, LB and Start. Otherwise they show as Button 0, Button 1 and so on, in the order the controller reports them.

Why is there no Vibrate button?

The button shows only when the browser reports vibration for the controller. Chrome and Edge often do on Windows and macOS. Other browsers and some controllers do not.

Does it work on a phone?

It can, with a Bluetooth controller paired to the phone. Support differs between browsers and phones, so try a button press first.

More from FLXCode

Share Gamepad Tester