The Gamepad Tester

Observe buttons, analog sticks, triggers, and supported vibration output in your browser. Guided checks retain evidence and explain their limits.

Button Testing

Verify browser-visible press and release transitions

Stick Center

Sample repeated center offset and stability

Vibration Output

Send supported output to a confirmed target

Trigger Testing

Check mapped range and release transitions

Stick Sweep

Review edge reach and directional coverage

Input Profile

Confirm semantic controls before testing

Extra Browser Axes

Observe extra axes without inferring sensor type

Export Results

Export one immutable diagnostic snapshot

Preparing Gamepad API...

Controller Compatibility

Compatibility is capability-based. A controller can be tested only when the operating system and browser expose it through the Gamepad API, and each control or output path is evaluated separately.

XB

Xbox-style controllers

Common examples

  • - Xbox Series X/S
  • - Xbox One
  • - Xbox Elite
  • - Compatible XInput devices

Browser limits

  • Standard sticks, face buttons, D-pad, bumpers, and triggers are commonly exposed
  • Paddles, profiles, and accessory-specific controls may remain unavailable
  • Vibration depends on the browser-reported actuator
PS

PlayStation-style controllers

Common examples

  • - PS5 DualSense
  • - PS4 DualShock 4
  • - Compatible third-party models

Browser limits

  • Mapped sticks, buttons, D-pad, and triggers are commonly exposed
  • Touch position, gyro, speaker, microphone, and adaptive-trigger force are not standard checks
  • Known Sony WebHID output remains experimental and requires explicit association
NS

Nintendo-style controllers

Common examples

  • - Switch Pro Controller
  • - Joy-Con when exposed by the browser
  • - Compatible third-party models

Browser limits

  • Stick and button mappings vary by browser, operating system, and connection
  • A semantic input profile may be required before diagnostics
  • Gyro, NFC, and detailed HD rumble are outside the standard browser test
ST

Handheld and Steam input

Common examples

  • - Steam Deck browser input
  • - Windows handheld controls
  • - Steam Controller

Browser limits

  • Built-in controls may be exposed as a standard or nonstandard Gamepad
  • Operating-system remapping layers can change labels and axis order
  • The browser tester cannot inspect the complete native input stack
GP

Third-party and generic gamepads

Common examples

  • - 8BitDo
  • - Logitech
  • - Retro-style USB pads
  • - Other HID gamepads

Browser limits

  • Live input works only when the browser exposes a Gamepad slot
  • Unknown descriptors and nonstandard layouts require profile confirmation
  • Unavailable buttons, triggers, or output paths are excluded from scoring

How compatibility is decided

Browser exposure

A current connected Gamepad slot must exist.

Mapping confirmation

Standard mapping is used only when reported; other layouts need a profile.

Per-capability results

Missing controls or output support stay unavailable instead of becoming failures.

Read browser compatibility guidance or troubleshoot detection.

Troubleshooting Common Issues

Start with repeat tests, official tools, and reversible checks. Open an issue for its evidence limits and safer decision path.

Stick Drift Problems

Check First

Your analog sticks move on their own without input, causing unwanted movement in games.

Common Symptoms:

  • -Character moves without touching sticks
  • -Camera drifts in one direction
  • -Menu cursor moves automatically
  • -Sticks don't return to center

First Checks:

Repeat a hands-off center check, compare an official calibration tool, and try only a small reversible in-game deadzone if the offset persists.

View Detailed Guide

Button Lag or Unresponsive Buttons

Check First

Buttons don't respond immediately or require multiple presses to register.

Common Symptoms:

  • -Buttons feel mushy or sticky
  • -Delayed response when pressing buttons
  • -Buttons get stuck in pressed position
  • -Some buttons don't work at all

First Checks:

Repeat deliberate press-and-release trials, compare another connection or official tool, and clean only external surfaces before considering repair.

View Detailed Guide

Connection Problems

Review

Controller disconnects frequently or isn't recognized by your device.

Common Symptoms:

  • -Controller disconnects during gameplay
  • -Not detected by computer or console
  • -Bluetooth pairing fails
  • -USB connection unstable

First Checks:

Check power and cable seating, reconnect or re-pair the controller, update official firmware, and compare another port or connection path.

View Detailed Guide

Need Help with a Different Issue?

Browse the current guide library for trigger, vibration, connection, mapping, maintenance, and other controller topics.

Frequently Asked Questions

Get instant answers to the most common questions about testing your gaming controllers

Still have questions? We're here to help!

View Complete FAQ