BeanNestTools

Controller input check

Press it, move it, and see what the browser receives.

Connect or pair your controller through the operating system, then press a button or move a stick. BeanNest shows browser-visible input without installing drivers or requesting USB access.

No installNo controller-data uploadNo USB permission

Gamepad test workspace

StatusWaiting for a controllerConnect or pair a controller, focus this page, then press a controller button or move a stick.
Buttons seen0
Buttons0
Axes0
Controller
None visible
Mapping
—
Live input

Buttons and analog values

Waiting for browser-visible controller buttons.

Live input

Raw axes

Waiting for browser-visible controller axes.

How to use it

Wake the controller, then exercise every input.

  1. 01

    Connect outside the page

    Pair Bluetooth or connect USB through your operating system. This page does not request WebUSB or install a driver.

  2. 02

    Press or move a control

    Some browsers do not expose a connected controller until you interact with it while the page is visible.

  3. 03

    Check every value

    Exercise buttons, D-pad, triggers, and axes. Reset Buttons seen if you want a fresh pass without changing the live values.

What the result means

The browser mapping is the source of truth for this page.

When the browser reports standard mapping, BeanNest can label the standard button positions and first four stick axes semantically. If mapping is not standard, the page deliberately falls back to Button N and Axis N instead of guessing what physical control they represent.

A visible value is not a hardware certification.

Operating-system drivers, browser mapping, wireless state, remapping software, and the controller itself can all affect what reaches this page. BeanNest does not calibrate firmware, measure USB polling rate, or diagnose electronics.

Controller identity and values stay local.

The controller ID, mapping, button values, axes, and Buttons seen set stay in memory in this tab. Analytics receives only the same coarse tool-start event used by other BeanNest tools.

Why is my connected controller still not visible?

Focus this page and press a controller button or move a stick. Some browsers delay Gamepad API exposure until visible-page user interaction.

Why do I see Button 0 instead of familiar names?

Your browser did not report standard mapping. BeanNest avoids assigning Xbox, PlayStation, Nintendo, or other physical labels when the browser cannot guarantee that mapping.

Does this test include vibration?

No. Browser, platform, and controller vibration support varies enough that lack of vibration could be misleading. This release stays read-only.

Can this page fix or calibrate my controller?

No. It observes browser input only. Calibration, firmware, repair, and operating-system remapping are outside the web page.

Keep checking

More input checks

Stick Drift Test

Sample standard-mapped left and right stick center offset for five seconds and compare the browser-observed result with a deadzone you choose.

Open tool →

Keyboard Test

Check the keyboard events your browser receives, including held keys, modifiers, physical key codes, and repeat state.

Open tool →

Mouse Test

Check mouse buttons, wheel input, browser double-click events, movement, and hold continuity locally.

Open tool →