How to Test a Controller on iPhone & iPad

iOS controller support has matured considerably, and you can test a controller properly on an iPhone or iPad without installing anything. There's one important caveat that trips people up constantly, and getting it right is the difference between a useful diagnosis and a false alarm.

Here's how to pair, how to test, and — crucially — what Safari can and cannot tell you.

Pairing a controller to iPhone or iPad

iOS supports Xbox, PlayStation, and MFi-certified controllers natively over Bluetooth. Pairing takes about thirty seconds once the controller is in the right mode.

Put the controller into pairing mode:

Xbox controller — hold the small pair button on the top edge near the USB port until the Xbox button flashes rapidly. Note that older Xbox One controllers using Microsoft's proprietary Xbox Wireless protocol cannot pair with an iPhone at all. Only Bluetooth-capable models — later Xbox One revisions and all Series X|S pads — will appear.

PS5 DualSense — turn it fully off, then hold the PS button and Create button together until the light bar flashes rapidly.

PS4 DualShock 4 — hold Share and the PS button together until the light bar flashes.

Backbone and clip-on controllers — these connect over the Lightning or USB-C port directly rather than by Bluetooth, so no pairing is needed.

Then on the device: open Settings → Bluetooth, wait for the controller to appear, and tap to connect.

The most common failure: a controller still actively connected to a console won't pair with your phone, because it holds one Bluetooth connection at a time. Turn the console off or disconnect the controller from it first.

iOS controller test: what Safari can and cannot read

This is the section that matters most, and it's where most iOS controller guides are vague.

Safari supports the Gamepad API, so browser-based controller testing works on iPhone and iPad. You can check stick positions, button presses, and trigger values live, without an app.

Safari does not support the vibration API. This is the critical limitation. If you run a vibration test in Safari and nothing happens, that tells you nothing about your controller's motors — it's a browser limitation, not a hardware fault. People conclude their rumble is broken on this basis regularly, and it usually isn't.

There is no Safari-based workaround for this, because on iOS every browser uses Apple's underlying engine — installing Chrome on an iPhone doesn't give you Chrome's gamepad implementation. To test vibration properly, you need to use the controller on a desktop, or judge it in a game that uses rumble.

What can you test on iOS reliably? Stick positions and drift: Yes Button presses: Yes Trigger analog values: Usually D-pad: Yes Vibration/rumble: No — Safari limitation Adaptive triggers: No — not supported on iOS Advanced haptics: No — not supported on iOSGyroApp-dependent

Being clear about this saves people from returning working controllers.

iPhone gamepad test: the steps

1. Pair the controller as above, or plug in a clip-on.
2. Open Safari and go to a controller test page such as the button test.
3. Press any button — browsers don't expose a gamepad until it sends input, so if the page shows nothing, press something first.
4. Work through each input and watch what registers.

That's the whole process. If inputs register, your controller and its connection are working.

iPad controller test: spotting a failing stick

The most valuable thing you can check on a phone is drift, because it's the fault that ends most controllers and it develops gradually enough to catch early.

Set the device down on a table with the test page open.

Take both hands completely off the controller and rest it on a flat surface too.

Watch the stick readouts for fifteen seconds. A healthy stick rests at or very near centre and stays there. An off-centre reading, or one that wanders on its own, is drift.

Run a stick drift test for a clearer readout, and write the value down with the date. Drift is progressive, so a recorded baseline is what lets you spot degradation months later — while a warranty claim is still possible and while cleaning still works.

Also rotate each stick slowly through its full range and confirm it reaches maximum in every direction. A stick that can't reach its corners has range wear even if it rests cleanly.

iOS controller settings worth knowing

iOS has system-level controller options that catch people out.

Settings → General → Game Controller lets you customise button mappings per controller and, on recent iOS versions, per app. If your buttons seem mapped wrongly, check here before assuming the controller is faulty.

Battery level for connected controllers appears in the Batteries widget, which is more convenient than most platforms.

Screen recording and system gestures can occasionally intercept controller input. If a specific button seems to do nothing in a game but registers in the browser test, check whether iOS has bound it to something.

When a controller connects but doesn't work in a game

This is the most common iOS controller complaint, and it's usually not the controller.

Test in Safari first. If a browser test registers your inputs, the hardware and connection are fine, and the problem is app-specific.

The app may not support controllers. Many iOS games are touch-only, and no amount of pairing changes that. Check the App Store listing, which lists controller support.

The app may need controller support enabled in its own settings.

Relaunch the app with the controller already connected, since many only scan for controllers at startup.

Some competitive mobile games deliberately restrict controllers to preserve input parity. That's policy rather than a bug.

Common problems

Controller won't appear in Bluetooth. Confirm it's not still connected to a console. Confirm it's a Bluetooth-capable model — this is specifically what stops many older Xbox One controllers working. Remove any stale pairing from the Bluetooth list and pair fresh rather than reconnecting.

Connects then drops. Usually battery or interference. Charge fully, move away from other 2.4GHz devices, keep line of sight.

Buttons in the wrong places. Check Settings → General → Game Controller for a mapping override, and note that Switch controllers in particular often map unexpectedly on iOS because their layout differs from what apps assume.

Vibration doesn't work in the browser. Expected — Safari doesn't support it. Judge rumble in a game instead.

The short version

iOS supports Xbox, PlayStation, and MFi controllers over Bluetooth, and Safari supports the Gamepad API, so you can test sticks, buttons, and triggers on an iPhone or iPad without an app. The one limitation that matters: Safari does not support the vibration API, so a failed rumble test in the browser tells you nothing about your motors, and installing another browser won't help since all iOS browsers use Apple's engine. Pair by putting the controller in its specific pairing mode, remembering that a pad still connected to a console won't connect to your phone and that older Xbox One controllers using proprietary wireless can't pair at all. Record your stick resting values with the date, since drift is progressive and a baseline is what lets you catch it early.