GameControllerTest.com
Multi-platform controller profile

GameSir Controller Test

Test GameSir controller buttons, sticks, D-pad, triggers, and mapping online across browser-supported wired or wireless modes.

Live browser diagnostic

Complete controller check

Run every essential check from one private dashboard.

Not connected
Local-only test

Connect with USB, Bluetooth, or a supported wireless adapter. Then press any controller button so your browser can expose it. Your readings are processed on this device.

Detected device No controller detected Gamepad API ready · waiting for input
L1
R1
L
R
Update rate— Hzbrowser-observed
Buttonsreported
Axesreported
Mappingbrowser label
Live input

Sticks and triggers

Left stickX 0.000 · Y 0.000
Right stickX 0.000 · Y 0.000
Left trigger 0%
Observed range: not sampled
Right trigger 0%
Observed range: not sampled
Neutral sample

Stick drift and deadzone

Set the controller on a steady surface and do not touch either stick during the sample.

Ready for an 8-second sample.
Full movement

Range and circularity

Rotate each stick slowly around the outer edge, then sweep the center in several directions.

Move the sticks to begin range tracking.
Input coverage

Buttons and D-pad

Press and release every available control. Analog buttons show their reported value.

No button activity yet.
Raw browser data

Axes and mapping

Use these values to spot unusual layouts. A blank standard mapping does not automatically mean the controller is defective.

View raw browser data
Connect a controller to view raw data.
Optional capability

Vibration check

Browser haptics are not available for every controller, connection method, operating system, or browser.

Connect a controller to check browser support.
Private test record

Keep your result

Reports are stored in this browser. Sharing is optional and puts only the selected result in the link.

Diagnostic readings describe what this browser receives, not electrical measurements from the controller. Confirm important findings in the game or device where you plan to use the controller.

Controller overview

What this browser check can reveal

GameSir controllers span wired, wireless, mobile, PC, and console-focused models. Connect the controller in the mode supported by your computer, then use the live tester to check every standard button, axis, stick, and trigger the browser exposes.

Some models use Hall-effect sticks or triggers, adjustable stops, rear controls, onboard profiles, or mode switches. Those features can change the values seen by the browser, and rear buttons may send mapped standard inputs rather than unique button indexes.

Use your exact model's official documentation for firmware and mode shortcuts. This page records the input delivered to the browser; it does not identify internal sensor technology or validate proprietary configuration features.

Connection notes

Start with a known, stable connection.

  • Live button and axis coverage for browser-supported modes
  • Stick center, circularity, and range inspection
  • Analog trigger and trigger-stop comparison
  • Raw mapping details for multi-platform models
Inspection workflow

A practical controller checklist.

  1. 01

    Confirm the controller appears and the reported name or identifier is plausible.

  2. 02

    Press and release every button, D-pad direction, stick click, bumper, and trigger.

  3. 03

    Run the hands-off drift sample, then sweep both sticks through their full range.

  4. 04

    Disconnect and repeat in the connection mode you actually plan to use.

  5. 05

    Verify any fault inside a supported game or console before making a purchase or repair decision.

Compatibility is a chain, not a promise

GameSir models vary widely; confirm the specific model and operating mode.

Frequently asked

GameSir Controller Test questions

Why does my GameSir controller have the wrong labels?

It may be operating in a different input mode, or the browser may not have a standard mapping for that device ID. Inspect raw indexes and reconnect in the recommended PC mode.

Can the tester confirm Hall-effect sensors?

No. It can show the input behavior received by the browser but cannot identify the physical sensor type or prove immunity from future drift.

Why do rear buttons duplicate face buttons?

Many controller profiles map rear controls internally to standard buttons. In that setup the browser sees the assigned action, not a separate rear-button input.