Path of Exile / Keybinds

PoE keybind setup: separate PoE 1 mouse binds from PoE 2 WASD.

PoE 1 and PoE 2 ask different questions of your hands. Start with the movement mode, keep defensive actions reachable, then place skills, flasks, dodge, labels, and menus around that choice.

Choose the input path Open the PoE setup hub

ScopePoE 1 and PoE 2

InputsMouse, WASD, controller

ReviewedAug 10, 2026

PoE 1Click movement baseline

PoE 2Choose mouse, WASD, or pad

Every versionRecheck after patches

Keep PoE 1 movement, core skills, flasks, and defensive actions in a stable mouse-and-keyboard map. In PoE 2, choose mouse, WASD, or controller first, then build around movement and test the active build. The right map follows the input mode, not a copied key list.

PoE 2's WASD and controller paths change which keys do the moving. Rebuild the map when the active build needs a different movement or flask layout.

PoE keybind setup decision
Path	Starting map	Best fit	Watch for
PoE 1 mouse and keyboard	Mouse movement or attack, nearby skill keys, a consistent flask row.	Players who want the classic cursor and menu workflow.	Dense builds can create conflicts between flasks, skills, and utility.
PoE 2 mouse	Cursor movement with skills and utility on the keyboard or mouse.	Players who prefer the PoE 1 style and frequent inventory work.	Check current action-bar and menu behavior in the active version.
PoE 2 WASD	WASD movement, mouse aim, nearby skills, and dodge within reach.	Players who want independent movement and aiming.	Do not place active skills on movement keys or assume every build uses the same map.
PoE 2 controller	Controller HUD, analog movement, and a pad-specific action map.	Combat-first sessions and players who prefer a gamepad.	Inventory, trade, crafting, and input switching can change the session.

PoE 1 baseline

Keep the classic loop visible.

Keep movement or attack on the mouse path you already understand.
Place the main skill loop on keys you can press without losing cursor control.
Give life, utility, and defensive flasks a consistent row. The familiar 1-5 pattern is a starting point, not a build rule.
Leave room for movement skills, guard skills, temporary buffs, and interaction actions.
Test the full loop in town, a low-risk map, and a trade or stash workflow before changing hardware.

PoE 2 baseline

WASD needs a clear ring around movement.

Choose the input mode in the current client before assigning skills.
If using WASD, leave W, A, S, and D available for movement and keep the mouse free to aim.
Put the main skill loop on nearby keys or mouse buttons that do not force your movement hand to leave the block.
Put dodge, the most important defensive action, and interaction where you can reach them while moving.
Test the mode in combat and in menus. A good combat map can still feel poor during inventory or trade.

Reserve the controls that must be reached without thought. Then decide where build-specific skills can live.

Life and mana

Keep the recovery row obvious.

Use a consistent location across characters where the game and build support it. Do not hide the action behind a modifier that you cannot repeat.

Utility flasks

Separate repeated utility from panic tools.

Assign the actions you press often to a row you can audit. Recheck the pattern when the current version changes flask behavior.

Dodge and movement

Protect the movement hand.

In PoE 2 WASD, dodge and movement compete for the same attention. Test the pair together instead of choosing one in isolation.

Build additions

Change one layer at a time.

When a guide adds a new skill, first identify its job. Do not move the whole keyboard because one utility action needs a new home.

Troubleshooting

When a bind stops behaving, isolate the layer.

Confirm the active input mode and recheck the movement row.
Test movement outside chat and away from an NPC interaction.
Temporarily move the new skill or utility action to a known free key.
Recheck the current patch notes and official forum reports before treating a bug as a hardware failure.
Keep a mouse and keyboard path available when the controller or WASD mode becomes a menu bottleneck.

Failure test

Find the bind that fails under pressure.

A map that looks tidy in town can break when movement, a flask, a dodge, and an interaction arrive together. Test the collisions before you move hardware or copy another build's layout.

Trigger movement and the most important defensive action together.
Use the same hand to reach a flask, skill, and label action.
Open inventory, stash, and trade after a combat test instead of treating menus as a separate game.
Change one bind, then repeat the same loop. Keep the old map until the new one survives the test.
Write the active game and patch beside the layout so a PoE 2 change does not silently become a PoE 1 rule.

PoE / Hardware

Need to choose the physical input?

The existing PoE guide compares controller and mouse/keyboard across combat, inventory, trade, labels, and switching.

Compare input methods

How I checked this page

PoE 1 continuity, PoE 2 movement choice.

PoE 1 favors a stable map for the active mode. PoE 2 adds a movement decision that should stay repeatable before you add binds.

WASD and controller behavior are patch-sensitive. Recheck the live client when a bind stops responding after chat or interactions.

Path of Exile home Path of Exile forum thread

What is the best PoE keybind layout?

The best map keeps movement, defenses, and the actions your build uses most in reachable positions. Exact keys should follow the movement mode and the player.

Are PoE 1 and PoE 2 keybinds the same?

No. PoE 2 adds distinct mouse, WASD, and controller workflows. Rebuild the movement ring for the active game instead of copying a single list.

Where should I put flasks?

Use a consistent, easy-to-audit row for the flask actions your build actually uses. Recheck the active game and current flask system before treating a row as universal.

Is WASD better in PoE 2?

It can fit players who want independent movement and aiming. Mouse and controller remain valid paths, especially when menu work or input preference changes the decision.