How to transfer a Minecraft world to another device

Transfer a Minecraft world as a verified copy, not as a move that immediately removes the source. The safest route depends on the Edition and the access available on both devices. Java computers normally use a copied world folder. Bedrock devices may use Export World, a supported file workflow, or an official Realms transfer path. None of these methods converts a Java world into Bedrock or the reverse.

Confirm the Edition and destination first

Launch Minecraft on the destination device and identify whether it is Java or Bedrock Edition. A Java world must arrive in a Java installation; a Bedrock world must arrive through a Bedrock-compatible path. Signing into the same Microsoft account can restore access to a game licence or service, but it does not automatically copy every local world between devices.

Check that the destination has enough free space for the transfer file, the imported world, and a backup. Update only when necessary for compatibility, and do not let the first launch upgrade the only copy of an older world.

Back up and verify the source world

Close the world and let Minecraft finish saving. Create a complete backup before copying anything. For Java, the copied folder should directly contain level.dat and directories such as region. For Bedrock, use Export World where the platform offers it and preserve the resulting .mcworld, or use the current official transfer option for that device.

Open or inspect the backup before relying on it. A zero-byte archive, incomplete cloud upload, or folder missing its world data is not a transfer copy. Keep the original device and world unchanged until the destination version has been opened and checked.

Move a Java world between computers

On the source computer, find the world under the Java installation's saves directory and copy the complete world folder. Compressing that folder into a ZIP can make transfer through an external drive or trusted cloud storage easier. Do not send only the region directory; player data, dimensions, settings, and metadata live elsewhere too.

On the destination computer, install and launch the matching Java Edition once, then close it. Extract the transferred folder into its saves directory. Avoid double nesting such as saves/World/World/level.dat. Restart Java Edition and look for the copied world in Singleplayer under a distinct name.

Move a Bedrock world through a supported path

Where Bedrock offers Export World, export a copy and transfer the .mcworld file using a storage method both devices support. On the destination device, open the package with Minecraft and wait for the import to complete. Do not unzip a normal .mcworld import or rename a Java archive to imitate one.

Mobile and console storage rules vary. When ordinary file access is unavailable, Realms can be the official bridge: upload the verified source world from a supported device, confirm the Realm copy, then download it on the destination device where the current service permits. Back up the active Realm world before replacing a slot, and follow current Minecraft Help because menus and limits can change.

Verify the destination before retiring the source

Open the copied world locally. Check the world name, spawn position, known builds, player inventory where relevant, important containers, dimensions, and a few distant landmarks. A successful import message alone does not prove that you transferred the correct or newest copy.

Play briefly, save, close, and reopen it. Then create a fresh backup on the destination device. Only after this test should you archive the source copy or prepare the old device for reset, sale, or uninstall.

Treat cross-edition moves as a separate conversion problem

Copying a world does not convert its Edition. Java and Bedrock store blocks, entities, dimensions, packs, commands, and player data differently. Renaming .zip to .mcworld changes only the filename. Third-party converters can lose or alter data and need their own research, backups, and validation; MapMC does not claim that an ordinary transfer performs this conversion.

If the destination runs another Edition, keep the original world safe and decide whether a supported conversion workflow is acceptable before changing anything. For a new MapMC order, selecting the destination Edition at generation time is safer than trying to convert after delivery.

Use this transfer completion check

• Source and destination run the same Minecraft Edition.
• A complete, dated source backup exists outside the live world folder.
• The copied world imports or appears without overwriting another save.
• Spawn, builds, inventory, dimensions, and known landmarks were checked.
• The destination copy survives a save, close, and reopen cycle.
• A new destination backup exists before the source is removed.

Keeping both copies until the last check is complete turns a risky move into a reversible transfer.