Help me choose a Framework
A framework is the foundation of a FiveM roleplay server. It keeps track of players, their characters, jobs and money, and almost every script you add is built on top of it. That makes it the first decision for a new server, and the one that is hardest to change later.
All UNIQ resources work on the three most popular frameworks: ESX, QBCore and QBox. This page explains how they differ and which version of our resources you need for each.
Short on time? Starting a brand new server? Go with QBox. Already running a server? Stay on the framework you have. Switching rarely pays off unless something is really holding you back.
At a glance
| ESX | QBCore | QBox | |
|---|---|---|---|
| Core resource | es_extended |
qb-core |
qbx_core |
| Around since | The earliest of the three | After ESX | The newest, built from QBCore |
| Out of the box | The essentials | Many systems of its own | Modern community resources such as ox_inventory |
| Best for | Servers with an existing ESX setup | Servers that want everything from one team | New servers that want a clean, modern base |
| UNIQ version to buy | ESX | QBCore/QBox | QBCore/QBox |
ESX
ESX has been around the longest, and a huge number of free and paid scripts were written for it over the years. The current, maintained version is ESX Legacy.
It gives you the essentials, like jobs, money and basic player management. Most other systems, such as the inventory, interaction menus, vehicle keys or a phone, come from resources you add yourself.
A good fit if:
- your server already runs on ESX
- you rely on older scripts that only exist for ESX
- you prefer a lighter base and want to choose every system yourself
Keep in mind:
- you will install more resources yourself before the server feels complete
- some newer scripts focus on QBCore and QBox first
QBCore
QBCore came after ESX and ships many systems of its own: inventory, target, vehicle keys, fuel, an admin menu, a phone and more. Everything comes from the same team, so the pieces are designed to work together.
It is very widely used, so it is easy to find tutorials, guides and people who can help.
A good fit if:
- your server already runs on QBCore
- you use a custom inventory or scripts that change QBCore's core files
- you want a full set of features from a single source
Keep in mind:
- you depend on QBCore's own version of each system, even where a stronger community resource exists
- replacing those systems later is possible, but it takes work
QBox
QBox started as a fork of QBCore. Instead of building every system itself, it uses well-known community resources by default, such as ox_inventory and ox_lib.
qbx_core stays compatible with QBCore, so most QBCore scripts run on QBox without changes. That is also why the same version of our resources works on both.
A good fit if:
- you are starting a new server
- you want a modern, well-maintained base without building it piece by piece
- you already replaced QBCore systems with ox resources and want to go all the way
Keep in mind:
- it is built around
ox_inventory, so a custom inventory is not a good match - scripts that edit QBCore's internals may need changes before they work
Which version of our resources do I need?
Every UNIQ resource comes in two versions:
- ESX for servers running
es_extended - QBCore/QBox for servers running
qb-coreorqbx_core
Pick the version on the product page before you add it to your cart. If you are not sure which framework your server uses, look in your server.cfg for ensure es_extended, ensure qb-core or ensure qbx_core.
The ESX version will not run on a QBCore or QBox server, and the other way around. If you bought the wrong version, open a ticket on our Discord before buying again.
Thinking about switching?
Moving an existing server to another framework affects every script, every database table and every player's data. Before you do it:
- Set up a separate test server on the new framework.
- Install your full list of resources there and check that each one works.
- Plan how you will move player data. Each framework stores it differently.
- Switch the live server only when everything works on the test server.
Going from QBCore to QBox is the easiest move, because most resources keep working. Moving between ESX and QBCore/QBox is a bigger job and usually means replacing scripts with their other version.
Still not sure?
Ask us on Discord. Tell us what kind of server you are planning, and we will tell you what we would pick.
Last updated November 22, 2026