Minecraft Server Requirements in 2026: What Actually Matters (And What Changed)

Type “Minecraft server requirements” into a search bar and you’ll get a dozen nearly identical pages, most written by hosting companies, most quoting Java 21 as the current requirement. That was true through most of 2025. It’s not the full picture anymore.

In March 2026, Mojang shipped Java Edition 26.1 — the first release under a new “year.drop” version scheme (26.1, 26.2, and so on, replacing 1.x.x) — and it’s also the first version that requires Java 25 to run, on both client and server. If you’re setting up a server today, the honest answer to “what do I need” depends on which generation of Minecraft you’re actually running, not just how many friends are joining.

The versioning change nobody updated their guide for

Here’s the split that matters before you pick any hardware:

If you’re running any release from 1.20.5 up through the last 1.21.x builds, Java 21 is still correct — nothing changes for you. But if you or your players update to 26.1 (“Tiny Takeover”) or later, the server jar simply won’t start on Java 21. Paper, Purpur, and most plugin ecosystems needed a few days to catch up with compatible builds after 26.1 shipped, which is worth checking before you commit to updating a live server with a plugin-heavy setup.

One quieter change matters just as much for planning: 26.1 raised the client’s default memory allocation from 2 GB to 4 GB and switched the default garbage collector from G1GC to ZGC on supported systems. That’s a client-side change, not a server one, but it’s a useful signal — Mojang is building for a heavier baseline across the board, and server RAM guidance from 2024 undersells what’s comfortable today.

CPU: the bottleneck almost nobody budgets for

The single most misunderstood part of server sizing is this: Minecraft’s world logic runs on one CPU core, not across all of them. World ticking, redstone evaluation, entity AI, and chunk loading are handled sequentially on the server’s main thread. A 16-core Xeon with a modest clock speed will lose to a 6-core consumer chip with a higher one, every time.

• Single-thread performance is what to check — not core count, not total GHz across all cores.
• 3.5 GHz+ base clock is a reasonable floor for 10+ players without stutter.
• 4.5 GHz+ boost clock is where heavy mods or 20+ concurrent players stop feeling sluggish.
• Modern AMD Ryzen chips (5000/7000/9000 series) currently lead single-thread benchmarks that map well to Minecraft’s workload, though a recent Intel Core i5/i7 performs comparably.

If your server’s tick rate (TPS) drops below 20 during normal play, it’s almost never a RAM shortage — check CPU load on that one main thread first.

RAM: sized by workload, not guesswork

RAM requirements genuinely did shift upward with the move to the Java 25 runtime and the denser chunk/registry data in recent versions. These figures reflect a 26.x-era baseline rather than older 1.18-era advice you’ll still find floating around:

Vanilla (no mods, no plugins)

Paper/Spigot with plugins

Modded (Forge/Fabric/NeoForge)

Storage and how fast worlds actually grow

A brand-new world is under 500 MB. It doesn’t stay that way. SSD storage is no longer optional advice — spinning HDDs cause visible stutter during chunk generation and autosaves that players notice immediately, especially with WorldEdit or large builds in progress.

NVMe is worth paying for on anything public-facing or 20+ players; SATA SSD is fine below that. Whatever world size you expect, roughly triple it to leave room for backups, mod jars, and plugin data.

Network: the part self-hosters underestimate

If you’re renting hosting, skip this — providers run enterprise connections. If you’re hosting from home, your upload speed, not download, is the ceiling. Most residential plans advertise download speed and bury upload at a fraction of it.

Also worth knowing before you self-host: some ISPs run Carrier-Grade NAT, which blocks incoming connections outright regardless of port forwarding. Check with your ISP directly if players can’t connect even after forwarding the right ports.

Server software: it changes your hardware math

• Vanilla — the official jar, unoptimized, no plugin support. Use it only if unmodified gameplay is the actual goal.
• Paper — the practical default for most servers. Performance patches typically cut CPU/RAM load 30–40% versus vanilla, and it runs standard Bukkit/Spigot plugins.
• Purpur — a Paper fork with deeper configuration options, similar performance profile.
• Forge — required for most mods rather than plugins. Heavier on resources, and compatibility between mods can be finicky.
• Fabric — lighter-weight modding alternative to Forge, faster startup, smaller but fast-growing mod ecosystem.

If your server exists mainly to run WorldEdit for large-scale terraforming — carving out circles, spheres, or domes with commands like //sphere or //cyl — you’ll want Paper or Purpur specifically, since WorldEdit’s brush and selection tools lean on the same single-thread performance discussed above. We cover the actual command syntax in our WorldEdit commands guide for circles and spheres if that’s the direction you’re headed.

Self-hosting vs. paid hosting: the honest math

Self-hosting reads as “free” until you actually total it up. For a 10-player Paper server with a moderate plugin set, a realistic monthly self-hosting bill looks like this:

A hosted server with equivalent specs, DDoS protection, and automated backups typically runs $8–20/month. Below roughly 15–20 players, hosting is usually both cheaper and less maintenance than self-hosting. The calculation flips mainly if you already own idle hardware and a fast, stable upload connection — then self-hosting is close to free at the margin, and the main cost is your own time.

Whatever route you take, once the server’s running smoothly, the fun part starts — actually building. If you’re planning circular structures, towers, or domes at scale, browse the tool set below.

Frequently asked questions