Support

Controller test support and troubleshooting

Use this page when a controller does not appear, mappings look wrong, vibration is unavailable or a diagnostic result needs interpretation.

Last updated: June 3, 2026

Connection checklist

Most browser controller problems start before the test data arrives. Work through the simple checks first, then rerun the live input test.

  • Connect the controller by USB for the first test, then compare Bluetooth or 2.4G later.
  • Press any controller button after loading the page to wake the browser Gamepad API.
  • Close games or launchers that may hold exclusive controller access.
  • Try Chrome, Edge and Firefox if one browser does not expose the device correctly.
  • Disconnect and reconnect the controller if the page still shows stale input.

Interpreting common results

A small stick center offset is normal. The important question is whether the offset is large enough to move a game character or camera when the stick is untouched.

If a trigger never reaches the full range, test slowly several times. If the value remains capped, the issue may be hardware wear, driver mapping or platform-specific behavior.

  • Use stick drift for center noise.
  • Use circularity for outer-gate travel.
  • Use polling rate only for same-browser comparisons.
  • Use vibration results as capability detection, not proof that the controller motor is broken.

Contact support

Email support@controllertestonline.com with the controller model, operating system, browser name and version, connection mode and a copied health report.

Screenshots of the live input panel help diagnose mapping issues. Do not send private account credentials or unrelated personal information.

Need a diagnostic report?

Run the live controller test, copy the health summary, then include it in support, resale or repair notes.

Start controller test