WASD Swapped With Arrow Keys? How to Switch Them Back
You press W and the cursor jumps up a line instead of typing a letter. You press the up arrow and a w appears. Nothing is broken: your keyboard has a built-in swap layer that exchanges the WASD cluster with the arrow keys, and it has been switched on — almost always by accident, with a two-key shortcut pressed while reaching for something else.
It takes seconds to undo once you know which shortcut your keyboard uses. The one genuinely useful step first is working out where the swap is happening, because a keyboard-level swap and a game-level rebinding look identical while you are inside the game.
Find out whether W is sending a letter or an arrow.
Run the keyboard test →Symptom check: which cause is yours?
| Symptom | Likely cause | Primary fix |
|---|---|---|
| WASD acts as arrow keys in every application | The keyboard's hardware swap layer is toggled on | Press the Fn shortcut for your board, usually Fn + W |
| Swap happens in one game only | Corrupted or altered in-game key bindings | Reset that game's controls to default |
| WASD types entirely different characters | Wrong OS keyboard layout (AZERTY, Dvorak, Colemak) | Set the input method back to your physical layout |
| Swap persists on a second computer | Onboard memory profile on the keyboard itself | Factory-reset the keyboard, or fix the profile in its software |
| Only some keys are swapped, not the full cluster | A remapping utility such as PowerToys or AutoHotkey | Close or clear the remapping tool's active rules |
First: find out where the swap lives
This takes ten seconds and decides everything that follows. Leave the game, open a text editor or the keyboard test, and press W.
- It types w: your keyboard is fine. The swap only exists inside that game, so skip to the in-game bindings section.
- It moves the cursor, or registers as Arrow Up: the swap is in the keyboard hardware and affects every application. Start with the Fn shortcut below.
- It types some other character entirely: this is not a swap at all, it is a keyboard layout mismatch. Jump to the layout section.
The keyboard test is more informative than a text editor here because it shows the physical key position (event.code) separately from the character produced (event.key). With a hardware swap, pressing W lights up ArrowUp — the keyboard rewrote the signal before it left the device, so the computer genuinely believes you pressed the arrow key.
1. Toggle the hardware swap off
Most gaming keyboards — Redragon, Royal Kludge, Corsair, Akko, Ducky, Keychron, Razer, and much of the compact market — ship with a swap layer intended for games that cannot be rebound. The toggle is a two-key combination, and manufacturers have never agreed on which one. Try these in order, pressing each once and then testing W:
- Fn + W — by far the most common, and the first thing to try.
- Fn + Windows key — also used for the Windows-key lock on some boards, so test W afterwards to see which one it did.
- Fn + Left Arrow or Fn + Up Arrow — the mirror-image shortcut, common on Royal Kludge and similar 60 and 75 percent boards.
- Fn + Esc held for three to five seconds — on many boards this is a factory reset, which clears the swap along with every other custom setting.
- Fn + Spacebar held for three seconds — the reset combination on some Redragon and Ajazz models.
Press one combination, test, and only then try the next. Pressing several in a row makes it impossible to tell which one worked, and some of these shortcuts toggle other features — Windows-key lock, an LED profile, a Bluetooth channel — that you will then need to undo separately.
If none of them work, check the keyboard's manual or product page for "WASD swap", "arrow swap", or "gaming mode". It is worth spending two minutes on this: manufacturers reuse layouts across ranges, and the correct combination is always documented somewhere.
2. Power-cycle the keyboard
If the shortcut does not respond, the keyboard's controller may be holding a stuck modifier state — a stuck Fn is a common cause, and it makes every other key behave as though it is on a secondary layer.
Unplug the USB cable, or switch a wireless board off and remove its dongle. Wait ten to fifteen seconds so the controller fully loses power and its volatile state clears, then reconnect. On a board with a battery, also hold the power switch off for the full wait rather than tapping it. Then try the Fn shortcut again.
3. Reset the onboard profile
Keyboards with onboard memory store the swap in the keyboard itself, which is why it survives a reboot and follows the board to another computer. Two ways to clear it:
Through the manufacturer's software — iCUE for Corsair, Synapse for Razer, the Keychron or VIA web configurator, and so on. Open the active profile, look at the key assignments for W, A, S, D and the arrow cluster, and reset them to default. If you have several onboard profiles, check whether the keyboard has simply switched profiles; there is usually a shortcut such as Fn + 1 through Fn + 4 to select one.
Through a hardware factory reset — normally Fn + Esc held for several seconds, or a specific combination listed in the manual. This wipes lighting effects, macros, and custom bindings as well, so use it after the software route rather than before.
For QMK or VIA boards, open the configurator and inspect each layer. A swap is often a leftover keymap edit on a layer you forgot about rather than a built-in feature, and it will persist until that layer is corrected or the board is reflashed with a known-good keymap.
4. Fix in-game bindings
If W types w outside the game, the keyboard is innocent and the game's control configuration is the problem. This happens after a settings file gets corrupted, after a controller profile is applied, or when a game auto-detects a layout incorrectly.
Open the game's Controls or Key Bindings screen and use Reset to Default rather than rebinding keys individually — a partial rebind leaves conflicting assignments that cause stranger problems later. If resetting inside the game does not stick, delete or rename the game's settings file so it regenerates on the next launch; the location is usually documented in the game's support pages or its community wiki.
Also close any remapping utilities running in the background. Windows PowerToys Keyboard Manager, AutoHotkey scripts, Steam Input controller layouts, and some streaming or macro tools all apply their own remapping, and a rule left over from another game will silently follow you into this one.
5. Check the operating system keyboard layout
If WASD produces unrelated characters rather than arrow movement, nothing is swapped — your OS is interpreting the keyboard as a different physical layout. An accidental press of Win + Space (Windows) or Ctrl + Space (macOS) cycles input methods and is the usual trigger.
Windows: go to Settings → Time & Language → Language & Region, open the language options, and confirm the correct keyboard is listed, for example US QWERTY. Remove layouts you never use so the cycle shortcut has nothing to switch to.
macOS: go to System Settings → Keyboard → Input Sources and remove any source you did not add deliberately.
Layout problems are easy to confirm on the keyboard test: the physical position stays correct while the produced character is wrong, which is exactly the signature of a layout mismatch rather than a hardware fault.
Undone the swap? Confirm W types a letter and the arrows still move.
Re-run the keyboard test →FAQ
Why do gaming keyboards have this swap feature at all?
It exists for games that do not let you rebind movement controls — a long tail of older titles, emulated games, and browser games hard-wired to the arrow keys.
Swapping the clusters in hardware lets a player keep the WASD hand position they already know without touching the game's settings. Left-handed players who prefer the arrow cluster use the same feature in the other direction.
How do I tell whether the swap is in the keyboard or the game?
Leave the game, open a text editor or a keyboard tester, and press W. If it types w, the keyboard is fine and the game's key bindings are the problem. If it moves the cursor up or registers as Arrow Up, the swap is in the keyboard and applies to everything.
Can the swap turn on by accident?
Yes, and that is how it usually happens. The toggle is a two-key Fn combination sitting under the same hand position as common shortcuts, so it is easy to trigger while reaching for something else.
Because most keyboards store the setting in onboard memory, it survives a reboot and travels with the keyboard, which makes it feel like a much more serious fault than it is.
Does the swap follow the keyboard to another computer?
On most keyboards, yes. The swap is applied by the keyboard's own controller before the signal reaches the computer, so no driver is involved.
That also makes it a useful test: plug the keyboard into a different machine, and if the behaviour follows it, the cause is definitely the keyboard rather than your operating system.
My keyboard has no Fn key. What now?
Full-size boards without an Fn key rarely have a hardware swap layer, so the cause is almost certainly software: a remapping utility, a game binding, or an onboard profile applied through the manufacturer's software.
Close any remapping tools, reset the game's controls, and check the keyboard's configuration software for a custom profile.