QBCore has left FiveM: why to move to QBox and how to migrate

QBCore is no longer a FiveM project. In late 2026 it rebranded around Mantle, a new platform that has nothing to do with FiveM, and Cfx.re removed QBCore from the txAdmin recipe list. If your server runs on QBCore, the best next home for it is QBox: it grew out of QBCore, it is actively developed, and it runs most of the scripts you already have.

The short answer

• QBCore for FiveM is over. The project says it is "withdrawing from all other platforms to focus on Mantle".
• Your server still runs. Nothing was switched off, and the code is still on GitHub.
• Move to QBox. It started as a copy of QBCore, so it is the closest framework to what you have, and most QBCore scripts work on it unchanged.
• Plan it, don't panic. Do the migration on a copy of your server, test it, then switch.

What happened to QBCore

• 23 August 2026: the FiveM code, qb-core and about 70 qb- resources, was moved out of the main QBCore organisation into a separate one, qbcore-fivem.
• 29 October 2026: Cfx.re removed QBCore from the txAdmin recipe list and marked it deprecated. New servers set up through txAdmin can no longer pick it.
• 31 October 2026: qbcore.org and the QBCore GitHub profile were rewritten around Mantle. The profile now says QBCore is "no longer pursuing implementations for other platforms".

Mantle is a platform for building multiplayer worlds in Unreal Engine 5. It is a different engine and a different game, so nothing from a FiveM server carries over to it.

Did QBCore shut down?

For FiveM, in practice, yes. The repositories are still public and not archived, and the code is open source, so nothing disappears overnight. But the project has left, the old documentation is kept only "as a reference", and nobody has promised security fixes or updates. A framework without maintainers gets riskier every month: exploits stay open, and platform updates that break something stay broken.

Why QBox

• It comes from QBCore. QBox started as a copy of QBCore, so jobs, gangs, player data and the way scripts talk to the core will all feel familiar.
• Your scripts keep working. qbx_core includes a bridge that answers QBCore's functions and events, so most QBCore scripts run without changes. You can convert them properly later, one at a time.
• It is actively developed. The latest qbx_core release, 1.24.1, came out on 30 October 2026.
• It is the framework Cfx.re lists. The txAdmin recipe list describes QBox as "the most modern and optimized framework, while compatible with QBCore resources".
• A new server takes minutes. Pick the QBox recipe in txAdmin and you have a working base to migrate into.

How the migration works

QBox publishes a full migration guide. In outline:

1. Set up a test server. Install QBox with the txAdmin recipe on a separate server. QBox needs MariaDB 10.9 or newer.
2. Copy your database and run the conversion on the copy. Vehicles, jobs, gangs, inventories and clothing are converted.
3. Swap the resources QBox replaces. qb-inventory becomes ox_inventory, qb-target becomes ox_target, and qb-menu, qb-input and the progress bar are covered by ox_lib. Multicharacter and the connection queue are built into qbx_core.
4. Go through your scripts. Most run through the bridge. Scripts built directly on qb-inventory, qb-target or qb-menu need a QBox version or an update.
5. Test with your staff, then switch. Keep your backups for a good while after going live.

Never run the migration on your live server.

What does not carry over

According to QBox's guide, a few things have to be set up again: houses and apartments, saved outfits, phone contacts and messages, weapon attachments, bank transaction history and weed plants. Staff permissions also change names, from qbcore.admin style to group.admin style. Tell your players before the switch so nobody is surprised.

Not ready to move yet?

Staying on QBCore for a few more months is fine for a stable server. Keep your own copy of every qb- resource you use, watch the qbcore-fivem repositories for security fixes, and don't build new systems on parts you will replace anyway.

Starting a new server? Start on QBox. If you are weighing ESX instead, our framework comparison covers the differences.

Your Zerio scripts on QBox

Every Zerio script sold for QBCore also runs on QBox, so migrating does not mean buying anything again:

• FiveM scripts for QBox
• FiveM scripts for QBCore
• Standalone FiveM scripts that don't depend on a framework at all

Not sure how a script will behave after the move? Ask in our Discord before you start, and we'll tell you what to expect.

Sources

• qbcore.org and the QBCore GitHub profile, the project's own statements
• txAdmin recipe list, where QBCore is marked deprecated
• QBCore FiveM on GitHub, where the FiveM code now lives
• QBox migration guide and qbx_core on GitHub