Xbox Controller on Mac: Wireless Setup & Driver Guide (2026)

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

Most Xbox controllers work on a Mac without a driver, and the model number in the battery compartment decides how yours connects. The short version: the Series X|S and Elite pads run over Bluetooth, most older Xbox One controllers are USB-only, and wireless Xbox 360 pads do not connect to a Mac at all, while the wider Mac controller landscape covers the third-party options.

Where most setup advice goes wrong is treating an Xbox pad on macOS as a single driver problem. It is really three questions stacked on each other: whether macOS can see and read the controller, whether your launcher or translation layer can, and whether the actual game implements controller input at all. A pad can show up in System Settings, register every button in Steam, and still do nothing in the title you launched.

The variable that settles everything is the controller generation. Microsoft shipped Bluetooth only from the Xbox One S revision onward, and Apple added support generation by generation, so a Model 1537 and a Model 1914 need completely different answers despite both being, on the box, an Xbox controller.

As an Amazon Associate, we earn from qualifying purchases.

Before You Start: What macOS Handles on Its Own

Modern Xbox controllers do not need a driver on macOS, because Apple builds the support into the operating system. The version you are running decides which pad is covered:

• macOS Catalina 10.15 added native Bluetooth support for the Xbox Wireless Controller, which is the Model 1708 generation introduced with the Xbox One S.
• The Big Sur generation extended Apple's Game Controller framework to the Xbox Elite Series 2 and the Xbox Adaptive Controller.
• macOS 11.3 added native support for the Xbox Series X|S controller, Model 1914.
• macOS Ventura 13 and later expose a System Settings > Game Controllers panel for checking and customizing supported pads.
• macOS 15 Sequoia materially improved wired Xbox controller support over USB, a change Valve matched in the Steam client.

Any Mac, Intel or Apple silicon, uses this same native stack, so there is no separate M-series driver to hunt down. The Game Controllers panel is the most useful diagnostic tool on the machine: if sticks and buttons respond there but the controller does nothing in a game, your problem has moved out of the pairing and driver layer and into the game or your launcher.

Pair an Xbox Wireless Controller Over Bluetooth

This applies to the Model 1708, the Elite Series 2 in both the full and Core bundles, the Model 1914 Series pad, and the Adaptive Controller.

1. Press the Xbox button to power the controller on.
2. Hold the controller's Pair button until the Xbox light flashes rapidly on the Series and Elite pads. On a Model 1708, the same button drives pairing.
3. Open the Apple menu and go to System Settings > Bluetooth.
4. Find the controller under nearby devices and choose Connect.
5. On Ventura 13 or later, open System Settings > Game Controllers and confirm the sticks, triggers and buttons register.

If the controller pairs but then behaves badly, the fix is usually to forget it and start over rather than to install anything. Forget the device from the Bluetooth list, power-cycle the controller, and pair again. Persistent pairing and reconnection trouble is often a firmware problem rather than a software one, so check the firmware section below before ruling the pad out.

Connect a Wired Xbox Controller Over USB

A wired connection is the cleanest way to test whether a controller works at all, because it removes the radio, the pairing and the battery from the equation. It is also the practical route for a Model 1537 or 1697, which have no Bluetooth.

The cable is the first thing to check. A charge-only USB cable will power a controller without ever making it visible to the Mac, which is why "it charges but nothing happens" is usually a cable problem and not a Mac problem. Use a data-capable cable: the Series, Elite and Adaptive pads take USB-C, while the older Xbox One revisions take Micro-USB. An Anker USB-A to USB-C data cable handles USB 2.0 data and charging; USB-C-only Macs need a USB-C to USB-C cable or a hub.

1. Connect the controller directly to the Mac, or through a known-good hub.
2. On Sequoia and newer, allow the accessory prompt if macOS shows one.
3. Check System Settings > Game Controllers for correct input.
4. If the Mac reads the pad correctly but the game does not, work on the game and launcher layer instead of reinstalling anything.

On pre-Sequoia macOS, wired support for modern Xbox controllers is noticeably less uniform than Bluetooth, so a Series or Elite pad that fails over a cable on an older system is not necessarily faulty.

Xbox 360 Controllers on Mac

Xbox 360 wired and wireless controllers are entirely different problems, and only one of them is still worth attempting in 2026.

A wired Xbox 360 controller uses USB, and current macOS, especially the Sequoia release, often detects it without any driver. Real-world reports show inverted axes, a pad that works in the macOS test screen but not in a specific Unity or Steam title, and inconsistent rumble, so treat it as "often works natively, test against your target game" rather than a guarantee. NVIDIA documents Xbox 360 USB controllers among the gamepads supported for GeForce NOW on Mac, which makes cloud play a reliable way to confirm the pad itself is fine.

A wireless Xbox 360 controller uses a proprietary 2.4 GHz radio and is not Bluetooth, so no amount of pairing will connect it to a Mac. The historical setup paired the Xbox 360 Wireless Gaming Receiver (Model 1086) with a third-party driver, and neither half of that stack is a sound recommendation now: the driver is dead and the genuine receiver is scarce with heavy clone risk in the marketplace. If you own the hardware already, experimentation costs nothing, but do not buy a receiver to build a modern Mac setup. A further trap is the Play & Charge cable, which supplies charging only and does not turn a wireless 360 pad into a wired USB controller.

Xbox Accessories, Elite Profiles and Firmware Without Windows

Microsoft's Xbox Accessories app, the tool for firmware updates, button mapping and Elite Series 2 profiles, is available on Xbox consoles and Windows 10 and 11, with no native macOS version. That leaves Mac owners with two things they cannot do directly in macOS: update controller firmware and build Elite profiles.

Firmware is the more important of the two, because pairing and reconnection behavior can hinge on it. The clean official route without a Windows PC is an Xbox One or Xbox Series console, which will update a supported controller on its own. On an Intel Mac, booting into Windows through Boot Camp gives you the normal Windows workflow. On Apple silicon there is no Boot Camp, and virtual machines should not be treated as a dependable firmware-flashing environment: Parallels can present a Mac-connected controller to Windows as a virtual Xbox pad for games, and CrossOver cannot install Windows hardware drivers at all because it has no Windows kernel.

Elite profiles work around the gap because the controller stores them. Configure up to three custom profiles plus the default on an Xbox console or Windows PC, save them to the controller, then reconnect to the Mac and use them. One nuance matters here: Apple's Game Controller framework can expose the Elite's four paddles as independent inputs when no hardware profile is active, but once an onboard profile is loaded, the paddles follow that stored mapping instead. A paddle that seems to do nothing on the Mac is often assigned through a profile rather than broken. If a stick behaves inconsistently, stick drift testing will tell you whether it is a hardware issue, since macOS software cannot repair physical sensor wear.

Mapping a Controller to Keyboard and Mouse

Some Mac games expose keyboard and mouse controls but no gamepad input, and that is the one case where a mapper earns its place. Confirm first that the controller works natively in System Settings, then add a single mapper, not several.

• Joystick Mapper is a Mac App Store utility that maps buttons, axes and triggers to keyboard and pointer actions over USB or Bluetooth. Its minimum is macOS 10.9.
• Gamepad Mapper requires macOS 12 or later, lists Xbox Series, Xbox One and Xbox 360 controllers, and includes dead-zone controls. Several controller features sit behind in-app purchases.
• The maintained community fork of Enjoyable supplies a universal Apple-silicon and Intel build reporting support across recent macOS versions.
• Controlly is aimed at driving the pointer, scrolling and keyboard shortcuts from a gamepad, which suits desktop and remote control more than adding XInput to a game.
• ControllerMate is limited to roughly macOS 10.13 and 10.14 and is not a modern option.

A mapper that synthesizes keystrokes needs Accessibility permission under System Settings > Privacy & Security, which is expected behavior rather than a red flag. The most common failure after installing one is double input: a physical controller and a virtual one both visible to the game, or Steam Input and a mapper running at the same time. Keep a single translation layer active, and compare Steam Input on against off when a game misbehaves. The full PC controller mapping guide covers the same conflict in more depth for cross-platform setups.

If you would rather not fight a legacy pad at all, the cleanest replacements are controllers with documented Mac support. The 8BitDo Pro 2 Hall Effect pairs Bluetooth 4.0 and USB-C with Hall-effect sticks, two back buttons and profiles, and 8BitDo documents macOS 13.2 and later. The 8BitDo SN30 Pro covers the same ground in a compact, D-pad-first shell. A Sony DualSense is another safe fallback, since Apple added native support for it in the same macOS 11.3 generation as the Series Xbox pad, though its adaptive triggers and advanced haptics depend on the game.

Steam recognizes Xbox-family controllers through its controller settings, but Valve is explicit that support ultimately depends on the individual game, so a pad working in Big Picture does not promise a working title. Xbox Cloud Gaming accepts compatible Bluetooth or USB controllers in supported browsers, and GeForce NOW documents both Xbox Wireless pads over Bluetooth or USB and Xbox 360 pads over USB on Mac. When a controller works in a cloud service but not in a native game, the game's own controller implementation is the suspect, not your Bluetooth pairing.

Common Mistakes to Avoid

• Assuming every Xbox One pad has Bluetooth. Models 1537 and 1697 do not; Model 1708 introduced it.
• Buying the Xbox Wireless Adapter to add wireless to a Mac. It is a Windows accessory and does nothing on macOS.
• Installing 360Controller on macOS 11 or newer. Its own final release says it will not work, and there is no Apple-silicon build.
• Expecting a Play & Charge cable to make a wireless Xbox 360 controller wired. It charges only.
• Reading "System Settings sees it" as "the game will work." Game-level support is a separate layer from macOS recognition.
• Running Steam Input and a keyboard-and-mouse mapper at once, which produces double inputs and flickering prompts.
• Debugging a game before testing the controller in System Settings > Game Controllers, which sorts a pairing problem from a game problem in seconds.
• Using a charge-only cable for a wired setup, which powers the pad without making it detectable.

Frequently Asked Questions

Conclusion

The Xbox-on-Mac problem is almost always a generation problem rather than a software one. A Series X|S or Elite pad connects over Bluetooth with no driver at all, a Bluetooth-capable Model 1708 works on Catalina and later, and the older Xbox One and 360 hardware needs either a USB cable or a replacement rather than a driver from a bygone era. The 360Controller package and the Xbox Wireless Adapter belong in the same drawer: useful history, wrong tool for a current Mac.

If you are buying a controller specifically for a Mac, the safest single pick is the current Xbox Wireless Controller, which Apple supports natively from macOS 11.3 and which pairs as readily as any Bluetooth accessory. For Xbox 360 hardware, prefer wired testing on current macOS over chasing a scarce wireless receiver. For everything else, decide by model number first and stop installing drivers you do not need.

Where to go next: the complete Mac controller compatibility guide for the non-Xbox options, the 8BitDo lineup review if you want documented Apple support out of the box, the PC controller mapping guide for translation-layer conflicts, and the Steam Deck setup guide if your Xbox pad is heading to SteamOS instead.