How much RAM does your Minecraft server need?
Start with the server software and workload, then compare memory alongside CPU resources. A player count alone cannot tell you how much RAM your world needs, and adding memory is not a fix for every kind of lag.
Describe the server you will actually run
A small Paper world, an established SMP and a large modpack are different workloads. Begin with the pack author’s server requirements if there is a pack. Include its exact release, because changing the Minecraft version or mod list can change the requirements.
Think about the busy session rather than only the first empty login. Players exploring different areas, active world content and installed software can change resource use. A useful request explains what will happen on the server, rather than asking how many players fit into a single gigabyte.
- Record the software, version and modpack release
- List plugins and any existing world you want to move
- Estimate simultaneous activity rather than total community membership
- Tell Sift whether the project is a new world, an existing SMP or a network
Compare Sift’s memory and CPU allocations together
Sift’s Minecraft catalog pairs higher memory tiers with more Ryzen 9 CPU threads. The allocations below are the listed resources, not a benchmark, an exclusive physical-core claim or a promise of a particular player capacity.
The plan descriptions suggest workloads to discuss with Sift. Check a demanding modpack’s requirements before choosing a tier; a plan name cannot replace that check. Prices and your billing currency are available on the Minecraft hosting page.
- Seed: 4 GB memory, Ryzen 9 · 2 CPU threads. Vanilla or Paper with a few friends.
- Realm: 6 GB memory, Ryzen 9 · 3 CPU threads. A busy SMP or lighter modpack.
- Frontier: 8 GB memory, Ryzen 9 · 4 CPU threads. More headroom for mods and players.
- Universe: 12 GB memory, Ryzen 9 · 5 CPU threads. For demanding modpacks and networks.
Check the bottleneck before buying more memory
When a server is already running, collect evidence during the problem. Note the time, what players were doing, recent software changes and any errors. A crash while loading a pack is a different issue from a running server slowing down during exploration.
Paper’s documentation describes profiling with spark to identify work taking time on the server. A profile can help you investigate performance rather than guessing from the RAM figure alone. Use the documentation for your installed version and remove private information before sharing logs.
Memory is only one part of the order
Sift lists unmetered storage for Minecraft plans. That means no fixed storage figure is advertised; it does not mean unlimited physical capacity. Discuss a large existing world or unusual storage needs before ordering.
Also choose a region near the community and confirm availability. A memory upgrade does not shorten the network route between a distant player and the server. Keep the software, resource and location decisions separate so each solves the problem it is meant to solve.
What to send if you are unsure
Send the pack’s public link, the exact version, your expected activity and the region you prefer. If you already run the world elsewhere, describe the issue you are trying to improve without sharing account passwords or private access tokens.
Use Custom plan if the listed allocations do not match the project, or ask Sift to help choose a tier. Agree the resources, displayed billing price and availability on Discord before paying. No fixed player count or performance result is assumed by this guide.
Documentation and further reading
For your Sift order, confirm the software, resources and region with us before paying.