The most direct offline archive: export to a single .mcworld

To keep an offline copy of your world, the safest approach is to export it as a standalone .mcworld file and store it locally or in the cloud. A .mcworld is just a ZIP archive with a renamed extension, containing a complete world save — a single file that’s easy to keep and ready to tap open and import back into the game anytime. To learn about the format first, see What is a .mcworld file.

With TopoBlocks you can export in one tap: select a Bedrock world → export as .mcworld → save it to the Files app, iCloud, or cloud storage. Exporting only copies and packages; it never touches the world you’re playing — that’s the product’s hard line: every export and snapshot is a fresh copy with a traceable hash and size, and restoring only creates a new copy instead of overwriting your current world.

.mcworld is Bedrock’s world format, so this export-archive path is aimed at Bedrock worlds. If you have a Java Edition world and want to turn it into a Bedrock .mcworld, you first need a format conversion (Java → Bedrock, a one-way paid step, priced in the app, with an automatic refund on failure) — that’s a separate process, covered in What carries over when converting a Java world to Bedrock.

Manual snapshot vs cloud backup: know the difference first

Beyond exporting files, TopoBlocks can also make a local manual snapshot: it records the world’s version at a given moment (including hash, size, and source), and later you can “restore as a new copy” to return to that state.

  • Local manual snapshot / export — free. It runs on your device, and you control where each copy is stored and when it’s made, which is great before updating the game, switching devices, or making big changes to a world.
  • Automatic cloud backup + version history — requires a World Pro subscription (¥22/month, 20GB). It automatically keeps multiple historical versions and syncs across devices, saving you manual steps. Whether it’s worth it depends on how often you change things, and exact retention limits are shown in the app.

In other words, if you just want a single offline copy, the free manual export is enough; if you want “a backup that’s always there without lifting a finger,” then consider subscribing. For a systematic look at backup strategy, see Backing up your Minecraft world.

When you should definitely export a copy

  • Before updating the game / a major version bump — version upgrades occasionally go wrong, so export the old version first and you can roll back anytime. See How to back up your world before updating the game.
  • Before switching phones / reinstalling the system — put the .mcworld in iCloud or cloud storage, and tap to import it back on the new device.
  • Before big edits or experiments on a world — keep a clean copy, and there’s nothing to panic about if things break.

Whatever the case, remember two things: exporting doesn’t touch the original file, and restoring only creates a new copy — you’ll never lose your current world because of a backup or restore. If you later want to upgrade to the automatic cloud option, learn more in World cloud backup; the manual path stays free and available anytime.