You want to know how to make a Minecraft server your friends can actually join, one that doesn't chug every time a creeper detonates a chunk, and one that stays up when your laptop lid closes. There's a pile of outdated advice out there, so here's the clean 2026 version from someone who has spun up hundreds of these. Two real paths (hosted or self-host), why Paper wins almost every time, how much RAM to hand it, the settings that actually change how the server feels, locking it down with a whitelist, and getting people connected.
First decision: hosted or self-hosted?
Pick your path before you open a single config file. Self-hosting on your own PC is genuinely fine for learning, and for a throwaway weekend world with two or three friends. You download the server jar, run it, forward a port on your router. Costs nothing but electricity.
The problems arrive quickly. Your home upload speed is almost always the real bottleneck, not your CPU. The machine has to stay on around the clock or the world goes dark the moment you shut it down. Opening port 25565 to the internet points a hole straight at your home network, and there's zero DDoS protection when some 12-year-old you beat in a build contest decides to boot you offline. A rented box in a datacenter sidesteps all of it: always on, and the attack surface isn't your bedroom.
My honest take: for anything meant to outlive a weekend, rent a box. Our game server hosting gives you instant setup, one-click installs, full FTP access, and DDoS protection out of the gate, with nodes in Frankfurt, London, and Gravelines so ping stays low across Europe. UK and EU players usually land in single digits to low double digits. I'll still walk you through the self-host steps, because understanding how the pieces fit makes you better at running the thing whichever route you take.
Pick your server software (just use Paper)
Vanilla's own server jar runs, but it's slow and has no plugin support at all. Your realistic 2026 lineup is Vanilla, Paper, Purpur, Fabric, and Forge. Fabric and Forge are mod loaders; reach for those only if you're running a specific modpack. For a normal survival or SMP with plugins, Paper is the answer.
Paper is a performance fork of Vanilla that patches dozens of tick-eating bugs, adds heavy async work under the hood, and runs the entire Bukkit and Spigot plugin ecosystem. Purpur layers extra gameplay toggles on top of Paper if you want them later. Start with plain Paper. Grab the latest build for your exact Minecraft version from the PaperMC site, and match it to whatever version your friends are launching, or nobody connects. There's a fuller breakdown on our Minecraft Paper hosting page if you want the deeper reasoning.
How much RAM does it actually need?
RAM is where people either overspend wildly or starve the server. Rough numbers for Paper:
- 2 to 4 GB handles a near-vanilla survival world, up to about 5 players, light plugin list.
- 6 to 8 GB is the sweet spot for 10 to 20 players with a real plugin stack (EssentialsX, LuckPerms, a live map, a couple of quality-of-life plugins).
- 10 GB and up is for big communities, heavy Forge modpacks, or servers pushing large render distances.
Don't just dump 32 GB on it and walk away. Java's garbage collector actually behaves worse with an oversized heap unless you tune the flags, and you'll get periodic freezes when it finally sweeps everything at once. Use Aikar's flags (the well-known G1GC tuning set) in your startup command, and leave the JVM a little under your total memory so the OS keeps some headroom. We went deep on this in how much RAM a Minecraft server needs, which sizes it by player count and plugin load.
Step by step: get it running
Here's the ordered path. On a hosted panel, steps 2 through 4 collapse into a click or two, and I'll flag where.
- Install Java. Minecraft 1.20.5 and newer need Java 21. Grab a JDK 21 build; Temurin from Adoptium is the reliable one. On a VASTROX game server the correct Java is already installed.
- Get the Paper jar. Download the latest Paper build for your version. On our panel, pick Paper from the game installer dropdown and it pulls the right build for you.
- Do the first run. Start the jar once. It generates the files, stops, and asks you to accept the EULA. Open eula.txt and set eula=true. This one line trips up more beginners than everything else combined.
- Set your startup command. Something like java -Xms6G -Xmx6G, then Aikar's flags, then -jar paper.jar nogui. Hosted panels give you a memory slider instead, so you skip the flags entirely.
- Edit server.properties. This is where you set the stuff that matters (next section).
- Start it for real. Watch the console until you see "Done" and a startup time. If it hangs or throws an error, the console tells you exactly why. Read it. Don't guess.
The settings that actually matter
Most defaults are fine and you can leave them alone. A handful genuinely change how the server feels under load:
- view-distance: default is 10. Drop it to 8 for a smoother ride with more players. Every extra chunk of view distance is real CPU and RAM.
- simulation-distance: keep this at 6 or lower. It drives mob and redstone ticking and it's the bigger performance lever of the two, so tune it first.
- difficulty: normal or hard for actual survival. Set it to hard and nobody can accidentally leave the world stuck on peaceful.
- online-mode: keep it true so only legitimate accounts connect. Touch it only for a private offline setup, and even then, don't.
- max-players: set it to what your RAM honestly supports, not 100 on a 4 GB box.
Pre-generate the world with a plugin like Chunky before you open the doors. Generating chunks on the fly while players sprint into fresh terrain is the single most common source of stutter I see. Pre-gen a 5,000 block radius overnight and border exploration is smooth afterward.
Plugins: start small
The urge is to install thirty plugins on day one. Fight it. A lean, deliberate list beats a bloated one every single time, and every plugin you add is a potential lag source or a crash waiting for the next update. My default starter set:
- LuckPerms for permissions and ranks. It's the standard and nothing else is close.
- EssentialsX for homes, warps, /tpa, and a basic economy.
- Vault if you're bridging economy or permissions between plugins.
- CoreProtect for block logging and rollbacks. The first time someone TNTs your spawn, you'll be glad you can undo it in ten seconds instead of restoring a backup.
Add gameplay plugins after that, one at a time, restarting and checking the console between each. If ticks suddenly drag, you know precisely which plugin did it. And if things do get sluggish, our guide on how to fix Minecraft server lag walks through reading a timings report to find the real culprit instead of throwing more RAM at it.
Lock it down with a whitelist
Unless you're deliberately going public, turn the whitelist on. It's the whole difference between a calm friends' SMP and waking up to a griefed spawn.
- In server.properties set white-list=true, or run /whitelist on from the console.
- Add each friend by their exact username: /whitelist add PlayerName. Since the Microsoft account migration, spelling is strict; one typo and they can't get in.
- Run /whitelist reload to apply it.
- Make yourself operator with /op YourName so you can run commands in-game.
Keep op limited to people you'd hand your bank card to. An op can do anything, up to and including deleting the world.
Getting your friends connected
This is the step where self-hosting gets fiddly and hosted stays trivial. Rented a server? Hand friends the IP and port from your panel, they add it under Multiplayer, done. No router config, nothing to open.
Self-hosting means port forwarding. Log into your router, forward TCP port 25565 to your PC's local IP, then give friends your public IP (search "what is my IP"). If your ISP puts you behind CGNAT, which plenty do now, port forwarding simply won't work, and you're looking at a tunneling service or, more sensibly, a hosted box. Someone in the same house connects to your local IP; everyone else needs the public one.
That's the full loop: pick Paper, size the RAM to your player count, keep the plugin list tight, whitelist it, hand out the IP. If you'd rather skip the router dance and the always-on PC, spinning up a proper Paper server takes about two minutes and it's online whether your computer is or not. Either way, you now know how to make a Minecraft server that actually holds up. Go build something worth defending.