ESX vs QBCore vs Qbox for your FiveM server
Pick ESX Legacy if you want es_extended with ESX’s own slot inventory or ox_inventory. Pick Qbox if you want QBCore-compatible scripts on ox_inventory, ox_lib and ox_target. QBCore’s own team has left FiveM, so stay on QBCore only if your server depends on its qb- resources, such as qb-inventory and qb-target. When you buy scripts, the real split is ESX versus the QBCore family. Qbox runs most QBCore scripts through its bridge, but an ESX-only script needs ESX.
Every current FiveM script we make supports ESX, Qbox and QBCore in one package. Our Ultimate subscription plan includes every script we sell.
What to compare
The framework is the core resource your other scripts ask about players, jobs, money and items: es_extended on ESX, qbx_core on Qbox and qb-core on QBCore. A job, shop or robbery script reads the player’s job and pays or charges money through the framework. That’s why each script is written for one or more frameworks.
Six things change the choice:
- What the txAdmin recipe installs, inventory included
- How often the core gets releases
- Which inventory and ox resources work with it
- What the database needs
- What it takes to move to it from another framework
- Which scripts you can buy for it
Here’s how the three compare, checked on each project’s GitHub and docs on 31 October 2026:
| ESX | Qbox | QBCore | |
|---|---|---|---|
| Core resource | es_extended |
qbx_core |
qb-core |
| txAdmin recipe | ESX Legacy, in Popular Recipes | Qbox, in Popular Recipes | QBCore Framework, by URL only since 29 Oct 2026 |
| Latest version | 1.16.4, released 18 Oct 2026 | v1.24.1, released 30 Oct 2026 | 1.3.0 in fxmanifest; no GitHub releases |
| Newest code change to the core | 18 Oct 2026 | 30 Oct 2026 | 17 Jun 2026 |
| Inventory in the recipe | ESX’s own (esx_inventory) |
ox_inventory | qb-inventory |
| ox_inventory 2.48.1 bridge | Yes | Yes | No |
| Core dependencies | esx_lib, oxmysql |
ox_lib, oxmysql, OneSync; the README also recommends ox_inventory | oxmysql |
| Player record | users table, identifier |
players table, citizenid |
players table, citizenid |
| Database | MySQL-compatible, MariaDB in the install guide | MariaDB 10.9.0 or newer; MySQL not supported | MariaDB in the install guide |
ESX
ESX Legacy suits a server that wants the inventory built into the framework and frequent core releases. Five releases, 1.16.0 to 1.16.4, came out between 11 and 18 October 2026. Release 1.16.0 added a slot inventory with drag-and-drop and a storage API, which ships in the core as esx_inventory. The recipe also installs ox_lib.
ox_inventory is optional. If it’s installed, es_extended sets its Config to "ox" by itself. The ox_inventory ESX page asks for ESX Legacy 1.6.0 or newer, with ox_inventory starting right after es_extended. To move existing inventories, you run convertinventory esx in the server console.
The catch: with ox_inventory, weapons become items, and esx_shops, esx_weaponshop and esx_policejob stop working, so you’ll need replacements for those. ESX also keeps players in a different table from Qbox and QBCore. None of the ESX, Qbox, QBCore or ox pages we checked for this guide offers a converter between the two families.
Qbox
Qbox suits a server that wants QBCore-compatible scripts on the ox stack. It started on 27 September 2022 as a fork of QBCore. qbx_core declares provide 'qb-core' and carries a bridge, so a script looking for qb-core finds it. The recipe installs ox_inventory, ox_lib, ox_target, ox_doorlock and ox_fuel. The core turns on multicharacter, a queue and multijob by default.
It asks more of your server: OneSync, FXServer build 10731 or newer, and MariaDB 10.9.0 or newer. Releases are less frequent than ESX’s. Release v1.24.1 came on 30 October 2026, after v1.24.0 on 22 August 2026 and v1.23.0 on 15 April 2025.
The catch: the Qbox FAQ says QBCore scripts work “in most cases”. The exceptions are scripts that access database tables directly, read qb-core files not meant for other resources, use functions in invalid ways, or work in “other unexpected ways”.
Moving a QBCore server to Qbox is a database job. Qbox’s migration guide has you back up first, build a separate test server and convert a copy of your database there. You run qbx_core, then convertjobs for jobs and gangs, then convertqbinventory, which qbx_core added in v1.24.1, for inventories, stashes, trunks and gloveboxes. Weapon attachments don’t carry over, and ox_inventory drops any item it doesn’t know, so add your qb-inventory items to ox_inventory first. Adding items to ox_inventory helps with that part.
QBCore
QBCore suits a server that already depends on QBCore’s own qb- resources, such as qb-inventory and qb-target. It also suits a server running QBCore scripts that read qb-core’s tables or files directly. Its only core dependency is oxmysql.
QBCore’s team has left FiveM. Its docs say QBCore “has withdrawn from other platforms” and now builds for Mantle, a new Unreal Engine 5 platform. The FiveM code lives on in the qbcore-fivem organisation on GitHub.
qb-core doesn’t publish GitHub releases. Its fxmanifest says 1.3.0. Its last merged code change is from 17 June 2026. The commits after it, up to 24 August, only touched code-scanning setup and repository files. qb-inventory’s newest merged fix is from 11 September 2026. On 29 October 2026, Cfx.re took QBCore out of txAdmin’s Popular Recipes and marked its recipe deprecated in the recipe list. The recipe file is still online, so txAdmin can still deploy it through Remote URL Template.
The catch: ox_inventory 2.48.1 ships framework bridges for ESX, Qbox, ND and ox, but not for qb-core. On QBCore, plan on qb-inventory or another inventory that supports QBCore.
What it means for our scripts
In each current script’s config, set Config to 'esx' or 'qb'. On Qbox, leave it on 'qb', because Qbox’s bridge answers as qb-core. Config is where you name your inventory. Our Advanced Police Job, for example, supports ox_inventory and qb-inventory. One package covers all three frameworks, so switching frameworks doesn’t mean buying again.
The scripts use each framework’s own tables. Our evidence script, for example, stores its gunshot residue value in users by identifier on ESX and in players by citizenid on Qbox and QBCore.
Scripts with a package per framework or ESX only
These scripts are sold as two packages, one for ESX and one for QBCore that also runs on Qbox: Bullet Effects, Ownable Drug Labs, Drug Selling to NPCs, Ownable Gas Stations & Fuel System, Gang Areas, NPC Robbery and Darkweb System. Where a script is sold in separate ESX and QBCore versions, Ultimate includes both.
These scripts support ESX only: All-in-One Bar Job, Ownable Garage System, Job GPS Tracker System, Gang Camps, Garage Robbery, Jewelry Robbery, Shop Robbery, Mechanic Job with Tuning, and Trunk & Glovebox System.
Which fits your server
- Starting a new server with how to make a FiveM server: pick the recipe by the inventory you want. ESX Legacy gives you ESX’s own, and Qbox gives you ox_inventory. With its team gone from FiveM, QBCore is a poor start for a new server.
- On ESX with esx_policejob, esx_shops or ESX-only scripts such as Gang Camps: stay on ESX, and add ox_inventory only once you’ve replaced the resources it breaks.
- On QBCore and built around qb- resources such as qb-inventory and qb-target: you can stay for now, but expect few core updates. Try Qbox on a copy of your server when you’re ready to move.
- On QBCore but want ox_inventory: go with Qbox, since ox_inventory has no qb-core bridge.
- On QBCore with scripts that read qb-core’s tables or files directly: test them on Qbox on a copy of your server first. Those are exactly the cases the Qbox FAQ lists as exceptions.
- Buying lots of scripts before you’ve settled: most of ours run on all three, and the Ultimate plan includes every script we sell. Which scripts a roleplay server adds first can help you choose.
If you already run a server, look in its resources folder. The core resource there tells you which column is yours: es_extended, qbx_core or qb-core.

