To send your world to a friend, the most reliable approach is to first export it as a single .mcworld file, then share it via a cloud drive:

  1. Export the .mcworld. A Bedrock world normally lives as a loose save folder (level.dat, db/, and more), and sending the folder directly makes it easy to miss files or scramble the structure. Exporting to a single .mcworld packs everything with the correct structure into one file.
  2. Upload to iCloud or a cloud drive. Put the file into iCloud Drive, or any cloud drive such as Google Drive or Dropbox.
  3. Send the share link. In the cloud drive, choose “Create share link” for the file, and send the link (plus any access code) to your friend.
  4. Your friend downloads and imports. Your friend downloads the .mcworld to a device running Bedrock and opens it in the Files app to import. For this step, see What is a .mcworld file and how to open it.

With TopoBlocks you can handle the “export + share” part in one tap: select the world and export a shareable .mcworld directly, skipping the hassle of hunting down folders and packaging by hand.

Sharing doesn’t touch your own world

There’s a product red line worth stressing here: exporting/sharing never overwrites your original save. What you send out is the copy generated by the export, a separate file from the world you’re playing, and TopoBlocks generates a new, traceable version every time. So you can send the copy to your friend and keep playing your original world at the same time, with no impact on either.

If you care more about “keeping a safe copy” than about sharing, the steps are actually the same: export a .mcworld and store it. To learn more about exporting save backups, see How to back up your world before updating the game.

A few common situations to sort out first

  • Is your friend on Bedrock? Only Bedrock can import .mcworld; Java Edition can’t open it. If your friend plays Java, you’d first need Java Edition to Bedrock (playable on iPhone) — a one-way conversion, pay-per-use, automatic refund on failure, and Bedrock can’t be converted back to Java Edition.
  • Friend’s import fails? Usually the world isn’t broken; the file structure got messed up during download (for example, the system added an extra .ZIP suffix, or wrapped it in an extra folder). These simple structure problems can be diagnosed and fixed for free on-device, producing a new file that imports correctly without touching the original; for the deeper approach, see Import and repair worlds.
  • Right next to each other and don’t want to bother with a cloud drive? The same .mcworld can also be sent directly via AirDrop, with no upload or download.

For paid features (such as Java Edition to Bedrock conversion), prices are as shown in the app and failures are refunded automatically; export, on-device diagnosis, and simple structure repair are free by default.