How to back up and restore Minecraft worlds

A useful Minecraft backup is a separate copy you can identify, open and restore after the working world is damaged or changed. It is not merely another shortcut to the same folder. Back up before changing game versions, installing mods or add-ons, replacing a Realm slot, moving devices, editing chunks, or making major changes to a MapMC world.

Preserve the untouched download first

For a MapMC world, keep the original Java ZIP or Bedrock .mcworld in a stable folder before importing it. Treat that file as the clean delivery copy. Import or extract a separate working copy and give it a clear name. If later experiments fail, you can start again without paying for or downloading the same result under pressure.

Do not edit an archive in the browser's temporary downloads area. Move it to a location that is included in your normal computer backup or external-drive routine. Record the download date, edition and world name so several similarly named files do not become impossible to distinguish.

Back up a Java Edition world

Close the world and ideally close Minecraft before copying its files. Java worlds normally live inside the installation's saves directory. The world folder you copy should directly contain level.dat and folders such as region. Copy the entire folder, not only the visible region files, and compress the copy if you need a portable archive.

Minecraft Java can also create managed backups through its world-edit flow, and the official help documentation explains how to open the backups folder. Use a name containing the world, date and game version. Store at least one copy outside .minecraft so reinstalling or cleaning the game directory does not remove both the working world and its backup.

Back up a Bedrock Edition world

Bedrock storage differs by platform. Where the game offers Export World, create a .mcworld export and move it to a controlled local or cloud folder. On mobile, confirm whether the world's storage follows the application or an external location before uninstalling the game. On consoles, normal filesystem access is limited; official cloud or Realms workflows may be the practical backup path.

Wait for Minecraft to finish saving and quit the world cleanly before copying or exporting. A file with the right extension but zero or implausibly small size is not a trustworthy backup. Keep the source world until the exported copy has been tested.

Verify a backup before relying on it

A backup is only useful if it can be restored. Check that the archive opens, the expected files exist, and the stored size is plausible. On a non-critical device or under a new world name, import or extract a test copy. Confirm the spawn area, recent builds, player data and important containers.

Do not overwrite the only working world during this test. Verification should produce an additional copy. If Minecraft asks to upgrade an older world, accept or create another backup first and perform the upgrade on the test copy.

Restore to a copy, then compare

For Java, extract the backup so the direct parent of level.dat sits inside the saves directory. Avoid double nesting such as saves/World/World/level.dat, which can make the world disappear from Singleplayer. For Bedrock, open a valid .mcworld package and let Minecraft import it as another local world.

Launch the matching edition and version, identify the restored copy, and compare known landmarks or recent edits. Only after the restored world works should you archive or remove a damaged working copy. Keep names distinct until you are certain which one is current.

Understand the Realms boundary

Realms maintains backups according to its current service rules, but those backups are not a replacement for every local copy. Before replacing a Realm slot, download or back up the active world. After uploading a MapMC world, join it locally and with a second permitted player to verify spawn, permissions and gameplay.

Realm retention, button names and upload limits can change. Follow current Minecraft Help rather than a fixed screenshot or old limit copied into a permanent checklist. Preserve a local export even when automatic Realm backups are available.

Use a simple three-copy habit

Keep the untouched MapMC download, one working world, and one dated backup stored separately. Add another backup before upgrades, mods, add-ons, commands, server migration or large manual builds. This is deliberately simple: a clean source, a playable copy and a restore point.

When something fails, stop editing, duplicate the damaged world for diagnosis, and restore a copy rather than repeatedly experimenting on the only save. Clear naming and one tested restore are more valuable than a folder full of unverified archives.