A great FiveM roleplay server is a stack of well-chosen resources. These are the frameworks and core scripts that the best servers run in 2026 — most are free and open-source on GitHub, with a few paid picks worth the money.
Quick answer
Most FiveM roleplay servers in 2026 are built on a framework (Qbox, QBCore or ESX) plus oxmysql for the database, ox_lib, ox_inventory and txAdmin for management. Jobs, housing, phones and vehicles go on top of that core. Most of these resources are free and open-source on GitHub.
A FiveM roleplay server is not one script — it is a stack. Get the base right and everything else slots in; get it wrong and you spend months fighting crashes. This guide lists what actually runs on serious servers in 2026, in the order you should install it, with the trade-offs nobody mentions on the store page. Not sure whether GTA or Red Dead roleplay fits your community? Read FiveM vs RedM first.
The base stack every FiveM server needs
Before a single job or phone script, five things have to be stable. Install them in this order:
- txAdmin — ships with FiveM. Your web panel: start/stop, live console, players, bans, scheduled restarts, automatic backups.
- A framework — ESX, QBCore or Qbox. This is the foundation; pick one and never mix.
- oxmysql — the standard MySQL wrapper. Almost every script depends on it, so it must start early.
- ox_lib — the shared library (UI, menus, callbacks, notifications) that most modern scripts require.
- pma-voice — proximity voice, radio and phone-call audio.
Get those five running with zero console errors before you add anything else. Nearly every "my server is broken" post is someone who installed 40 resources at once and cannot tell which one failed.
Choosing a framework: ESX vs QBCore vs Qbox
Your framework decides which scripts you can use, so this is the one decision that is expensive to reverse.
- ESX — the veteran. The largest resource library on the planet and a huge amount of legacy content. If you want maximum choice of ready-made scripts, ESX still wins.
- QBCore — modern, modular, and the default choice for most new RP servers over the last few years. Great documentation, huge community, strong job/economy ecosystem.
- Qbox — the actively developed fork of QBCore, rebuilt on the ox ecosystem (ox_lib, ox_inventory, ox_target as defaults). If you are starting fresh in 2026 and want the most modern, best-performing base, Qbox is the one to look at.
Rule of thumb: ESX for the widest script selection, QBCore for the biggest community, Qbox for the cleanest modern base. Whatever you pick, check that the scripts you want support it before you buy.
The ox ecosystem — the modern standard
The Overextended (ox) resources are free, open-source and cross-framework — they run on ESX, QBCore and Qbox. They have effectively become the default layer under everything:
- ox_lib — shared UI, menus, context menus, progress bars, callbacks, caching. Thousands of scripts list it as a dependency.
- ox_inventory — slot-based inventory with weapons, stashes, shops, crafting hooks and metadata.
- ox_target — the "third eye" interaction system, lighter than the older qb-target.
- oxmysql — the MySQL wrapper everything queries through.
- ox_doorlock — door locking with a proper in-game editor, used by nearly every police/business script.
- ox_fuel — a lightweight, no-nonsense fuel resource.
Inventory: ox_inventory vs qb-inventory vs qs-inventory
The inventory touches every item, shop, job and drug script you will ever run, so it is worth getting right. In 2026 the picture is clear:
- ox_inventory (free) — the de facto default. Runs on QBCore, ESX and Qbox (via a bridge) and is extremely light: roughly 0.08 ms idle with 64 players. Best performance-per-euro on the list, because it costs nothing.
- qs-inventory (paid, ~€35-50) — the polished commercial alternative. Worth it if built-in crafting and a slicker UI matter more to you than shaving resmon.
- qb-inventory (free, legacy) — the old QBCore default. On modern builds it has been outperformed by ox_inventory on essentially every metric. Only stay on it if you are locked in by old scripts.
If you are starting today: ox_inventory, and do not look back.
Voice: pma-voice (and the alternatives)
Voice is the single most immersion-critical resource on an RP server. pma-voice is the go-to: proximity chat, radio channels, phone-call integration, and it is performant and actively maintained. mumble-voip is the older option, and SaltyChat is the alternative some servers prefer for its radio feel — but it needs an external client, which costs you players who will not install it. For 99% of servers, pma-voice is the right answer.
txAdmin — how you actually run the server
txAdmin is not optional, it is your cockpit. It ships with FiveM and gives you a recipe-based installer (deploy a full QBCore/ESX base in minutes), a live console, player management and bans, scheduled restarts (do them — long uptimes leak memory on FiveM), automatic backups and a permissions system for your staff. Learn its scheduled-restart and backup features on day one, not after your first wipe.
Jobs, dispatch and the police stack
Once the base is stable, jobs are what make it a roleplay server. The Project Sloth (ps-) resources are the most-used free options in the QBCore world:
- ps-dispatch — the free dispatch/alerts standard: crime notifications, blips, callouts to police and EMS.
- ps-mdt — a full police MDT: records, warrants, reports, vehicle lookups.
- ps-hud — the widely used HUD (health, armour, hunger, thirst, voice, vehicle).
- Ambulance/EMS — death, injuries, revive and hospital flow; framework-specific.
- Mechanic — repairs, tuning and vehicle status.
Add police and EMS before illegal jobs. A server with drugs and heists but no working police loop turns into deathmatch within a week.
Phone, garages and housing
- Phone — the most-used resource on any RP server. qb-phone is the free classic; lb-phone and gksphone are the popular paid options with far more apps and polish. This is one place where paying is usually worth it.
- Garages & vehicle keys — vehicle persistence is core RP. qb-garages is the free baseline; jg-advancedgarages is the common paid upgrade.
- Housing — ps-housing and qb-houses are the free routes; most large servers eventually buy something with interiors and shells.
- Banking & shops — keep these framework-native (qb-banking / esx equivalents) so your economy stays consistent.
Free vs paid (Tebex) — how real servers actually mix
Not everything worth running is free. Many polished frameworks, MLOs, phones and job systems are sold through Tebex, FiveM's official marketplace. There is no shame in mixing: the pattern that works is a free, solid core (framework + ox suite + pma-voice + txAdmin) plus a handful of paid resources for unique content — a phone, a housing system, a signature MLO.
Two warnings. First, escrow: most paid resources ship partly encrypted, so you cannot fully edit or debug them — factor that in before building your server around one. Second, and far more important: never install leaked or cracked scripts. They are the number-one source of backdoors on FiveM servers, they get your Cfx.re key revoked, and they are exactly the thing our FiveM & GTA hosting policy forbids. A leaked script that gives an attacker your database is not a bargain.
Start order matters more than you think
Dependencies must be ensured before the scripts that use them, or resources fail to start with cryptic errors. A correct server.cfg order looks roughly like: oxmysql → ox_lib → framework core → ox_inventory / ox_target → everything else. If a resource will not load, that order is the first thing to check — see fixing "couldn't load resource".
Keeping your resource list lightweight
Every resource you ensure adds server tick overhead, even when idle. Open resmon (F8 → resmon 1) regularly and read it honestly: anything sitting above ~0.5 ms idle deserves questioning, and one badly written script can cost more than twenty lean ones. Drop what you do not use, and prefer actively maintained resources — an abandoned script is the usual root cause of the random crashes and memory leaks that appear months later. FiveM is heavily single-thread bound, so raw CPU clock speed matters more than core count.
Security basics for a public RP server
A popular FiveM server attracts exploiters as much as players. Validate server-side anything that touches money or items — never trust a client-side check. Keep txAdmin behind a strong password with 2FA, restrict your database to localhost, and audit any script that was given to you rather than bought or downloaded from source. Our game server security checklist covers the wider hardening, and the VPS hardening checklist covers the box underneath.
If your server disappears from the list
A resource conflict, an expired Cfx.re key, a heartbeat problem or a blocked port can all knock you out of the FiveM server list. Work through FiveM server not showing in the list, and if players get stuck connecting see stuck on "Connecting".
A clean base: txAdmin + a framework (ESX/QBCore/Qbox) + oxmysql + ox_lib + ox_inventory + pma-voice. Get that stable with zero console errors first, then add jobs, phone and housing — one at a time.
FiveM lives and dies on single-core CPU performance, and an RP server with 60 players and a full script list is genuinely demanding. Our FiveM hosting runs high-clock CPUs with txAdmin and MySQL ready to go, behind multi-Tbps Frankfurt filtering.
FiveM is a Cfx.re / Rockstar Games project. Grand Theft Auto V is a trademark of Rockstar Games / Take-Two Interactive. All resource and script names are the property of their respective authors. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Rockstar Games, Take-Two, Cfx.re or any script developer. You must own a legitimate copy of the game and download resources from their official sources.