How to choose a VPS for a Minecraft server
Minecraft performance depends on fast CPU cores, enough memory, low network latency and a realistic view distance. Choose for the actual edition, player count and modpack rather than a generic “game VPS” label.
Start with edition and server software
Java Edition has the broadest plugin and mod ecosystem. Bedrock uses a different server and protocol and typically has different memory requirements. Paper and its derivatives can improve Java server performance, while Forge or Fabric modpacks add their own CPU and RAM demands. Confirm licensing and plugin compatibility before ordering a long-term plan.
A practical resource baseline
| Scenario | Starting resources | Notes |
|---|---|---|
| Vanilla, 2–5 players | 2 fast vCPU, 3–4 GB RAM | Moderate view distance |
| Paper, 10–20 players | 3–4 fast vCPU, 6–8 GB RAM | Profile plugins and pregenerate world |
| Medium modpack | 4+ vCPU, 8–12 GB RAM | Check modpack guidance |
| Large public community | Dedicated high-clock CPU or multiple services | Load test and DDoS protection |
Do not assign all system memory to the Java heap. The OS, filesystem cache, network buffers and backup jobs need room. Excessive heap can also create long garbage-collection pauses.
Why CPU speed matters more than core count
The main game tick has substantial single-threaded work, so recent architecture and sustained clock speed often beat many slow cores. Extra cores still help chunk generation, networking, plugins and backups. Watch milliseconds per tick and TPS during actual play; average CPU usage can hide one saturated core.
Pregenerate the world before launch to avoid expensive chunk creation when players explore. Reduce simulation and view distance gradually and profile entities, farms and plugins instead of applying random “optimisation” flags.
Location, traffic and DDoS protection
Choose a region close to most players and test routes from their networks. A geographically nearer data centre can still have poor peering. Stable latency and low packet loss matter more than a very high port speed for a small server.
- Confirm included monthly traffic and port rate.
- Ask whether game traffic is covered by DDoS mitigation.
- Check whether protection changes the server address during an attack.
- Use a domain record so the underlying IP can change later.
- Restrict administration and RCON to trusted IPs or a VPN.
A maintainable server setup
Run the game under a dedicated non-root user. Pin Java and server versions, accept the EULA explicitly, set memory limits and manage the process with systemd or a container supervisor. Expose only the game port; keep SSH, RCON and dashboards protected. Send logs to rotation and alert on repeated crashes, low disk space and unavailable status.
Test updates on a copy of the world. Plugins and mods can depend on exact versions, and a world upgraded to a new game version may not downgrade safely.
World backups that restore correctly
Coordinate saving before copying world files, or use the server's supported save procedure. Store timestamped copies outside the VPS and retain several generations. A provider snapshot helps with fast rollback but should not be the only copy. Regularly restore into a temporary server and join it to verify the world.
Frequently asked questions
How much RAM do ten players need?
For a tuned Paper server, 4–6 GB may be enough, but view distance, plugins and player activity matter more than the count alone.
Is NVMe necessary?
It improves chunk loading, saves and backups, especially for a busy world. Fast CPU and sufficient RAM remain equally important.
Can Java and Bedrock players join together?
Bridges such as Geyser can enable cross-play, but add setup and compatibility work. Test authentication and plugins before launch.
Should I choose VPS or dedicated hosting?
A VPS suits small and medium communities. Sustained large workloads that need guaranteed high-clock cores may justify a dedicated server; compare our VPS vs dedicated guide.
Related: a reliable backup plan for VPS data.