Using a controller
A keyboard is fine for a while. A controller is better for anything with platforming in it, and modern browsers support them without any software to install.
How the browser sees a controller
Browsers expose gamepads through a standard interface. When a controller matches a common layout, the browser reports it in a normalised form: face buttons, shoulders, triggers, sticks and a directional pad all arrive at fixed positions regardless of the make.
That is why an Xbox pad, a DualShock, a Switch Pro controller and an 8BitDo all work here without being configured. They all describe themselves in the same standard layout, so a single default mapping fits them all.
Unusual controllers, especially adapters for older hardware, sometimes do not match that layout. They still work, but the buttons may land in the wrong places until you remap them, which takes a few seconds.
Getting connected
- Plug the controller in, or pair it over Bluetooth.
- Open an emulator page and press any button on the pad. Browsers deliberately hide gamepads until you press something, so nothing appears until you do.
- A controller badge appears in the header once it has been seen.
If the badge never appears, the usual cause is that the browser has not received a button press from that device yet. Press a face button rather than moving a stick, since a slightly drifting stick may not register as a deliberate input.
The default layout
| Game Boy | Controller | Keyboard |
|---|---|---|
| Directional pad | D-pad or left stick | Arrow keys |
| A | Right face button | X |
| B | Bottom face button | Z |
| L and R (Advance only) | Left and right shoulders | A and S |
| Start | Start | Enter |
| Select | Select or Back | Shift |
| Fast forward | Right trigger | Hold Space |
The left stick doubles as the directional pad, which suits controllers whose pad is uncomfortable for long sessions.
Changing the buttons
Press Controller in the header. You will see the detected pad and a list of every input. Press Rebind next to one, then press the button you want to use for it.
Mappings are stored per controller, identified by how the device describes itself. So an unusual pad only needs setting up once, and plugging in a different controller later does not disturb it. Reset to defaults undoes your changes for the connected pad.
Sound stays off until you touch the page
This one confuses people, so it is worth stating plainly: browsers block audio until you interact with the page, and a gamepad button press does not count. The browser only accepts a real click, tap or key press as permission to start sound.
So if you load a game and drive it entirely with a controller, it will be silent. Click anywhere on the page once and audio starts. This is a browser security rule, not something an emulator can opt out of.
Steam Deck
The built in controls report themselves as a standard gamepad, so they work with no setup in desktop mode. Two things are worth knowing.
If you launch the browser from Gaming Mode, Steam's own input layer may intercept the controls and send them as mouse and keyboard instead of as a gamepad. If your inputs are moving a cursor rather than the game, change the controller layout for the browser to a gamepad template, or use desktop mode.
The trackpads and gyro are not used. Fast forward sits on the right trigger, which is comfortable there.
Phones and tablets
On a touchscreen, on screen controls appear automatically, with shoulder buttons added on the Game Boy Advance page. A Bluetooth controller also works if your device supports one, and pairing it does not remove the touch controls.
For a better time on a phone, turn the device sideways and add the page to your home screen so it opens without browser toolbars taking up room.
If something is not working
- No badge appears. Press a face button on the pad while the emulator page is focused. Click the page first if you have been using another window.
- Buttons are in the wrong places. The controller does not match the standard layout. Rebind them once and it is remembered.
- Inputs stop when you click away. That is deliberate. The game pauses when the window loses focus. Click back on the screen to carry on.
- A direction sticks. A worn stick may be drifting past the threshold. Use the directional pad, or rebind that direction to the pad explicitly.
Read next
Troubleshooting for sound, speed and saving problems.