App Store Almost every Roblox control problem has one symptom and three or four possible causes, which is why the usual answer — a list of keys — so rarely helps. This page settles the causes a browser can actually settle: whether your key reaches software at all, what your controller is really sending, and which half of Roblox owns the binding you are asking about.
Shift lock turns Roblox’s third-person camera into a shooter camera: your character faces wherever the mouse points and strafes instead of turning. It is the single most-searched Roblox control, and when it fails there are three causes that look identical from the inside. One of them can be ruled out right here.
Click this panel first, then press the key. If nothing registers, the key is not reaching software at all — which is a keyboard problem, not a Roblox one.
A small padlock icon sits at the right of the screen and Left Shift toggles the camera-locked mode.
Working as intended — nothing to change.
No padlock icon, and Left Shift does nothing. This is the default state for a new account.
Roblox menu → Settings → Shift Lock Switch → On. It is an account setting, so it follows you into every experience.
The setting is visible but greyed out, and the game shows "Set by Developer" beside it.
Nothing on your side changes this. The creator of that experience disabled shift lock for everyone in it, and no account setting, reinstall or device will override it.
The setting is missing entirely.
Shift lock is a mouse-and-keyboard mode. On touch it has no equivalent unless the creator built one, and on a controller the right stick already does what shift lock is for.
Another single symptom over several causes. Nothing connected, a pad the browser cannot map, a stick that no longer rests at centre, or — the one almost nobody suspects — a second phantom device created by an overlay running in the background, sending alongside the real one. That last case is what a camera drifting on its own usually is, and it is not Roblox.
A pad stays invisible to a browser until it sends something. Press a face button and this fills in.
The camera is the part of Roblox the client owns most completely, so unlike almost everything else on this page these keys really are the same in every experience — right up until a creator decides otherwise.
Mouse 2 (hold) Scroll Up / Scroll Down I / O Scroll Up The least-known binding in Roblox, and the answer to “how do I zoom out” on a laptop trackpad, where scroll gestures often do nothing at all.
An experience can lock the camera distance, force first person, or take the camera over completely. If zoom does nothing in one place and works everywhere else, that is the creator’s choice rather than a broken key — the same rule as shift lock.
Two fingers pinch to zoom and a drag on the right half turns the camera. There is no first-person toggle and no shift lock unless the creator built one — the mouse-shaped half of the camera simply has no touch equivalent.
Here is the rule underneath every answer above. Roblox is a client running millions of experiences, so a key belongs to one of two layers: the client’s, which behaves the same everywhere you go, or the experience’s, which is whatever one creator decided. Type any key and find out which.
—
Roblox runs the same experience on four very different input systems. This is what the client itself provides on each, and what simply has no equivalent — which is why a place built around shift lock feels wrong on a phone through no fault of the player.
This browser can tell what kind of input your device has, so the column below that applies to you can be picked out rather than left for you to find. It is a reading, not a claim — the signals it used are listed, and you can override it.
The complete client layer.
No equivalent: 8 controls.
No equivalent: 8 controls.
No equivalent: 8 controls.
| Client control | PC key | PC | PlayStation | Xbox | Mobile |
|---|---|---|---|---|---|
| MoveLeft stick on a controller; an on-screen thumbstick on touch. | W / A / S / D | Yes | Yes | Yes | Yes |
| JumpThe client draws a jump button on touch. An experience can script around it but cannot remove it. | Space | Yes | Yes | Yes | Yes |
| Shift lock (camera follows mouse)Mouse-only by nature. Creators can disable it per experience, which is why it sometimes silently does nothing. | Left Shift | Yes | — | — | — |
| Rotate cameraRight stick on a controller; drag on touch. | Mouse 2 (hold) | Yes | — | — | — |
| Zoom / first personPinch on touch. Some experiences lock the camera distance entirely. | Scroll | Yes | — | — | — |
| Zoom without a wheelI zooms in, O zooms out — the same camera distance the scroll wheel changes. | I / O | Yes | — | — | — |
| Equip toolThe number row maps to backpack slots. This is the seam where the two layers meet most often. | 1 – 0 | Yes | — | — | — |
| Backpack / inventoryAn on-screen button on touch and console. | ` | Yes | — | — | — |
| ChatCan be disabled by the experience or by account settings. | / | Yes | — | — | — |
| Leaderboard / player listHeld rather than toggled. | Tab | Yes | — | — | — |
| Roblox menuNever available to an experience. This one is absolute on every platform. | Escape | Yes | Yes | Yes | Yes |
The client layer is small and fixed. Everything memorable about a given Roblox game — the ability on Q, the sprint on Shift — is the experience layer, and it evaporates the moment you join a different place.
On touch, a virtual joystick appears on the left, dragging on the right moves the camera, a jump button sits bottom-right and tools appear in a bar at the bottom. Experiences often replace this with their own buttons.
Sticks cover movement and camera cleanly, but there is no cursor, so anything an experience built around pointing needs its own controller path — and not every creator writes one.
Roblox has no keybind settings. There is no screen anywhere in the client that lets you change what a key does, and there never has been — the controls are decided by Roblox for the client layer and by each creator for everything else.
The only real option, and it exists more often than people expect. Anything built by the creator — sprint, abilities, vehicles — can be rebound if the creator wrote a menu for it. Check there before anything else.
Holds camera mode, shift lock, sensitivity, graphics and volume. No key assignments of any kind.
Keyboard or mouse software that swaps keys before they reach the browser or app will work, because Roblox only ever sees the result. It is a blunt instrument — it applies to everything you do, not just Roblox — and it cannot help with anything an experience reads directly.
Not a rebind, but worth knowing: the controller layer is a separate map, so an action awkward on your keyboard may sit somewhere comfortable on a pad. The client layout is fixed there too.
This page is about which layer owns a key. These are about the device sending it.
Because most of them are not Roblox’s. The client owns movement, the camera, shift lock, the menu, chat and the player list — those are the same everywhere. Everything else is scripted by whoever built the experience you are in, so the same key does something different in the next place you visit. There is no global setting for those.
For the client layer, you largely cannot — Roblox does not expose a rebinding screen for movement or camera. For the experience layer, it depends entirely on whether that creator built a settings menu. This is the single most common Roblox control question and the honest answer is that it is not one setting, it is two systems.
Shift lock locks the character to face wherever the camera points, on Left Shift. It is a client feature, but creators can disable it for their experience — so when it silently does nothing, that is usually a deliberate choice by that place rather than a bug on your end. It is also mouse-shaped by nature and does not exist on touch.
No, and the table on this page shows where it diverges. The client draws its own on-screen controls on touch, so movement and jump are always there, but the mouse-shaped controls have no equivalent. An experience written around shift lock will feel different on a phone through no fault of yours.
No. The Roblox menu is absolute on every platform. A handful of keys are reserved that way, and this page marks them — it is worth knowing which ones a creator can never intercept.
The page checks. It reads what your browser exposes — touch points, a connected gamepad, pointer type and a physical keyboard — and lines that up against the client layer, so you can see which parts of Roblox exist on the device you are reading this on.
Because the creator of that experience turned shift lock off for everyone inside it. Roblox lets them do that, and when they do, the setting stays visible but greyed out with that label. No account setting, reinstall, device or client version overrides it — it is a decision made in the place you are standing, not a fault on your side. In any other experience the same setting works normally.
Roblox menu → Settings → Shift Lock Switch → On, and then Left Shift toggles it. When it does not work there are exactly three causes and they look identical from the inside: the switch is off, the experience disabled it, or the key is not reaching software at all. The panel at the top of this page settles the third one outright by showing whether your Left Shift arrives in the browser — and note that it must be the left key, because Right Shift does nothing in Roblox even though it works perfectly everywhere else.
Press O to zoom out and I to zoom in. They do exactly what the scroll wheel does, and they are the answer on a laptop trackpad where Roblox often ignores scroll gestures. Holding I all the way takes you into first person. An experience can lock the camera distance, so if these do nothing in one place and work everywhere else, that is the creator’s choice rather than a broken key.
Usually one of two things, and neither is Roblox. Either the right stick on your controller no longer rests at centre, or a second phantom controller is being created by an overlay running in the background — Steam Input is the common one — so two devices send to the game at once. The controller panel on this page shows both directly: how many pads the browser can see, and where your sticks actually rest. Roblox exposes no controller deadzone setting, which is why this is more visible here than in games that let you hide it.
Four possible reasons. Nothing is connected; nothing has been pressed yet, because a pad stays invisible until it sends something; the pad arrives without a standard mapping, which is common for PlayStation controllers on Windows and usually needs DS4Windows; or the pad works fine and the experience simply has no controller support for what you are trying to do. Controller support in Roblox is written per experience, so plenty of them handle movement and leave menus, chat and building to a keyboard.
No. Roblox has no keybind settings — there is no screen anywhere in the client that lets you change what a key does, and there never has been. Roblox Settings holds camera mode, shift lock, sensitivity, graphics and volume, and no key assignments at all. What can work: the experience’s own settings menu, which more creators provide than people expect, and remapping software on your own machine, which swaps keys before they ever reach Roblox.
Its own settings menu, and realistically nowhere else. Those binds live in the experience layer — one creator wrote them and can change them in any update — which is why searching for one game’s control list so rarely turns up anything reliable, and why no two answers agree. The client layer, which is genuinely fixed everywhere, is the table on this page.
No. It holds the verified client-layer defaults and answers questions about them. Nothing is read from Roblox, nothing you type leaves the page, and the only things measured are your own keyboard and controller as the browser receives them.
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.