Epic Games Store Every other shooter asks you to reach one key at a time. A build fight asks for wall, stairs, floor, cone, edit, confirm and reset inside a second — and you are dead the moment you stop moving to find them. That single constraint decides whether a layout works, and the shipped default fails it outright: four of the seven sit on the function row.
WASD is outlined in cyan — that is where three fingers already live. The dashed box is everything the same hand can still reach without letting go. Type your binds in, or load a reference layout, and every key you use is painted by whether it falls inside it.
—
Everything above is a keyboard problem. Epic never had it on controller: Builder Pro puts all four pieces on shoulders and triggers, so the thumbs never need to leave the sticks. Which leaves the two constraints that belong to this layout alone — whether your thumbs actually stay down when you build under pressure, and how much slower your two trigger pieces are than your two bumper pieces. A browser can read both off your own pad.
RT / R2 The piece you throw most, on an input that has to travel before it registers.
LT / L2 Half of all height gained, also on a trigger — and usually the second half of a wall-and-ramp.
LB / L1 A bumper: a switch, no travel. Nothing to tune here.
RB / R1 Also a bumper, and the reason a box tops off faster than it walls up.
Push both sticks as if you were strafing and aiming, then place the four pieces without letting either stick fall back.
Wall and stairs sit on the triggers. The page times how far yours have to move before the press registers.
Not skill and not a setting: a bumper is a switch and a trigger is a ramp. Your two most used pieces are the two on ramps. If your ramps feel late in a fight, that is a real measurement rather than a feeling, and the number above is it.
Almost nobody notices they stop strafing to build. It is invisible from inside the game because the piece still goes down — the cost is entirely in where you were standing while it did. This drill exists because it is the one part of building you cannot self-assess.
The bench above scores reach, which is a geometry problem your fingers solve once. This scores a habit under load, which is a motor problem you solve continuously. Switching input device does not carry either result across, and the page does not pretend it does.
These are the building binds exactly as the game ships them on PC, read from the verified entry behind /controls/fortnite/. Load “Shipped default” in the bench above and watch it score.
| Action | Default key | Reachable while moving |
|---|---|---|
| Wall | F1 | No — hand leaves WASD |
| Floor | F2 | No — hand leaves WASD |
| Stairs | F3 | No — hand leaves WASD |
| Roof | F4 | No — hand leaves WASD |
| Trap / place item | F5 | No — hand leaves WASD |
| Edit | G | Yes |
| Rotate piece | R | Yes |
| Change material | Mouse 2 | Yes |
Preferences are choices between things that both work. A key you cannot press while moving does not work for an action you only ever use while moving. That is the whole argument, and it is why the rebuild is universal rather than fashionable.
A 60% keyboard has no function row at all, so the default pieces live on a layer behind a modifier. The bench accounts for board size in the reach column — pick yours before judging a layout you found online.
On controller, Builder Pro puts every piece on a shoulder or trigger so the thumbs never leave the sticks. It is the same rule this page tests, applied by the developers — which is why the controller default is in far better shape than the keyboard one.
The bench above tests the layout. These test the hardware it runs on.
There is no single answer, but there is a hard test every good layout passes and the default fails: all four pieces, edit, confirm and reset have to be pressable while your left hand stays on WASD. Q, E, C, V, F, the modifier column and the mouse side buttons all qualify. The function row does not.
The shipped PC layout puts wall, floor, stairs and cone on F1 to F4. Reaching the function row means taking your hand off the movement keys, so you stop moving at the exact moment you are being shot at. This is not a matter of taste — it is a layout that cannot be used as intended.
Both work. Mouse side buttons free the left hand entirely, which suits players who already use two thumb buttons comfortably; a keyboard cluster keeps everything in one place and does not depend on your mouse having extra buttons. The bench on this page scores either.
It changes how far the reach is, not whether it is possible. A 60% board has no function row at all, so a default layout is not merely awkward there — the keys are on a layer behind a modifier. Pick your board in the bench and the reach column updates.
Builder Pro is the controller preset that puts every build piece on a shoulder or a trigger, so both thumbs stay on the sticks. It is the same rule this page tests, applied by the developers themselves — and it is why the controller default is in far better shape than the keyboard one, which is a genuinely odd thing to be able to say about a game.
Because it is. Builder Pro puts wall on RT and stairs on LT, which are analog triggers with real travel, while roof and floor sit on the bumpers, which are switches. Your two most-thrown pieces are the two that have to move before they register. The drill on this page times your own triggers so you can see the gap in milliseconds instead of arguing about whether you imagined it.
The two things that actually move are not sensitivity. First, keep both thumbs on the sticks while the pieces go down — almost every player unconsciously stops strafing to build, which is invisible from inside the game and is what gets them hit. Second, pull the triggers with a snap rather than a squeeze, because the clock starts when the trigger passes its threshold and not when your finger starts moving. The Builder Pro drill here measures both off your own pad.
No. Nothing in the browser can see the game. You type your binds in, or load one of the reference layouts, and the page tests them against the movement constraint.
I answer from this site only — the 28 browser tests, the controls library for 46 games, the sensitivity converters and the two games. I can tell you which page to open, how a tool works and what its result means.
I will not guess. If something is not on the site, I will say so.
Answers come from this site's pages.