For server owners · 7 min read · updated on Oct 9, 2026

How to create a FiveM server: a step-by-step guide

Learn how to create your own FiveM server: license key, server artifacts, txAdmin, server.cfg, picking a framework, security basics and getting your server listed, step by step.

Getting a FiveM server up and running is quicker than most people expect. The real work starts afterward: configuration, scripts, staff and community. This guide walks you through the whole process, from zero to your first public server, while skipping version-specific details that change all the time. For exact commands and the latest notes, the official docs at docs.fivem.net are always your best reference.

What you need

Before you dive in, figure out three things: where the server will run, which operating system it'll use, and how you'll test it.

• Hardware or hosting: Your own PC is fine for early testing. For a server that's online 24/7, you'll want a rented dedicated server or VPS, or a game server host that offers FiveM. How much CPU, RAM and bandwidth you need depends heavily on your player count, framework and scripts. Start small and scale up once you see how the server handles real load.
• Operating system: FXServer runs on both Windows and Linux. Windows is often easier for beginners, while Linux is common on rented servers and usually lighter on resources.
• A legal copy of GTA V: The server itself doesn't need GTA V. But to connect and test your server as a player, you need a legitimate copy of GTA V and the FiveM client.
• Some patience with text files: A lot of the setup happens in config files, so a decent text editor will save you plenty of headaches.

Step 1: Cfx.re account and license key

Every FiveM server needs a license key. You can get one for free through the Cfx.re Portal:

1. Sign in with your Cfx.re account, or create one.
2. Generate a new server key in the portal.
3. Enter the IP address your server will run on and pick the right server type.
4. Copy the key and treat it like a password. Keep it out of public screenshots and Git repositories.

Step 2: Download the server artifacts

"Artifacts" is what the community calls the actual server software (FXServer). There are separate builds for Windows and Linux, and you'll find the official download through the server setup guide in the FiveM docs.

• Create a dedicated folder for the server software, such as server, and extract the artifacts there.
• Keep the server software separate from your data (resources and config). That makes updates much easier down the road.
• Don't just grab the newest build blindly. There's usually a recommended build, and that's the one to go with.

Step 3: Set up txAdmin

txAdmin is the web panel that ships with FXServer. It handles installation, restarts, logs, bans and a lot more.

1. Start FXServer without any extra parameters (FXServer.exe on Windows, the included start script on Linux).
2. The console shows an address for the txAdmin panel along with a PIN. Open that address in your browser.
3. Link txAdmin to your Cfx.re account and set a master admin password.
4. During setup, choose Popular Recipes or a template. A recipe automatically downloads a starter setup, such as a minimal default server or a framework template.
5. Enter your license key, let the recipe run, and start the server.

Recipes are the safest route for beginners: the folder structure, database connection (for framework recipes) and a first server.cfg are all set up for you.

Step 4: Understanding server.cfg

server.cfg is the heart of your server. Here are the key entries in general terms:

endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"

sv_hostname "My Server | Serious RP | English"
sets sv_projectName "My Server"
sets sv_projectDesc "English serious RP server with a whitelist and active support"
sets tags "roleplay, serious rp, english, whitelist"
sets locale "en-US"
sv_maxclients 32

sv_licenseKey "YOUR_LICENSE_KEY"

A few notes:

• Open your ports: Port 30120 has to be reachable from outside over both TCP and UDP, in your firewall and, if you're hosting at home, via port forwarding on your router.
• Player slots: How many players you can allow depends on OneSync and your Cfx.re settings, among other things. Check the current rules in the docs instead of guessing a number.
• Keep your name and description honest: A clear name that states your style and language attracts the right players. Names stuffed with emojis and all caps tend to drive people away.

Step 5: Pick a framework

A roleplay server almost always needs a framework to handle jobs, inventory, money and characters. The three big options are ESX, QBCore and Qbox. Which one fits best depends on your scripts, your coding skills and your team.

For a detailed breakdown, check out our guide ESX vs. QBCore vs. Qbox. The official docs live at docs.esx-framework.org, docs.qbcore.org and docs.qbox.re.

Step 6: First resources and testing

Resources (scripts, maps, vehicles) go into the resources folder and are started in server.cfg with ensure resourcename.

• Start small: Add resources one at a time and restart the server after each one. That way, you'll know right away what broke if something stops working.
• Stick to trusted sources: Use scripts from reputable sources. Leaked scripts aren't just unfair to the developers, they often come with backdoors.
• Read the console: Errors in the server console or the txAdmin log almost always tell you which resource is causing trouble.
• Test it yourself: Connect to your own server, either via direct connect in the FiveM client or through the server list. Test character creation, jobs, vehicles and everything new players will see first.
• Watch performance: The built-in resource monitor helps you spot scripts that eat up way too much processing time.

Step 7: Security from day one

Most server problems aren't caused by hackers but by skipping the basics.

• Admin permissions via ACE: FiveM handles permissions through the ACE system (add_ace, add_principal). Only give admin rights to people who actually need them, and work with groups instead of individual permissions for everyone.
• Lock down txAdmin: Use strong passwords and no shared accounts. Every staff member gets their own login with the right permissions.
• Backups: Back up your database and config regularly, automatically and to a second location. A backup you've never tested isn't really a backup.
• Keep artifacts up to date: Install server software updates regularly, ideally on a test server first.
• Protect your license key and database credentials: Don't post them on Discord and don't push them to public repositories.

Step 8: Go public and get listed

Once everything runs smoothly, it's time to go public. As soon as your server shows up in the FiveM server list, it gets its own join link in the format cfx.re/join/xxxxxx. You can share it anywhere, and players land straight on your server.

To help players actually find you, a toplist listing is worth it. On GS2THETOP, adding your server takes about 30 seconds: just enter your cfx.re join link, and the details are pulled from the public server list. You can get started here.

A few tips for launch:

• Clean tags make sure your server shows up in the right categories, like Serious RP or Whitelist.
• Votes count monthly: Rankings only count player votes from the current month, and nothing can be bought. See How ranking works for details. With the free gs2thetop script, your players automatically get an in-game reward for voting.
• Build your team: If you're looking for support staff, developers or mappers, Team search can help.

Wrapping up

On the technical side, you can have a FiveM server running with a license key, artifacts and a txAdmin recipe in a single afternoon. What makes a server great comes after that: a well-thought-out concept, stable scripts, a reliable team and solid security basics. Take your time with testing before you go public, because first impressions with new players matter. You'll find more walkthroughs in our guides.