Best VPS for Minecraft in 2026 — Top 5 Tested & Ranked

What Actually Kills Your TPS (It's Not What Reddit Says)

Go to r/admincraft right now and search "TPS lag." Every other reply says "get more RAM." I believed this for two years and wasted money on servers with 8GB of memory that still stuttered.

Then I ran a test that changed how I think about Minecraft hosting. Same Paper 1.20.4 server, same config, same 20 bot players wandering randomly. One server: Contabo, 8GB RAM, CPU benchmark score of 3,200. Other server: Vultr, 2GB RAM, CPU benchmark score of 4,100.

Vultr held a flat 20 TPS for 30 minutes straight. Contabo dropped to 18 within 10 minutes and dipped to 16 when two bots flew off generating new chunks.

The server with a quarter of the RAM outperformed the one with four times the memory. Because Minecraft's game loop — tick processing, entity AI, redstone, chunk generation — runs on a single thread. When your server lags, it is because that one thread cannot keep up. More RAM does not make a single thread run faster. A faster CPU does.

This does not mean RAM is irrelevant. It means you need to know which problem you actually have:

• TPS drops during gameplay (chunk generation, redstone, lots of entities): CPU problem. You need faster single-thread performance. Look at CPU benchmark scores: 4,000+ keeps you at 20 TPS with 20 players. Below 3,500, expect drops during exploration or redstone activity. Core count does not help — a 1-core fast server beats a 4-core slow server every time for Minecraft.
• Server crashes with "Out of Memory" or refuses to start: RAM problem. Vanilla with 10 players needs 2GB of heap. Forge with 100+ mods loads every mod class into memory — ATM9 genuinely needs 6-8GB just to start. If Java cannot allocate the heap, nothing else matters.
• Players complain about "rubber-banding" but your TPS is 20: Network problem. PvP feels terrible above 50ms. Block placement desyncs above 80ms. The fix is not a better server — it is a closer datacenter. A VPS in Dallas puts every US player under 40ms. One in New York leaves west coast players at 60-70ms.
• Brief freezes every 30-60 seconds: Garbage collection. Java is pausing to clean up memory. This is almost always because -Xms and -Xmx are set to different values, forcing Java to resize the heap during gameplay. Set them equal and the freezes stop. Use Aikar's flags.
• Lag when players fly fast or teleport: Disk speed. The server is generating or loading chunks from storage and the disk cannot keep up. NVMe drives handle this dramatically better than standard SSD. If your world is large and players explore aggressively, disk I/O matters.

Managed Minecraft hosting (Apex, Shockbyte, BisectHosting) hides all of this behind a control panel. You pay 3-4x more per GB of RAM for the convenience. A VPS gives you root access, better hardware per dollar, and the ability to run a Discord bot, Dynmap, and a website on the same box. The tradeoff: you need to install Java and run a jar file from a terminal. If you can follow a 10-minute guide, VPS is the better deal. If SSH makes you nervous, Linode has phone support that will walk you through it.

#1. Vultr — My Players Thought We Were on a Dedicated Box

A friend joined the test server and asked me what dedicated hosting company I was using. I told him it was a $12/month VPS. He did not believe me until I showed him the Vultr dashboard.

What made the difference was not any single metric. It was everything being just good enough simultaneously. The CPU held 20 TPS through every stress test I threw at it — 20 players wandering, chunk generation during Elytra flight, a massive piston door plus a sorting system running at the same time. The network put my New York players at 12ms and my Dallas player at 22ms from the Atlanta datacenter. And the DDoS protection stopped two attacks that I only found out about from the access logs days later.

The 9 US datacenter locations are what pushed Vultr to first place over providers with technically better hardware. In Minecraft, a faster CPU helps TPS, but a closer server helps every player's experience. I pinged all 9 Vultr locations from 5 US cities. Every location had at least one Vultr datacenter within 30ms. A player in Atlanta connecting to Vultr Atlanta sees 8ms — PvP at that latency genuinely feels like a LAN game.

The $12/mo plan gives you 2GB RAM, which is enough for vanilla Paper with 15-20 players using Aikar's flags. For modded, you need the $24/mo 4GB plan, which is where Vultr's value proposition weakens compared to Contabo. If your community plays vanilla survival or light plugins, Vultr is the clear pick. If they want modpacks, keep reading.

#2. Contabo — The Only Way I Could Afford ATM9

All The Mods 9 has over 400 mods. It needs a minimum of 6GB heap just to start the server. On every other provider on this list, 8GB of RAM costs $24-36/month. On Contabo, it costs $6.99.

That price is not a typo and there is not a hidden catch in the billing. I paid $6.99 for 8GB RAM, 4 vCPU, and 200GB SSD. I allocated 6GB to the Java heap, loaded ATM9, invited 10 players, and ran it for two weeks. The server never crashed. Players explored, built industrial setups with Applied Energistics and Create mod, ran quarries — the modded Minecraft experience that people actually want to play.

The honest cost of that cheap price is CPU speed. Contabo's benchmark score is 3,200 — 22% below Vultr. On vanilla with 20 players, TPS dipped to 18 during heavy chunk generation. On ATM9 with 10 players, it sat at 17-18 TPS most of the time. For a modded survival server where people are building and exploring, 18 TPS is genuinely fine. You will not notice the difference. For competitive PvP or elaborate redstone engineering, the missing 2 TPS becomes visible.

The things Contabo doesn't give you

No DDoS protection. If someone decides to hit your server, you are exposed until you set up TCPShield or a similar proxy. There is a setup fee on monthly billing that gets waived on 12-month contracts. And the network latency is higher (2.1ms) than Vultr or Linode, which means players feel slightly more delay. For a private server with friends, none of this matters. For a public server listed on server directories, the DDoS risk is real — I have seen servers knocked offline within days of being listed on Minecraft server lists.

#3. Kamatera — Started With 5 Friends, Scaled to 25

This is the provider for Minecraft communities that are still figuring out what they need.

A group I play with started as 5 friends on vanilla Paper. We needed 2GB RAM and 1 vCPU. Six weeks later we had 15 regulars and added Dynmap. Then someone wanted to try a modpack. Then we added a Discord bot. By month three we needed 4 vCPU and 8GB RAM — a completely different server than what we started with.

On a fixed-plan provider, each of those changes means migrating to a new server. New IP address (break everyone's bookmarks), copy the world over (pray nothing corrupts), reconfigure everything. We went through this once on Vultr and lost 3 hours of playtime to migration issues. On Kamatera, I clicked a slider, confirmed the new config, the server rebooted in about a minute, and everyone reconnected. Same IP, same world, no migration. We went from a $9/month config to a $24/month config over three months without a single server move.

The CPU benchmark score is 4,250 — second highest on this list. When we were still on vanilla with 15 players, TPS held at a perfect 20 even during Elytra exploration. The $100 free trial covers a full month of testing, which is enough time to actually build a community and see if the server holds under real use with real players, not just bots.

What makes this harder than it needs to be

Kamatera's configuration screen has more options than a Minecraft modpack settings menu. CPU type, CPU count, RAM, disk size, disk type, network speed, datacenter — all independent sliders. If "pick a plan and click deploy" is your comfort zone, this is going to feel overwhelming. The 3 US datacenter locations (New York, Dallas, Santa Clara) are fewer than Vultr or Linode, so some players will have higher ping. And if your community is small and stable, you are paying a premium for scaling flexibility you may never use. Contabo gives you more RAM per dollar and Vultr gives you more datacenters.

#4. Linode — For When You've Never Touched a Linux Terminal

I watched my 16-year-old nephew try to set up a Minecraft server on a VPS. He got as far as connecting via SSH, typed apt install java, got an error, and texted me "it's broken." On any other $12/month VPS, that is where the story ends. On Linode, I told him to call their support number.

He was skeptical. "VPS companies have phone support?" They do if it is Linode. He called, a human answered within three minutes, and she walked him through installing OpenJDK 21, downloading the Paper jar, accepting the EULA, setting Aikar's flags, and starting the server. He was playing Minecraft with his friends 25 minutes after that call.

That experience is not something you can benchmark or put in a comparison table, but it is the reason Linode is on this list. The hardware is unremarkable — 2GB RAM, standard SSD, CPU score of 3,900 (good, not great). The 9 US datacenters match Vultr's geographic coverage. The Akamai DDoS protection works. None of it is best-in-class. But Linode is the only VPS provider where a complete beginner can get unstuck by calling someone, and for a lot of people setting up their first Linux server to play Minecraft with friends, that is what matters.

When to pick something else

Skip the $5 Nanode — 1GB cannot run a Minecraft server. The realistic entry point is the $12/mo 2GB plan, which handles vanilla Paper with 8-10 players before TPS starts feeling soft. At $12/mo for 2GB, you are paying the same as Vultr with a slower CPU and no NVMe. If you are comfortable with SSH and just need the best hardware, Vultr is objectively better at the same price. Linode's value is the safety net of real human support when things go wrong at midnight, and the knowledge that the Akamai backbone provides excellent network stability for public servers. If that safety net matters to you — if you are running a server for your kid's friend group and do not want to debug Java at 10 PM — Linode earns its place.

#5. Hostinger — The Elytra Test That Changed My Rankings

Hostinger was going to be fourth. The specs are good — 4GB RAM and the highest CPU score (4,400) at $6.49/month. But I ranked it below Linode because of only 2 US datacenter locations. Then I ran the Elytra stress test.

The test: one bot flying at maximum Elytra speed in a straight line for 5 minutes, forcing the server to generate hundreds of new chunks while 15 other players are logged in doing normal things. This is the single most punishing disk + CPU combination in Minecraft, and it is what actually happens when players explore new territory.

On Contabo (standard SSD): TPS dropped to 14. Visible stutter. Players in the base felt the lag even though they were nowhere near the explorer.

On Vultr (standard SSD, faster CPU): TPS dropped to 17. Noticeable but playable.

On Hostinger (NVMe, fastest CPU): TPS never dropped below 19. The NVMe storage was reading chunk data and writing new chunks fast enough that the CPU thread was never waiting on disk. Chunk generation is an I/O-bound operation disguised as a CPU-bound one — the CPU does the work, but it spends most of its time waiting for the disk to deliver the data it needs. NVMe eliminates that wait.

So why is Hostinger fifth instead of first? Two US datacenters. If your players are in New York and your server is in Hostinger's Virginia datacenter, great — 15ms. If your players are in Los Angeles, they are looking at 60ms to an east coast server. For a casual survival world, 60ms is fine. For PvP, it is not. Vultr puts a datacenter in LA, Chicago, Dallas, Atlanta, Miami, and four other cities. That geographic flexibility outweighs raw hardware for most Minecraft communities.

But if your players are all on the east coast, or if exploration and world generation are central to your gameplay, Hostinger's NVMe advantage is real and it costs $5.50 less than Vultr per month. For a small friend group where everyone is within 500 miles of each other, this is actually the best deal on the list.

The $50 I Spent So You Don't Have To

Three mistakes from testing that will save you money and frustration.

Mistake 1: I ran a public server on Contabo without DDoS protection. Listed it on a Minecraft server directory. Twelve hours later, it went offline. The DDoS lasted about 40 minutes. Nobody was attacking us specifically — bots scan server lists and hit everything they find. I set up TCPShield (free tier) and it never happened again. If you are running a public server on Contabo or Kamatera, set up a TCP proxy before you list the server anywhere. Do not learn this the way I did.

Mistake 2: I set -Xmx to 8G on an 8GB VPS. Left nothing for the OS. The server ran great for about an hour, then the OOM killer terminated the Minecraft process without warning. No crash log, no error — the server just vanished. I thought the VPS had rebooted until I checked dmesg and found the kernel had killed Java for consuming all available memory. The rule is simple: allocate 80% of VPS RAM to Java, leave the rest for Linux. On 8GB, set -Xmx to 6G.

Mistake 3: I used the default Paper config for a modded server. Paper's built-in entity optimizations conflict with some Forge mods that depend on vanilla entity tick behavior. A mob farm that worked perfectly in single-player broke completely on the server. Players spent two hours debugging before I realized Paper was throttling entity ticks in ways the mod did not expect. For modded servers, use Forge or Fabric — do not try to run mods on Paper. They are separate ecosystems for good reason.

Side-by-Side Numbers

TPS measured with Paper 1.20.4, Aikar's flags, view distance 10, simulation distance 8. "20-Player TPS" is minimum TPS over 30 minutes with bot players. "Elytra TPS" is minimum during 5-minute continuous chunk generation.

Vanilla Path vs Modded Path

The right VPS depends entirely on whether your community plays vanilla or modded. These are fundamentally different workloads with different bottlenecks.

Vanilla / Light Plugins (Paper + EssentialsX + WorldGuard)

CPU is king. You need 2GB RAM for up to 15 players, 4GB for 15-30. The server software (Paper) is already heavily optimized and barely touches more than 2GB of heap with standard plugin loads. Your priority is single-thread CPU speed and low network latency.

Recommended order: Vultr (best CPU + most DCs) → Hostinger (best CPU overall, if geographic coverage is not critical) → Kamatera (if you might scale later)

Modded (Forge/Fabric with 50+ Mods)

RAM is king. Forge with 100+ mods loads every class into the heap at startup. ATM9 idles at 5GB before any player joins. The CPU matters less because modded servers typically have fewer concurrent players (5-15 vs 20-30 on vanilla) and modded gameplay tends to be slower-paced (building, automation) rather than fast-paced (PvP, Elytra).

Recommended order: Contabo (8GB for $7 is unbeatable) → Kamatera (if you need to scale from light to heavy mods) → Hostinger ($8.99 for 8GB if you also want fast chunk generation)

Not Sure Yet

Start with Kamatera's free trial. Begin small (2 vCPU / 2GB), play for a few weeks, and watch the resource usage. If RAM stays under 70%, you are on vanilla territory — move to Vultr for the datacenter coverage. If RAM hits 90%, you are on modded territory — move to Contabo for the price-per-GB. Kamatera's $100 credit covers a month of testing, and the scaling flexibility means you can figure out what your community actually needs before committing.

How I Tested

Paper 1.20.4 on every server. Identical server.properties: view-distance 10, simulation-distance 8, max-players 20, online-mode true. Aikar's JVM flags with -Xms and -Xmx set equal. I allocated 80% of VPS RAM to the Java heap.

• TPS stability: 20 headless bot players (using a custom bot client), each wandering randomly for 30 minutes. spark profiler logging TPS at 1-second intervals. The number that matters is minimum TPS, not average. A server averaging 19.8 with dips to 12 feels worse than one averaging 19.5 that never goes below 18.
• Chunk generation stress: One bot flying in a straight line at max Elytra speed for 5 minutes, forcing continuous chunk generation alongside 15 other connected players. This is the hardest thing you can do to a Minecraft server, and it is exactly what happens when players explore.
• Player latency: Measured average and P99 ping from 5 US cities (New York, Chicago, Dallas, Los Angeles, Miami) over 10-minute sessions.
• Redstone torture test: A world with a massive piston door, a 64-furnace super smelter, and an item sorting system all running simultaneously with 20 players present. This tests sustained single-thread load, not burst capacity.
• Memory pressure: Gradually increased player count until the server OOM-killed or TPS dropped below 15. This determines the practical player limit for each plan.

The results confirmed the pattern: Vultr and Hostinger (high CPU scores) led on TPS metrics. Contabo (high RAM) lasted longest before OOM under player scaling tests. Kamatera was the only one where I could dynamically change resources mid-test. Linode landed in the middle on everything but won on the intangible of accessible support.

Frequently Asked Questions

How much RAM do I need for a Minecraft server?

Vanilla (1-5 players): 2GB. Vanilla (5-15 players): 3-4GB. Vanilla (15-30 players): 6-8GB. Modded, light pack: 4GB. Modded, heavy pack like ATM9: 8-12GB. These are Java heap numbers (-Xmx flag) — the OS needs another 500MB-1GB on top. On a 4GB VPS, set -Xmx to 3G. On 8GB, set it to 6G. Always set -Xms equal to -Xmx to prevent heap resizing lag.

VPS vs managed Minecraft hosting — which is better?

Managed hosting (Apex, Shockbyte, BisectHosting) gives you a web panel to install plugins without SSH. Easier, but 3-4x more expensive per GB of RAM and you lose control of Java version, JVM flags, and server software. A VPS costs less, gives you root access, and lets you run a Discord bot, Dynmap, and website alongside Minecraft. If you can follow a 10-minute tutorial to install Java and run a jar file, VPS is the better deal. If SSH makes you uncomfortable, Linode's phone support bridges the gap.

Can I run modded Minecraft (Forge/Fabric) on a VPS?

Yes. 4-8GB RAM runs most modpacks. Check the pack's recommended specs before buying. ATM9 with 400+ mods needs 8GB minimum just to start. You need Java 17+, enough storage for mod files and world data (50GB is usually plenty), and decent single-thread CPU. Contabo at $6.99 for 8GB is the best value for modded. Important: Paper/Spigot (for plugins) and Forge/Fabric (for mods) are separate ecosystems — you cannot use Bukkit plugins on a Forge server.

How do I protect my Minecraft server from DDoS attacks?

Step one: choose a VPS with built-in protection (Vultr, Linode, Hostinger). Step two: never share your real server IP — use a domain name. Step three: for public servers, put it behind TCPShield (free tier) or Cosmic Guard, which hide your IP and filter attacks. I learned this the hard way — a public server on Contabo got DDoSed within 12 hours of being listed on a server directory. Enable whitelist for private servers, and configure BungeeCord/Velocity IP forwarding properly for server networks.

What Java flags should I use for a Minecraft server?

Use Aikar's flags. For 4GB heap: java -Xms4G -Xmx4G -XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1MixedGCCountTarget=4 -jar server.jar nogui. The critical detail: -Xms and -Xmx must be equal. If they differ, Java resizes the heap during gameplay, causing the every-30-seconds stutter that drives players crazy.

Can I run Minecraft and other things on the same VPS?

Yes, and it is one of the main reasons to pick VPS over managed hosting. A 4GB VPS comfortably runs a Minecraft server (2-3G heap), Dynmap, a static website via Nginx, and a Discord bot simultaneously. Allocate 60-70% of RAM to Minecraft instead of 80%, leaving room for everything else. On Contabo's 8GB plan, I ran a 20-player MC server, Dynmap, a website, and a Discord bot at the same time without issues. Just make sure your start script uses screen or tmux so everything survives if your SSH session disconnects.

Paper vs Fabric vs Forge — which should I use?

Paper for vanilla + plugins (EssentialsX, WorldGuard, LuckPerms). Fastest server software with built-in optimizations that squeeze extra TPS. Fabric for lightweight mods (Sodium, Lithium, Iris) that enhance vanilla — fast startup, performance-friendly. Forge for heavy modpacks (ATM9, FTB, Tekkit) — the only option for most large packs, but hungrier on RAM and CPU. Start with Paper if unsure. Worlds transfer between Paper and vanilla, but not easily between Paper and Forge.