How to Set Up a FiveM Server in 2026 (Step-by-Step Guide)

Setting up a FiveM server sounds intimidating, but the modern toolchain makes it genuinely approachable. This guide takes you from an empty folder to a running server you can invite friends to — and points out the decisions that matter later.

Before you start: what you need

• A machine to run the server (a rented host, a VPS, or your own PC for testing).
• The latest FiveM server artifacts (the server build).
• A free Cfx.re license key from keymaster.fivem.net.
• 30–60 minutes.

Step 1 — Choose where to host

Your first real decision is hosting. There are three routes:

For a first public server, a dedicated FiveM host is the least painful path. Look for one with DDoS protection, NVMe storage and a location close to your players — latency matters enormously for roleplay.

Step 2 — Get your license key

Head to keymaster.fivem.net, sign in with your Cfx.re account, and register a new server key. You can lock it to an IP later. Keep this key private; it identifies your server.

Step 3 — Download the server artifacts

The artifacts are the actual FiveM server build. Always use a recent recommended artifact rather than the newest possible one — bleeding-edge builds can break resources. We track the current recommended version in our server artifacts guide.

On Windows you download a ZIP; on Linux you pull a tarball. Extract it into a dedicated server/ folder, separate from your resources.

Step 4 — Install txAdmin (the easy way)

Modern FiveM artifacts ship with txAdmin, a web-based control panel that handles almost everything: deployment, restarts, player management, bans and console access.

1. Start the server executable once.
2. txAdmin prints a local URL and a PIN.
3. Open it in your browser, create an admin account, and link your license key.
4. Use the recipe deployer to install a full framework automatically.

This is the single biggest reason server setup got easier — txAdmin can deploy a complete ESX or QBCore base for you in a few clicks.

For the full click-by-click walkthrough — the setup wizard, the database, ports, scheduled restarts and admin accounts — follow our dedicated txAdmin installation tutorial.

Step 5 — Choose your framework

If you have not decided yet, read our full ESX vs QBCore vs Qbox comparison. The short version:

• ESX — the largest ecosystem, easiest to find scripts and tutorials.
• QBCore — modern and roleplay-first.
• Qbox — a performance-focused continuation of QBCore.

txAdmin can deploy any of them as a starting recipe. From there you build on top.

Step 6 — Add and configure resources

With a framework running, you add resources — each in its own folder inside resources/, each enabled in your server.cfg with an ensure resourcename line.

Order matters. Your framework and its dependencies should start before the scripts that rely on them. A typical server.cfg groups them logically:

# Core
ensure oxmysql
ensure es_extended

# Gameplay
ensure my-inventory
ensure my-hud
ensure my-garage

As you add resources, watch two things: dependencies (does this script need a specific inventory or framework version?) and performance (how much does it cost per frame?). We cover the latter in depth in our server optimization guide.

Step 7 — Configure server.cfg essentials

At minimum, set:

• sv_hostname — your server name in the browser.
• sv_maxclients — player slots (start conservative).
• sv_licenseKey — your key from step 2.
• endpoint_add_tcp / endpoint_add_udp — networking.
• One or more admins via your framework or txAdmin.

Step 8 — Test, then go live

Connect locally with connect localhost, then have a friend connect via your public IP or your host’s connect address. Walk through the core loop: spawn, get a job, open your inventory, drive, interact. Fix errors shown in the txAdmin console before you announce anything.

Common beginner mistakes

• Chasing the newest artifact instead of the recommended one.
• Installing 200 resources on day one — start lean, add deliberately.
• Ignoring resmon until the server already lags with 30 players.
• Skipping backups of your MySQL database.

What to do next

Once your server is stable, focus on two things that decide whether players stay: a coherent set of well-optimized core resources (inventory, HUD, jobs) and performance. Read our framework comparison and optimization guide next — they are where good servers become great ones.