How to Make a FiveM Server (2026) — Step by Step

Making a FiveM server is genuinely doable in an afternoon — if you do the steps in the right order. Most first servers die because someone grabbed a “prebuilt” pack, hit 47 console errors, and quit. Here’s the order that works, from someone who runs a live 500-resource city.

1. Get a license key and a box

Create a Cfx.re license key at the Cfx.re keymaster (free). For hosting: your own PC is fine for testing with friends; for anything public, get a VPS or dedicated box — FiveM cares more about single-core CPU speed and RAM than core count. 8 GB RAM is a workable floor for a small QBCore city; 16 GB gives you headroom.

2. Install the server artifacts

Download the latest recommended server artifacts (not the bleeding-edge optional build) from Cfx.re, unpack them, and create a separate server-data folder alongside. Your server.cfg lives in server-data, and it’s where your license key, ports, and resource list go.

3. Pick a framework — before you install anything else

For roleplay, that’s QBCore or Qbox (ESX is the older third option). This choice decides which scripts you can run, so make it first, not after you’ve collected 40 random resources. Not sure which? I wrote a full QBCore vs Qbox comparison. Short version: QBCore has the bigger script ecosystem; Qbox is the leaner, more actively modernized fork.

4. Database: MariaDB + oxmysql

Roleplay frameworks need a database. Install MariaDB (or MySQL), create a database and user, and use oxmysql as the connector resource — it’s the standard. Put your connection string in server.cfg and confirm the console shows a clean connection before you add gameplay resources. Half of all “my server is broken” posts are a bad database string.

5. Install the framework and core resources in dependency order

Order matters more than anything else in this hobby. A sane QBCore boot order: oxmysql → ox_lib → the framework core → inventory (ox_inventory or qb-inventory) → targeting (pick one: qb-target or ox_target — running both is the classic conflict) → jobs, economy, phone, dispatch. Add resources a few at a time and restart between batches, so when something breaks you know which addition did it.

6. Configure identity & sync

Enable OneSync in server.cfg (you want it on for anything beyond a handful of players), set your server name, tags, and max clients, and set up multicharacter if your framework build didn’t ship with it. Install txAdmin (bundled with the artifacts) — it gives you a web panel for restarts, bans, and live console instead of babysitting a terminal.

7. Test like a player, then optimize

Join your own server and actually play: spawn, buy something, take a job, crash a car. Watch the console for errors and resmon for resource cost. A healthy idle server sits low; if something eats milliseconds while nobody is using it, fix or replace it now — it only gets worse under load. If the city stutters, my lag-fixing guide covers the usual suspects.

The shortcut most people regret

The $5 “full server” pack. It’s almost always a leak dump: broken dependencies, duplicate resources, sometimes worse. I’ve written up why leaked scripts wreck servers — read that before you spend even five bucks. If you’d rather skip the whole setup grind, a properly configured framework install is exactly the kind of job I do for a flat $90.