ESX vs QBCore vs Qbox for your FiveM server
Run ESX Legacy if you want es_extended with ESX’s own slot inventory or ox_inventory. Run QBCore if you want its txAdmin recipe as shipped, with qb-inventory and qb-target. Run Qbox if you want QBCore-compatible scripts on ox_inventory, ox_lib and ox_target. For buying scripts the split is ESX against the QBCore family: Qbox runs most QBCore scripts through its bridge, while an ESX-only script needs ESX.
Every current FiveM script we make supports ESX, QBCore and Qbox in one package, and our Ultimate subscription plan includes every script we sell.
What to compare
A framework is the core resource your other scripts call for players, jobs, money and items: es_extended on ESX, qb-core on QBCore and qbx_core on Qbox. A job, shop or robbery script reads the player’s job and pays or charges through it, so it is written for one or more frameworks.
These 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 moving to it from another framework takes;
- which scripts you can buy for it.
Checked on each project’s GitHub and docs on 19 October 2026:
| ESX | QBCore | Qbox | |
|---|---|---|---|
| Core resource | es_extended |
qb-core |
qbx_core |
| txAdmin recipe | ESX Legacy | QBCore Framework | QBox Framework |
| Latest version | 1.16.4, released 18 Oct 2026 | 1.3.0 in fxmanifest; no GitHub releases |
v1.24.0, released 22 Aug 2026 |
| Newest commit to the core | 18 Oct 2026 | 24 Aug 2026 | 30 Sep 2026 |
| Inventory in the recipe | ESX’s own (esx_inventory) |
qb-inventory | ox_inventory |
| ox_inventory 2.48.0 bridge | Yes | No | Yes |
| Core dependencies | esx_lib, oxmysql |
oxmysql | ox_lib, oxmysql, OneSync; the README also recommends ox_inventory |
| Player record | users table, identifier |
players table, citizenid |
players table, citizenid |
| Database | MySQL-compatible, MariaDB in the install guide | MariaDB in the install guide | MariaDB 10.9.0 or newer; MySQL not supported |
ESX
ESX Legacy suits a server that wants the inventory inside 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. When it is present, es_extended switches its Config to "ox" on its own. The ox_inventory ESX page asks for ESX Legacy 1.6.0 or newer, starting ox_inventory right after es_extended, and convertinventory esx in the server console to move existing inventories.
Its limit: with ox_inventory, weapons become items, and esx_shops, esx_weaponshop and esx_policejob stop working, so those need replacements. ESX keeps players in a different table from QBCore and Qbox, and none of the ESX, QBCore, Qbox or ox pages checked for this guide offers a converter between the two families.
QBCore
QBCore suits a server that wants the recipe’s own qb- resources, qb-inventory and qb-target among them, or that runs QBCore scripts which read qb-core’s tables or files directly. Its only core dependency is oxmysql.
qb-core publishes no GitHub releases; its fxmanifest says 1.3.0. The newest commit to qb-core is dated 24 August 2026, and to qb-inventory 11 September 2026.
Its limit: ox_inventory 2.48.0 ships framework bridges for ESX, Qbox, ND and ox, and none for qb-core. On QBCore, plan on qb-inventory or another inventory that supports QBCore.
Qbox
Qbox suits a server that wants QBCore-compatible scripts on the ox stack. It began on 27 September 2022 as a QBCore fork. qbx_core declares provide 'qb-core' and carries a bridge, so a script that looks for qb-core finds it. The recipe installs ox_inventory, ox_lib, ox_target, ox_doorlock and ox_fuel, and the core turns on multicharacter, a queue and multijob by default.
It asks more of the server: OneSync, FXServer build 10731 or newer, and MariaDB 10.9.0 or newer. Releases come less often than ESX’s: v1.24.0 on 22 August 2026 followed v1.23.0 of 15 April 2025, with commits through 30 September 2026.
Its limit: 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 over is a database job. Qbox’s converting page has you back up first, change job and gang grades to numbers, run qbx_core and convertjobs, and set up ox_inventory. On 19 October 2026 its link for converting inventories led to the ox docs home page, and convertinventory in ox_inventory 2.48.0 accepts esx and esxproperty only. Decide how qb-inventory items carry over before you switch, and see adding items to ox_inventory.
What it means for our scripts
In each current script’s config, set Config to 'esx' or 'qb'; on Qbox it stays 'qb' because Qbox’s bridge answers as qb-core. Config names your inventory: our Advanced Police Job, for example, supports ox_inventory and qb-inventory. One package covers all three, so a framework switch needs no second purchase.
The scripts follow the 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 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 server from how to make a FiveM server: pick the recipe by the inventory you want, ESX Legacy for ESX’s own, QBCore Framework for qb-inventory, QBox Framework for ox_inventory.
- On ESX with esx_policejob, esx_shops or ESX-only scripts such as Gang Camps: stay on ESX, and add ox_inventory only after replacing the resources it breaks.
- On QBCore and wanting ox_inventory: Qbox, since ox_inventory has no qb-core bridge.
- On QBCore with scripts that read qb-core’s tables or files directly: test them with Qbox on a copy of the server first, because those are Qbox’s listed exceptions.
- Buying many scripts before you settle: most of our scripts run on all three, and the Ultimate plan includes every script we sell. See which scripts a roleplay server adds first.
If you already run a server, the core resource in its resources folder tells you which column applies: es_extended, qb-core or qbx_core.

