Minecraft server hosting: what actually matters before you pay

RAM: the advertised number versus the RAM your world actually eats

RAM is where loaded chunks, entities and whatever your plugins keep in memory all live. The figure on the sales page is a ceiling handed to the Java process, not a measurement of what your server needs. What pushes the number up: view distance, players spreading out across the map (each one loads their own area), how much world has been explored, and plugins that hold data in memory.

When RAM is too tight, the Java virtual machine spends its time cleaning up memory instead of running your world. The symptom looks like a network problem: short, repeated freezes, even though the cause is entirely internal. The classic trap is shared RAM, where several servers compete for the memory of one physical machine and the advertised ceiling is not guaranteed at the moment you need it.

• Ask whether the RAM is dedicated or shared with other instances on the same machine
• Check you can add RAM later without starting over or migrating your world
• A high view distance often costs more memory than a few extra players
• Economy, permissions and logging plugins all take a slice of that memory

CPU decides your TPS, and RAM will not rescue it

A Minecraft server calculates its world in ticks, and most of that work happens on a single thread. So single-core speed matters more than core count. A machine with many slow cores can feel worse than one with fewer, faster cores. The exception is Folia, which splits world regions across threads, so extra cores finally earn their keep.

TPS is the number of ticks computed per second, and the target is 20. When it drops, everything in game slows down: mobs, redstone, crop growth. The usual culprits are mob farms, piles of entities in one place, or terrain generation while players explore fresh land. Adding RAM fixes none of that, because the processor is the thing running out of headroom.

• Look at the processor generation, not just the advertised core count
• Ask how many game servers share the same physical machine
• Paper is already far lighter than vanilla, and Folia goes further on multi-core
• A server that stutters with two players online has a CPU or plugin problem, not a RAM problem

Server location is measured from your players, not from you

Latency comes from physical distance and from how good the network route is. If most of your players are in North America, a North American datacenter gives lower ping than a very powerful machine on the other side of the planet. It is decisive in PvP, where a delay changes who wins a fight, and much less of an issue on a relaxed survival server.

Ask for the city, or at least the country, of the datacenter, and whether the host gives you a test address so you can measure ping before you commit. Read what they say about DDoS protection too. A public server eventually attracts someone with a grudge, and that protection is worth more to you than one more gigabyte.

• Pick the region your players live in, not the one you happen to live in
• Ask for a test address and measure ping before you order
• Steady ping beats low ping that spikes
• Check DDoS protection, especially if the server will be public

File access: the criterion everyone forgets, and the one that blocks everything

Installing a plugin means dropping a .jar into the /plugins folder and restarting the server. If a host will not let you upload your own files, you cannot install a plugin you made yourself. Some of the simplest offers only expose a curated plugin catalogue, which is fine for plenty of people but stops any custom plugin dead.

So check for FTP or SFTP access, or at minimum a file manager in the panel, the ability to edit server.properties and config files, a console you can read startup errors in, free choice of Minecraft version and server software (Paper, Spigot, Bukkit, Folia), and how you would get your world back if you left. Backups deserve the same question: automatic or your job, and downloadable or locked in the panel.

• FTP or SFTP access, or a file manager that accepts your own .jar uploads
• A visible console so you can read errors when the server starts
• Free choice of Minecraft version and server software
• Automatic backups, and crucially, backups you can download
• An exit route: the ability to take your world folder with you

The categories of hosting, and who each one suits

There are several ways to run a server, and none of them is better in the abstract. Prices move constantly and differ by country, so you will not find any here. Compare them yourself, on the sites of the hosts themselves, on the day you buy.

A Minecraft-specific host installs the server software for you and hands you a ready-made panel, with support that knows the game. A general-purpose VPS gives you a bare machine: total freedom, but you install Java and the server yourself from a command line. A dedicated machine is aimed at networks of several servers, with the sysadmin work that implies. Self-hosting at home looks free until your upload bandwidth, your IP address and opening a port on your home network become the real conversation. And free plans are mostly for trying things out: they usually sleep the server when nobody is playing and cap resources tightly.

• Minecraft-specific host: ready panel, fast setup, less freedom underneath
• General-purpose VPS: full control, but Java, updates and security are on you
• Dedicated machine: for multi-server networks, with real admin work attached
• Self-hosting: fine for friends, demanding on bandwidth and security
• Free plan: good for a trial, rarely for a public server you want to keep

Test your plugin online before you pick a host

More often than not, the reason someone starts shopping for hosting is not the world, it is one specific plugin they want running on their server. It is worth checking that the plugin exists and behaves before you commit to a monthly bill.

That is what Minax is for. You describe the plugin in plain English, the AI writes the Java, compiles it into a .jar, and a self-correction loop feeds compile errors back in until the build comes out valid. Then you can launch that plugin online on a test server and check in game that the commands do what you meant. No host, no install, no port forwarding. Once you are happy, the .jar is yours: drop it into /plugins at whichever host you choose, now knowing what your machine will actually have to run.

On cost, the rule is simple: downloading a plugin the community has already published costs nothing, and each generation uses credits. Creating or editing a plugin needs credits, in packs paid once, with no subscription: 50 credits for €17.99 VAT included. To edit a plugin you already made, there is also a pack of 15 credits for €5.99. Credits from a pack stay valid for 36 months.

• Describe the plugin in plain English, get a compiled .jar back
• Launch it online and check the commands in game, with no host
• Adjust your description and regenerate if the behaviour is off
• Choose your host afterwards, knowing what it has to run

Frequently asked questions