Use Realms if you want the simplest supported setup. Use a managed server if you want plugins, mods, cross-play or backups without running hardware. Self-hosting is free and educational, but your computer, network and updates become part of the service.
You don’t need to become a sysadmin to have a private world. You just need to pick the trade-off you’re comfortable owning.
Choose one of four paths
| Option | Best for | Main drawback |
|---|---|---|
| Minecraft Realms | Small groups that want Mojang’s simplest setup | Limited control and customization |
| Self-hosting at home | Tinkerers who want full control and have the hardware | Security, uptime, port forwarding and maintenance are yours |
| Free host | Casual groups with no budget | Queues, manual starts, lower resources, or other limits |
| Managed paid host | Groups that want control without running hardware | Recurring cost, and provider quality varies |
Our dedicated Realms vs server hosting comparison covers the first decision. If you’re eyeing a spare PC, read self-hosted vs paid hosting before you expose a port.
Decide your edition and customization first
Ask every friend what they play on. Java Edition is the usual choice for plugins and modpacks. Bedrock covers phones, tablets, consoles and the Bedrock client on Windows. A Java server with Geyser can support many Bedrock clients, but there are limits — read the Java and Bedrock cross-play guide before promising that every mod or console will work.
Then decide: vanilla, plugin-based, or modded. Every modded player normally needs the same loader, Minecraft version and compatible client mods. Plugins run server-side and usually need nothing installed on the client.
Size for players online at once
Count the busiest session you realistically expect — not everyone in the group chat. Four people online together and 30 invited members are completely different workloads. For a normal small vanilla world, 2–4 GB is a common starting range. Modpacks and big groups need more, but adding RAM doesn’t fix every performance problem. Use the full Minecraft server RAM guide instead of guessing from a sales slider.
Use this launch checklist
- Choose Java, Bedrock, or a documented cross-play setup.
- Choose vanilla, plugins, or mods. Record the exact versions.
- Create or upload the world. Keep an untouched local copy before importing.
- Enable a whitelist or allowlist. Add only people you recognize.
- Set difficulty, game mode, spawn protection and permissions. Don’t hand out operator casually.
- Confirm backups and test one restore. A backup you’ve never restored is only a hope.
- Share the server address privately. Don’t post a home IP or private-world address publicly.
- Join once from another connection if you can. It catches firewall, port, DNS and edition mistakes.
- Agree on rules: who may invite, who may use commands, who can restore a backup.
For a more defensive setup, continue with the private server security guide.
What a managed host should make clear
Look for a permanent address, world export, backup retention, supported server software, accessible logs, transparent CPU/resource info, and a clear cancellation policy. “Unlimited” is useless when fair-use limits are hidden.
Also separate uptime from play availability. A scale-to-zero world can keep a permanent address while its compute sleeps; startup may be automatic, but a free shared-capacity tier can still queue. A conventional rented server may run 24/7 but cost more while empty. Neither is wrong — they’re just different bills.
Bottom line: use Realms for the simplest supported experience, a managed host for customization without home infrastructure, or self-hosting when learning and control justify the work. Whatever you choose: whitelist the world, keep an export, test a restore, and make version compatibility explicit before game night.