Skip to content

Minecraft

Minecraft Java Server Requirements: Java, CPU, RAM and Storage

Match the runtime to the server version, then size resources around world activity and recovery needs instead of a fixed player-per-gigabyte rule.

MinecraftRequirementsJavaCPURAMStorage
Reading time
4 min read
Published
Updated
Maintained by
EnderHost Team

A Minecraft Java server requires a compatible Java runtime, enough memory for the complete process, CPU capacity for its tick workload, storage for the world and backups, and a reachable game port. The exact requirements depend on the Minecraft version, server software and extensions. Player count alone cannot produce a reliable hardware specification.

Which Java version does the server need?

Check the server project’s release instructions before selecting a runtime. The following is Paper’s published recommendation table, checked on September 25, 2026. It is not a statement that EnderHost offers every listed legacy version, or that every modpack supports the same runtime.

Paper recommended Java versions
Paper versionRecommended Java
1.7.10–1.118
1.12–1.16.411
1.16.516
1.17–1.1917
1.20–1.21.1121
26.1+25

Fabric’s current Java guidance also identifies Java 25 for Minecraft 26.1. For a modpack, follow the pack’s release notes and supported loader/runtime combination. Older software may require older dependencies and needs a separate maintenance decision.

java -version

Run this in the environment that actually starts the server. A panel may use a different container runtime from the VPS shell. Likewise, the Java bundled with a desktop Minecraft launcher does not establish which Java a standalone server command uses. Check the startup log as well as the selected runtime.

How much CPU, RAM and disk should you plan?

Capacity worksheet
ResourcePlan aroundEvidence to collect
CPUTick work, exploration, entities and extension behaviorBusy-period MSPT and a profile of slow ticks
MemoryHeap plus native overhead and any colocated servicesStartup peak, sustained heap and total process/container usage
StorageExisting worlds, future growth, extensions and logsCurrent usage and growth across representative sessions
Recovery spaceRetained backups, temporary archive and restore workspaceA complete backup size and a trial restore into a separate directory
NetworkPlayer routes, downloads and permitted game trafficConnection tests from players in the expected regions

For memory, use the Minecraft RAM sizing guide to distinguish heap from the hosting limit. For CPU, the TPS/MSPT guide explains why spare aggregate CPU does not rule out a busy tick thread. Neither table substitutes for a representative load test.

Include space to recover, not just space to run

Suppose your files occupy 12 GiB. One additional full copy already takes the uncompressed total to 24 GiB; restoring another copy could take it to 36 GiB before growth, logs or archive overhead. This is an arithmetic example, not a minimum plan size. Compression varies, and remote backups still need room for local staging if your workflow uses it.

Track growth after exploration and scheduled tasks. Set a free-space alert that leaves enough time to act. A full filesystem can interrupt saves even when CPU and RAM appear healthy. Keep at least one recoverable copy outside the server’s own failure boundary.

Which ports and access are required?

Java servers commonly use TCP 25565, but a hosting panel can assign a different port. Use the actual allocation in the configuration, firewall and connection instructions. Optional query, remote-console, proxy or cross-edition services have separate settings; do not open them just because a generic tutorial lists them.

A prelaunch check you can repeat

  1. Record Minecraft version, server build, Java runtime, extensions and configured memory limit.
  2. Start privately and inspect the full startup log. Confirm that the intended world and extensions loaded.
  3. Join using the supported client configuration and test the expected activities, including exploration or additional dimensions.
  4. Capture peak memory, disk growth and tick behavior; investigate the resource that actually limits the workload.
  5. Create a backup and restore it into a separate test location before opening to the community.

Use those results to compare Minecraft hosting plans. If you need operating-system control or several independent services, compare the responsibilities in VPS versus game server hosting before choosing a larger machine.

Sources and references

Hosting documentation. Publication and update dates reflect this edition.

Related articles

Related topics

Hardware we trust. Software you know.

PREPARING YOUR EXPERIENCE