FiveM Server Requirements Calculator

What a slot count really requires, what hosting companies publish for it, and how to measure your own server. Cfx.re publishes no RAM or CPU figures, so every number here is quoted from a named source or is your own input.

The peak number of players online at once. FiveM accepts 1 to 2048[2].

The slider stops at 256; type a number for larger servers.

What hosts publish for 48 slots

Vendor guidance, not measurements. Each row is the smallest tier that host publishes covering your slot count. Nothing is interpolated.

HostTier usedRAMCPU and notes, as published
Space-Node[14]64 players6 to 8 GB4 cores at 3.5 GHz+; "standard RP server"
Flux[15]48 slots plan8 GB5.5 vCores, plus 2 GB for MySQL
Supercraft[16]64 players32 GB6 cores at 3.5 GHz
SSD Nodes[17]up to 64 slots4 to 8 GB"4 GB is a sensible floor, and 8 GB is comfortable at 32 to 64 slots"; no core count, single-core speed first

The hosts disagree by a wide margin because they assume different servers. Flux states the reason itself: memory follows the resource list and not the slot count[15]. No source gives a figure per script or per resource, so this page has no input for it.

For 48 slots

Required by FiveM[2][1]

sv_maxclients 48

onesync on or legacy is required (from 32 slots)

No subscription needed (up to 48 slots)

RAM, range across hosts

4 to 32 GB

Lowest and highest figure from 4 of 4 hosts.

CPU cores, range across hosts

4 to 6 cores

The server itself runs 3 timed threads[5]. Per-core speed comes first.

An estimate built from vendor guidance. Use it to pick a first plan, then measure your own server.

Formula

For each host, take the smallest published tier that covers your slots. RAM and cores shown are the lowest and the highest of those figures. Slot rules come from the Cfx.re docs.

What Cfx.re says about server hardware

One sentence, on the server hosting page: "We recommend a x86-64 system running Linux or Windows (7/2008 R2+), decent upstream connectivity and preferably a multi-core processor."[1] There is no official RAM figure, no core count and no bandwidth figure, which is why this page gives no bandwidth number.

The server source shows why per-core speed matters. FXServer schedules three loops, each on its own thread[5]:

  • svMain: every 1000/20 ms, resource scripts and events. Hitch warning above 150 ms.
  • svNetwork: every 1000/100 ms, network packets. Hitch warning above 150 ms.
  • svSync: every 1000/120 ms, OneSync entity state. Hitch warning above 100 ms.

A community contributor on the Cfx.re forum puts it this way: FXServer uses three cores, so a CPU that is fast on a few cores matters more than a very high core count[13]. The hosts listed above say the same about single-core speed[17][15]. Cores beyond those three serve what runs next to the server, such as a database and txAdmin.

With onesync off the server only relays traffic between clients; with it on, the server tracks entity state itself[2]. From 32 slots OneSync is required, so larger servers always carry that work.

Custom vehicles: a cost on each player's PC

Streamed models and textures are downloaded by every client and loaded into that client's memory. The server stores the files, serves them and reads each asset's header when the resource starts[6]. So car count is not an input to the server estimate above. There is also no honest average size per car: measure your own files with the Resource Inspector and enter the results here.

First-join download

Fastest possible download

Enter both values

Size x 8 / speed. A lower bound: your server's upload speed and other players joining at the same time can only make it slower. The client keeps a cache[10], so this is the first join.

Largest single asset

FiveM's console warning[6]

Enter a value

Tiers at 16, 32, 48 and 64 MiB, checked per asset against the memory figure in the file header, not the size on disk. It is a warning. FiveM does not block the asset.

Shrink an oversized texture dictionary with the Texture Optimizer.

Cfx.re lists 8 GB of RAM as the minimum and 16 GB as recommended for a player's PC[10]. How much of that your cars use depends on which models are near the player, so it can only be measured in game. Background: streaming budget, server resource limits explained and reducing server file size.

Measure your own server

  • txAdmin dashboard. The thread performance chart shows tick durations for svMain, svNetwork and svSync[11], and the stats card shows FXServer memory in MB[12]. Read both at peak player count. That memory figure is what your RAM plan has to cover, next to the database and the operating system.
  • Hitch warnings in the server console. They mean a resource is not performing as it should; the profiler, which runs on server and client, shows which one[9].
  • resmon in the client console (F8). Lists CPU msec, memory and streaming memory per resource on that player's game[7]. It is a developer command and can answer "Access denied" on a production client[8]. It measures the client, not the server.
  • svgui on the server. Opens the server debug GUI[2].

Check a tick time

Against the server's own constants[5]

Enter a value

Measured ms / 50 ms. svMain is scheduled every 50 ms and warns above 150 ms.

Setting up: installing cars with txAdmin, the server.cfg reference, and the Car Pack Builder for merging single-car resources.

Sources and method

Checked on 10 October 2026. Slot rules, thread timings and warning thresholds are taken from Cfx.re's site, docs and source code. RAM and core figures are hosting companies' own published sizing, shown per host and as the range they span; they are sales guidance and were not verified by us. The download time and tick percentage are unit conversions of numbers you enter. Nothing on this page is a benchmark.

Primary sources (Cfx.re site, docs and source code, txAdmin source)

Community statement (not staff)

Vendor guidance (hosting companies describing their own sizing; not measurements)

Not sourced, and therefore not on this page: server RAM per script or per resource, server RAM per custom vehicle, a bandwidth figure per player, and an average size for a modded car.

What the calculator tells you, and what it will not guess

Cfx.re publishes one sentence about FiveM server requirements: an x86-64 system running Linux or Windows, decent upstream connectivity and preferably a multi-core processor. It gives no RAM figure, no core count and no bandwidth figure. So this calculator does not produce one from a formula of its own. For the slot count you enter it shows two things: what FiveM itself requires at that size (the sv_maxclients line, the OneSync mode and the Element Club tier), and what four hosting companies publish as their sizing for it, per host and as the range they span.

Custom vehicles are handled in a separate section, because streamed models and textures are downloaded and held in memory by each player's game and not by the server process. There you enter figures you measured with the Resource Inspector: the streamed size of your resources, to get the first-join download time, and the memory of your largest asset, to see which of FiveM's oversized-asset warnings it triggers. A third section lists the tools that measure a running server and checks a tick time against the 50 ms interval in the server source. Every figure on the page is linked to its source in the list at the bottom.

How to use it, step by step

  1. 1Set the player slots to the peak number of players you expect online at once, not the number you would like to advertise.
  2. 2Read the three results: what FiveM requires at that slot count, the RAM range and the CPU range across hosts. The table shows which host published which figure.
  3. 3For your cars, run the resources through the Resource Inspector and enter the streamed size and the largest asset's memory in the vehicle section.
  4. 4Once the server runs, open the txAdmin dashboard at peak time and enter the svMain tick duration to compare it with the 50 ms interval.

Reading the results

The slot rules are the firm part. The Cfx.re docs state that sv_maxclients accepts 1 to 2048, that values from 32 need OneSync on or legacy, and that values above 64 need OneSync on. The default limit is 48 players; Element Club Argentum raises it to 64, Aurum to 128 and Platinum to 2048, the last two with OneSync Infinity. Enter the result in your server.cfg or build the file with the Server.cfg Generator.

The RAM and CPU ranges are vendor guidance and they are wide. For 32 slots the four hosts publish between 4 GB and 16 GB; for 64 slots, between 4 GB and 32 GB. They disagree because each assumes a different server: one of them, Flux, says outright that memory follows the resource list and not the slot count. Treat the low end as a starting plan for a light server, the high end as what a host sells for a large roleplay city, and then measure.

On CPU, the FiveM server source schedules three loops on separate threads: svMain every 50 ms for scripts, svNetwork and svSync for networking and entity state. That is why the hosts and a community contributor on the Cfx.re forum all say per-core speed matters more than core count. Extra cores serve what runs next to the server, such as the database and txAdmin.

The vehicle section is arithmetic on your own numbers. Download time is size times 8 divided by line speed, a best case. The asset check uses FiveM's thresholds of 16, 32, 48 and 64 MiB per asset, which are console warnings and not a block. To bring either number down, shrink texture dictionaries with the Texture Optimizer and merge single-car resources with the Car Pack Builder. The background is under streaming budget and in the server resource limit guide.

Common mistakes

  • Budgeting server RAM per custom car. Streamed assets are loaded by each player's game; on the server they cost disk space and upload.
  • Sizing for the advertised slot count when a fraction of it is ever online.
  • Counting cores without looking at per-core speed. The server's work runs on three threads.
  • Reading a host's sizing table as a measurement. It describes the plans that host sells.
  • Setting more than 48 slots without the Element Club tier that allows it.

Frequently asked questions

What are the official FiveM server requirements?

Cfx.re's server hosting page says: "We recommend a x86-64 system running Linux or Windows (7/2008 R2+), decent upstream connectivity and preferably a multi-core processor." That is the whole official statement. There is no official RAM, core count or bandwidth figure.

How much RAM does a 32-slot FiveM server need?

There is no official figure. The four hosts quoted on this page publish 4 GB (Space-Node), 6 GB plus 1 GB for MySQL (Flux), 4 to 8 GB (SSD Nodes) and 16 GB (Supercraft) for 32 slots. The spread comes from the scripts and framework each assumes, so start low, read the FXServer memory figure on the txAdmin dashboard at peak time and adjust.

Do custom cars increase the server's RAM requirement?

Not in the way old calculators claimed. Streamed models and textures are downloaded by each client and loaded into that client's memory. The server stores and serves the files and checks each asset's header when the resource starts, printing a warning above 16 MiB. What a heavy car list costs is download time on first join and memory on players' PCs.

Do more cores make a FiveM server faster?

Only up to a point. The server source runs three timed loops on their own threads: svMain, svNetwork and svSync. A CPU that is fast on a few cores serves those better than many slow cores. Additional cores help the database, txAdmin and the operating system.

How many players can a FiveM server have?

sv_maxclients accepts 1 to 2048. A server supports up to 48 players by default; according to fivem.net, Element Club Argentum allows 64, Aurum 128 and Platinum 2048, the last two with OneSync Infinity. The docs add that 32 slots or more require OneSync on or legacy, and more than 64 require OneSync on.

How do I measure what my server really uses?

The txAdmin dashboard charts tick durations for the svMain, svNetwork and svSync threads and shows FXServer memory in MB. The server console prints hitch warnings when a loop runs late, and the built-in profiler shows which resource is responsible. On a player's game, the resmon command lists CPU time, memory and streaming memory per resource; it is a developer command, so a production client can refuse it.

Why is there no bandwidth result?

No primary source gives one. Cfx.re only asks for "decent upstream connectivity". The page shows how long a first join takes for a streamed size and line speed you enter, which is the part that can be calculated.

More answers about conversions, limits and plans are in the general FAQ.

Have a gta5-mods.com link ready?

Paste it into the converter and download a FiveM resource with the stream folder, meta files and fxmanifest.lua in place.

  • 3 conversions free, no account needed
  • 2 more free if you leave an email
  • After that: $15 once for unlimited conversions and the Pro tools. No subscription, 14-day refund policy