Qbox vs QBCore: Which Framework Fits Your FiveM Server?

Qbox began as a QBCore fork and keeps a bridge so most QBCore scripts still run. Choose Qbox for a new server built on Overextended resources. Stay on QBCore if your live server depends on QBCore-specific resources and migrating solves no problem you can name.

This is a documentation comparison, not an RPScripts test. Both frameworks' docs were reviewed on 13 October 2026; verify against the current docs before you act. RPScripts sells FiveM resources, including ones listed for QBCore and Qbox, and the shop links below go to our own categories.

Qbox vs QBCore at a glance

Sources: Qbox introduction, Qbox FAQ, Qbox conversion guide and the QBCore core object docs.

What is Qbox?

Qbox is a FiveM roleplay framework. Its docs say it started as a QBCore fork whose goal was "improving upon QBCore while maintaining backwards compatibility", and that it uses Overextended's resources while not being affiliated with that team. The FAQ adds that many Qbox resources have been refactored since the fork. For install steps and the bridge in more depth, see the Qbox framework guide.

What is QBCore?

QBCore is the roleplay framework Qbox forked from. Resources typically fetch its core object with exports['qb-core']:GetCoreObject(), which the QBCore docs call "the backbone of the qb-core framework". Its Windows install guide has you pick the txAdmin "QBCore Framework" template; see the QBCore framework guide and how to install and test QBCore scripts.

Will QBCore scripts work on Qbox?

Most will. The Qbox FAQ answers "Will my QBCore scripts work with Qbox?" with "Yes (in most cases)" and says the bridge layer covers "the documented and proper ways of using qb-core". You do not have to convert a resource for it to run. The FAQ lists what does not carry over:

• direct access to database tables;
• direct access to qb-core files that aren't meant to be used by other resources;
• invalid usages of existing functions;
• multijob resources that touch Qbox's tables directly or keep Qbox's core data in their own table. They work only by calling qbx_core exports to add, change or remove jobs.

Before you buy or install a resource, check its stated Qbox support and whether it reads framework tables or core files. A QBCore label alone does not test that.

Which should you choose?

Qbox fits when

• You are starting a new server and want the Qbox recipe and its ox-based setup.
• Your must-have resources declare Qbox support or use documented QBCore APIs only.
• You can rehearse the database and character conversion on a full copy.

QBCore fits when

• Your live server is stable and the move would not fix a problem you have measured.
• A critical resource edits core files or reads core tables directly.
• You have no restore-tested backup or staging copy.

This is an editorial recommendation from the documented differences, not a performance or popularity ranking. If you are still choosing between these two and ESX, read the FiveM frameworks comparison. Starting from scratch? See how to create a FiveM server.

Migrating QBCore to Qbox

The conversion guide recommends installing Qbox from its txAdmin recipe to avoid issues, and its installation page says to have MariaDB installed and that MySQL is not supported. Outline, with the guide's own warnings:

1. Back up files and database, then restore the backup somewhere else. A backup you have not restored is unproven (backup and restore guide). Success check: the restored copy starts and a character loads.
2. Update the config files (server.cfg, ox.cfg, permissions.cfg, voice.cfg). The recipe downloads them; without the recipe, add or update them manually from the latest versions in the Qbox txAdminRecipe repository.
3. Change job and gang grades to numbers. The guide notes grades are numbers in Qbox but strings in QBCore (jobs.lua, gangs.lua).
4. Set up ox_inventory following the ox_inventory documentation for QB frameworks; the guide says to back up first. Do it on a copy.
5. Run the SQL file shipped with qbx_core (adds last_logged_out, sets citizenid collation to utf8mb4_unicode_ci), and for multijob run convertjobs in the txAdmin console after starting the server. If a foreign key error appears, other tables' citizenid collation may need the same change.
6. Do not use external multijob/multigang resources unless guaranteed Qbox compatible; the guide warns that incompatible ones or resources that modify the core's database tables "may lead to data corruption".
7. Test by category: characters, jobs, money, inventory, then vehicles, housing, phones and admin tools. Keep the untouched pre-migration backup for rollback.

Rewriting QBCore calls into Qbox exports is optional and can be done one call at a time, since both styles work together. See also converting scripts between ESX, QBCore and Qbox.

Find resources for either framework

If you need scripts, browse the Qbox scripts or QBCore scripts category. Each listing states its framework support; read the dependencies before installing.

FAQ

Is Qbox better than QBCore?

Neither is better for every server. Qbox suits new builds that want its ox-based design; QBCore suits stable servers built on QBCore-specific resources. Decide from your resources, data and team, not from a ranking.

Is Qbox a fork of QBCore?

Yes. The Qbox docs say it started as a QBCore fork in 2022. Many resources have since been refactored, so it is no longer a drop-in copy.

Do I need to convert my QBCore scripts for Qbox?

Usually not. The Qbox FAQ says the bridge layer covers the documented and proper ways of using qb-core. Scripts that read database tables or core files directly can still break.

Can I move a live QBCore server to Qbox?

Yes, with the official conversion guide: back up and restore-test first, change job and gang grades to numbers, set up ox_inventory and run the qbx_core SQL on a copy before touching production.

Does Qbox work with MySQL?

The Qbox installation page says it expects MariaDB, that MySQL is not supported, and lists MariaDB 10.9.0 as the minimum. Re-check that page for the current version before you install.