How to create a FiveM server

Running your own FiveM server lets you:

• Create your own multiplayer GTA V server: roleplay, races, deathmatch or free roam.
• Fully customize the gameplay with scripts, vehicles, maps (MLOs) and jobs.
• Host from 32 to 128 players and beyond, depending on your configuration and hosting.
• Grow a loyal community around a world and rules that are entirely your own.

In 2026, FiveM remains the most active multiplayer scene in GTA V, driven by roleplay and by the arrival of GTA V Enhanced. Creating a server has never been more accessible: txAdmin now handles the whole installation end to end, right from your browser.

FiveM (FXServer) is mostly single-threaded: CPU clock speed matters more than the number of cores. Make sure your machine meets these requirements:

• ✔ RAM : 8 GB minimum for a small server; 16 to 32 GB for an ESX/QBCore roleplay server with lots of scripts
• ✔ CPU : 4 high-frequency cores (3.5 GHz or more): per-core speed matters more than core count
• ✔ System : 64-bit Windows or Linux (Linux recommended for a production server)
• ✔ Connection : Stable bandwidth and low latency; the server listens on port 30120 over TCP and UDP
• ✔ Hosting : Local PC for testing, VPS or dedicated server with SSD/NVMe storage for a 24/7 server

Before installing, choose the foundation of your server. It determines what your players will be able to do:

CFX Default (no database)

The default FiveM template: free roam, with no database to configure. Ideal for getting started, testing, or a non-roleplay server (races, deathmatch, sandbox).

ESX

The classic roleplay framework: jobs, economy, inventory, companies. A very large script ecosystem. Requires a MySQL/MariaDB database.

QBCore / Qbox

The popular modern alternative for roleplay, modular and actively maintained (Qbox is a community fork). Also requires a MySQL/MariaDB database.

The FiveM server runs on the "artifacts" (FXServer), the official Cfx.re server software. In recent builds, txAdmin is bundled in: nothing to install separately.

1. Go to the artifacts page (runtime.fivem.net) and pick your system: Windows or Linux
2. Download the Recommended build (stable, recommended for production), not the Latest build
3. Extract the archive into a dedicated folder for your server (for example server/)

Linux :

mkdir -p ~/fxserver && cd ~/fxserver
# Téléchargez l'archive .tar.xz depuis runtime.fivem.net, puis :
tar xf fx.tar.xz

txAdmin is the web admin panel bundled with FXServer. It drives the installation, startup and management of your server from the browser.

FXServer.exe

./run.sh

The server.cfg file is the heart of the configuration. txAdmin generates one during deployment; here are the essential directives to know:

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

sv_hostname "Mon serveur FiveM"
sv_maxclients 48

# Ressources de base
ensure mapmanager
ensure chat
ensure spawnmanager
ensure sessionmanager
ensure hardcap

# Base de données (ESX / QBCore)
set mysql_connection_string "mysql://user:password@localhost/fivem?charset=utf8mb4"

sv_licenseKey "VOTRE_CLE_KEYMASTER"

• sv_hostname - Server name shown in the FiveM server list
• sv_maxclients - Maximum number of players (up to 2048; 32 to 64 is common for roleplay)
• sv_licenseKey - Your Keymaster license key, required to start
• endpoint_add_tcp / endpoint_add_udp - Listening address and port (30120 by default, over TCP and UDP)
• ensure - Each resource loads with ensure; the core resources (mapmanager, chat, spawnmanager, sessionmanager, hardcap) are essential
• mysql_connection_string - For ESX/QBCore, set the MySQL connection string via oxmysql

All your server content (scripts, maps, vehicles, jobs) takes the form of resources. Here is how to manage them:

ensure es_extended
ensure esx_menu_default

Database (roleplay frameworks)

ESX and QBCore store players, vehicles and inventories in a MySQL/MariaDB database. Create the database, import the framework .sql file, then connect it via the oxmysql resource. Without a database, these frameworks will not start.

FiveM uses port 30120 over TCP and UDP by default. For your server to be reachable from the Internet, this port must be open.

Ports to open

• TCP + UDP 30120 (default, over TCP and UDP, can be changed in server.cfg)
• txAdmin uses port 40120 for its web interface: keep it for administration, do not expose it publicly

Firewall rule examples

Windows Defender :

New-NetFirewallRule -DisplayName "FiveM Server" -Direction Inbound -Protocol TCP -LocalPort 30120 -Action Allow
New-NetFirewallRule -DisplayName "FiveM Server UDP" -Direction Inbound -Protocol UDP -LocalPort 30120 -Action Allow

Linux UFW :

sudo ufw allow 30120

Linux iptables :

sudo iptables -A INPUT -p tcp --dport 30120 -j ACCEPT
sudo iptables -A INPUT -p udp --dport 30120 -j ACCEPT

txAdmin centralizes all your server administration from the browser:

• View and manage connected players live (kick, ban, warn)
• Access the live console and restart the server in one click
• Schedule automatic restarts and announcements
• Monitor performance and stability, with crash protection

• ✔ Backups: regularly back up your database and your resources/ folder off the machine. Automate it: a manual backup always ends up forgotten.
• ✔ Updates: regularly replace the artifacts with a newer Recommended build, and keep your resources up to date to fix vulnerabilities and bugs.

• ✔ Watch each resource's compute time with the resmon command: a single poorly optimized resource can drag down the whole server.
• ✔ Limit the number of active resources: every script consumes CPU time on the main thread. Add them gradually and test.
• ✔ Use oxmysql (asynchronous) and optimized queries: badly handled database access is a common cause of roleplay lag.
• ✔ Host on a high-frequency CPU and NVMe storage, and schedule regular restarts via txAdmin to start fresh.