FiveM Server Hosting: What You Actually Need in 2026

The one number that decides everything

FXServer does not spread your server work evenly across a CPU. The process runs a small set of named threads, and the one that executes every server-side resource tick is called svMain, which is why the error message server owners see in their console when something stalls is a warning that the thread svMain hung. txAdmin exposes exactly this in its dashboard, describing its performance chart as an insight into your server performance on all three threads. Everything your community experiences as rubber banding, delayed events and a frozen inventory is that one thread taking too long to finish a tick.

The practical consequence is uncomfortable for anyone shopping on core count. If a single resource loop takes 8 ms to run, buying a second CPU socket does not make it take 4. It takes 8 on a faster core and 12 on a slower one. That is the whole hardware decision in one sentence, and it is why a modern four-core machine with a high sustained clock will hold a 48-player roleplay server that a sixteen-core enterprise CPU from 2016 struggles with. It also means that after a point, no hardware fixes a badly written script, which is the territory the server optimization guide covers with resmon and the profiler.

CPU: clock speed over core count

Read the CPU model, not the core count. Shared game hosts run your instance on large multi-tenant boxes, and the honest ones tell you which. ZAP-Hosting states on its FiveM page that its infrastructure uses Intel E5-2650v4 processors on 328 GB DDR4 host systems. That is a twelve-core Broadwell server part designed for density and virtualisation, not for one thread finishing a Lua tick as fast as possible. Compare it with what a game-specific dedicated range advertises: the OVHcloud GAME-1 2026 lists an AMD Ryzen 7 9800X3D at 8 cores and 16 threads with a 4.7 GHz base and 5.2 GHz boost, water cooled and explicitly sold as a high-frequency processor for online gaming.

Neither is wrong, they are different products at very different prices. The point is that the number on the plan card, four cores or eight cores, tells you almost nothing until you know what generation and what clock those cores run at. When a host does not publish the CPU model at all, that is information too. Ask before you pay, and if the answer is vague, assume the oldest plausible part.

The second thing to establish is whether your vCPUs are shared or dedicated. On a shared plan you get a slice of a physical core that other tenants also use, which is fine at 3 am and unpredictable at 9 pm on a Saturday. Dedicated vCPU plans cost more per core and are the correct purchase for a game server, because the failure mode of oversubscription is exactly the intermittent tick spike that is impossible to debug from inside your own server.

RAM: sized by what you stream, not by slots

Cfx.re does not publish a RAM requirement for FXServer. The Linux and Windows setup guides list prerequisites like git and an extraction tool and say nothing about memory, so any per-slot RAM table you find online, including the reasoning below, is a planning heuristic rather than a specification. What is verifiable is where the memory goes. The FXServer process is the smallest part. Your database engine, the assets your resources hold, and txAdmin running on Node are the three consumers that scale.

That reframes the question usefully. A 64-slot server running a lean ESX build with a handful of scripts uses far less memory than a 32-slot server carrying six custom MLOs, four hundred add-on vehicles and a clothing pack. RAM tracks your content library and your database size, and only loosely tracks player count. In vendor terms, the 8 GB tier that Contabo sells as Cloud VPS 4 at 5.50 EUR per month with 4 vCPU, or that OVHcloud sells as VPS-2 2027 at 8.50 USD per month with 4 vCores and 75 GB of NVMe, is a realistic home for a normal community server. The step up, the 24 GB OVHcloud VPS-4 at 23.37 USD per month, is where a heavy roleplay build with a large database belongs.

One caveat that catches people who buy on the RAM number alone: Contabo lists 12 vCPU and 48 GB for 25.00 EUR per month, far more memory per euro than the game-oriented offers. That is a legitimate deal for a database or a build server. It is not automatically a better FiveM box than a smaller machine with faster cores, because you have bought the resource FiveM cares about least.

Bandwidth, and the asset download nobody budgets for

There are two completely different kinds of traffic on a FiveM server and only one of them is small. Ongoing state synchronisation while people play is modest. The expensive one is the initial resource download: every player who joins for the first time, or after you push an update, pulls your streamed assets over HTTP from your server. That is pure outbound bandwidth, and it is why one server owner in the Cfx.re cookbook thread on caching proxies describes pushing 100 GB per day depending on resources.

Run the arithmetic before you pick a plan. A 4 GB asset pack is about 32,768 megabits. On a 200 Mbit/s port, the slowest tier Contabo lists, that is roughly 164 seconds of transfer for one player who saturates the link on their own. Ten first-time joins at once and the queue is measured in double-digit minutes. On the 1 Gbps port that OVHcloud gives its VPS-2, the same pack moves in about 33 seconds of link time. Port speed, not the monthly traffic allowance, is what your new players actually feel, and the allowance itself is usually generous: Contabo and OVHcloud both advertise unlimited traffic on the plans above, and Hetzner states traffic on its AX line is unlimited and free of charge.

Two levers reduce the pain. The first is offloading downloads entirely, which FXServer supports through fileserver entries pointing at a caching proxy or CDN, configured with a line like fileserver_add ".*" "http://10.0.0.1/files" where the URL must not end in a slash. The second is having less to download in the first place: compressed textures, no duplicate props across three MLO packs, and a critical eye on add-on vehicle folders, which is the part the guide on adding cars goes into. Whatever is left, your players stare at a loading screen while it transfers, so it may as well be one that tells them what is happening.

Location beats hardware, permanently

Latency has a floor you cannot buy your way past. Light moves through fibre at roughly 200,000 km per second, so a London to New York round trip, about 5,600 km each way, costs around 56 milliseconds of pure propagation before a single router touches the packet. No CPU upgrade, no NVMe drive and no optimisation pass gives that back. If your community is French and your server is in Dallas, every player pays that tax on every interaction, all the time.

So decide the region before the specs. Look at where your Discord members actually live, not where you live, and check that the host serves it. ZAP-Hosting lists Dallas, Frankfurt, Montreal, Singapore, Sydney, London, Los Angeles and Ashburn on its FiveM page. GPORTAL, on the plans visible in August 2026, was quoting FiveM slots out of Dallas. OVHcloud and Contabo both operate multiple continents. A cheap host with one datacenter on the wrong side of an ocean is not cheap, it is a permanent handicap on the one metric players complain about first. If you are split across two regions with no majority, that is an argument for the region with the better peering, not for the middle of the Atlantic.

VPS, dedicated, or a managed FiveM host

Cfx.re calls using one of its authorised hosting partners the fastest and easiest way to set up a FiveM server, and lists GPORTAL, Shockbyte, Nitrado, Nodecraft, xREALM and ZAP-Hosting on its hosting page. That recommendation is worth taking seriously and it is worth being honest about why. A managed FiveM host beats a raw VPS on several real criteria: the server is deployed and running in minutes without you touching a Linux shell, DDoS filtering is included and already tuned for game traffic, the panel handles restarts and file uploads, and there is someone to email at 2 am. If nobody on your team has run a Linux box before, that is not a small advantage, it is the difference between a server that exists and one that does not.

What you give up is control, and it costs more per unit of hardware. A slot-based plan rarely tells you the CPU model, often caps how much you can change, and in many cases gives you a file manager rather than a shell. A VPS at the same money buys measurably more machine, plus root, which means your own MariaDB tuning, your own cron jobs, your own reverse proxy for asset downloads, and the ability to run a Discord bot on the same box instead of paying for a second one.

A dedicated machine is the third step, and it is a bigger jump in price than in capability for most servers. The OVHcloud GAME-1 2026 at 199.20 USD per month, with a matching 199.20 USD installation fee, is roughly ten to twenty times a competent VPS. It is the right purchase when you are consistently at 100 or more concurrent players, when you need the database on the same physical box for latency, or when a noisy-neighbour problem has already cost you a weekend. It is the wrong purchase as a first server, and the number of 20-player communities paying for one is not small.

Root access, txAdmin and the backup nobody has

txAdmin is not optional in practice. It is the official web panel and in-game menu for managing and monitoring a FiveM server, and it ships with the server artifact. Its own feature list is precise about what it covers: starting, stopping and restarting the server and individual resources, the recipe deployer that gets a server running in under 60 seconds, a performance chart across the three threads, player management with bans, warns and whitelisting, Cfx.re authentication with admin permissions and action logging, and monitoring with automatic restarts on crash plus a live console and RAM and CPU readouts.

Read that list again for what is missing. txAdmin does not advertise database backups. Its recovery story is about restarting a crashed process, not about restoring a dropped players table. That distinction is the single most important hosting question nobody asks before buying: if your database is corrupted on a Friday night, what exactly restores it, and who runs that restore? On a VPS the answer is a mysqldump on a cron job that you set up yourself, plus whatever snapshot the provider offers, and OVHcloud including a daily backup of the previous 24 hours on its VPS range is a genuine reason to prefer it over a cheaper box with none. On a managed host, ask whether backups cover the MySQL database or only the server files, because those are very different products.

The related trap is buying a plan with no real database access. If you cannot reach MySQL from outside the panel, you cannot run a migration script, you cannot debug a script that writes malformed rows, and you cannot move to another host without begging for a dump. This matters more the more of your stack is editable: the whole argument in the escrow versus open source guide is about being able to change what you run, and a host that locks the database undoes half of that. Before installing anything, check you can connect to the database with a client, then follow the full installation walkthrough for the artifact, the licence key and server.cfg.

Slots, the Cfx licence, and unlimited offers

Slots are not a hardware feature and they are not really your host to sell. The Cfx.re server command documentation defines sv_maxClients as an integer from 1 to 2048, with values from 32 requiring OneSync enabled and values above 64 requiring full state awareness. On top of that, the Cfx.re guide on game server hosting providers states plainly that to use more than 48 slots you need FiveM Element Club Argentum or above, obtained through the Cfx Portal and attached to your own account.

Read from the fivem.net hosting page in August 2026, the three tiers are Argentum at 15 USD per month plus VAT for up to 64 slots with OneSync Infinity, Aurum at 25 USD per month plus VAT for up to 64 with OneSync and up to 128 with Infinity, and Platinum at 50 USD per month plus VAT for up to 128 with OneSync and up to 2048 with Infinity, plus animated server icons and a magenta highlight in the public listing. That is a recurring cost sitting on top of your hosting bill, and it is the line most first budgets miss entirely.

Which is what makes an unlimited slots advertisement worth a second look. Either the host is bundling an Element Club subscription into the price, in which case ask whose account it is tied to and what happens when you leave, or the number is decorative. Setting sv_maxClients to 300 on a box that hitches at 60 does not give you a 300-player server, it gives you a 300-slot queue for a broken one. The real ceiling is tick time on svMain, and the honest way to raise your effective capacity on a slot-limited plan is to stop paying for players who are not playing, which is all an AFK kick really does.

What it actually costs, by player tier

Every price below was read from the vendor page in August 2026 and several of these providers run rolling promotions, introductory terms and multi-year commitments, so treat them as a band rather than a quote. The Contabo figures in particular are introductory rates on a 24-month subscription, and every OVHcloud VPS price is published as a starting figure rather than a flat rate.

Stacked into realistic monthly budgets, the picture looks like this. Note how the shape of the bill changes at 64 slots, where a fixed subscription joins the hardware line, and again at 128, where slot-based hosting stops being the cheaper option.

Three costs are missing from almost every budget thread and they are not small. The Cfx.re subscription above 48 slots, already covered. A second environment, because pushing untested scripts to a live server is how communities lose weekends, and a test box is the cheapest VPS on this page. And the scripts themselves, which for a serious roleplay build will exceed a year of hosting in the first month. If that total is starting to look uncomfortable, the monetization guide covers what is actually allowed to pay for it under the Cfx.re rules.

The three traps, collected in one place. Paying for cores your main thread will never use, when the same money buys a higher clock. Buying a plan with no shell and no database access, which is invisible until the first migration or the first restore. And treating an advertised slot count as capacity, when the number that limits you is milliseconds per tick. Get the region right, buy clock over cores, check the port speed against the size of your asset pack, and confirm who is responsible for the database backup. Everything else is adjustable later.

Related: How to make a FiveM server · FiveM server optimization