Qbox is the newest major RP framework for FiveM and the direct successor to QBCore. It was built by developers from the QBCore community who wanted to modernize the framework without the baggage of backward compatibility. This article covers what Qbox does differently, how migration from QBCore works and when the framework is the right choice.
What is Qbox?
Qbox is an open-source RP framework that builds on the architecture of QBCore but has rewritten or replaced nearly every component. The core is lighter, the code is better structured and the default components come from the ox ecosystem: ox_lib, ox_inventory, ox_target and ox_fuel.
The project lives on GitHub under the Qbox Project organization and is actively maintained. In 2026, Qbox is the fastest-growing FiveM framework by commits and new contributions.
What changes compared to QBCore?
The ox library as foundation
Where QBCore uses its own components (qb-inventory, qb-target, qb-menu), Qbox replaces them with ox alternatives:
| QBCore | Qbox | Notes |
|---|---|---|
| qb-inventory | ox_inventory | Better UI, weight system, item metadata |
| qb-target | ox_target | Faster raycast, less client-side load |
| qb-menu | ox_lib (menu/context) | Unified UI components |
| qb-input | ox_lib (input dialog) | Built-in validation |
| qb-fuel | ox_fuel | More realistic fuel consumption |
| qb-doorlock | ox_doorlock | Better performance with many doors |
Better code quality
Qbox uses more strictly structured Lua with type annotations, better error handling and fewer global variables. The codebase is smaller and more readable, which makes it easier to find bugs and customize scripts.
Performance
Thanks to the ox components and the cleaned-up core, the baseline resource usage of Qbox is lower than QBCore. In benchmarks a standard Qbox installation uses roughly 15 to 25 percent less server-side tick time than a comparable QBCore setup. The difference grows as more players come online.
Backward compatibility with QBCore scripts
Qbox includes a compatibility layer that allows many QBCore scripts to work without modification. Scripts that call QBCore.Functions are forwarded to the Qbox equivalents through a bridge. This works for most common scripts, but not all:
- Scripts that call qb-inventory or qb-target directly without going through the framework need adjustment.
- Scripts that use internal QBCore functions outside the public API may not work.
- UI elements that rely on qb-menu or qb-input must be rewritten to ox_lib.
Migrating from QBCore
A migration from QBCore to Qbox is more manageable than from ESX to QBCore, but it is not a one-click operation. Here is the step-by-step process:
- Backup: make a full backup of your server, including the database, resources and server.cfg.
- Install Qbox: use the Qbox recipe in txAdmin for a clean installation on a test server. This gives you the complete base set.
- Migrate the database: Qbox uses the same database structure as QBCore for player data. The
players,player_vehicles,player_housesandapartmentstables are compatible. Inventory data needs to be converted from qb-inventory format to ox_inventory format; migration scripts are available on GitHub. - Test scripts: install your scripts one by one and test them. Start with the core (jobs, vehicles, housing) and only then add cosmetic scripts.
- Configure ox components: configure ox_inventory, ox_target and ox_doorlock. The configuration files are in the resource folders and well documented.
- Check the QBCore bridge: test whether QBCore scripts work correctly through the bridge. Watch the server console for error messages pointing to missing functions.
Qbox versus ESX and QBCore
A detailed comparison of all three frameworks is available in ESX vs QBCore vs Qbox. The short version:
- ESX: the largest script ecosystem, but an aging codebase. Good if you want lots of ready-made scripts.
- QBCore: a solid middle ground, but gradually being overtaken by Qbox. Existing QBCore servers run fine as they are.
- Qbox: the best performance and most modern code. Recommended for new servers in 2026.
Our recommendation
Starting a new FiveM server? Choose Qbox. In 2026 the framework has enough scripts, active support and the strongest technical foundation. The ox libraries have become the standard for new script development, so scripts you buy or download are increasingly likely to use ox_lib.
Running an existing QBCore server that works well? Migration is not urgent. QBCore is still maintained and most scripts work. Migrate when you are planning a major rebuild anyway, not as a goal in itself.
Qbox runs on all FiveM plans at HostValues. txAdmin offers Qbox as a recipe during first-time setup. See also our txAdmin setup guide for the first steps.
