How to Start a FiveM Server in 2026: The Complete Guide

Starting a FiveM server is technically straightforward and practically difficult. Getting a server online takes an afternoon. Getting one that people want to play on takes months.

This guide covers the whole path, including the parts people skip.

First: should you?

Worth being blunt before you spend money. Most new FiveM servers close within three months. The reasons are consistent — no distinct identity, no players, an owner who underestimated the workload, or a staff team that burned out.

Start if you have a clear idea of what your server is for and access to at least a handful of people who'll play it from day one. Don't start because you want to run something big. Nobody joins a server because it has potential.

What it costs

Realistic monthly figures for a server up to roughly 64 slots:

• Hosting: £15–£50/month for dedicated game hosting, or £20–£60 for a VPS you manage yourself.
• Domain: £10–£15/year.
• Paid resources: £0–£300+ upfront. This is where budgets disappear.
• Discord: free, though most communities end up paying for bots or boosts.

Budget £30–£80/month to run something credible, plus whatever you spend on scripts. Assume you'll spend more than you planned on scripts.

Step 1: Choose your hosting

Three options, in rough order of who they suit:

Managed FiveM hosting. Purpose-built control panels, one-click artifact updates, support that understands FiveM. Costs more per unit of hardware. Right choice for a first server.

A VPS or dedicated box. Far better value and total control, but you're responsible for the OS, security, updates and everything breaking at 3am. Fine if you're already comfortable with Linux.

Your own PC. Free, and a bad idea beyond testing. Home connections have poor upload, your IP is exposed to everyone who joins, and the server dies whenever you close your laptop.

What actually matters in the specs

Single-core CPU performance above everything else. FiveM's main thread is largely single-threaded, so a high-clock 6-core beats a low-clock 16-core comfortably. Ignore core-count marketing.

RAM scales with players and asset volume. 8 GB is workable for a small server; 16 GB is safer once you have real content.

Location should match your intended playerbase, not you. A UK server hosted in Dallas will bleed UK players regardless of how good it is.

Step 2: Get the server files

You need the server artifacts from Cfx.re's official runtime builds. Use a recent recommended build rather than the newest available — bleeding-edge artifacts periodically break things, and there's no upside to being first.

Managed hosts usually handle this through their panel.

Step 3: License key and server.cfg

Register a free server key at keymaster.fivem.net and put it in your server.cfg. Without it your server won't appear in listings.

The essentials in server.cfg:

• sv_hostname — your server name as players see it
• sv_maxclients — slot count
• sv_licenseKey — your Keymaster key
• endpoint_add_tcp / endpoint_add_udp — usually 0.0.0.0:30120
• add_principal — your own admin permissions
• ensure lines for each resource, in load order

Never share your license key or commit it to a public repository. Keys get scraped from public GitHub repos constantly.

Step 4: Use txAdmin

txAdmin ships with the server artifacts and is the standard management layer — web-based control panel, player management, live console, scheduled restarts, automatic backups and a guided first-time setup that will configure a working base server for you.

There's no good reason not to use it. Run the setup wizard and let it do the initial work.

Step 5: Pick a framework

The framework provides your core systems — characters, inventory, jobs, money. This decision is expensive to reverse, so make it deliberately.

ESX — the oldest and most widely supported. Enormous resource library, huge amount of documentation and community knowledge, and a lot of that ecosystem is ageing.

QBCore — became the default for serious roleplay servers. Cleaner architecture than ESX, strong resource availability, well suited to RP-focused design.

Qbox — a modernised continuation of the QBCore lineage. Better code quality and performance, smaller ecosystem. Increasingly the choice for new servers starting fresh.

For a new roleplay server in 2026, QBCore or Qbox. Choose ESX only if you have a specific dependency on something that requires it.

Step 6: Database

You'll need MariaDB or MySQL. Managed hosts typically provide one. On a VPS, install MariaDB, create a database and user, and put the connection string in your config.

Set up automated backups on day one. Not later. The single most common catastrophic failure in this hobby is a database loss with no backup, and it ends communities permanently. txAdmin can schedule these — configure it before you have anything worth losing.

Step 7: Resources

Install deliberately and test after each addition. The temptation is to add fifty scripts in one evening; the result is a server that crashes for reasons you can no longer isolate.

A sensible starting set: inventory, jobs your server actually uses, a phone, a decent HUD, and a voice resource. That's it. Add more once the base is stable.

On paid resources

Buy from Cfx.re's own asset store or established, reputable creators. Leaked scripts are a bad idea for practical reasons more than moral ones — they're a common malware and backdoor vector, and a backdoored resource means someone else controls your server.

Watch performance from the start

Use resmon in-game to check resource cost. Anything sitting above 1.00ms while idle deserves scrutiny. Performance problems compound quietly and are far harder to untangle once you have sixty resources installed.

Step 8: Rules, staff and Discord

The technical work is the easy half.

Write your rules before you open. Vague rules are unenforceable and every enforcement decision becomes an argument.

Recruit staff carefully and slowly. Handing admin permissions to whoever volunteers first is how servers get destroyed from the inside. Give minimum necessary permissions and log actions.

Set up Discord properly. Applications, support tickets, announcements, rules, and staff-only channels. Your Discord is where your community actually lives — the server is where they play.

Step 9: Legacy or Enhanced?

New consideration as of 2026. FiveM Enhanced entered early access on 21 July 2026 with real technical advantages: the rebuilt server needs up to 50% less RAM per player and syncs at up to 120 Hz against Legacy's 30–40 Hz.

But Asset Escrow isn't supported at early access, so most paid resources can't ship there yet, and the entire established playerbase is still on Legacy.

Start on Legacy. Test Enhanced on a second instance. Our migration guide covers the decision in full.

Step 10: Getting players

Your server now exists and nobody knows. This is the part that actually determines whether you're still running in six months — and it's covered properly in How to Get Your First 50 Players.

The short version: list everywhere, have a clear identity, and open with enough people that the first arrivals find something happening.

Ready to launch? List your server on FiveBrowse — free, and it's where players actually look.