How to Choose the Right Minecraft Server Plan
Table of Contents
How to Choose the Right Minecraft Server Plan
Choosing a Minecraft server plan feels like it should be straightforward, but it’s one of the most common sources of frustration for new server owners. Pick too little and your server stutters. Pick too much and you’re wasting money on resources you’ll never use.
This guide breaks down exactly what you need based on what you’re actually running.
Understanding the Key Resources
RAM
RAM is the resource you’ll see advertised most prominently, and for good reason — it’s often the bottleneck for Minecraft servers. RAM holds your world data, player data, plugin data, and the Java Virtual Machine itself.
However, RAM alone doesn’t determine performance. A server with 16GB of RAM but a weak CPU will still lag.
CPU
Minecraft’s main game loop is single-threaded, meaning it primarily uses one CPU core. Clock speed (GHz) matters far more than core count. A 5.0 GHz single core will outperform four 2.5 GHz cores for Minecraft.
Some tasks use additional threads — chunk generation, network I/O, and certain plugins — but the main tick loop is always single-threaded. This is why budget VPS hosting with many low-clock-speed cores often performs poorly for Minecraft.
Storage
World files grow over time as players explore. A fresh vanilla world is tiny, but after months of exploration, world sizes of 5-10GB are common. Modded servers with world generation mods can grow even faster. SSD or NVMe storage is essential — spinning disk drives will cause chunk loading lag.
RAM Guidelines by Server Type
Here’s a practical breakdown. These assume you’re using Paper or Purpur (optimized server software), not vanilla.
Vanilla / Semi-Vanilla
| Players | Recommended RAM |
|---|---|
| 1-5 | 2-3 GB |
| 5-15 | 3-4 GB |
| 15-30 | 4-6 GB |
| 30-50 | 6-8 GB |
| 50+ | 8-12 GB |
Vanilla Minecraft is relatively lightweight. The main RAM consumers are loaded chunks and entities.
Plugins (Survival, SMP, Minigames)
| Players | Recommended RAM |
|---|---|
| 1-10 | 3-4 GB |
| 10-25 | 4-6 GB |
| 25-50 | 6-10 GB |
| 50+ | 10-16 GB |
Plugins like WorldGuard, EssentialsX, and LuckPerms are lightweight. Economy plugins, dynamic maps (Dynmap/BlueMap), and minigame frameworks (Citizens, MythicMobs) consume significantly more.
Light Modpacks (Create, Better MC, Cobblemon)
| Players | Recommended RAM |
|---|---|
| 1-5 | 4-6 GB |
| 5-15 | 6-8 GB |
| 15-25 | 8-12 GB |
Light modpacks add new blocks, items, and mechanics but don’t drastically alter world generation or add hundreds of entities.
Heavy Modpacks (ATM10, RLCraft, Vault Hunters)
| Players | Recommended RAM |
|---|---|
| 1-5 | 6-8 GB |
| 5-10 | 8-12 GB |
| 10-20 | 12-16 GB |
| 20+ | 16+ GB |
Heavy modpacks can have 200+ mods that each consume memory. ATM10, for example, benefits significantly from 10GB+ even with just a handful of players.
Common Mistakes
Mistake 1: Over-Provisioning
This is surprisingly common. Someone buys a 16GB plan for a vanilla server with 5 friends. The extra RAM sits completely unused while they pay for it monthly.
More RAM doesn’t make a server faster if it already has enough. Once Minecraft has sufficient memory for its loaded chunks, entities, and plugins, additional RAM provides zero benefit. In fact, too much RAM can cause longer garbage collection pauses if not configured properly.
The fix: Start with the recommended range for your server type and player count. Monitor actual RAM usage through your hosting panel. If you’re consistently using less than 60% of your allocation, you’re over-provisioned.
Mistake 2: Under-Provisioning
The flip side. Running a 200-mod pack on 4GB because “it should be enough.” Symptoms include:
- Frequent server crashes with “OutOfMemoryError”
- TPS dropping below 15 during normal gameplay
- Long server startup times (5+ minutes)
- Chunk loading delays, especially near unexplored areas
The fix: If your server regularly uses 85%+ of its RAM, or you’re seeing out-of-memory crashes, it’s time to upgrade.
Mistake 3: Ignoring CPU Requirements
Some players fixate entirely on RAM and ignore CPU. A server with 16GB of RAM but a shared, low-clock-speed CPU will lag with 20 players doing redstone work, even if RAM usage is fine.
CPU bottlenecks show up as low TPS (below 20) while RAM usage looks healthy. If you’re experiencing this, the solution isn’t more RAM — it’s a host with better CPUs.
Mistake 4: Not Accounting for Growth
A server that handles 10 players perfectly today might struggle at 25 next month if your community grows. Choose a host that makes upgrading easy — ideally without downtime or data migration.
Mistake 5: Choosing Based on Price Alone
The cheapest 8GB plan and a mid-priced 8GB plan are not the same thing. The cheap plan likely over-allocates, meaning your 8GB is shared with other customers. The mid-priced plan may offer dedicated resources. Always check whether resources are guaranteed.
Server Software Matters
Your choice of server software dramatically impacts resource requirements:
- Vanilla: The official Mojang server. Unoptimized. Avoid for anything beyond small friend groups.
- Paper: The standard for optimized servers. Significant performance improvements over vanilla with full plugin support. Start here.
- Purpur: Fork of Paper with additional configuration options and optimizations. Great for servers that want maximum control over performance tuning.
- Fabric + Lithium/Starlight: For modded servers. Fabric is the mod loader; Lithium and Starlight are optimization mods that significantly reduce resource usage.
- Forge/NeoForge: Required for many modpacks. Generally more resource-intensive than Fabric-based setups.
Switching from vanilla to Paper can sometimes feel like upgrading your hardware — it’s that significant. If you’re running vanilla and experiencing performance issues, switch to Paper before upgrading your plan.
How to Monitor What You Actually Need
Once your server is running, don’t just guess at resource usage. Actually measure it.
Check RAM Usage
In your hosting panel, look for real-time memory graphs. Java’s memory usage will fluctuate in a sawtooth pattern — this is normal. The “teeth” are garbage collection cycles. What matters is:
- Peak usage: The highest point before garbage collection runs
- Baseline usage: The lowest point after garbage collection
- Free headroom: You want at least 15-20% free at peak times
Check TPS
Run /tps in-game (requires operator permissions). Healthy is 20.0. Anything below 18 consistently means your server is struggling — likely a CPU issue.
For deeper analysis, install the Spark profiler plugin. It shows exactly what’s consuming your server’s resources, down to individual plugins and game mechanics.
Check Disk Usage
World files grow forever unless you set world borders. Check your storage usage monthly. If you’re approaching your disk limit, either prune unused chunks with a tool like MCASelector or upgrade your storage.
When to Upgrade
Clear signs you need more resources:
- RAM: Usage consistently above 85%, or out-of-memory crashes
- CPU: TPS regularly below 18 during normal gameplay
- Storage: Less than 20% disk space remaining
- Player experience: Players complaining about lag that isn’t network-related
When to Downgrade
Yes, this is valid advice. If your server has been running for months and consistently uses less than half its RAM, you’re paying for resources you don’t need. Downgrade and save the money.
Choosing a Plan on Witchly
On Witchly, our plans scale from lightweight to heavy-duty. Since we don’t over-allocate, the RAM you see in your plan is the RAM your server actually gets. You can monitor real-time resource usage on your dashboard and upgrade or downgrade as needed.
If you’re unsure where to start, sign up at Dashboard and deploy a free server instantly — no payment needed. Run your intended setup, load your plugins or modpack, invite your players, and check the resource graphs after a day of gameplay. That real-world data is worth more than any guide — including this one. When you outgrow the free tier, upgrade to Elite for dedicated hardware.
Quick Decision Framework
Still not sure? Answer these three questions:
- What am I running? Vanilla, plugins, light mods, or heavy modpack?
- How many concurrent players? Not total members — how many are online at the same time during peak hours?
- What’s my growth plan? Staying small or trying to grow?
Match your answers to the tables above, add a 20% buffer for comfort, and pick the closest plan. You can always adjust later.