Buyer's guide

How to choose Minecraft server hosting

What actually separates one Minecraft host from another, written by people who run the machines. Sizing, hardware, pricing traps, and the questions worth asking before you pay.

#Size the plan to what you run, not to how many players you expect

The most common sizing mistake is picking RAM from a player count. Player count barely moves memory use. What moves it is how much the server has to keep loaded: the number of mods, the number of loaded chunks, and the size of the entity and block-entity population.

A vanilla server with thirty players will sit comfortably in 3 GB. A kitchen-sink modpack with two players will not. Packs like All The Mods, RLCraft and Vault Hunters load thousands of classes and hundreds of registries before anyone joins, and that baseline is paid whether the server is busy or empty.

If you are between two tiers, let the pack decide rather than the player count.

#"Dedicated RAM" is a phrase, not a guarantee

Nearly every host advertises dedicated or guaranteed RAM. The phrase is not standardised, and it does not always mean what it sounds like.

Hosts run many customer servers per physical machine. The question is what happens when all of them want their full allocation at once. If the memory limit is enforced by the kernel for each container, your allocation is yours and a busy neighbour cannot take it. If the host has sold more memory than the machine physically has, something gives when the machine fills: swapping to disk, memory reclaim, or the kernel killing processes.

You cannot usually verify this from outside before buying. What you can do is ask: is my RAM limit hard-reserved, and do you oversell memory on a node? A host that reserves memory properly will answer plainly. A vague answer is itself an answer.

The symptom of getting this wrong is a server that behaves for a week and then stutters at peak evening hours, when your neighbours are busiest.

#Single-core speed decides your TPS

A Minecraft server's main tick loop runs on one thread. Paper and its descendants move some work off that thread, and Folia goes further by regionising it, but for most servers the tick is still one core doing one thing at a time, twenty times a second.

That has a consequence which surprises people: a plan advertising eight cores is not four times faster than one advertising two. What decides whether you hold 20 TPS is how quickly a single core finishes a tick. Extra cores help with chunk generation, world saving and garbage collection, but they cannot make the tick loop itself run faster.

So when you compare hosts, the processor model and its single-core clock matter more than the core count printed on the plan card. A host that names its CPU is telling you something. A host that says only "high performance hardware" is telling you something too.

#More RAM does not mean a faster server

Allocating a very large heap can make a Minecraft server slower. The Java heap has to be garbage collected, and the larger it grows, the longer a collection pause can run. A pause long enough to miss ticks shows up in game as a freeze.

Give the server what the workload needs plus headroom, rather than everything the machine has. If you are running it yourself, leave memory for the operating system and for the JVM's own overhead, which sits outside the heap. The mechanics are in how the heap flags actually work.

#The renewal price is the price

Introductory pricing is normal in this market. A plan advertised at a low monthly rate is often a first-term promotion, with the rate stepping up when the term renews.

Find the renewal price before you commit. It usually lives in the checkout summary or the terms rather than on the pricing page. Work out the annual cost at the renewal rate and compare hosts on that number instead. The cheapest host in month one is not always the cheapest in month five.

Longer billing terms usually carry a real discount, and also real commitment, so read the refund policy at the same time.

#What is in the plan, and what is in the cart

Two plans at the same RAM and the same price can be different products once you add what you need. Things that are sometimes included and sometimes charged for:

• A dedicated IP address, or a subdomain instead of an IP and port
• Automatic backups, and how many are retained
• A mod and plugin installer
• Scheduled tasks such as nightly restarts
• Extra users with their own logins and permissions
• A database for plugins that want one

Price a like-for-like build with the features you actually want before comparing headline numbers. This is where a cheaper plan often stops being cheaper.

#Put the server near the players, not near you

Latency is measured between each player and the server, so the location that matters is your group's, not yours. If your players are spread across continents, someone will have a worse time and no host can fix that.

Measure rather than guess. Most hosts publish a per-region test you can run from a browser. Pick the region with the lowest ping for the bulk of your group, and if two are close, favour the players who play most.

Twenty milliseconds of difference is not noticeable in normal play. A hundred and fifty is.

#Backups that survive the machine dying

There is a difference between a backup kept on the same machine as the server and one kept somewhere else. The first protects you from deleting your own world. Only the second protects you from the machine failing.

Ask where backups live, how many are retained, and how a restore is performed. Then test a restore before you need one. A backup you have never restored is a hypothesis rather than a backup.

#Check you can leave

Confirm you can get your data out before you put data in: the world folder, the mods, the configs and the player data, as a file you can download yourself.

A host that makes this easy expects to keep you by being good rather than by being awkward to leave. It is worth checking on the way in, while you still have leverage.

#When you should not buy hosting at all

Two situations where paying a host is the wrong answer.

If the server is for a handful of friends, you own a reasonably modern PC, and you do not need it up while that machine is off, self-hosting is cheaper and often faster than an entry-level plan. Your own machine very likely has quicker cores than a shared budget slot. Self Hostd does this for free, without port forwarding.

If you want a world to dip into occasionally with no fixed schedule, a free host may be enough, provided you accept queues, sleeping servers and deletion after inactivity.

Paying makes sense when the server needs to be reachable whether or not your PC is on, when the pack is heavier than your hardware, or when you want someone else to be responsible at three in the morning.

#Where Hostd fits, and where it does not

We run Minecraft Java on four tiers from 3 GB to 14 GB, on AMD Ryzen 9700X with DDR5 memory and NVMe storage, with memory reserved for each server rather than oversold. A subdomain, DDoS protection, daily backups, the mod installer, scheduled tasks and extra users sit in the plan rather than the cart, and first plans carry a seven-day money-back guarantee.

Where we are not the right answer:

• If the lowest headline price per gigabyte decides it for you, PebbleHost undercuts us, and we would rather point at that than argue with it.
• If you want round-the-clock live chat with a person, we do not staff that. Apex Hosting does.
• If your players sit in a region we do not run in, latency outweighs everything else on this page. Host where they are.
• If the pack runs happily on the PC you already own, use the PC.

#Frequently asked questions

How much RAM does a Minecraft server need?

Vanilla or lightly plugged Paper runs about ten players in 3 GB. Most Fabric, Forge and NeoForge modpacks want 6 GB. Kitchen-sink packs such as All The Mods, RLCraft and Vault Hunters want 10 GB or more. Mod count drives memory far more than player count does, so size the plan to the pack.

Is more RAM always better for a Minecraft server?

No. The Java heap has to be garbage collected, and a larger heap means a longer worst-case collection pause. A pause long enough to miss ticks appears in game as a freeze. Allocate what the workload needs plus headroom rather than everything available.

Does CPU core count matter for a Minecraft server?

Less than people expect. The main tick loop is single-threaded, so single-core speed decides whether you hold 20 TPS. Extra cores help with chunk generation, world saving and garbage collection, but they cannot make the tick itself run faster. Compare the processor model rather than the core count.

What does dedicated or guaranteed RAM actually mean?

It depends on the host, because the phrase is not standardised. What matters is whether the limit is enforced per container by the kernel, and whether the host sells more memory than a machine physically has. Ask both questions directly before buying.

Why is my Minecraft server lagging when it has plenty of RAM?

Usually because the bottleneck is not memory. Check TPS first: if it sits at 20, the server is keeping up and the problem is network or client side. If TPS is falling, the usual causes are a single expensive mod, too many entities in one chunk, or a heap large enough that garbage collection pauses are missing ticks.

Can I move my Minecraft server to another host later?

Yes, if your current host lets you download the world folder, mods, configs and player data. Keep the Minecraft version the same or newer and keep the same server software and mod list, and builds and inventories come across intact. Confirm this is possible before you commit, not after.

Written and maintained by the Hostd engineering team. Last updated 2026-08-11. Notice a mistake? Tell us.