Why single-core clock speed matters more than core count, what specs you actually need at 32, 64 and 128 players, and the point where a cheap VPS stops being enough.
Most FiveM hosting advice is written by people selling hosting. So before any recommendations, here is the single technical fact that determines everything else.
The FiveM server runs its game logic on one thread. It does not spread across cores. A 32-core server at 2.1GHz will perform worse than a 6-core server at 5.0GHz for the same player count.
Almost every bad hosting decision comes from not knowing that.
Hosting providers advertise core counts because cores are cheap to advertise and easy to compare. For a web server or a database, more cores genuinely means more throughput.
FiveM does not work that way. The main server thread handles the tick — player sync, entity state, script execution. Extra cores help with the operating system, with your database, and with streaming, but they do not make the tick faster.
What makes the tick faster is single-core clock speed and instructions per clock. In practice that means you want a modern high-frequency CPU rather than a many-core datacentre chip.
If a host advertises the core count in large text and the CPU model in small text, read the small text.
The other thing that gets buried: on shared and oversold VPS plans, your allocated vCPU is competing with other tenants for real cycles. Your tick suffers in a way that does not show up in any spec sheet.
This is why two VPS plans with identical listed specs can perform completely differently. It is also why the classic symptom of cheap hosting is not consistently bad performance — it is inconsistent performance. Fine at 3am, stuttering at 9pm when everybody else on the box is also busy.
If you are troubleshooting stutter that comes and goes with no change to your server, suspect your neighbours before you suspect your scripts.
These are working figures with headroom, assuming a reasonably optimised resource set. Add margin if you run heavy scripts or a lot of streamed assets.
Up to 32 players
32 to 64 players
64 to 128 players
Above 128 players
At this point you are into bare metal with a hand-picked CPU, and your bottleneck stops being hardware and becomes your own resource optimisation. No CPU rescues a server running forty unprofiled scripts.
People overbuy RAM because it is the easiest spec to understand. A FiveM server with 60 players and a normal resource load rarely exceeds 8-10GB.
Where RAM does matter is streamed assets. If you run twenty MLOs, several vehicle packs and custom clothing, the server holds more in memory and your clients stream more. That is a real reason to go from 8GB to 16GB. Wanting a bigger number is not.
Game panel hosting — you get a control panel, one-click FXServer install, and no root access. Genuinely good for a first server. You cannot misconfigure the operating system because you cannot touch it. The tradeoff is that you also cannot fix anything the panel does not expose, and per-slot pricing gets expensive as you grow.
Right choice if: this is your first server, or you do not want to administer Linux or Windows.
VPS — you get root, you install everything yourself, you own the consequences. Far more flexible, usually better value per unit of performance, and you can run your database, your Discord bot and your web panel on the same box.
Right choice if: you are comfortable with a terminal, or willing to learn, and you want control.
Dedicated / bare metal — the whole machine. No noisy neighbours, no vCPU contention, and you can pick the exact CPU. More expensive and more responsibility.
Right choice if: you are past 64 concurrent players, or you have been fighting inconsistent performance on a VPS and ruled out your own scripts.
Windows builds are easier to troubleshoot when something goes wrong, and the error output is friendlier. For a first server, that matters more than efficiency.
Linux uses fewer resources and is what most large servers run, but you will be reading logs in a terminal. If you already know your way around one, go Linux. If you do not, do not make learning Linux part of launching your first server — do one hard thing at a time.
Put the server near the majority of your players, not near yourself. This sounds obvious and gets ignored constantly by owners who host next to their own house.
Beyond that, raw distance is less important than route quality. A well-peered datacentre 2,000km away frequently beats a badly-peered one 500km away. If a host offers a test IP, ping it from a few of your actual players' connections before committing rather than trusting a map on their website.
Not optional. FiveM servers get attacked, especially once you have a competitor or a banned player with a grudge.
What matters is not the advertised capacity in Gbps — everybody claims a large number. What matters is whether the filtering understands game traffic. Generic web-focused mitigation will happily drop legitimate UDP game packets and your players get kicked, which achieves the attacker's goal for them.
Ask specifically whether they filter game protocols, and whether mitigation is always-on or triggered. Triggered mitigation means the first minute of every attack lands.
This is the part hosting comparisons leave out, because it does not sell servers.
If your server stutters, upgrading hardware is often the more expensive way to avoid a free fix. A single script with a badly written loop can eat more tick time than the difference between a mid-range and a top-end CPU.
Before you upgrade, check your actual numbers. Open the server console, run `resmon 1`, and watch it with players online rather than on an empty server — idle figures hide the loops that cost you frames.
Our free resmon calculator helps you work out what your resource budget should be for a given player count, and the server.cfg optimizer catches the configuration mistakes that cost performance for no reason. Both are free and neither needs an account.
If a resource is over budget, fix or replace it before you pay for more hardware. It is nearly always cheaper.
Then spend the money you saved on not overbuying on optimising what you run.
Single-core clock speed, dedicated rather than shared cores, NVMe storage, game-aware DDoS filtering, and a location chosen for your players. Everything else is detail.
And profile your resources before you upgrade anything. Most "I need better hosting" problems are one bad script.
If you are still building the server itself, the complete setup walkthrough covers getting FXServer running, and the performance optimisation guide covers the resource side in more depth.
Written by
xFiveM Shop Editorial TeamResearch-led FiveM guides with disclosed review and update standards
