A small FiveM server for testing and up to 32 players gets by with 4 to 6 GB RAM and 2 fast vCores. A roleplay server with 64 to 128 slots, ESX or QBCore, its own database and many vehicles needs more like 8 to 16 GB RAM and 4 to 6 vCores. Per-core performance matters more than the core count, because FXServer processes scripts and sync largely in a few threads.
The calculator's figures are guidelines. Poorly optimised scripts, endless loops or very many streaming assets can load a server more than the player count alone. Measure with the txAdmin profiler after launch and scale specifically.
Per-core performance counts
Many FiveM scripts run on the main thread. A high clock speed – such as the AMD Ryzen 9 9950X with up to 5.7 GHz – keeps server ticks short. More cores mainly help when the database, txAdmin and other services run on the same server.
Plan for the database
ESX and QBCore store players, inventories and vehicles in MariaDB or MySQL. If the database runs on the same server, plan 1 to 2 GB of extra RAM. Our MariaDB guide shows how to secure it.
Streaming assets
Custom vehicles, clothing and MLOs are loaded at startup and streamed to players. Many assets need more storage and RAM – and a good uplink so joining stays fast.
OneSync above 32 slots
For more than 32 players, OneSync must be enabled. Also check which slot count your Cfx.re licence allows – you need the licence key in any case.
Linux or Windows
FXServer and txAdmin run on Linux and Windows. Linux saves resources, Windows is more familiar for some tools. On our Ryzen root servers you can choose.
See Windows VPSStep-by-step setup
From FXServer to txAdmin and the database: our FiveM guide walks you through the complete setup.