FiveM Controls List

How FiveM controls work

A control in FiveM is a game input identified by a number. GTA V groups its inputs into a fixed enum, so pressing space is not read as the letter "space" but as INPUT_JUMP, control ID 22. You read these client-side with IsControlPressed(group, id) for a held key, IsControlJustPressed for a single tap and IsControlJustReleased for the release. Because the IDs come from the game itself, the same number works on ESX, QBCore, Qbox or standalone, and it keeps working even if the player has rebound the key, which is why scripts read control IDs instead of raw scan codes.

One physical key can back several controls. E, for example, is INPUT_PICKUP (38), INPUT_CONTEXT (51) and INPUT_TALK (46) at once, which is why two scripts both listening for E can clash. The default bindings in the tables below are what a fresh install ships with; players can change them in the pause menu, but the numeric ID never changes.

Most-used FiveM control IDs

These are the controls scripts reach for most often: the interact and movement keys, combat inputs and the core vehicle controls. If you just need a key for an interaction prompt, 38 (E, INPUT_PICKUP) and 51 (E, INPUT_CONTEXT) are the usual picks, and 47 (G, INPUT_DETONATE) is a common free-ish key for a secondary action.

All FiveM control IDs (0 to 360)

The table below lists all 361 controls in the FiveM control enum, from ID 0 to 360, with the default keyboard and controller binding for each. On-foot controls sit in the low IDs (movement 21 to 36, combat 24 to 47), vehicle controls run from INPUT_VEH_MOVE_LR (59) through the flight, sub and hydraulics inputs, then cellphone (172 to 186), frontend/menu (187 to 217), script axes (218 to 235), cursor (237 to 242) and the replay editor (288 onward). A dash means the game ships no default binding for that control on that device.

Control groups (0, 1, 2) and DisableControlAction

Every control native takes a control group as its first argument. In practice you pass 0 almost every time: it covers gameplay controls on foot and in vehicles, and the Cfx.re docs use it in their own examples. The three documented groups are:

To stop the game from acting on a control, call DisableControlAction(0, id, true) once per frame. It only lasts a single frame, so scripts keep a list of control IDs and disable them in a loop while a menu or minigame owns the input; DisableAllControlActions(0) blocks every control at once. You can still read a disabled control with IsDisabledControlJustPressed, which is how you reuse a vanilla key for your own action without the game reacting to it.

Lua snippets: read, disable and reuse controls

Reading a key is a per-frame check inside a thread. This one fires an event the moment the player taps E (control 38).

-- client.lua | run an action when the player taps E
-- INPUT_PICKUP = 38, control group 0 = PLAYER_CONTROL
CreateThread(function()
    while true do
        Wait(0)
        if IsControlJustPressed(0, 38) then
            TriggerEvent("myscript:interact")
        end
    end
end)

The DisableControlAction list pattern: build a table of control IDs and disable them all every frame while your NUI is focused, so clicks and keys do not leak into the game.

-- client.lua | block game input while a NUI menu is open
-- attack, aim, detonate, throw, melee and the weapon wheel
local DISABLED = { 24, 25, 47, 58, 263, 264, 257, 140, 141, 142, 12, 13 }

CreateThread(function()
    while menuOpen do
        Wait(0)
        for _, control in ipairs(DISABLED) do
            DisableControlAction(0, control, true)
        end
    end
end)

To repurpose a game key, disable it and read it back with the disabled-control natives. Here the vehicle X key (control 73) drives a custom action instead of ducking.

-- client.lua | reuse a game key without the vanilla action
-- disable INPUT_VEH_DUCK (73, the X key in a vehicle), then read it yourself
CreateThread(function()
    while true do
        Wait(0)
        DisableControlAction(0, 73, true)
        if IsDisabledControlJustPressed(0, 73) then
            TriggerEvent("myscript:vehicleAction")
        end
    end
end)

Rebinding keys with RegisterKeyMapping

Hard-coding a control ID is fine for reading the game's own inputs, but for a key that opens your script, the modern FiveM approach is RegisterKeyMapping. You register a +commandand bind a default key to it; FiveM then adds a row to Settings > Key Bindings so every player can rebind it without editing your code, and two resources no longer fight over the same physical key.

-- client.lua | let players rebind the key from FiveM Settings > Key Bindings
RegisterCommand("+openInventory", function()
    TriggerEvent("inventory:open")
end, false)

RegisterKeyMapping("+openInventory", "Open inventory", "keyboard", "F2")

Need more than this list? The authoritative, always-current source is the Cfx.re control reference at docs.fivem.net (game-references > controls), which is where the 361 IDs above come from. For analog inputs (sticks, triggers) use GetControlNormal(0, id), which returns a -1.0 to 1.0 value instead of a boolean, and GetControlInstructionalButton to resolve the on-screen button glyph for a control at runtime.

Scripts with configurable keybinds

If you would rather configure a keybind than write a control loop, several Var FiveM scripts expose their keys in the config. The FiveM emote script opens its React menu with M and adds an 8-slot emote wheel plus Numpad keybind slots, the FiveM interaction script is a standalone system whose hold-to-confirm panels use a configurable hold duration and key bind, the FiveM keypad script gates any action behind a NUI PIN with a plug-and-play example command, the FiveM dispatch script accepts or refuses alerts on configurable keybinds (default Y and G), and the FiveM AFK script toggles with a configurable command and exit key. The keypad, dispatch and AFK scripts run on ESX, QBCore and standalone.

Related: FiveM blips list · FiveM emote list · FiveM weapon list