FiveM Server Requirements
There is no single hardware specification that guarantees a particular player count. Resource quality, scripts, game mode, OneSync configuration and workload matter more than a generic “64-slot CPU” promise.
Supported operating systems
| System | FiveM server guidance |
|---|---|
| Windows (64-bit) | Supported FXServer platform. Download the matching recommended artifact. |
| Linux (x86-64) | Supported FXServer platform. Use a supported, maintained distribution and the correct Linux artifact. |
| macOS | No native supported FXServer artifact. Develop from macOS using a remote Windows/Linux host or a supported Linux VM/container environment; see Docker. |
The FiveM client and the FXServer server have separate requirements. The normal FiveM client runs on Windows, not as a supported native macOS/Linux client. See the official platform support FAQ .
Practical sizing estimates
These are planning starting points, not official requirements or guaranteed player capacities:
| Workload | Initial test allocation | Notes |
|---|---|---|
| Empty or minimal test server | ~2 vCPU, 4 GB RAM, 20 GB free disk | Validate with real resources and players. |
| Small roleplay server | ~4 fast vCPU, 8 GB RAM, SSD | Database, voice and framework scripts add load. |
| Heavier production server | 8+ modern CPU threads, 16+ GB RAM, NVMe | Load-test actual concurrent players and resource timings. |
Prefer strong CPU single-thread performance, enough memory headroom and storage that accommodates logs, artifacts, resources and off-server backups. Use profiling and monitoring to size your server rather than promising fixed “players per core.”
Network ports
| Port | Protocol | Purpose | Exposure |
|---|---|---|---|
30120 | TCP and UDP | Default FiveM game endpoint | Open to players |
40120 | TCP | Default txAdmin web interface | Keep private |
Open player ports in both the operating-system firewall and the hosting-provider firewall. On a home connection, forward game traffic to the server’s private IP. Restrict txAdmin to a VPN, SSH tunnel or trusted administration network; a public rule for 40120 is not a requirement to let players join.
If another game port or txAdmin port was configured, use the actual configured value. See Networking and txAdmin Security.
Software and account prerequisites
- Current recommended Cfx.re server artifact for the selected platform (Legacy vs Enhanced is a separate choice).
- A Cfx.re Portal registration key .
- On Linux: tools to download/extract the selected archive, plus Git if following the manual vanilla resource setup.
- On Windows: a compatible archive extractor such as 7-Zip for
server.7z. - On Windows for an Enhanced server: the Microsoft Visual C++ 2017 Redistributable (x64) , installed before the first start.
- Database: not required for a vanilla/basic CFX recipe. MariaDB/MySQL is normally needed for persistent roleplay frameworks such as QBCore and ESX ; follow the chosen recipe’s supported versions and credentials.
- A Windows PC with FiveM for the client join-and-spawn acceptance test.
Enhanced: Check the official Enhanced onboarding requirements before using a different artifact or runtime.