If Fortnite suddenly ignores your controller on PC — the sticks are dead in a match, or Windows never detects the pad at all — you are not alone, and in almost every case it is a five-minute fix. This is one of the most-searched Fortnite PC problems, and it splits into two very different situations: the controller isn't detected at all, and the controller works fine in the menus but goes dead the second a match starts. They have different causes and different fixes, so the first job is figuring out which one you have.
This guide covers both, in the order that resolves the most cases fastest, plus the current Chapter 7 Season 4 context — because Epic has been squashing controller-related bugs on the live build, and one of your "fixes" might just be waiting for a patch.
Quick answer: If your controller works in the lobby but dies in a match, open Settings → Input and set Ignore Gamepad Inputs = OFF and Lock Input Method as Mouse = OFF — those two toggles silently kill your pad in-game. If the controller isn't detected at all, plug it in with a USB cable before launching Fortnite, and for a PlayStation controller enable Steam Input or install DS4Windows (Windows treats PS pads differently from Xbox pads). Xbox controllers are plug-and-play on Windows 10/11; DualSense/DualShock usually need Steam or DS4Windows. This applies to Fortnite Chapter 7 Season 4 "Override" on the current build (v42.20). Epic has actively patched controller bugs this season, so if a fresh update broke your pad, check @FortniteStatus before reinstalling anything.
First: which problem do you actually have?
Before you touch a single setting, work out which of these three you're looking at. It saves you from "fixing" the wrong thing.
- Not detected anywhere — the controller does nothing in menus, in-game, everywhere. This is a Windows/connection/driver problem, not a Fortnite problem. Go to the "Controller not detected at all" section.
- Works in menus, dead in-game — you can navigate the lobby with the pad but your character won't move once the match loads (or you can only zoom in and out). This is almost always a Fortnite input-setting or Steam Input conflict. Go to "Works in the menu but not in the match."
- Worked yesterday, broke after an update — everyone lost controller function around the same time. That's a live bug, not your setup. Go to "Is it a current Fortnite bug?"
Fortnite is built around XInput, the controller standard Windows uses for Xbox pads. That single fact explains most PC controller pain: an Xbox controller speaks XInput natively and just works, while a PlayStation controller speaks a different language (DirectInput) and needs a translator — Steam Input or DS4Windows — before Fortnite recognizes it as a real controller.
Controller not detected at all on PC
Run these in order. Most "not detected" cases are solved by step 1 or 2.
1. Plug it in with a cable, before you launch Fortnite. Wireless is convenient and flaky. A wired USB connection removes Bluetooth dropouts and guarantees the pad has power. Just as important: connect the controller before you open Fortnite. Some builds only bind a controller that's already present at launch, so a pad you plug in mid-session can go unseen. Cable in first, then launch.
2. Swap the USB port and the cable. Epic's own device-troubleshooting guidance is blunt about this: if a device stops being recognized, try a different USB port. Front-panel ports on a desktop are often underpowered — use a rear port wired straight to the motherboard, or a powered USB hub. A dead or charge-only cable (some cables carry power but no data) will also make a controller "invisible." Test with a cable you know does data transfer.
3. Confirm Windows sees it — the joy.cpl test. This is the single most useful diagnostic because it tells you whether the problem is Fortnite or your PC. Press Win + R, type `joy.cpl`, and hit Enter. Select your controller, click Properties, and press buttons / move the sticks. If the inputs light up here, your hardware and drivers are fine and the problem is inside Fortnite (skip to the in-game section). If nothing registers in joy.cpl, Fortnite was never going to see it — it's a driver, cable, or hardware issue.
4. Xbox controller: it should be plug-and-play. Windows 10 and 11 recognize Xbox Wireless, Series X and S, and Xbox One controllers natively over USB or Bluetooth, with no extra software. If an Xbox pad isn't detected, it's almost always the cable/port (step 2) or a firmware update it hasn't installed — open the Xbox Accessories app from the Microsoft Store, connect the controller by USB-C (firmware updates don't run reliably over Bluetooth), and apply any update.
5. PlayStation controller: use Steam Input or DS4Windows. A DualSense or DualShock 4 uses DirectInput, which Fortnite doesn't natively read as a game controller on PC. Two ways to fix that: add Fortnite to Steam and let Steam Input translate the pad, or install DS4Windows, which emulates an Xbox 360 controller so Fortnite sees a supported XInput device. DS4Windows relies on the ViGEmBus driver as the bridge — if it prompts you to install ViGEmBus, do it, or the emulation won't work. DualSense has partial native Bluetooth support on Windows, but wired + one of these tools is the reliable route.
6. Disconnect other input devices. If you have a second controller, a racing wheel, a flight stick, or a plugged-in phone charging as a device, Fortnite can bind "player 1" to the wrong one and leave your real pad idle. Unplug everything except the controller you want to use, then relaunch.
7. Update or reinstall drivers, and charge wireless pads. Stale controller drivers cause dropped and missed inputs. Reinstall the driver (for third-party pads, reinstall the tool's driver too), and if you're wireless, make sure the battery is actually charged — a low battery drops the connection and reads as "not detected."
Works in the menu but not in the match
This is the most common — and most annoying — version, and it's the one players are hitting most this season. Your pad navigates the lobby fine, then your character won't move, or you can only zoom in and out. It's rarely a hardware fault. Work through these:
1. Turn off the two toggles that kill your controller in-game. In Settings, open the input/keyboard-and-mouse tab and check:
- Ignore Gamepad Inputs — must be OFF. If this is on, Fortnite literally discards controller input during a match, which is exactly the "dead in-game" symptom.
- Lock Input Method as Mouse — must be OFF. When on, Fortnite locks you to mouse-and-keyboard once you're in, ignoring the pad.
Epic itself pointed players to these settings when an input-swap bug was breaking controllers. They're the first thing to check, every time.
2. Set a real Controller Configuration. Go to Settings → Controller, pick an actual preset (Builder Pro is the default competitive layout), and hit Apply. A blank or mismatched preset means the pad is connected but has nothing bound, so nothing happens in-game.
3. Kill the Steam Input conflict. This is the hidden cause of "works in menu, dead in-game." If you launch Fortnite through the Epic Games Launcher but Steam is running — especially in Big Picture mode — Steam's controller layer can intercept your pad's input before Fortnite ever receives it. Open Steam → Settings → Controller and disable desktop/generic controller support, or turn Steam Input off for the Fortnite shortcut. If you're launching Fortnite from Steam, the opposite can be true — make sure Steam Input is enabled and set to a gamepad profile.
4. Reconnect the controller mid-session. If it dropped out during play, unplug and replug (or re-pair) the pad, then load a new match. This forces Windows and Fortnite to re-enumerate the device.
5. Verify your game files. In the Epic Games Launcher, go to Library → Fortnite → the three dots → Manage → Verify. This repairs corrupted config and input files. Per Epic Store support, "Your saved data will not be affected" — so you won't lose settings or progress by running it.
Is it a current Fortnite bug — or your setup?
Here's the context that most guides miss. Chapter 7 Season 4 "Override" has had a run of controller bugs that were Epic's fault, not yours. In early September 2026, controller players couldn't build or edit properly, and Epic worked through it publicly:
"We released an update today that should have fixed the keyboard and mouse building/editing bug, and are working on the controller bug / shotgun editing bugs now. We'll post an update when we have more info and this resolved."
— @FortniteStatus, replying to a player report, September 4, 2026 (x.com/FortniteStatus)
A day later, on September 5, Epic confirmed the fix: "We've fixed the building & editing bug that would prevent players, especially on controller, from quickly building or editing."
The takeaway: if your controller broke right after an update, and other players are reporting the same thing at the same time, don't reinstall drivers and rebuild your whole setup — it may be a server-side or client bug that Epic is already patching. Check @FortniteStatus on X and status.epicgames.com first. If it's a known issue, the fix is a patch, not you. Fortnite runs on a roughly two-week update cadence (v42.10 landed September 3, v42.20 on September 17, with the next update expected around October 1), so a hotfix is rarely far off.
If, on the other hand, only you are affected and everyone else's pad is fine, it's a local setup issue — work back through the sections above.
Which controllers work with Fortnite on PC?
- Xbox controllers (Series X and S, Xbox One, Xbox Wireless): natively supported over USB or Bluetooth via XInput. No extra software. This is the smoothest option on PC.
- PlayStation DualSense (PS5) and DualShock 4 (PS4): work, but on PC they usually need Steam Input or DS4Windows + ViGEmBus to be recognized as a proper controller.
- Nintendo Switch Pro and most third-party pads: function through Steam Input / XInput emulation rather than native Fortnite support.
Epic doesn't publish a single enumerated "supported PC controllers" list, so treat this as commonly-supported hardware rather than a guaranteed compatibility chart. When in doubt, the joy.cpl test (above) tells you whether Windows sees your specific pad.
FAQ
Why does my controller work in the Fortnite menu but not in the match? Because the two problems have different causes. Menu navigation and in-match input are handled separately, so a pad can be "connected enough" to move around the lobby while an in-game setting (Ignore Gamepad Inputs / Lock Input Method as Mouse) or a Steam Input conflict blocks it during play. Turn both of those settings off and disable Steam's controller layer if you launch from Epic.
How do I get my PS5 controller working in Fortnite on PC? Add Fortnite to Steam and enable Steam Input, or install DS4Windows (with the ViGEmBus driver) so Windows presents your DualSense as an Xbox controller. Connect it by USB for the most reliable result. A raw DualSense over Bluetooth with no helper software is the setup most likely to be ignored in-game.
Do Xbox controllers need any extra software for Fortnite on PC? No. Windows 10 and 11 recognize Xbox controllers natively via USB or Bluetooth. If an Xbox pad isn't working, it's usually the cable/port, a firmware update pending in the Xbox Accessories app, or an in-game setting — not missing software.
My controller broke right after a Fortnite update — is it me? Possibly not. Chapter 7 Season 4 has had controller bugs Epic patched directly, and Epic announces these on @FortniteStatus. If lots of players report the same failure at the same time, wait for the hotfix and check status.epicgames.com before reinstalling anything.
Will verifying my Fortnite files delete my settings or skins? No. Verifying game files in the Epic Games Launcher only repairs damaged install files. Epic's support states your saved data will not be affected — your progress, locker, and settings stay intact.
How do I test whether it's Fortnite or my PC? Press Win + R, type `joy.cpl`, and press your controller's buttons in the properties window. If inputs register there, your hardware is fine and the issue is inside Fortnite. If nothing registers, it's a driver, cable, or hardware problem to fix at the Windows level first.
The bottom line
Ninety percent of Fortnite controller problems on PC come down to three things: an in-game setting quietly ignoring the pad, a Steam Input layer stealing your inputs, or a PlayStation controller that needs Steam or DS4Windows to be seen at all. Start by identifying whether the pad dies everywhere or only in-match, run the joy.cpl test to split Fortnite from Windows, and — if a patch just dropped — check @FortniteStatus before you tear your setup apart. This all applies to Chapter 7 Season 4 "Override" on the current build; re-check Epic's status page after any new update.
Playing more than Fortnite? If you're grinding ranked, currency, or carries in other games, timesaver.gg runs live boosting and in-game services across 19+ titles.
