8BitDo button mapping
8BitDo buttons feel wrong when the profile is off. Open the 8BitDo app, load the right profile, then rebind the back buttons.
What the pad is actually sending
An 8BitDo pad is not one controller — it presents a different device depending on the position of the mode switch. That single fact explains most “my buttons are wrong” complaints.
| Mode | Reports as | Use it for |
|---|---|---|
| X | Xbox controller (XInput) | Windows games, most emulators |
| D | Generic HID / DirectInput | Older emulators that ignore XInput |
| S | Switch Pro Controller | Switch, and emulators with a Pro profile |
If the switch sits in D while the emulator expects an Xbox pad, every face button lands on the wrong action and the triggers may not register at all. Check the switch before you touch any software.
Writing a profile to the pad
- Install 8BitDo Ultimate Software for your model from the support site.
- Connect by USB cable for the first profile write — wireless writes can fail silently.
- Open Custom Profiles and load the profile that matches your platform.
- Select a back paddle, choose Assign, then press the button or key you want it to send.
- Hit Save to controller, not just Save. A profile that stays in the app disappears the moment you unplug.
The two back paddles
P1 and P2 ship unbound. They are the only buttons you can map to keyboard keys, which is what makes them useful for emulator hotkeys — save state, fast forward, or a mapper button. Macros belong here too: a single paddle can send a short sequence instead of one key.
If a button still does nothing
Test in the 8BitDo app’s own input view first. If the app shows the press, the pad is fine and the emulator is dropping it — rebind inside the emulator instead. If the app shows nothing, the profile was not written to onboard memory; repeat the save step over USB.
For controllers that never appear in the app at all, the pairing itself is the problem — see 8BitDo controller not connecting.