# FiveM server hardware requirements

> What hardware a FiveM server needs by size: CPU single-thread speed, RAM for server and database, NVMe storage, bandwidth per player and OneSync overhead.

Source: https://fam-tools.com/guides/fivem-server-requirements-hardware · FAM Tools · published 2026-09-11 · updated 2026-09-11 · about 9 min

**Short answer.** Prioritise a CPU with high single-thread performance, then enough RAM for the server, the database and caches, then fast NVMe storage and a good network. As a rough guide, small servers run well on a modern 4-core CPU with 8–16 GB RAM; busy roleplay servers with 100+ players want the fastest cores available and 32 GB or more, often with the database tuned or separated.

## Key points

- Order of importance: **single-thread CPU → RAM → NVMe → network**.
- The database needs its own share of RAM and CPU.
- Scripts and streamed assets drive load more than player count alone.
- Measure with txAdmin and the profiler before buying bigger hardware.

There is no single official spec for a FiveM server because the load depends almost entirely on what you run: a vanilla vMenu server with 32 players and a heavy roleplay server with 200 scripts and 128 players are different machines. What does hold everywhere is which components matter, in what order.

## A rough sizing guide

*Rules of thumb. Your resources and streamed assets change the picture.*

| Server | CPU | RAM | Storage |
| --- | --- | --- | --- |
| Development / friends (≤ 10) | Any modern 4-core | 8 GB | SSD |
| Small public (≤ 48) | Modern 4–6 core, high clock | 16 GB | NVMe |
| Medium RP (48–128) | Fast 6–8 core, top single-thread | 32 GB | NVMe |
| Large RP (128+) | The fastest single-thread CPU available | 64 GB+ | NVMe, database tuned or separate |

## CPU: single-thread speed first

The FiveM server’s main game thread runs scripts and synchronisation. When one tick takes too long the console prints a “server thread hitch warning”, and players feel it as rubber-banding. Extra cores help the database and other processes; a faster core helps the server itself.

## RAM

The server process, MariaDB (with its buffer pool), txAdmin and caches all need memory. Running out causes swapping and stalls that look like script lag. Give the database a sensible buffer pool rather than letting it fight the server for memory.

## Network and bandwidth

Game sync traffic is modest per player, but resource downloads are not: every new player downloads every streamed asset. A server with gigabytes of cars and MLOs needs good upload bandwidth, or new players wait a long time on the loading screen. Keeping assets lean helps as much as a bigger pipe — see [texture optimisation](https://fam-tools.com/guides/fivem-texture-optimization).

## Signs you have outgrown your hardware

- Hitch warnings appear only at peak player counts.
- The database is slow even with indexes.
- RAM is full and the machine swaps.
- The profiler shows no single bad resource — just too much total work.

Before upgrading, profile: one bad script can make any hardware look too small — see [server performance](https://fam-tools.com/guides/fivem-server-performance).

## Questions

### How much RAM does a FiveM server need?

Around 8–16 GB for small servers and 32 GB or more for busy roleplay servers, including the database.

### What CPU is best for FiveM?

One with high single-thread performance. The main server thread benefits from fast cores more than many cores.

### Does a FiveM server need an SSD?

Yes — NVMe storage keeps the database and resource loading fast.

### Why do new players take long to download my server?

Every streamed asset is downloaded on first join. Large asset packs need good upload bandwidth, or leaner assets.

## Related

- https://fam-tools.com/guides/fivem-server-hosting-options
- https://fam-tools.com/guides/fivem-server-thread-hitch-warning
- https://fam-tools.com/guides/fivem-server-performance
- https://fam-tools.com/guides/fivem-max-players-slots