GuidesOnly show guides for your app
GuidesGuidesUpload a world from your PC, generate a fresh one, switch which world is active, and reset safely — plus the 3D map and datapacks.
Your world is the one part of a Minecraft server you can't just reinstall — it's the thing you actually care about. The Worlds page is where you bring worlds in, spin new ones up, and switch between them, all without touching a jar or hand-editing a config. Get comfortable here early, because the habits that keep a world safe (a backup before big changes, renaming instead of deleting) are much easier to build now than to learn the hard way.
| At a glance | |
|---|---|
| You need | A running Minecraft server |
| Time | Ten minutes |
| Before you start | Take a backup — on free, backups store to your own Google Drive |
Got a single-player world, or a build you made offline, that you want to host? Open the Worlds page and use the folder upload — your browser lets you select an entire world folder at once (the one containing level.dat, region/, and so on) and uploads the whole thing. This is how a world you built on your own computer becomes a server everyone can join.
💡 Tip: Upload the world folder itself, not a
.zipof it — the browser folder upload handles the directory directly, so there's nothing to unzip afterwards.
Starting new? The Worlds page can generate a world for you: give it a seed (or leave it random) and a world type (default, flat, and so on), and Falix creates it. Handy when there's a specific seed everyone's excited about, or when you want a flat creative canvas.
Every world has a 3D map powered by BlueMap — a rendered, explorable model you can pan and zoom right in the browser. It's a great way to see how far builds have spread, find your way around a big map, or show off spawn without loading the game.
A server folder can hold several worlds, but only one is the "main" world the server loads. That's decided by the level-name property — it's simply the name of the world folder to load. You'll find it on the Properties (Config) page. Point level-name at a different world folder, restart, and the server loads that world instead. That's the clean way to keep multiple worlds on one server and swap between them.
🎯 Good to know: Vanilla loads one world at a time. If you want several worlds live at once — a hub, a survival world and a creative world you can
/mvtpbetween — that's a job for a multi-world plugin like Multiverse-Core, installed from the Plugins page on a plugin-capable server. It's a plugin matter, not a panel setting, so its own docs cover the commands.
Want a completely fresh start on the same server? The reliable recipe:
world → world_old) so you can go back.Renaming instead of deleting means the old world is still there if you change your mind — and this is exactly the moment to have that backup from the top of the guide.
🎯 Good to know: Rename instead of deleting (e.g.
world→world_old) so the old world is still there if you change your mind.
Datapacks tweak world generation, recipes, loot, and functions without any mod or plugin — they're vanilla-friendly, and players don't install anything on their end. The Datapacks page installs them straight into the right place: your world's datapacks folder (<world>/datapacks). Because they live inside a specific world, a datapack applies to that world only — install to the one your level-name points at. After installing, restart or run /reload for the server to pick them up, and /datapack list in the console shows what's active.
Worlds grow. Every chunk a player visits is saved forever, so a well-travelled map can balloon on disk. The world map view has tools to trim unused regions and chunks for people who need to reclaim space — powerful, and easy to cut too much, so it gets an advanced-only mention here rather than a step-by-step. Back up first, always.
After uploading or generating, set level-name to that world (if it isn't already), restart, and join — you should spawn in the right place. The BlueMap view is a quick sanity check that the world loaded and looks like what you expected.
level-name probably doesn't match the folder name, or you uploaded a .zip instead of the folder. Check that level-name equals the world folder's exact name and that the folder contains level.dat.