X
X
X
X
All systems operational · 200 Tbps+ DDoS protection active
Sign Up Sign In 08505574494

How to Buy a Minecraft Server: RAM and CPU Guide

HomepageArticlesMinecraft ServerHow to Buy a Minecraft Server: RAM,...
How to Buy a Minecraft Server: RAM, CPU and Setup Guide

What determines a good Minecraft server purchase is not the amount of RAM — the number that actually decides player experience is the processor's single-thread performance. RAM matters because running out causes crashes, but once you have enough, adding more does not raise TPS. This guide covers how much capacity each player count really needs, which settings move performance more than hardware does, what to check on location and DDoS protection, and the official rules for making money from a server.

Settle three questions before you buy

Choosing a plan only makes sense after you have these answers:

  • How many concurrent players? Registered player count is irrelevant; concurrency decides. Size for your evening peak.
  • Which server software? Vanilla, Paper (plugins) and modded installs have completely different resource profiles. A modded server can need twice the RAM of a plugin server at the same player count.
  • What kind of world? A continuously expanding survival world behaves very differently on disk and CPU than a fixed-map minigame server.

Without those three answers, the plan you buy is either wasted money or inadequate within three weeks.

How much RAM do you need?

Practical ranges by server type and concurrent player count:

Vanilla server

  • 1–5 players: 4 GB
  • 5–10 players: 4–6 GB
  • 10–20 players: 4–8 GB

Paper (plugin-based) server

  • 1–10 players: 4 GB
  • 10–30 players: 4–8 GB
  • 30–60 players: 8–12 GB

Modded server (20–80 mods)

  • 1–5 players: 4–8 GB
  • 5–10 players: 8–12 GB
  • 10–20 players: 8–16 GB

Full modpacks (FTB, ATM, RLCraft and similar)

  • Light packs: 8 GB
  • Medium packs: 8–12 GB
  • Heavy packs: 12–16 GB

These figures are the server's total RAM, not the heap you allocate to Minecraft. The operating system and other processes need their own share.

What RAM does not fix: TPS and CPU

The most expensive misconception among new server owners is reaching for a RAM upgrade the moment lag appears. Adding RAM improves performance only if you were genuinely memory-starved.

A Minecraft server does most of its work on a single thread. What decides TPS is therefore not core count but single-thread performance. A four-core server on a high-clocked current-generation processor can deliver higher TPS than an eight-core server on an older one.

Worse, over-allocating RAM can hurt: a very large heap lengthens garbage collection phases, producing more noticeable freezes. The real sources of lag are usually:

  • CPU saturation (excessive redstone, hoppers or heavy plugins)
  • Entity counts — mob herds, dropped item piles, runaway farms
  • High simulation distance
  • Badly written or conflicting plugins

JVM tuning: Aikar's flags

The G1GC configuration commonly used on Minecraft servers meaningfully reduces GC-induced freezes. The core rules:

  • Set -Xms and -Xmx to the same value — this eliminates wasted allocation.
  • Never set an -Xmx you could not support if fully consumed. The operating system needs separate capacity.
  • For servers at 10 GB or below, values such as -XX:G1NewSizePercent=50, -XX:G1MaxNewSizePercent=80 and -XX:InitiatingHeapOccupancyPercent=10 are used; above 10 GB these become 35, 60 and 15 respectively.

Two settings worth half your performance: view-distance and simulation-distance

These two values in server.properties can matter more than the hardware you bought.

view-distance controls how many chunks around each player are sent to the client. It drives RAM and bandwidth, and the chunk count grows fast:

  • view-distance 8 → 289 chunks per player
  • view-distance 10 → 441 chunks
  • view-distance 12 → 625 chunks
  • view-distance 16 → 1,089 chunks

simulation-distance determines how many chunks are actively ticked: mob spawning, crop growth, redstone logic. This is the primary CPU consumer.

The correct approach is keeping simulation distance below view distance — players see distant terrain without those chunks being processed. Practical values by player count:

  • 5–10 players: view 10–12 · simulation 8–10
  • 20+ players: view 8–10 · simulation 6–8
  • Modpack servers: view 6–8 · simulation 4–6

If your server lags, lower these two values and test before upgrading the plan. In most cases the problem resolves right here.

Server software and Java version

If you plan to use plugins, vanilla server software will not do the job — Paper is today's default choice for both performance and plugin support. For setup steps see our guide on how to set up a Minecraft server, and for the plugin side, how to add plugins to a Minecraft server.

An important change landed on the Java side in 2026, and it is the most common post-purchase failure:

  • Minecraft 1.20 – 1.21.11: Java 21
  • Minecraft 26.1 and later: Java 25

On the wrong Java version the server will not start at all, throwing UnsupportedClassVersionError in the console. Ask which Java versions a provider can install before you buy.

Location, ping and DDoS protection

On a game server, player experience is defined not by average performance but by latency in the worst moments. If your player base is in Turkey, hosting in Turkey buys 40–60 ms over overseas locations — a gap no amount of optimisation recovers.

On DDoS there is a technical detail worth knowing: Minecraft Java Edition uses TCP, but most attacks aimed at game servers are UDP-based and target saturating the infrastructure. The right question for a provider is not "how many Gbps of protection" but which layer the protection operates at and whether it covers UDP floods. We explained what those capacity figures actually mean in our DDoS protection capacity guide.

Attack frequency is also high on infrastructure hosting game servers, so resources need to be isolated for an attack on a neighbour not to reach you.

Domain and SRV record: connecting without a port

What lets your players type myserver.com instead of myserver.com:25565 is an SRV record — visually a small detail, but a large one for how serious a server looks.

The record is defined as:

  • Service: _minecraft
  • Protocol: _tcp
  • Name: _minecraft._tcp (for the root domain) or _minecraft._tcp.play (for a subdomain)
  • Priority / Weight: 0
  • Port: 25565 (or your server's port)
  • Target: A hostname pointing at your server's IP

If your panel asks for a single value, enter it as 0 25565 play.myserver.com. Allow a few hours for propagation. For all DNS record types see our DNS records guide, and register your domain from our domain search page.

The rules for making money from a server

Most guides skip this section, but it is the most critical one if you are building a commercial server. Minecraft's official usage guidelines do not prohibit earning money from a server — they clearly limit how you may earn it.

What is allowed

  • Charging for server access — provided the cost is the same for everyone and all paying players get the same access.
  • Accepting donations — as long as donors receive no exclusive in-game benefits.
  • Selling cosmetic items (excluding capes and cape-like features).
  • Using in-game currency that has no real-world value and cannot be cashed out.
  • Displaying advertising that grants no competitive advantage.

What is prohibited

  • Charging different prices to different players.
  • Selling gameplay advantages for money (pay-to-win).
  • Building play-to-earn mechanics involving real-world currency.
  • Gating in-game content behind NFTs or similar systems.

Branding and disclosure rules

You must make clear that you — not Mojang or Microsoft — are responsible for the server, avoid official Minecraft logos and brand assets in marketing, and not make "Minecraft" your primary brand or domain element. Content is also expected to be suitable for players of all ages.

Read these rules before designing your revenue model; correcting it afterwards means a dispute with players who already paid.

Nubitro Minecraft servers

Nubitro Minecraft servers run in Istanbul, Turkey with NVMe M.2 SSD storage and 1 Gbps unmetered traffic, on infrastructure carrying 200 Tbps+ DDoS protection as standard.

The plans and roughly what they carry:

  • Starter — 2 cores / 4 GB RAM / 50 GB NVMe: small friend groups and light plugin setups.
  • Silver — 4 CPU / 8 GB RAM / 60 GB NVMe: mid-sized plugin servers, 10–30 concurrent players.
  • Gold — 6 CPU / 16 GB RAM / 80 GB NVMe: busy survival servers, medium-weight modpacks.
  • Premium — 6 CPU / 32 GB RAM / 100 GB NVMe: heavy modpacks, multi-world networks or several server instances.

Because resources are assigned through hardware partitioning, neighbour load does not reach your TPS — and on a game server, that consistency matters more than average speed. Review current configurations and pricing on our Minecraft server hosting page, or see our VDS buying guide for general server selection criteria.

Frequently Asked Questions

How much RAM is enough for a 20-player server?

On a Paper server running a reasonable number of plugins, 8 GB comfortably handles 20 concurrent players. A modded install at the same player count may want 12–16 GB. What the server runs matters as much as how many people are on it.

I added RAM but the lag remains — why?

Because memory probably was not the problem. Common causes are CPU saturation, excessive entity counts, high simulation distance and heavy plugins. Lower simulation-distance first, then profile to find which plugin is eating tick time.

More cores or higher clock speed?

For Minecraft, clock speed. Since the server does most of its work on one thread, strong single-thread performance matters more than core count. Extra cores help with chunk generation and background tasks.

Do my players need to install anything?

Not if you use plugins — they run server-side only. If you use mods, yes: every player needs the same mod set or they cannot connect.

Can I make money from my server?

Yes, within the rules. Access fees must be the same for everyone, donations must not grant in-game benefits, and pay-to-win mechanics are prohibited. Selling cosmetics and using non-cashable in-game currency are allowed. Read the official usage guidelines before building your revenue model.

A managed panel or my own server?

Panel-based products get you started quickly but limit configuration freedom. On your own server you control the Java version, JVM flags, multiple server instances and your backup scheme. If you plan multiple worlds or a proxy network, your own server is the only sensible option.

Summary

  • Settle concurrent player count, server software and world type first.
  • On a Paper server, 4–8 GB suits 10–30 players and 8–12 GB suits 30–60.
  • Modded installs want noticeably more RAM at the same player count.
  • TPS is decided by single-thread CPU performance, not by RAM.
  • Over-allocating RAM can lengthen GC phases and increase freezes.
  • -Xms and -Xmx should match and stay within what the system can support.
  • simulation-distance is the primary CPU consumer; keep it below view-distance.
  • Minecraft 1.20–1.21.11 needs Java 21; 26.1 and later need Java 25.
  • A Turkish location is worth 40–60 ms for domestic players.
  • On DDoS protection, UDP coverage and operating layer matter more than the Gbps figure.
  • An SRV record lets players connect without typing a port.
  • Read the official usage guidelines before designing monetisation — pay-to-win is prohibited.
Powered by WISECP
💬
Top