The right server size depends on what you and your friends do in the world. Exploring new terrain, building farms, running plugins, or installing a modpack can all change the workload. RAM matters, and so does CPU time.
Start with a practical allocation, then check your server during a normal play session. Real usage from your world will tell you more than a player-count estimate.
A practical starting point
When you create a Minecraft Java server, MaximusHost recommends starting with 4–8 GB RAM and 2–4 vCPU. The create form offers 1–24 GB RAM and 1–8 vCPU, so you can choose an allocation that fits your plans and adjust it as your world grows.
As a rough planning aid:
- A lightly used Vanilla world for a small group can often begin near the lower end of the recommendation.
- A Paper server with several gameplay plugins may need more headroom when players are exploring or using active farms.
- A modded Fabric, Forge, NeoForge, or Quilt server commonly benefits from starting nearer the middle or upper end because mods add memory use and startup work.
- A busy world with frequent new-chunk generation, redstone, entities, or automation can need more CPU as well as more RAM.
These are starting points rather than fixed rules. Two worlds with the same number of players can use different resources.
What makes a server use more RAM?
RAM holds the server process, loaded chunks, entities, mods or plugins, and temporary work. It is not simply “RAM per player.” Usage can rise when players spread out and load different terrain, when simulation distance is high, or when a modpack keeps additional systems in memory.
Common contributors include:
- World activity. Exploring fresh terrain, teleporting between far-apart bases, and generating chunks can create short, heavy bursts.
- Simulation and view distance. More loaded chunks and ticking entities increase the work the server holds and processes.
- Mods and plugins. Libraries, content mods, claims, maps, economy systems, and automation can add a meaningful baseline before anyone joins.
- Entities and machines. Item piles, villagers, mobs, hoppers, redstone, and modded machines can raise both memory and CPU pressure.
- World history. A long-lived world with many visited areas and player projects deserves monitoring even if the player list is small.
More RAM can help when usage repeatedly approaches the allocation or the server reports memory errors. If players experience lag, check CPU use and console messages too; memory is only one possible cause.
RAM and CPU work together
Minecraft performs time-sensitive simulation work. If CPU usage peaks during chunk generation, large farms, or busy periods, adding RAM alone may not improve responsiveness. Conversely, a server that is running out of memory can become unstable even when CPU use looks modest.
Open Resources in your server manager to review memory and CPU use. Check while players are doing their usual activities, and compare readings across a few sessions. Startup, a restart, or exploring new terrain can create short-lived spikes.
Vanilla, plugins, and modpacks
Vanilla is generally the simplest baseline because it does not load a third-party mod or plugin stack. Paper is often chosen for a plugin-oriented server, but every plugin still has its own cost and compatibility requirements. Fabric, Forge, NeoForge, and Quilt are mod-loader ecosystems; the required mods, their dependencies, and their Minecraft version matter more than the loader name alone.
Before changing a modded server’s resources, check whether a recent mod update, missing dependency, or version mismatch is causing a problem. More RAM is not a substitute for a compatible stack. See the Minecraft Java mods guide for the management steps.
When to adjust resources
Consider increasing RAM or vCPU when normal gameplay repeatedly shows high usage, slow simulation, memory failures, or trouble during predictable busy periods. Make one measured change, restart if required, and observe again.
Consider reducing resources when recent usage remains comfortably below the allocation across representative sessions. Leave enough headroom for exploration, events, backups, and occasional spikes; cutting too closely can make a previously stable server fragile.
Choose and adjust resources on MaximusHost
When creating a server, choose RAM and CPU in the resource fields and review the estimate shown before you continue. After creation, open Resources to check usage and change your allocation. The Resources guide explains the controls.
MaximusHost bills server usage in credits rather than through a fixed monthly Minecraft plan. Review the estimate for your selected resources and expected running time, and check Billing and Credits for how storage is handled while a server is stopped. Back up your world before a major version or mod change.
Next step
If you know which server software you want, review Minecraft Java hosting and create your server from My Servers → Create New Server. If you are unsure about sizing, begin near the recommendation and use your own resource readings to guide later changes.
