GamepadHealth / LIVE INPUT
Gamepad tester
Connection status
Connect your controller and press a button
Browsers only reveal a controller after it receives input — that’s a privacy protection, not a sign of a problem. If it’s already plugged in, press any button or move a stick now.
Unnamed controller
—
Move a stick or press any button
Detailed health check
Follow guided steps for a separate, explainable health report.
This turns on as soon as your browser detects controller input above.
Guided observation
Follow one clear step at a time
This flow records bounded browser observations. The local report is calculated only after the phases finish.
Step 1 of 7
Leave the controller untouched
Place it on a stable surface and release every stick, trigger, and button for a short uninterrupted window.
Movement restarts this window so an accidental touch cannot become a device finding.
Step 2 of 7
Move the left stick around its full circle
Trace the outer edge in every direction, then release the stick so it returns to center.
Move only the requested stick. A wrong movement is ignored rather than marked as failure.
Step 3 of 7
Move the right stick around its full circle
Trace the outer edge in every direction, then release the stick so it returns to center.
Coverage here is an interaction requirement, not an accuracy or hardware verdict.
Step 4 of 7
Press each standard-mapped button once
Work through the face, shoulder, menu, stick, directional, and home controls exposed by the browser.
If a control is unavailable or unclear, continue with this phase marked inconclusive.
Step 5 of 7
Press and release both triggers slowly
Move the left and right triggers from rest to their available end and back to rest.
Digital-only or raw mappings remain unsupported for analog interpretation and receive no penalty.
Step 6 of 7
Produce gentle changing input
Slowly move a stick or press a button while the visible-tab observation window completes.
This observes browser updates. It does not claim USB polling rate or end-to-end latency.
Step 7 of 7
Optionally confirm one short vibration
Start the vibration yourself, then report whether you physically felt it.
A successful API command does not prove that a motor worked; your confirmation remains separate.
Observation flow complete
All guided phases have a recorded state
You completed the interaction flow. Unsupported and inconclusive phases remain separate.
- Rest calibration
- Left stick
- Right stick
- Buttons
- Triggers
- Input stability
- Haptics
The local v1 report uses provisional thresholds and is not a hardware certification. Unsupported and inconclusive phases stay unscored.
Press each standard-mapped button once. Repeated or unexpected input is not treated as a failure.
The browser could not complete the command. Retry or continue with this step inconclusive.
The browser completed the command. Your physical confirmation is still required.
Use the button below to request one short vibration.
This browser/controller combination does not expose a haptics command. No penalty is applied.
This step will be recorded as inconclusive, not as a controller failure.
The browser does not expose the controls required for this step. It is unsupported, not failed.
Directional coverage is being observed for the left stick.
The interaction requirement is complete. Review the instruction, then continue.
Keep the controller still while the uninterrupted rest window fills.
The browser delayed sampling, so the rest window restarted without a hardware conclusion.
Input moved during the rest window. The window restarted; this is not a failure.
Directional coverage is being observed for the right stick.
Keep producing gentle input while the visible-tab observation window fills.
There was not enough clean, changing input. Retry or continue as inconclusive.
The phase is paused. Return to the visible tab or reconnect the selected controller.
Press and release both triggers through their available travel.
Analog trigger mapping is not exposed here. This step is unsupported, not failed.
- Axes
- Buttons
- Timestamp
- —
- Haptics API
- AXIS 0
- AXIS 1
- AXIS 2
- AXIS 3
- AXIS 4
- AXIS 5
- AXIS 6
- AXIS 7
- AXIS 8
- AXIS 9
- AXIS 10
- AXIS 11
- AXIS 12
- AXIS 13
- AXIS 14
- AXIS 15
- AXIS 16
- AXIS 17
- AXIS 18
- AXIS 19
- AXIS 20
- AXIS 21
- AXIS 22
- AXIS 23
- AXIS 24
- AXIS 25
- AXIS 26
- AXIS 27
- AXIS 28
- AXIS 29
- AXIS 30
- AXIS 31
Raw mapping: use the numbered values. The standard controller diagram does not apply.
The browser delayed this preview. This is an environment notice, not a controller failure.
Connection status
Connect your controller and press a button
Browsers only reveal a controller after it receives input — that’s a privacy protection, not a sign of a problem. If it’s already plugged in, press any button or move a stick now.
Connection status
Controller detected
Live normalized input, guided observations, and the local report are available below.
Connection status
Multiple controllers detected
Choose which connected controller to preview. This selection remains only on this page.
Connection status
Controller disconnected
Reconnect or interact with the controller to continue. No hardware failure is inferred.
Connection status
Sampling paused
Return to this visible tab to continue local input sampling.
Connection status
Preparing controller detection
The connection interface is loading. No input is recorded while you wait.
Connection status
Connection interface unavailable
The interface could not prepare controller detection. This is not a controller health failure.
Connection status
Controller detection isn’t available here
Your current browser or connection doesn’t expose the controller data this test needs. That’s a browser limitation, not a sign that the controller has a problem.
GamepadHealth
Test result
Right stick
Not testedButtons
Not testedAnalog triggers
Not testedInput stability
Not testedThis is a browser test with provisional thresholds, not a definitive hardware diagnosis.
Measurements and technical details
Provisional score thresholds — physical multi-device calibration is still required before public release.
Overall Health Score
A score appears only after supported checks are completed.
Findings and next actions
- Left stick
- Right stick
- Buttons
- Analog triggers
- Input stability
Evidence summary
- Left center radial p99
- —
- Right center radial p99
- —
- Left directional range
- —
- Right directional range
- —
- Average trigger travel
- —
- Button coverage
- —
- Observed input interval median / p95
- —
Starting deadzone suggestion
Derived from the rest-window p99 plus a safety margin. Use it only as a starting in-game setting; games apply deadzones differently.
- Left stick
- —
- Right stick
- —
Method and limitations
The score uses versioned integer calculations from bounded browser observations. It is not a hardware certification.
- Browser timing is not USB polling rate or end-to-end latency.
- A missed interaction can make a phase inconclusive; it does not prove a broken control.
- No model benchmark, percentile, battery health, or physical wear claim is produced.
No significant deviation was observed in the tested checks.
Some checks showed a deviation. Repeat those steps.
Some checks could not be completed. Try the missing steps again.
{0} normal · {1} recheck · {2} no result
Measurement complete. Review the center offset and deadzone suggestion below.
Within the provisional range
The eligible browser observations stayed within the provisional v1 range.
Review recommended
One or more observations are outside the preferred range. Retest before making a decision.
Strong deviation observed
A strong browser-observed deviation appeared in this category. Retest and interpret it with the reported confidence; it is not proof of physical damage.
Unsupported
The browser/controller combination did not expose this measurement. No score penalty was applied.
Not tested
This category was not completed and was excluded from scoring.
Inconclusive
The evidence was not clean or complete enough to score this category.
Excellent
Good
Fair
Poor
Critical
High
Medium
Low
Not available
{0}: the observation stayed within the provisional range. {1}
{0}: the observation is outside the preferred range. {1}
{0}: a strong deviation was observed once. {1} This is not proof of physical damage.
Center offset
Directional range
Return to center
Rest stability
Button coverage
Trigger travel
Trigger return
Observed input interval
Browser sample quality
Repeat this phase before deciding.
Retest at rest and use the deadzone suggestion only as a starting point.
Retest in a visible tab with steady interaction.
Free browser-based controller test
GamepadHealth: Controller Tests & Result Guides
Choose a controller test for stick drift, deadzone, buttons or input stability. Read result guides and check browser support, with no software installation.
No install or account needed — raw controller input never leaves your browser.
Simple and explainable
From connection to a useful report
Each stage keeps one clear task on screen and explains what the browser can and cannot observe.
-
1
Connect your controller
Use a supported browser and interact with the controller when prompted.
-
2
Follow guided checks
Complete focused stick, button, trigger, and stability steps without hidden background tests.
-
3
Review honest results
See tested, unsupported, and inconclusive areas separately instead of receiving false zero scores.
Built around clear limits
A calm diagnostic experience with no hidden claims
Browser support is explicit
Unsupported and interaction-required states remain separate from controller health.
Methods stay visible
Every future metric must explain its browser-observed method and confidence.
Local-first by default
Raw controller inputs stay in this page. A result is saved on the server only when you choose Share. Optional analytics follow your privacy preferences.
Choose the right controller test
Start with the full gamepad test for an overview. Choose stick drift for unwanted movement, deadzone for a resting-center suggestion, buttons for missed inputs, or input stability for uneven updates. The guides explain how to interpret each result and what to check next.
How to use it
- Choose the full check for an overview, or a focused test for a specific symptom.
- Connect a controller, press a button and choose its device tab.
- Follow the instructions, then read the normal, review and unavailable results.
- Keep a share link only if you want to save the completed full check.
What the result means
A normal result describes only the controls and conditions tested here. Game settings, deadzones, remapping and connection changes can produce different behavior. Repeat the same check before comparing results.
Limits of this measurement
What to try next
Keep a share link only if you want to save the completed full check.
Does this browser test diagnose hardware damage?
No. It reports browser-observed input and cannot certify internal hardware, USB polling rate, end-to-end latency, battery health or physical wear.
Four controllers, separate tests
Connect up to four gamepads and press a button on each. Choose its numbered tab before starting. Each controller keeps its own test progress while the page stays open; a result is saved on the server only after Share.
Gamepad connected but not detected?
Confirm the operating system sees the controller, return to this tab and press a face button. Try a data-capable USB cable or another port, then temporarily close remapping software. Test one change at a time.
Does a normal result mean every game will work?
A normal result describes only the controls and conditions tested here. Game settings, deadzones, remapping and connection changes can produce different behavior. Repeat the same check before comparing results.