How to Make a FiveM Server with QBCore in 2026

Step 1: Spin up the FiveM server itself

This is the part hosting handles for you. On BruceNode you pick the FiveM plan, set the region, deploy. The server comes up with txAdmin pre-installed. You'll see the panel login info in your dashboard after the 60-second provision finishes.

If you're self-hosting, you'd be running the standard fxserver build with txAdmin alongside it. The QBCore install steps below assume txAdmin is what you'll use to deploy recipes, which is the modern standard.

Step 2: Deploy the QBCore recipe via txAdmin

txAdmin's "deploy" feature uses recipes — JSON files that describe what to install, in what order, with what configs. The qbcore-framework recipe is the official one and handles 90 percent of the setup automatically.

In txAdmin:

1. Go to Settings → Server.
2. Click Deploy a new server.
3. Pick Use a remote recipe.
4. Paste the QBCore recipe URL: https://raw.githubusercontent.com/Qbox-project/txAdminRecipe/main/recipe.yaml (or the qbcore-framework variant if you prefer the original — both are maintained, qbox is the active fork in 2026).
5. Set your install path, server name, MySQL credentials when prompted.
6. Hit deploy.

txAdmin downloads all the QBCore resources, sets up the server.cfg, runs the SQL schema against your MySQL database, and writes a starter set of jobs and items. When it finishes you'll see a green checkmark and a "start server" button.

Step 3: MySQL setup

The biggest variable in QBCore setup is the database. Three options:

A. Use your host's bundled MySQL. If your host gives you MySQL on the same node as your FiveM server, this is the easiest path. Connection latency is near-zero, no firewall to configure. Most managed FiveM hosts include this.

B. Use an external MySQL. Spin up a managed MySQL elsewhere (Aiven, PlanetScale, your own VPS). Slightly more setup, more flexibility. Pick this if you want to swap servers later without migrating the database.

C. Self-host MySQL on the same box. Only viable if you're running FiveM on a VPS you fully control. Not recommended for managed hosting because most managed FiveM hosts don't let you run a separate MySQL daemon in the same container.

For most servers, A is the right call. Latency under 1ms means QBCore's hundreds of per-tick queries don't slow your TPS.

After the recipe deploys, txAdmin will have written the schema. You can verify by connecting to your MySQL with HeidiSQL or DBeaver and listing tables. You should see players, characters, bank_accounts, items, vehicles, jobs and 20-something more.

Step 4: server.cfg basics

txAdmin writes most of server.cfg for you, but two lines you'll want to know exist:

sv_licenseKey "cfxk_xxxxx_xxxxx"        # your keymaster licence
sv_hostname "Your RP Server Name"        # what shows on the server list

Plus the QBCore-specific exports near the bottom:

ensure qb-core
ensure qb-multicharacter
ensure qb-spawn
ensure qb-apartments
ensure qb-banking
# ... and 30+ more qb-* resources

You generally don't edit these by hand — txAdmin's resource manager UI is faster and safer. But knowing where they live helps when you need to debug an order issue.

Step 5: Configure your first jobs

Out of the box QBCore ships with a generic set of jobs. To customise (which is most of what you'll do as an admin):

1. Open qb-core/shared/jobs.lua in the file manager.
2. Each job is a table with name, label, grades, payment, default duty status. Edit existing or add new.
3. For more involved jobs (police, EMS, mechanic), the actual logic lives in dedicated resources (qb-policejob, qb-ambulancejob, qb-mechanicjob). The jobs.lua entry is just the metadata; the dedicated resource is the gameplay.
4. Restart the server (or use refresh + ensure qb-core in the txAdmin console) for changes to apply.

Don't try to add a deep custom job on day one. Get the stock jobs working first, learn the QBCore patterns, then build.

Step 6: Add your phone

QBCore doesn't ship with a phone — you pick one. The big options in 2026:

• gksphone — paid, polished, the most popular paid option
• lb-phone — paid, modern UI, growing fast
• qb-phone — free, basic, fine for starting out
• roadphone — paid, good for police RP

The free qb-phone is the path of least resistance. Drop it into resources, ensure it in server.cfg, restart, the phone item should appear in your QBCore inventory automatically.

For paid phones, follow the vendor's install doc — they generally provide their own QBCore integration and may require swapping out the default qb-inventory item.

How much hosting you actually need

QBCore is heavier than vanilla FiveM. The framework itself idles around 800 MB RAM. Per-player overhead is roughly 50 MB. Math:

• 16-player server: ~2 GB allocated (base) gets tight. Recommend 3-4 GB for breathing room.
• 32-player server: ~3-4 GB base + plugins. Recommend 6-8 GB.
• 64-player active server: ~6-8 GB base + plugins. Recommend 12-16 GB, especially if you're running multiple heavy job resources, custom MLOs, and high render distance.

CPU matters more than RAM at the upper end. FiveM and QBCore are single-thread bound on the main game loop, so single-core clock speed determines TPS ceiling.

Use the resource calculator to plug in your numbers, it does this math for you.

Common QBCore issues and how to fix them

"Server starts but I can't connect, says framework not loaded." The qb-core resource didn't start in time, or it crashed. Check txAdmin console for the first error after server boot. Usually a missing dependency (another resource that qb-core depends on).

"Players can connect but lose their character on relog." Database connection dropped, or QBCore can't write to MySQL. Verify the connection string in your server.cfg and that MySQL is reachable from the FiveM server's network.

"TPS drops to 15-17 on any active server." A specific resource is hot-looping. Open txAdmin's resource performance view and find the resource using > 1ms per tick. Usually a poorly-written third-party script.

"Inventory items don't appear after install." You added items to qb-core/shared/items.lua but didn't restart qb-core. refresh then ensure qb-core in the txAdmin console.

"Police job lets anyone use commands as cop." You forgot to set permissions in server.cfg. QBCore uses ace permissions — see server.cfg for the add_ace lines and follow the pattern.

Resources to add after the core setup is stable

Don't bolt these on day one. Get the vanilla QBCore experience working with your friends for a week, then start adding:

• A custom map (MLO) — most popular RP servers have at least one MLO. Free options on GTA5-Mods, paid ones on FiveM stores.
• Custom vehicles — cars beyond the GTA base set. Pack files drop into resources/[vehicles]/.
• Drugs and crime resources — qb-drugs, qb-storerobbery and similar give the criminal side things to do.
• A garage rework — the default garage is functional but spartan. Paid alternatives are richer.
• Better dispatch — ps-dispatch is the community favourite in 2026, replaces the default police call system.

Each addition is one resource folder dropped in + one ensure resource-name line in server.cfg + a restart.

Picking a plan

For a small RP server with friends (under 16 active players), the Standard tier on BruceNode FiveM hosting handles it. For 32+ active players with custom resources, move to Premium. For a public 64-player server with heavy customisations, the Ultimate tier or talk to support about a dedicated allocation.

For a deeper walkthrough on RP server philosophy (rules, whitelisting, community-building), see our FiveM roleplay server guide.

Use code BRUCE20 for 20% off your first month.

Start a FiveM server →