What Is a Gamepad Tester?
A gamepad tester is a live view of input states a browser receives from a connected controller. It is useful when you want to know whether a face button, direction pad, stick, or trigger changes the values delivered to a web page. This online gamepad tester reads the Gamepad API in the active tab and redraws the current state while the tab is visible. It does not install a driver, upload input data, or claim to inspect controller electronics.
The visual is intentionally generic. When a browser reports standard mapping, it can place common controls in familiar groups. The numbered button and axis panels remain available even then, because controllers and browsers may expose extra inputs or omit optional ones. When mapping is unknown, neutral labels avoid assigning a physical meaning that the API has not established.
How to Get Started
Connect a controller by its supported cable or wireless connection, open this page in a current browser, and press a controller button. Some browsers do not reveal an already connected device until you interact with it while the page is focused. If the selector stays empty, verify that the operating system recognizes the device, return to this tab, press a button, then use Check again if needed. The tool reports when the Gamepad API itself is unavailable.
If several devices appear, use the active-device selector to pick the one you are holding. The connection line shows the device index, browser mapping type, button count, and axis count. A disconnect removes the old reading; reconnecting may reuse an index, so confirm the selected device before interpreting values. The page pauses live polling while hidden and resumes when visible.
What This Gamepad Tester Can Read
For each exposed button, the page shows its numeric index, pressed flag, touched flag, and analog value. A digital press often moves between zero and one. A pressure-sensitive input may report intermediate values. The touched flag is browser and device dependent; “not touched” does not imply that a physical sensor exists and failed. Press and release one input at a time to see which browser index changes.
Every exposed axis appears as a signed decimal value. On a standard mapped controller, the first four axes are commonly the X and Y coordinates of the left and right sticks. The small plots show those pairs moving around a center point; the numeric values are more useful for fine comparisons. This gamepad button test and stick view reveal delivered states, not the exact force, travel distance, or electrical scan rate inside the device.
How Analog Sticks and Axes Work
An axis normally ranges approximately from negative one to positive one, with zero near its center. Left and right or up and down are signs along a coordinate, not separate buttons. A diagonally held stick changes both axes at once. The plotted dot is calculated directly from the pair of browser values; distance from center is the square root of X squared plus Y squared. Small nonzero center readings can occur without a practical control problem.
The Gamepad API does not promise that every non-standard device uses the first two axes for a left stick. For an unknown mapping, the tester displays Axis 0, Axis 1, and so on, without a stick label. Move one physical control at a time and observe which numbers change. The browser or operating system may apply calibration and deadzones before the page sees the readings.
How Triggers Are Reported
Under standard mapping, the left and right triggers occupy known button positions and may expose analog values from zero to one. The dedicated trigger panel shows those values and a meter so you can compare a released state with a partial or full squeeze. If a browser returns only binary values, the meter can only show those binary states. A value near one means the browser reported a strong activation; it is not a calibrated force measurement.
Under a non-standard mapping, the page leaves triggers among numbered buttons and axes. It would be misleading to call a changing Axis 4 a trigger without a documented layout. If your device uses a vendor-specific configuration, consult its own mapping information before matching a physical control to an API index.
Standard and Non-Standard Mapping
Standard mapping is the browser’s declaration that common control positions follow the Gamepad API standard layout. It enables descriptive labels such as face bottom, D-pad up, or left stick click. Those labels describe positions, not a console brand or the printed legend on your particular controller. Optional buttons may still be absent, and additional controls may appear only as numbered entries.
A blank or non-standard mapping means the browser has not made that layout promise. The raw panel shows the mapping value, connection flag, timestamp, every button, and every axis in a readable list. The timestamp comes from the API and can differ in resolution or behavior across browsers. It is helpful for seeing updates but is not a certified device polling interval.
Why a Controller May Not Appear Immediately
Browsers can require a button press or axis movement before exposing a gamepad, partly to limit passive device identification. The page must be visible and focused for some browser and operating-system combinations. A wireless device may also be paired yet not connected as an active input, and some adapters or virtual controllers expose an unexpected layout. Try one supported connection path at a time and confirm the device in another trusted application if the browser list remains empty.
A missing reading is not proof that the controller is broken. Browser permissions or policy, operating-system drivers, remote sessions, device compatibility, and browser version may all intervene. This page cannot read firmware, USB electrical timing, or inputs that the browser never receives.
Who Uses an Online Gamepad Tester?
Players can check whether a button or stick reaches a browser game before changing in-game bindings. Web game developers can compare the inputs their application receives with the same API view. People buying or troubleshooting a used controller can make a quick visible pass over exposed controls, then decide whether more specific vendor or native diagnostics are warranted. Repeat a puzzling observation after reconnecting or using another browser.
The live gamepad tester is best for the question “what is being reported right now?” It does not keep a pass or fail record or require a fixed test sequence. If you need to deliberately cover each button, sample resting sticks, observe travel bounds, and summarize a repeatable run, open the guided controller tester.
Browser and Device Limitations
The displayed data is the browser-exposed state after the device, driver, operating system, and browser have processed it. Values can be normalized, remapped, filtered, or unavailable. The interface cannot establish native-game FPS, diagnose a mechanical switch, measure exact USB polling, or certify that every physical input works. A pressed state proves only that this browser saw a pressed state in the current session.
The tool keeps readings local to the page. It does not transmit raw controller values or device identifiers as test results. Compare observations under the same browser and connection conditions, and read the measurement methodology and disclaimer before interpreting a discrepancy as a hardware defect.
Related Gaming Input Tools
Use the controller tester when a structured sequence and neutral summary would help you investigate inconsistent behavior. For mouse input, the mouse test shows delivered buttons, movement, and wheel events. The mouse double click test inspects closely spaced pointer transitions. These tools observe different browser input paths and their results are not interchangeable.