ESX, QBCore or standalone: how to choose a FiveM framework
The first big decision when building a FiveM roleplay server is the framework. It is the foundation that handles players, money, jobs, inventories and the database. Nearly every other script you install is written for one framework, so the choice shapes everything after it, and changing later is painful. Here is how to think about it.
What a framework does
A framework gives scripts a shared way to do common things. Instead of every script inventing its own idea of a player or a bank balance, they all ask the framework. That is why a job script from one author works with a shop script from another, as long as both support the same framework.
Without one, you have a standalone server, where every script is independent.
The main options
ESX is the longest-established framework. It has a huge library of scripts and many tutorials, because it has been used for years. Its age means a lot of older code, and quality varies between scripts.
QBCore is newer and widely used for roleplay. It has a modern structure, an active community and many ready-made scripts. Many servers consider its code easier to extend.
Standalone or custom means no shared framework. It suits small projects, racing servers or freeroam, where you only need a few scripts. It gives you full control, with more work.
Both ESX and QBCore are free and open source, and each has several versions and forks, so check the exact version a script supports.
What to compare
| Question | Why it matters |
|---|---|
| Which scripts do you want? | Check the frameworks supported by the scripts you must have |
| How experienced are you? | A framework with good documentation helps beginners |
| Is it actively maintained? | Old frameworks break as the game and FiveM update |
| How big is the community? | More answers, scripts and example servers |
| Do you plan to write your own scripts? | Look at how readable the framework's code is |
Browse the scripts you would buy or download before you decide, not afterwards. If your must-have job pack only supports one framework, that settles it.
Mixing frameworks
Avoid it. A script written for one framework often cannot talk to another, and converting scripts is slow, error-prone work. Some "bridge" resources exist, but they add fragile layers. Choose one and keep to it.
The database
Both frameworks store data in a MySQL or MariaDB database. You need one, with a user and password, and a resource that connects to it. A commonly used one is oxmysql. Without a working database, the framework will not load. Your hosting plan needs to provide one, or you run one yourself, as described in How to install and secure MariaDB if you use a VPS.
Setting up
The general path is the same for each:
- Create the database and import the framework's SQL file.
- Install the framework resource and its dependencies.
- Add them to
server.cfgin the correct order. See FiveM server.cfg and license key. - Start with the base setup and test it, before adding scripts.
- Add scripts one at a time. See How to install FiveM resources.
Follow the framework's own installation guide closely. Skipping a step, especially the database import, causes most first-day problems.
Performance and cost
Frameworks add overhead, and so does every script. The framework itself is light, but a server running a hundred scripts is heavy. Plan your memory and CPU by the number of scripts and players, not by the framework. How to choose the right plan can help you size it.
A sensible way to decide
- List the scripts and features you need.
- See which framework most of them support.
- Look at how recently the framework was updated and how active its support community is.
- Set up a test server with that framework, and try the essentials.
- Only then commit.
Take your time here. A day of testing can save weeks later.
Still stuck? Open a ticket on Discord - run /ticket in any channel, pick a department, and include your Server ID or Invoice ID so we can jump straight in.