Troubleshooting and Help

Controller not detected

This is the single most common issue, and there is a good chance it is the same cause for almost everyone: the browser does not register a controller until that controller sends its first input.

The Gamepad API your browser uses is intentionally quiet. A connected pad stays invisible to the page until you give it a reason to wake up. So the fix is almost always the first thing to try.

Press a button first

Once your controller is connected, press any button or nudge a stick. The viewer should detect it instantly and show its button and axis count. If you connected the pad before opening the page, this single step resolves most cases.

If pressing a button does nothing

• Check the physical connection. A loose cable or a half-seated dongle is easy to miss. Unplug and firmly reconnect.
• Confirm it is paired at the system level. Open your computer's Bluetooth or device settings and make sure the controller shows as connected there, not just powered on.
• Close apps that capture the controller. Steam Input, the Xbox app, DS4Windows, and similar tools can take exclusive control and hide the pad from your browser. Quit them fully and refresh.
• Refresh the page after connecting. A reload often clears a stuck detection state.
• Try another browser. If Chrome will not see it, that points to a driver or system issue rather than the tool itself.

Browser compatibility

The Gamepad API is supported across modern browsers, but the quality of that support varies. Chromium-based browsers give the most consistent experience, while others have quirks worth knowing.

If a feature like rumble does not work, try Chrome or Edge before assuming the controller is faulty. Opening the page in an in-app browser, such as a link tapped inside a social media app, is a common hidden cause, so open it in a real browser instead.

USB connection issues

Wired connections are usually the most stable, but a surprising number of problems trace back to one thing: the cable.

The charge-only cable trap

Many USB cables, especially the ones bundled with phones and power banks, are wired for charging only and carry no data. The controller will light up and charge, yet never appear in the browser.

• Use the cable that came with the controller, or one you know transfers data.
• If a pad charges but is never detected on multiple computers, suspect the cable first.
• Test the same cable with another device to confirm it moves data.

Other wired fixes

• Switch ports. Try a different USB port, ideally one directly on the machine rather than through a hub or monitor.
• Avoid unpowered hubs. Some controllers need more power than a daisy-chained hub provides.
• Reseat both ends. Especially on USB-C pads, a slightly loose connector can break data flow while still charging.

Bluetooth issues

Wireless pads add a layer that can go wrong, but the fixes are straightforward.

Pair at the system level first

The browser cannot pair a controller for you. The pad must already be connected in your computer's or phone's Bluetooth settings before the page can see it. If it is not listed there as connected, start there.

Common wireless fixes

• Put the controller in pairing mode properly. Each pad has its own button combination; holding the pair button until the light flashes is the usual method.
• Remove and re-pair. If a previously paired controller misbehaves, delete it from your Bluetooth list and pair it fresh.
• Charge it. Low battery can cause a controller to connect intermittently or drop inputs.
• Reduce interference. Move closer to the machine and away from other wireless devices or USB 3 hubs, which can swamp 2.4 GHz signals.
• Pick one connection. A pad connected by both cable and Bluetooth at once can confuse detection. Use one at a time.

Specific controller notes

Most pads follow a standard layout, but a few have quirks worth knowing.

Xbox controllers

Xbox Series and Xbox One pads work well over both USB and Bluetooth. Older Xbox One models without Bluetooth need the cable or an Xbox wireless adapter. If the Xbox app or Game Bar is running, it can capture the pad, so close it.

PlayStation DualSense and DualShock

DualSense and DualShock 4 are well supported over USB and Bluetooth. Some advanced DualSense features like adaptive triggers are not exposed to the browser, so the tool reads them as standard triggers. The viewer auto-detects PlayStation pads and switches to PlayStation button labels.

Nintendo Switch Pro Controller

The Switch Pro pad connects over USB and Bluetooth and reports a standard layout. Button positions may differ from the on-screen labels because Nintendo's physical layout is mirrored compared to Xbox. Use the label toggle if the symbols do not match.

8BitDo and third-party pads

8BitDo controllers often have multiple connection modes, switched by a startup button combination. If yours behaves oddly, check it is in the right mode, usually the one that emulates an Xbox or DirectInput pad. Most generic HID controllers work without any setup.

Phones and tablets

The tool is fully responsive and works on mobile, with a couple of extra steps.

• Pair before opening. Connect your Bluetooth controller in your phone's settings first, then load the page.
• Use a real browser. Chrome or Edge on Android, and Safari on iOS 16 or newer. Opening the link inside another app's built-in browser usually will not work.
• Wake the pad. As on desktop, press a button after the page loads so the browser registers it.

Making sense of your results

Once your controller is showing, here is how to read what the tool tells you.

Stick drift

Drift is when a stick reports movement while you are not touching it. Rest both thumbs off the sticks and watch the readings. Tiny values that flicker near zero are usually normal. A stick that consistently reports a clear offset at rest, or pulls in one direction, is the classic sign of drift.

Deadzone

The deadzone is the small range near center that the tool ignores so minor noise does not register as input. If a healthy stick still triggers the drift flag, nudging the deadzone slider up slightly can confirm whether the movement is genuine wear or just normal jitter.

Triggers and buttons

Pull each trigger slowly and watch the value climb smoothly from rest to full. A trigger that jumps, sticks, or never reaches full may have a worn sensor. For buttons, every press should light up its on-screen counterpart instantly. A button that needs a hard press, or registers on its own, is worth noting.

Rumble and polling rate

The rumble test drives the weak motor, the strong motor, or both, so you can isolate a dead one. Polling rate shows how often the controller reports to your computer; a steady figure is healthy, while a number that swings wildly can point to a flaky connection rather than a broken pad.

Using it as an OBS overlay

The viewer has a transparent background, so it drops straight into a stream. If the overlay misbehaves, these are the usual culprits.

• Add it as a Browser Source in OBS or Streamlabs and paste the page URL, then resize it to fit your layout.
• Controller not showing in OBS? The browser source needs to receive a button press too. Interact with the controller after the source loads.
• Overlay went blank after a while? Right-click the browser source and clear its cache, then click Cancel rather than OK to avoid resetting your settings, and refresh.
• Keep the window visible. If you capture a separate browser window instead, do not minimise it, as OBS cannot capture a minimised window.

Still stuck?

If you have worked through the relevant section and the controller still will not cooperate, it is worth a message. The details that help us most are the controller model, your browser, your operating system, and whether you are on cable or Bluetooth.