Free browser-based controller test
How Our Controller Tests Work: Method & Limitations
Learn what GamepadHealth measures, how incomplete tests are handled and why a browser result cannot certify hardware condition or end-to-end latency.
What this page covers
GamepadHealth samples values exposed by the browser Gamepad API. Evidence is bounded, phase-specific and labeled complete, unsupported, not tested or inconclusive.
How to use it
- Use a supported desktop browser in a secure context.
- Connect one controller and press a button so the browser can expose it.
- Follow the guided phases and repeat any inconclusive step.
- Read the evidence, confidence and limitations before acting.
How to interpret the result
Score version 1 uses a shared versioned configuration in TypeScript and PHP. Public numeric scores remain disabled until the physical calibration matrix is approved.
Important limitations
A safe next step
Read the evidence, confidence and limitations before acting.
Does an incomplete step mean a broken controller?
No. Missing input, an interrupted sample or unsupported features can prevent a conclusion. Repeat the step under the same conditions and read its status separately from the completed checks.