How to Install a Minecraft Map (Singleplayer and on a Server)

Download the map and find the world folder

Maps come as a zip. Before you worry about where it goes, get two things right: where you downloaded it from, and which folder inside the zip is actually the world.

Downloading safely

Stick to the established community sites — the big map repositories and mod platforms have moderation and report buttons, which is most of the protection you need. What matters more is what a download should look like:

• A map is a zip of ordinary game files. It should never arrive as an .exe, an installer, or anything that wants to run on your computer. A map cannot need that, so if it does, it is not a map.
• It should not require its own launcher. Adventure maps sometimes need a specific Minecraft version, or a resource pack, or a mod loader — that is normal. A custom launcher is not.
• Match the version. A map built for a newer Minecraft usually will not open in an older one, and going the other way converts the world permanently.

Which folder is the world?

This is the single most common thing people get wrong, so it is worth thirty seconds. Unzip the download and look inside. The world folder is the one that directly contains a file called level.dat.

Some maps unzip cleanly to exactly that folder. Others wrap it in another folder first — you open CoolAdventureMap and find another CoolAdventureMap inside it, and only then level.dat. In that case the inner one is the world; the outer one is just packaging. Copying the wrapper instead of the world is the reason a map does not show up, in singleplayer and on a server alike.

Install a Minecraft map in singleplayer

Singleplayer maps live in one folder called saves, next to the rest of your Minecraft data. Where that is depends on your system:

• Windows: %appdata%\.minecraft\saves — paste that into the address bar of any Explorer window and press Enter.
• macOS: ~/Library/Application Support/minecraft/saves — in Finder, use Go, then Go to Folder.
• Linux: ~/.minecraft/saves

Each folder in there is one world. Adding a map means adding one more.

1. Close Minecraft completely. Not just the world — the whole game. Minecraft reads the saves folder when it starts, so a map added while it is running will not appear.
2. Unzip the map somewhere convenient, like your desktop.
3. Copy the world folder into saves. The one that directly contains level.dat — if you see a folder inside a folder, use the inner one.
4. Start Minecraft and open Singleplayer. The map is in the list, ready to play.

That is the whole singleplayer process. If the map did not appear, it is almost always the wrapper folder — check that the folder you copied has level.dat sitting directly inside it, not one level down.

Upload a map to a Minecraft server

Putting a map on a server is the same idea with three extra things to get right: the server has to be stopped, the map has to travel as a zip, and the server has to be told which folder to load. Start with the map downloaded and unzipped on your computer, so you can see the folder that contains level.dat.

1. Stop the server. Fully stopped, not restarted. A running Minecraft server holds the world in memory and writes it back to disk when it shuts down, so anything you upload underneath it gets overwritten on the way out. This is the number one reason an upload seems to vanish.
2. Back up the world that is already there. In the panel's file manager, tick the current world folder and use Archive to zip it. If the new map is not what you hoped, the old world is one unzip away. Take a panel backup too if you want the belt and braces.
3. Zip the map folder on your computer. This is not optional: the browser uploader takes files, not folders, and dragging a folder in is simply refused. Zip the folder that contains level.dat so the zip has the world at its top level.
4. Upload the zip to the server's root folder — the same place as server.properties, alongside the existing world folder, not inside it. Drag and drop into the file manager works.
5. Unarchive it. Open the three-dot menu on the uploaded zip and choose Unarchive. A large map takes a few minutes and the page may tell you it is still working — let it finish and refresh rather than starting again. You should end up with the map's world folder sitting next to your old one.
6. Point the server at it. Open server.properties and set level-name to the name of the folder you just unpacked. Save.
7. Start the server and join. You are in the map.

If what you are actually doing is moving an entire existing server here from somewhere else — worlds, plugins and configs together — that is a slightly different job, covered in moving a server to a new host.

And if you have been playing a map alone and want to open it up, that is what a server is for: everyone plays in the same world whether or not you are online. HytHost Minecraft hosting gives you the file manager, SFTP and one-click backups used above, with plans from €2.59 a month.

Getting the map's Nether and End to load

Skip this section unless you are putting the map on a Paper or Spigot server. In singleplayer, and on a plain Vanilla server, every dimension travels inside the world folder and there is nothing to do.

The problem, when it happens, is unmistakable: the overworld is perfect, you walk through a portal, and the Nether is untouched wilderness. Nothing is broken and nothing is lost — the server simply looked for the Nether somewhere the map did not put it.

The check, before you start the server

Two folders decide this, and both are visible in the file manager.

• Look at your server. If you see folders ending in _nether and _the_end sitting next to your world folder, your server keeps each dimension in its own folder.
• Look at the map. If the map's world folder contains folders called DIM-1 and DIM1, it keeps its dimensions inside itself instead.

If both are true, they disagree, and that is the whole bug. Move the map's dimensions out to where the server expects them:

world/DIM-1   ->   world_nether/DIM-1
world/DIM1    ->   world_the_end/DIM1

Substitute your own world name if it is not world — a world folder called playworld pairs with playworld_nether and playworld_the_end. The server builds those names from level-name, so they always follow it.

If the map has no DIM-1 or DIM1 and instead has a folder called dimensions, it already keeps every dimension in one place and matches a server that does the same. Change nothing. Moving folders here would create ones the server never reads, which causes exactly the problem you are trying to avoid.

Worth thirty seconds of checking: once the server is up, go through a portal once and confirm the Nether is the map's, not a fresh one. It is much easier to fix before people build.

What is inside a world folder, and what is safe to touch

Open a world folder and it looks alarming. It is not — you never need to edit any of it to install a map. Knowing roughly what is what only helps when something goes wrong:

• The world itself — the chunk files, in a folder called region (or tucked under dimensions on newer versions). This is the terrain and everything built on it, and it is the part you actually care about.
• level.dat — the world's settings and its name. The file that marks a folder as a world.
• Your players — playerdata, holding one file per player: inventory, position, health. A downloaded map usually ships with none, which is why everyone starts fresh at spawn even though the world is fully built.
• Map extras — some maps ship a datapacks folder with custom recipes, functions or advancements. Leave it exactly where it is; it belongs to that world. Adding your own is covered in installing datapacks.
• Housekeeping you can ignore — session.lock and a few small files the server writes for itself. They get recreated automatically, so it does not matter whether the map's copies came along.

The practical takeaway: copy or zip the whole world folder, every time. Cherry-picking pieces out of it is how worlds end up half-loaded.

The map is not loading: what to check

Almost every failure here is one of six things, and none of them means your map is damaged.

Singleplayer

• The map is not in the world list. You copied the wrapper folder. Open it — if there is another folder inside and level.dat is in that one, move the inner folder into saves instead.
• Still not there after copying the right folder. Minecraft was open when you added it. Quit the game fully and start it again.

On a server

• The server started a brand-new empty world. level-name does not match a folder that exists, so the server made one. Check the spelling and capitals against the folder in the file manager. This is also what happens when you upload a map as world while level-name still points at something else — both folders sit there and the server loads the wrong one.
• The upload seemed to work but nothing changed. The server was running. Stop it, upload again, then start.
• The zip is there but the folder is not. The unarchive has not finished, or was interrupted. Give it a minute and refresh the file manager before retrying.
• The overworld is right but the Nether or End is brand new. The dimension folders are in the wrong place for your server — see getting the Nether and End to load.
• The world loads but everyone spawns with nothing. Expected. Player inventories live in playerdata, and a downloaded map ships without it — the builder's inventory was never part of the map. The world is fine.

One reassurance worth stating plainly: none of these damage the map. The world folder is just files, and as long as you kept the original zip you can always start again from a clean copy.