How to run a Minecraft server without paying for hosting

Paid Minecraft hosting starts at a few dollars a month and goes up fast once you want more than four players and a couple of plugins. For a small friend group, you probably do not need it. Here is how to do it on hardware you already have, and — more usefully — when that stops being a good idea.

Option 1: the machine you already own

The simplest setup is the official server jar on your desktop or an old laptop.

What you need

1. A current Java runtime. Recent Minecraft versions want Java 21 or newer; the server will refuse to start on an older one and the error message is unhelpful.
2. The server jar, or better, a Paper build. Paper is a drop-in replacement that is faster and fixes a long list of vanilla bugs.
3. Roughly 2 GB of RAM allocated for four or five players on a light world. Six or more, or any real plugin list, and you want 4 GB.

Create a folder, drop the jar in, run it once to generate the config, accept the EULA in the generated text file, then start it properly with a memory flag:

java -Xms2G -Xmx2G -jar paper.jar nogui

What it costs. Electricity, and the fact that the machine has to stay on. An old laptop idling as a server is a genuinely reasonable few dollars a year.

The catch. Your friends cannot reach it without either port forwarding or a tunnel, and that is where most people give up.

Option 2: skip port forwarding entirely

Opening port 25565 on your home router exposes your home IP to anyone who scans for it, and Minecraft servers get scanned constantly. If you do it, at minimum:

• Turn the whitelist on before the first friend connects, not after.
• Keep online-mode true so accounts are verified against Mojang.
• Do not run the server as an administrator account on your own machine.

The alternative most small groups now use is a tunnel: a service that gives you a public address and forwards traffic to your machine without opening a port. Latency is a little worse, the free tiers change addresses on restart, and it is dramatically safer than exposing your router.

If the only reason you are considering paid hosting is that port forwarding scared you, try a tunnel first. It solves exactly that problem for free.

Option 3: a spare single-board computer

A Raspberry Pi 5 with 8 GB of RAM will comfortably run a vanilla or light-Paper server for a handful of players. Put the world on an SSD rather than an SD card — world corruption on cheap SD cards is the single most common way people lose a save. Expect it to struggle past about eight players or once you add a heavy plugin set.

When to stop and pay for hosting

Self-hosting is right until one of these becomes true:

• You want the server up when you are asleep. Uptime is the thing hosting actually sells.
• You are past roughly ten concurrent players. Home upload bandwidth becomes the bottleneck before CPU does.
• You want it public. Public means a query port that gets hammered, occasional attacks, and a permanent moderation load.
• You care about backups more than you care about setting them up. Automated off-machine backups are worth the monthly fee on their own.

A realistic first week

1. Run Paper locally, whitelist on, four friends, vanilla settings.
2. Add nothing for a week. Find out what your group actually wants.
3. Add one plugin — usually land claims or grave keeping — and see whether anyone notices.
4. Set up an automated daily backup to a second drive. Test restoring it once.
5. Only then decide whether the thing you have built is worth moving to a host.

If it does go public, list it properly. A clear description, honest player numbers and a working Discord invite do more for a small server than any amount of paid promotion — the Minecraft server list is full of servers that got their first hundred players that way, and our Discord has an owners channel where people will look at your setup before you launch it.