8BitDo controller not connecting

8BitDo 8BitDo controllers / Windows 10, Windows 11, Switch Last verified October 2026 Risk: none
Quick answer

An 8BitDo controller won't connect when the pairing mode is wrong. Hold the pairing button, select the right mode, then pair over USB first.

Match the mode to the host first

Almost every failed first connection is a mode mismatch. The pad boots in whatever mode it used last, and that is rarely the one the host expects.

HostSwitch positionWhat the host should see
Windows PCXXbox Wireless Controller
SwitchSPro Controller
Android phoneD or A8BitDo / generic gamepad
macOSM or Apple modeWireless Controller

Check the printed legend on the pad — on the Pro 2 and Ultimate the switch is on the back edge, and it is easy to nudge into the wrong notch when the pad goes into a case.

Pairing sequence that works

  1. Set the mode switch with the pad switched off, then turn it on.
  2. Hold Start for about three seconds, then hold the small pairing button on the top edge until the LED blinks rapidly.
  3. On Windows, open Settings → Bluetooth & devices → Add device and pick the controller. Wait for “Connected”, not just “Paired”.
  4. If Bluetooth never lists the pad, plug in a USB cable first. The cable installs the driver and confirms the pad works, which separates a radio problem from a driver problem.

If it pairs but stays silent

A pad that pairs and then does nothing is usually in the wrong mode for that host, or the host has it as an audio/input hybrid device. Re-check the switch position, then test in the 8BitDo app’s input view before blaming the game.

If it still won’t pair

Remove every old 8BitDo entry from the host’s Bluetooth list — duplicates are the most common cause of a pairing that times out on the second attempt. Then reboot the host with Bluetooth off, turn it back on, and pair once.

Charging matters here too: a nearly flat pad blinks but never completes the handshake. Leave it on a cable for an hour before you retry.

Last verifiedOctober 2026
CorrectionsSpotted an error? See our editorial guidelines