Setup has gotten more approachable over the years. txAdmin recipes automate framework installation, documented walkthroughs cover every platform, and hosting panels handle most of the infrastructure configuration. The problem is not complexity. Most new owners stall out because they do things in the wrong order, downloading scripts before picking a framework, or configuring a server.cfg before generating a license key. The result is hours of frustration and a server that never launches.
Short answer: Building a FiveM server in 2026 means working through a fixed sequence. Confirm your hardware and hosting, generate a Keymaster license key, install FXServer, link txAdmin, choose ESX or QBCore, open the required ports, then add a starting script stack one resource at a time. Hardware first, software second, framework third, then ports and scripts. Follow the order and you will not get stuck.
FiveM server requirements: what your machine needs before you install anything
Before you touch a single file, confirm that your machine can handle the load. For a server up to 32 players, the recommended baseline is 4 CPU cores running at 3.0 GHz or better, 16 GB of RAM, a 100 GB NVMe SSD, and 100 Mbps upload bandwidth.
On where to run your server, the choice comes down to two paths. Self-hosting on a home PC is free, but you will deal with a dynamic IP that changes after router reboots, upload limits on most residential connections, and zero uptime guarantee. A VPS or a FiveM-friendly host addresses all three problems, with entry-level plans starting around $9 to $11 per month depending on the provider and resource tier. For a first build, paid hosting is the faster and more stable path. Providers like ZAP-Hosting and Nodecraft are officially approved FiveM hosting partners; using unapproved providers may conflict with FiveM's Terms of Service, so check the official Cfx.re partner documentation for the current list.
Before installing anything, generate your FiveM license key. Visit keymaster.fivem.net, log in with your Cfx.re account, click "New Server," enter your server's public IPv4 address without a port number, and click Generate. Copy the key immediately. Without it, FXServer will refuse to start, and this is the step most beginners overlook until they are already deep into the install.
FXServer installation
FXServer is the server runtime that powers every FiveM server. You download it from the official FiveM artifacts page, linked from fivem.net, and your first decision is which build to grab. The artifacts page lists three channels: Recommended, Optional, and Latest. Always pick Recommended. The Latest build gets updates faster but can introduce instability; the Recommended build is tested and production-ready. Check the artifacts page directly for the current recommended build number, since it updates regularly.
Installation steps
On Windows, create two separate folders before you do anything else: one for the server binary (for example D:\FXServer\server) and one for the server data (D:\FXServer\server-data). Extract the artifact into the binary folder, then clone the cfx-server-data repository from GitHub into the server-data folder. Keeping these two folders separate prevents confusion during updates, where you replace binary files without touching your resources or configuration.
Start command
To run the server, navigate to your server-data folder and execute: D:\FXServer\server\FXServer.exe +exec server.cfg. On Ubuntu, the process follows the same logic with different commands. Download the .tar.xz artifact using wget, extract it into /home/fivem/server, set execute permissions on the FXServer binary with chmod +x, and start the server pointing to your server.cfg. Linux hosting is the standard for production FiveM servers because most VPS providers run Ubuntu and the OS handles long-running game server processes more efficiently.
Linking txAdmin and configuring your server
txAdmin is not a separate tool you install. It comes bundled with FXServer and runs automatically when the server starts. When FXServer first launches, it prints a local URL (typically on port 40120) and a one-time PIN in the console. Open that URL in your browser, enter the PIN, and log in with your Cfx.re account to link and authorize the panel. If you are on a hosted panel, you may need to enable txAdmin in the startup or network settings tab and allocate the txAdmin port manually before it appears.
Once linked, txAdmin walks you through a setup wizard. You will enter your server name, select a deployment recipe, and provide database credentials. The recipe options include CFX Default, ESX Legacy, and QBCore. Do not skip the recipe. It automates framework installation, database import, and basic resource configuration; skipping it means manually handling SQL imports and dependency wiring, which adds significant troubleshooting time for no real benefit, especially if you are new to the process.
After the recipe runs, configure your server.cfg. Five settings matter immediately:
- sv_hostname, the name players see in the server list
- sv_licenseKey, must match the key you generated on Keymaster
- sv_maxclients, controls your player cap
- sv_endpointprivacy true, hides your server IP from the public list
- add_ace commands, defines your admin permissions
Save the file and restart the server after making changes. Most server.cfg settings are not applied live by FiveM and require a full restart to take effect.
ESX or QBCore: picking your framework and installing it
Your framework is the engine that powers your economy, jobs, inventory, and player data. You must choose one before adding any roleplay scripts, because everything else is built on top of it. ESX has been around longer, carries a library of over 2,000 pre-made scripts, and has simpler configuration for beginners. It is the right choice for new server owners who want to launch fast and stay under 64 players. QBCore is more modular, ships with modern systems like a built-in inventory and phone, and handles 128 or more players more efficiently, but it requires more setup time and a working understanding of Lua callbacks. For a full breakdown of the tradeoffs, see our framework fit guide.
For first-time builders, start with ESX Legacy. It has the largest support community, the most script compatibility, and the least configuration overhead. You can find it on the official ESX Framework GitHub organization. Keep in mind that migrating between frameworks later takes one to two weeks of rebuild work, so make the call now and commit to it.
Installing either framework follows the same sequence. Download the files from GitHub, place them in your resources directory, import the SQL file into your MySQL database, update the config file with your database credentials, and add the ensure line to server.cfg. One rule that cannot be broken: never run ESX and QBCore on the same server simultaneously. They conflict at the core level and will crash your server on startup.
Making your server visible: port forwarding and the server list
FiveM uses port 30120 on both TCP and UDP for all game traffic, player connections, resource downloads, and game data. Port 40120 on TCP is only needed if you want to access txAdmin from outside your local network. On Windows, open both ports using the netsh advfirewall command. On Linux, use UFW: ufw allow 30120/tcp and ufw allow 30120/udp, then reload. Skip these firewall rules and players on other machines will not be able to connect, even if the server appears to start correctly.
For home hosting, you also need to configure port forwarding on your router. Log into the router admin panel, find the Port Forwarding or Virtual Servers section, and create a rule forwarding external port 30120 on TCP and UDP to your server machine's local IP address. Before you do this, assign a static local IP or DHCP reservation to your server machine.If the machine's local IP changes after a router reboot, the forwarding rule silently breaks and players lose the ability to connect. After setting everything up, verify your server is public by searching for it in the FiveM server browser or running a port check on 30120.
Scripts, basic troubleshooting, and your next move
Before you open your server to players, you need a working core stack. Every new RP server needs proximity voice chat, an inventory system, an interaction system, a database layer, and an anticheat resource like ZeroTrust for public servers. On top of those, you will want job scripts for police and EMS, a housing resource, and a HUD. Do not install everything at once. Add one resource at a time, restart the server, and check for console errors before adding the next one. Script conflicts crash fresh installs constantly, and adding resources one by one makes the culprit obvious.
When something goes wrong, start with the console. Missing manifest errors almost always mean a typo in the ensure line in server.cfg or a missing fxmanifest.lua inside the resource folder. Connection failures usually point to a firewall rule that did not apply or sv_lan set to 1 in server.cfg. RAM crashes happen when your hosting plan is too small for the resource stack you have loaded. The license key error means the IP registered on Keymaster does not match where the server is actually running. For a deeper diagnostic pass once your server is live, see our guide on troubleshooting FiveM resource conflicts.
Hardware and hosting come first because they define what is possible. The framework comes before scripts because scripts depend on it. Following the sequence is what separates a server that launches from one that sits half-built for weeks.
Build in order, not in circles
Now you know how to make a FiveM server from scratch: hosting decision, FXServer installation, txAdmin setup, framework selection, port configuration, and a starting script stack. If you want to skip the trial-and-error phase and build with a structured roadmap instead, Learn FiveM: how to run and build a server maps out exactly what your server needs and in what order. Take what you have learned here, follow the sequence, and get your server online.
