Test your steering wheel and pedals. Right in the browser.

The JoyCheck controller tester family includes a steering wheel tester: plug in a racing wheel, run one guided mapping, and read rotation range, centre offset, pedal travel and a health score straight from the W3C Gamepad API, with nothing sent to a server.

Rotation range · Centre offset · Pedal linearity · Health score · 7 min read

A steering wheel tester reads the axes a racing wheel exposes to the browser and turns them into verdicts you can act on. Wheels are messier than gamepads: every brand puts steering and pedals on different axis numbers, some invert them, and Logitech’s drivers can merge throttle and brake into one shared axis. That is why this tester starts with a 60-second guided mapping instead of assuming a layout.

Updated on 2026-07-25 by Taimoor Bamazai, founder of Elites Algorithm (Dublin, Ireland and Pakistan) and the builder behind JoyCheck.

How do you test a steering wheel in the browser?

You test a wheel by letting the page watch you use it. Connect the wheel over USB, press a pedal or button once so the Gamepad API wakes the device, and start the guided mapping. The tester prompts four actions: turn the wheel lock to lock and let it settle, then press and release the throttle, the brake, and the clutch. From those four gestures it learns which axis is which, which direction each pedal travels, and whether your driver is merging pedals onto one axis.

After mapping, everything is live and the profile is saved on your machine for next time.

1. Connect and wake the wheel. Plug in over USB and press a pedal. A wheel stays invisible to the page until it produces input.
2. Run the guided mapping. Follow the four prompts. A pedal you do not have is one click to skip.
3. Read rotation and centre. The range bar shows how much of the axis your wheel sweeps; the centre chip shows how far from true centre it rests.
4. Sweep each pedal slowly. Press smoothly to full over a few seconds, hold, release. The sweep plot and verdicts appear immediately.
5. Export the report. JSON, CSV, or a copyable summary, for a warranty thread or a before-and-after comparison.

The same no-install checkup covers gamepads on the main controller tester, and the polling rate test times the update rate of any pad or wheel.

Do you need Logitech G HUB, or can the browser test the wheel?

You need both, for different jobs, and confusing the two is why so many wheel problems survive reinstall after reinstall. G HUB and Logitech Gaming Software are configuration tools: they set the rotation limit, the force feedback strength, and the combined-versus-separate pedal mode, and they load the firmware profile. What they do not show you clearly is what your PC actually receives when you drive.

That receiving side is what a browser tester verifies. If the wheel turns but your games see nothing, the split tells you where the fault is: readings alive in the browser mean the wheel and driver are fine and the problem is the game’s binding; readings dead in the browser mean the problem sits in the driver, the cable, or the hardware, and no amount of in-game rebinding will fix it. Our Logitech wheel setup guide walks the driver side step by step.

What does the pedal sweep tell you?

The slow sweep is the closest a browser gets to a bench test of a pedal’s sensor. You press one pedal smoothly to full over a few seconds while the tester records every value it receives, then it examines the press: how far the pedal reached, whether the curve climbed steadily, and whether it dipped or jumped on the way up.

A healthy potentiometer produces a smooth, monotonic ramp. A worn one produces dips and sudden steps at the same physical spot, press after press, because the resistive track inside has worn thin where the wiper spends most of its life. That pattern is the classic worn-potentiometer signature, and catching it early is the difference between a cheap sensor swap and a dead pedal mid-race.

These bands come from our own diagnostic testing and are working guides, not a manufacturer specification.

What this tester deliberately does not claim

Two honest limits, stated up front because they are exactly where wheel tools tend to overpromise.

Degrees are a conversion, not a measurement. The Gamepad API hands the page a unitless axis from -1 to +1[1]. If your wheel is set to 900 degrees in its driver, the tester can show you degrees only because you told it that number. What it genuinely measures is the fraction of the axis your wheel sweeps and where it rests, which is what you need for diagnosing range loss and centre drift.

Force feedback cannot be tested from a web page. The API’s haptics support extends to rumble actuators[2], and most wheels expose no actuator to the browser at all; their force feedback is driven by the manufacturer’s driver. The tester reports whether an actuator exists and sends a pulse only when one does. Any browser tool that claims to exercise your wheel’s force feedback motors is testing something else.

Which wheels work?

Any wheel that presents itself to the operating system as a game controller: the Logitech G27, G29, G920 and G923, Thrustmaster’s T150, TMX and T300 family, and most Fanatec bases in their compatibility modes. Axis counts and orderings differ across every one of them, and across driver versions of the same wheel[3], which is why the guided mapping exists. If a wheel runs a proprietary native mode the browser cannot see, switch it to its PC or compatibility mode and re-test.

If your gear is a gamepad rather than a wheel, the main controller tester covers sticks, buttons, triggers and rumble, and the stick drift test isolates the resting-value check.