In short: If you're setting up a new server and want to build on the ox resources (ox_lib, ox_inventory), Qbox is currently the obvious choice. If your server already runs stably on ESX and many of your own scripts depend on it, stay with ESX, since the project is actively maintained. QBCore is mainly worth it if you're continuing to run an existing QBCore server. For new projects in the QB ecosystem, Qbox is the better foundation.
All three frameworks solve the same basic problem: they manage players, characters, money, jobs, items and vehicles and provide an API for them to other resources. The differences lie in maintenance, the ecosystem, and how much legacy baggage you carry along. If you're just getting started, read our guide first Create a FiveM server.
The three frameworks compared
The information on releases and activity comes from the official GitHub repositories. As of October 2026.
| Criterion | ESX Legacy | QBCore | Qbox |
|---|---|---|---|
| Origin | Started in 2017, today as ESX Legacy in the repo esx_core |
Standalone framework, core resource qb-core |
Fork of QBCore, founded on September 27, 2022 |
| Maintenance (as of October 2026) | Very active: release 1.16.0 on 11.10.2026, 1.16.4 on 18.10.2026 | Last commits to the core repo in August 2026, no GitHub releases, version in the manifest 1.3.0 | Active: qbx_core v1.24.0 on 22.08.2026, commits through end of October 2026 |
| License | GPL-3.0 | GPL-3.0 | GPL-3.0 |
| Language and architecture | Lua 5.4, oxmysql, own library esx_lib; Jobs and items are stored in the database |
Lua 5.4, oxmysql; jobs, items and vehicles in Lua files under shared/ |
Lua 5.4, requires ox_lib and oxmysql; multicharacter, queue and multijob in the core |
| Ecosystem | Large selection of esx_-addons (jobs, shops, garages), custom esx_inventory; ox_inventory is officially supported |
Extensive qb--resource set (Jobs, Phone, Housing, Inventory) |
Own qbx_-resources plus Overextended resources such as ox_inventory |
| Compatibility and bridges | No bridge for QB scripts | Only uses QB scripts natively | Bridge layer provides qb-core ready; most QBCore scripts run without changes |
| Learning curve (estimate) | Moderate; many old tutorials refer to outdated ESX versions | Low barrier to entry, many guides | Medium; you need to know ox_lib and the ox conventions |
All three have more in common than the discussions on Discord servers would suggest: they all run on Lua 5.4, they all access the database via oxmysql, and they are all licensed under GPL-3.0. If you modify and redistribute scripts, the same license obligations therefore apply. The real difference for your day-to-day lies in the API your scripts call, and in which ready-made resources you can use without reworking them.
ESX Legacy
ESX is the oldest of the three frameworks. The current line is called ESX Legacy and is located in the repository esx-framework/esx_core. There you'll find, alongside the core, es_extended also base resources such as Multicharacter, Identity, Skin, Notify and Progressbar. The project is under active development: in October 2026, several releases came out within one week, from 1.16.0 to 1.16.4.
Advantages:
- A very large number of existing scripts and add-ons, including on the free market. An overview is provided on our page about FiveM mods and scripts.
- Jobs, job grades, and items are stored in database tables. You can manage them via SQL or an admin tool without touching any Lua files.
- ox_inventory officially supports ESX (
setr inventory:framework "esx"). - Extensive documentation for the core, events, xPlayer and the standard addons.
Disadvantages:
- Due to the project's age, many scripts written for older ESX versions are still in circulation and need adjustments with Legacy.
- No bridge layer for QBCore scripts. Anything written for QB needs to be rewritten, or you need to find an ESX version.
- Since es_extended switched to
esx_lib...builds on, you have another core dependency that you need to keep an eye on during updates.
QBCore
QBCore comes with a broad set of qb-Resources with: police and ambulance job, garages, houses, phone, inventory and much more. Especially for beginners this is convenient, because many parts are coordinated with each other. The GitHub organization is now called qbcore-fivem; the old address qbcore-framework redirects there.
Advantages:
- Large, cohesive resource package that gets you a playable server quickly.
- Jobs, items and vehicles in Lua files are easy to version, for example with Git.
- Many guides and third-party scripts with QB support.
Disadvantages:
- The Core is being developed more slowly than ESX and Qbox. The Core repo has no GitHub releases, and the latest commits are from August 2026 and mostly concern repo maintenance.
- ox_inventory comes with bridges for ESX, Qbox, ox_core and ND, but none for QBCore. If you want ox_inventory, you practically end up with Qbox.
- Assessment: For new projects there is hardly any reason, QBCore instead of Qbox, because Qbox largely supports QB scripts.
Qbox
According to its own documentation, Qbox is a QBCore fork from 27 September 2022. The goal was, QBCore to improve it while staying backwards compatible. Many resources have been reworked since then and rely on Overextended resources such as ox_lib and ox_inventory. According to its own statement, the Qbox team is not affiliated with Overextended itself.
Advantages:
- The bridge layer provides
qb-coreready. According to the FAQ, most QBCore scripts run without changes as long as they use the documented QB API. - Multicharacter, queue, multijob/multigang and Discord Rich Presence are built into the core and configurable.
- Clear rules for developers: no direct access to core tables, no changes to the core, no deprecated functions.
- You can find a selection of suitable resources in our overview of Qbox scripts.
Disadvantages:
- Stricter requirements: Qbox requires MariaDB (at least 10.9.0); MySQL and XAMPP are explicitly not supported. This also affects your choice when FiveM server hosting.
- QB scripts that write directly to database tables or use internal qb-core files do not work through the bridge.
- You also familiarize yourself with ox_lib and the ox conventions.
Migration: What breaks when switching
Switching frameworks on a running server is a major project. Make a complete backup of files and database beforehand, and test on a copy, never on the live server.
QBCore to Qbox
That is the easiest way, because Qbox is built exactly for this. According to the official migration guide, you must, among other things:
- Job and gang grades in
qbx_core/shared/jobs.luaandgangs.luaswitch from strings to numbers. - Set up ox_inventory and convert your inventory data (back up beforehand).
- The collation of the column
players.citizenidcheck,qbx_core.sqlfor the new tableplayer_groupsrun and thenconvertjobsin the txAdmin console. - Decide whether to use the built-in systems (Multicharacter, Queue) or disable them.
Scripts that exports['qb-core']:GetCoreObject() call, continue to run through the bridge. A direct export GetCoreObject off qbx_core does not exist.
ESX to QBCore or Qbox
There is no bridge here. You rewrite each script or replace it. These spots typically break:
- Core object and exports: ESX scripts get the object via
getSharedObjectand work withxPlayer. QB scripts use the Core object fromqb-coreandPlayer.PlayerData. - Events: Off
esx:playerLoadedbecomesQBCore:Client:OnPlayerLoaded, fromesx:setJobbecomesQBCore:Client:OnJobUpdate. The parameters differ, so check each handler individually. - Database schema: ESX stores players in
usersand vehicles inowned_vehicles, jobs and items in their own tables (jobs,job_grades,items). QBCore and use Qboxplayerswithcitizenidas keys and define jobs and items in Lua files. Player data must be transferred with your own script. - Inventory: If you already use ox_inventory under ESX, the inventory system stays with you when switching to Qbox. You should still check the item definitions and saved inventories.
Our article shows you how to concretely adapt individual scripts Convert FiveM code between ESX and QBCore.
Checklist for your decision
- Do you already have a running server? As a rule, stick with your framework. Exception: a switch from QBCore on Qbox is comparatively cheap.
- Which scripts do you absolutely want to use? For every paid or free script, check which frameworks it officially supports.
- Want ox_inventory? Then ESX or Qbox come into question, QBCore not without rework.
- Which database does your host offer? For Qbox you need MariaDB 10.9.0 or later.
- How much Lua can you do yourself? Every framework choice means you will need to adapt scripts. Plan time for this.
- Where do your scripts come from? Use reputable sources, see Sources for FiveM mods and scripts. Leaked resources are a legal and technical risk, more on this in Will my FiveM server be banned if I use leaks?
FAQ
Do QBCore scripts run on Qbox?
In most cases, yes. Qbox provides a bridge layer for the documented QBCore API. According to the Qbox FAQ, problems are caused by scripts that access database tables directly, use internal qb-core files, or use functions incorrectly.
Do ESX scripts run on QBCore or Qbox?
No, not without modification. Neither QBCore nor does Qbox provide an official ESX bridge. Some third-party scripts come with their own bridges for multiple frameworks; you need to check this for each script.
Is ESX still being developed?
Yes. The repository esx_core received several releases in October 2026, most recently 1.16.4 on 18 October 2026 (as of October 2026).
Can I use ox_inventory with QBCore?
Not officially. ox_inventory comes with bridges for ESX, Qbox, ox_core and ND. For QBCore does not exist. If you are coming from the QB environment and want ox_inventory, Qbox is the intended path.




