ESX vs QBCore vs QBox: which FiveM framework should you use?

Almost every FiveM roleplay server runs on one of three frameworks: ESX, QBCore or QBox. The framework handles the basics every script builds on: characters, jobs, money, inventory and permissions. Picking one mostly decides which scripts you can use and how much work it is to maintain your server.

The short answer

• Starting a new server today? Use QBox: it's actively developed and still runs QBCore resources.
• Already on QBCore? Move to QBox. QBCore has left FiveM, and most QBCore scripts keep working on QBox.
• Already on ESX? Stay on ESX Legacy. Switching frameworks on a live server means migrating your database and replacing many scripts.

ESX

ESX (es_extended) is the oldest of the three and still has a huge script ecosystem. Today's maintained version is ESX Legacy. Most paid script stores support it, and many server owners know it well.

• Good: biggest back catalog of resources, lots of documentation and community help.
• Watch out for: older free resources written for pre-Legacy ESX versions; they often need fixes.

QBCore

QBCore (qb-core) grew quickly from 2021 onwards and is the framework behind many popular servers. It comes with a large set of first-party qb- resources (inventory, phone, garages and so on), which makes it quick to get a full server running.

• Good: very complete starter set, large community, wide script support.
• Watch out for: in late 2026 the QBCore project withdrew from FiveM to focus on another platform. The code is still available, but nobody has promised to maintain it. What that means for your server.

QBox

QBox (qbx_core) started as a fork of QBCore and has become its actively developed successor. It leans on the Overextended libraries (ox_lib, ox_inventory, oxmysql) and focuses on performance and security. Crucially, it ships a compatibility layer so most QBCore resources run on QBox unchanged.

• Good: active development, modern code, works with the QBCore ecosystem.
• Watch out for: a few QBCore resources that reach deep into old internals may need small changes.

Side by side

	ESX Legacy	QBCore	QBox
Core resource	es_extended	qb-core	qbx_core
Development	Maintained	No longer developed for FiveM	Active
Runs QBCore scripts	No	Yes	Yes, via compatibility layer
Typical stack	ESX resources, ox libraries	qb- resources	ox libraries, qbx_ resources

What it means for buying scripts

Check that a script supports your framework before you buy, and whether it needs a different download per framework. Every Zerio script lists its frameworks on the product page:

• FiveM scripts for ESX
• FiveM scripts for QBCore
• FiveM scripts for QBox
• Standalone FiveM scripts that work without any framework

Scripts sold for QBCore also run on QBox, so moving from QBCore to QBox later doesn't mean buying again.