FiveM Server Requirements: RAM, CPU and Player Slots Explained

Practical starting points for RAM, CPU and storage

There is no official FiveM RAM number from Cfx.re. That is why plan shopping is confusing: one provider sells by slots, another by RAM, another by vague labels such as “premium”. The sensible approach is to start with the kind of server you are building, then check whether the plan gives enough memory for the resources you want loaded and enough single-thread CPU speed for the scripts you want running.

The table below is best read as practical allowance, not as an official minimum. It combines the usual host guidance with what each server style keeps loaded, from a bare freeroam or racing server to a framework-based roleplay stack. If you want the broader context behind CPU, RAM, storage and network bottlenecks, our game server hardware guide breaks down what each limit looks like in real server use.

Use this as the quick sizing view before you compare plans.

The main point is simple: a bare freeroam box and a loaded roleplay box are not interchangeable just because both say 48 slots.

FiveM slots explained: what the cap really means

FiveM slot numbers are mostly a licensing and configuration question, not a memory reservation. The server variable sv_maxclients accepts values from 1 to 2048. Free servers support up to 48 players with OneSync; above 48 you need a FiveM Element Club subscription bought through the Cfx Portal, starting from the Argentum tier.

There is one extra rule around OneSync. Values from 32 upwards require OneSync on, or onesync legacy; above 64, OneSync on is required. The important buying point is that a higher slot cap does not magically set aside RAM for those extra players. You still size the machine for your real peak concurrency and the weight of the resources running at that peak.

This ladder is the part to check before assuming a host’s “slot upgrade” solves a performance problem.

That is why a 64-slot plan can still be wrong for a busy RP community if the CPU is weak, and why a 32-slot freeroam server can be perfectly happy on modest RAM if it stays close to vanilla.

Why RAM follows the resource stack more than the slot count

FiveM memory use is driven by what stays started. Each resource you launch remains in memory with its code, state and supporting data, and frameworks add more of that than bare freeroam does. On a roleplay server, the usual RAM consumers are the framework itself, inventory systems, phones, housing, garages, jobs, police and EMS scripts, dispatch, custom UI, map packs, MLOs, vehicle packs and clothing packs. If you add a database on the same machine, that database is a separate process and needs its own memory as well. txAdmin also takes some memory because it is bundled with the server.

This is why two servers both set to 48 slots can need very different plans. A small freeroam server with little more than base scripts and a few lightweight extras can fit around 4 GB. A full RP stack with ESX or QBCore, lots of interiors, streamed cars, clothing and a local MySQL or MariaDB process can make far more sense around 16 GB.

• Frameworks and script stacks: cost heap memory and main-thread CPU. More systems usually mean more background state to keep live.
• MLOs, maps and streamed assets: increase memory, storage and join-time bandwidth. Players pay with longer downloads; the server pays with more files to host and track.
• Add-on vehicles and clothing: also add streamed content and supporting resource data. A huge pack is often felt first in joins and RAM, not in slot count.
• Database on the same machine: consumes its own RAM and CPU time. Some txAdmin recipes need it; the CFX Default recipe does not.

The practical rule is to ask “what resources stay loaded all day?” rather than “how many slots do I want on the advert?” That question gets you much closer to the right plan.

CPU: why single-thread speed matters so much on FiveM

FiveM exposes three server threads in performance metrics: svMain, svNetwork and svSync. They do different jobs, so the thread under pressure tells you what to fix. Most script logic runs on svMain, packet send and receive work sits on svNetwork, and entity synchronisation sits on svSync.

That is why clock speed and per-core performance beat raw core count for most communities. If a script has a bad loop every frame, waits on a synchronous database action or just does too much on every tick, it blocks svMain. The classic symptom is a console message saying server thread hitch warning. Buying more total cores does not necessarily cure that, because the slow work is still happening on the main script thread.

Use this thread view to separate script problems from network or sync pressure.

• svMain: heavy Lua or framework logic, event handlers and bad polling loops. Costs main-thread CPU time.
• svNetwork: packet processing and send volume. Costs CPU and bandwidth, especially when many clients join or updates are very frequent.
• svSync: entity creation, state and culling. Costs CPU hardest in crowded scenes with lots of nearby players and entities.

OneSync Infinity is on by default, and its culling helps because entities are only created for clients inside a focus zone of 424 units around a player. On Legacy, that culling work ran on the sync thread and processed around 16 players per tick. On the newer Cfx Server for GTAV Enhanced, culling can spread across multiple cores, so crowded scenes can scale better.

Tick rate is another trade-off. Legacy sync runs at 30 updates per second, or 40 with sv_useAccurateSends. Enhanced can be configured up to 120. Higher update rates can make movement and state feel smoother, but they cost more CPU on svNetwork and svSync, and more upstream bandwidth. Raise it only when you know why you need it.

Before upgrading CPU, profile the server. Run profiler record <duration>, then save and view the result to find the resource actually costing time. That gives you a fixable target; a bigger plan does not.

Storage and bandwidth: the quiet limits people miss

FiveM wants SSD or NVMe storage. Fast storage does not replace CPU, but it does help with resource loading, database activity, logs, backups and restart times. The practical storage ranges are straightforward: a basic server often fits in 10-15 GB, a medium RP setup in 20-40 GB, and a heavy modded stack in 50-100 GB+ once you include the database, logs and backups.

Bandwidth matters most on joins. Players download your streamed resources from the server, and their client caches those files. In Legacy, that cache stayed on disk forever; Enhanced cleans up files the server no longer serves. The important server-side effect is that upload bandwidth spikes when many players join after a restart or when you have just added a large car, clothing or map pack.

You can usually tell a bandwidth or asset-size problem from a CPU problem by when it appears. If joins suddenly become slow after adding content, but play is fine once everyone is in, you are looking at download volume or upstream limitations more than script execution. If the server hitches during normal play with RAM to spare, that points back toward the main thread and resource quality.

Legacy FXServer vs Enhanced Cfx Server: what changes when you buy a plan

FiveM for GTAV Enhanced entered early access on 21 July 2026 and ships with a new server called Cfx Server as a separate download, with txAdmin still embedded. Cfx.re says it optimises memory allocation per player and per entity, reducing RAM usage by up to 50%, and lowers CPU use in certain scenarios. That changes planning, but only if your host is actually offering the newer server rather than Legacy FXServer.

If the control panel, docs or support replies still talk about FXServer or Legacy, use Legacy figures when choosing RAM and CPU. Treat any future move to Enhanced as a bonus, not as a promise.

Settings that can change the load

Most performance settings move load from one place to another. A “faster” option usually means more work for CPU, more bandwidth, more RAM, or a player-facing compromise such as fewer NPCs or more aggressive vehicle culling. Change one thing at a time and watch the relevant thread or symptom afterwards.

A clean starting server.cfg only needs a few core lines:

endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"
set onesync on
sv_maxclients 48
sv_licenseKey changeme

Self-hosting: where the real bottlenecks show up fastest

Self-hosting works, but it exposes every weak point at once. Officially, FiveM supports Windows and Linux on x86-64, yet Linux FXServer is only provided as a courtesy port, so Windows is still the safer choice if you want the platform where issues are more likely to be fixed first. If you are learning the basics, our guide to self-hosting a game server covers the practical setup steps beyond the FiveM-specific bits.

• Ports: FiveM uses port 30120 on both TCP and UDP by default. txAdmin uses 40120. Do not expose txAdmin publicly any more than you need to; keep it behind a firewall, VPN or another access control layer where possible.
• Licence key: you need a free Cfx licence key and the sv_licenseKey line in the config.
• Upload speed: matters more than many people expect because clients pull streamed assets from you. Restarts and new content create the biggest spikes.
• Same PC as GTA V: if the machine is also running the game, the server and client fight over RAM, CPU time and disk access. That is a poor fit for busy communities.
• VPS limits: if you are thinking about running a game server on a VPS, watch for shared CPU behaviour and noisy-neighbour effects before putting an RP framework stack on it.

For self-hosting, the plan question becomes a machine question: enough RAM for the server and database, fast enough single-thread CPU for svMain, and enough upstream to feed asset downloads without choking normal play.

Reading the signs before you throw money at the plan

Most FiveM problems tell you what resource is short if you read the symptom properly. Upgrade when RAM sits close to its cap for long periods, when the main thread is regularly the limiting factor even after resource cleanup, or when your peak players keep pressing against the slot limit you actually want to offer. Until then, tune the bottleneck you can identify.

This flow helps separate RAM problems from script, bandwidth and licence limits.

What it costs, and when to tune first instead of buying bigger

In our FiveM server hosting comparison, entry plans come in both slot-billed and RAM-billed forms, which is why headline price alone is misleading. A cheap slot cap can still be weak for roleplay, while a higher-RAM plan may be the sensible choice if you are starting with ESX or QBCore and a database. For RP, the practical starting point is usually 8 GB or more, not the smallest plan on the page.

The price graphic is useful for seeing the entry spread, but compare what is being sold, not just the pound figure.

Conversion used: £1 = $1.33

FiveM server FAQ

How much RAM does a FiveM server need?

There is no official RAM figure from Cfx.re. In practice, about 2 GB suits testing, about 4 GB suits a small vanilla or freeroam server, and most framework-based communities start making sense from 8 GB upward. The real driver is your resource stack, not the slot cap on the package.

How many players can a FiveM server have for free?

Free servers support up to 48 players with OneSync. Above 48, you need a FiveM Element Club subscription, and sv_maxclients can be set up to 2048. That slot number is a licence and config limit, not a promise that the hardware can handle the load.

Does FiveM need a fast CPU or more cores?

For most servers, fast single-thread performance matters more because most script work runs on svMain. Extra cores still help network, sync and background tasks, and they matter more on Enhanced because some culling work can spread out, but bad scripts still need fixing first.

How much RAM does an ESX or QBCore server need?

8 GB is a typical starting point for an ESX or QBCore server with a lean-to-moderate stack and roughly 10-40 players. Standard RP commonly sits in the 8-16 GB range, and a full stack with many MLOs, add-on vehicles, clothing and jobs can push you toward about 16 GB or more.

Does FiveM Enhanced need less RAM?

It can. Cfx.re says the newer Cfx Server for GTAV Enhanced reduces RAM usage by up to 50% in some cases by optimising memory allocation per player and per entity, and it can also lower CPU use in certain scenarios. That only matters if your host is actually running Enhanced; a Legacy FXServer plan should still be sized with Legacy expectations.

More FiveM server guides

Compare FiveM hosts for your community, or read up on server hardware.