How to Back Up a Minecraft Bedrock World

Bedrock worlds live inside app storage, sync differently per platform, and can disappear after risky experiments, corrupted add-ons, or a bad update. A portable .mcworld export is the most reliable handoff between devices and the simplest insurance before you enable behavior packs that rewrite loot or generation. This guide covers export from local saves, Realm copies, restore after reinstall, and habits that keep backups usable months later.

When to back up

• Before installing behavior packs, marketplace mash-ups, or experimental world settings.
• Before major Bedrock version updates on a long survival realm you host locally.
• After finishing a large build milestone you cannot easily recreate.
• Before letting friends join a world with command blocks or operator permissions.

Treat exports like photographs: one copy on the device alone is not a backup if the phone is lost or the console storage is wiped.

Export from the world list (local worlds)

1. From Play, locate the world in your list.
2. Open world management pencil icon, edit button, or long-press menu depending on platform.
3. Choose Export or Export World.
4. Pick a destination you control: cloud drive app, USB storage on supported devices, or share sheet to another device.
5. Confirm the resulting .mcworld file size looks reasonable for your build (tiny files may indicate a failed export).

Menu labels move between updates. If you do not see Export, search the edit screen’s submenus or check that you are the world owner with export rights some education or managed profiles restrict sharing.

Realms and subscription worlds

When the canonical save lives on a Realm, you still need periodic downloads so you are not solely dependent on subscription uptime. From Realm settings, use the download or backup options your client version exposes to pull a local copy, then export that copy to .mcworld if you want a second off-device archive.

• Schedule downloads before billing changes or long breaks from the game.
• Label files with date and game version in the filename you store externally.
• Remember Realm packs and player inventories may differ slightly from a pure local export document which backup is “source of truth.”

Restore and import after reinstall

1. Install Bedrock from your platform store and sign in with the same Microsoft account.
2. Transfer the .mcworld back to the device if it lived in cloud storage.
3. Open the file with Minecraft same pattern as importing packs: tap or double-click and wait for import success.
4. Find the world on the Play screen under a name derived from the file; rename inside world settings if needed.
5. Re-attach behavior and resource packs the world requires before loading survival progress.

If worlds vanished immediately after an update, avoid creating a conflicting new world with the same name until you search storage and cloud sync. Our troubleshooting tool collects common “missing world” patterns by platform.

Organizing backups that still work later

• Keep at least two generations: latest and previous stable before big mods.
• Store version strings in a text note beside the file older exports may not load on much newer Bedrock builds without migration messages.
• Do not rename the internal extension; Bedrock expects .mcworld for full world imports.
• Test-import into a creative scratch world quarterly so you know the archive is not corrupted.

What backups do not capture by themselves

A world export includes terrain, chests, and many entity states, but separate global resource packs, skin locker items, and Marketplace entitlement live outside the file. After restore, reinstall packs from your library and revisit activating resource packs. Player maps on third-party servers are never inside your local export server staff handle those saves.

Conclusion

Bedrock backup discipline is simple: export .mcworld files on a schedule, store them off-device, and pull Realm copies before subscription gaps. Pair exports with pack documentation and version notes so restores survive updates. One hour of backup work beats weeks of rebuilding a survival base start before your next add-on experiment.