ESX Admin Commands — Complete 2026 Reference
Complete reference of ESX admin commands for FiveM RP servers — player management, vehicle spawning, money & jobs, world manipulation, plus a self-hosting setup guide for setting your first admin.
ESX is still one of the most-deployed FiveM frameworks in 2026, and every server admin needs a working knowledge of its built-in commands. This is the practical reference: every command that ships with esx-legacy, what it does, the syntax that actually works, and the gotchas that waste hours when they bite you. We'll also walk through the one piece nobody tells you up front — how to set yourself as the first admin on a fresh ESX install — and explain how to extend ESX with custom commands when the built-ins aren't enough.
How ESX permissions work
ESX uses a group field on every user row in the users table. The group string maps to a permission tier:
user— every regular player. Cannot run any admin command.mod— moderation tier. Player utilities (kick, freeze, teleport).admin— full day-to-day administration. Money, jobs, vehicles, ban.superadmin— unrestricted. Includes commands that can wipe player data.
When a player joins, their group is read from the database into ESX's player object. The framework checks that group before allowing any /command to run. If you change a player's group while they're online, they need to rejoin for it to take effect.
You will not see ESX admin commands work in the txAdmin web console — txAdmin runs its own command layer. ESX commands are typed in the F8 client console (the FiveM in-game console) or the chat box with a leading /.
Becoming an admin on your own server (the SQL trick)
This is the single most-asked ESX question and the one official docs are vague on. After installing esx-legacy on a fresh server, every player including you defaults to group = 'user'. To become an admin:
Frequently Asked Questions
How do I become an ESX admin on my own server?
Run the SQL `UPDATE users SET `group` = 'admin' WHERE identifier = 'YOUR_LICENSE'` on your server database, then rejoin. Your steam license appears in your `txAdmin` player list. After that, every ESX admin command works for you.
Why aren't my ESX admin commands working?
Three common causes: (1) your ESX user `group` is still 'user' in the database, (2) the `es_extended` resource is older than 1.10 and your command syntax is from a newer guide, (3) you're typing the command in chat without the leading `/`. Verify your group with `/showmyperms` and ensure you're on esx-legacy.
Are ESX admin commands the same on QBCore?
No. QBCore uses its own command system based on `qb-admin` and the `permissions.cfg` file. ESX commands like `/setgroup` won't work on QBCore. If you migrated, install qb-admin and follow the QBCore admin guide.
Can I add custom admin commands to ESX?
Yes. Use `ESX.RegisterCommand` server-side with a permission level (e.g. `admin`, `superadmin`). Pass arguments, suggestions, and a callback. Custom commands inherit ESX's group-based permission gating automatically.
