Sizing a Minecraft VPS: how much RAM and what kind of CPU you actually need

Minecraft is deceptively heavy for a game that looks like it runs on a toaster, and the way it uses a server is unusual enough that the obvious specs steer you wrong. The main simulation runs on a single thread, so a plan with eight slow cores can lag worse than one with two fast ones; and the world, the entities, and the chunks players keep loaded live in memory, so RAM is usually the wall you hit first. Before you rent anything it helps to know roughly how big your server will get, because <a href="/#calc">a quick sizing pass</a> up front is far cheaper than migrating a live world full of friends later. This guide covers the three specs that decide whether your server holds 20 TPS — memory, CPU, and disk — and how they scale with players and mods.

RAM is the number that matters most

For almost every Minecraft server, memory is the first and most important thing to size, because the running world — loaded chunks, entities, player inventories, and the Java heap itself — all lives in RAM. A small vanilla survival server for a handful of friends is comfortable around 2–4 GB; a busy public server or anything running Paper with a long view-distance wants 6–8 GB; and a heavy modded pack (think 150+ mods) can easily ask for 8–12 GB or more before it even feels smooth. The rough rule is that players add memory gradually but mods and world size add it in big steps, so size for the pack first and the player count second. Our guide on how much RAM a VPS needs walks through the same logic for general workloads, and it applies almost directly here.

A detail that trips people up: do not hand the entire server's RAM to the Java heap. The operating system, off-heap memory, and the JVM's own overhead all need room, so on an 8 GB box you might allocate around 6 GB to Minecraft and leave the rest free. Over-allocating the heap is a classic cause of a server that runs fine for an hour and then freezes during garbage collection. If you are weighing a cheaper plan with less memory, read our take on cheap VPS plans first — for Minecraft specifically, under-buying RAM is the single most common false economy, because it shows up as stutter the moment a few players spread out and load chunks in different directions.

CPU: single-core speed beats core count

Vanilla Minecraft, and even optimized forks like Paper and Purpur, run the main game tick — mob AI, redstone, block updates, world generation — on one thread. That means the specification to care about is per-core clock speed and single-thread performance, not how many cores the plan advertises. A VPS with two fast modern cores will almost always give you a steadier 20 TPS than one with six slow or heavily shared cores, which is the opposite of what the bigger-sounding plan suggests. Extra cores do help around the edges — chunk loading, network handling, and plugins can use them — but they never rescue a server whose main thread is too slow to keep up.

This is also why shared or oversold VPS plans hurt Minecraft more than most workloads: when the host packs many tenants onto one physical CPU, your single critical thread gets starved at exactly the wrong moment, and the game lags in visible, blocky ways. If you are comparing hosts, favor plans that are explicit about dedicated vCPU or a generous fair-use policy, and look at the actual CPU generation rather than just the core count. For a shortlist already filtered toward the kind of fast, well-provisioned boxes that suit game servers, our Minecraft VPS picks are a reasonable starting point, and the sizing calculator can translate a target player count into a plan before you commit.

Disk, location, and keeping the world safe

Minecraft worlds grow as players explore, and a server with an active map can accumulate tens of gigabytes of chunk data over a few months, so pick a plan with headroom and, ideally, NVMe or SSD storage — fast disk noticeably smooths out the chunk loading that happens as players move around the map. The other half of the equation is latency: because the server simulates everything and the client just shows the result, players feel every millisecond of ping, and a server far from your group will feel sluggish even when its TPS is perfect. Host the box near where most of your players actually are; our guide on server location and latency explains how distance translates into the lag players complain about.

Finally, treat the world folder as something you cannot afford to lose, because a corrupted save or a bad plugin update can erase months of building in seconds. Schedule regular backups of the world directory — most serious servers snapshot it daily and keep a week or two of history — and store at least one copy off the server itself. If your host offers automatic snapshots, turn them on, but do not rely on them alone; our guide on VPS backups and snapshots covers the difference between a convenient snapshot and a real backup, which matters a great deal the day something goes wrong.