Export and Share a Minecraft Bedrock Map (.mcworld)

To share a playable Bedrock map, export a .mcworld and test that file in a clean import. The work before export matters: players should arrive at the right location, receive the required packs and be able to finish the map without access to your development setup.

Choose the right deliverable

.mcworld: a world to import and play.
.mcstructure: a saved build or region, not a whole playable world.
.mctemplate: a world template with its own packaging requirements.
.mcproject: an Editor project backup, not the player-facing map download.

Renaming one of these extensions does not convert its contents. If the deliverable is a castle that other creators will place in their worlds, use the structure export guide. If it is an adventure with spawn points, rules and progression, prepare a world.

Prepare a separate release copy

Make a backup of the working world, then create a separate release copy. Keep your original unchanged so you can recover development tools and reproduce bugs. Give the copy a clear name such as Woodland Trial — release candidate 1; filenames alone are easy to confuse when several worlds are open.

Write down the intended first minute of play. Where does a new player spawn? Which direction should they face? What should they carry? Can they accidentally leave the starting area? Walk through this sequence with a second player rather than relying only on the author's saved position.

Remove test items, debug messages and temporary command blocks that are not part of the map.
Set the intended world spawn, player spawn behavior, game mode and difficulty.
Reset progression, scoreboards and temporary tags used during testing. Prefer a documented reset function over manually guessing which values changed.
Check chest contents, checkpoints, death recovery and the end condition.
Record any required experiments and the exact game version used for the release test.

Do not disable every experiment on an existing project just to make its settings look cleaner. If a required feature depends on one, explain that dependency and test a backup before changing it. A release checklist is useful only when it describes the actual map.

Check behavior and resource packs

List every active behavior and resource pack, its version and why the map needs it. Remove unrelated packs from the release copy only after confirming they are unnecessary. Make sure you have permission to redistribute any third-party files included with the world.

The critical test is a recipient environment that does not already have your development packs installed. If textures or scripts work only on your own machine, the export is not ready. When a pack cannot be bundled, provide its original download link and a precise installation order; do not claim the map is a single-file installation.

Export from a normal world or Minecraft Editor

Normal Bedrock world on a device with export support

Save and leave the world. Open its edit/settings screen and use Export World in the file-management area, then save the .mcworld outside your game folders. Microsoft documents this world-export step in its world-template workflow. Menu placement can vary between releases and devices; this desktop workflow is not a promise of console filesystem access.

Minecraft Editor project

Open the project and use File → Export → Shareable World. The 26.30 release notes distinguish this playable .mcworld from Project Backup and World Template. They also document the disabled Export World button on the Edit Project screen. Avoid following an older screenshot that points to that button.

Keep the exported candidate unchanged while testing. If you fix something, export a new candidate rather than overwriting the file a tester is currently reviewing.

Run a recipient acceptance test

Import the candidate into a separate test installation or have a tester import it on another device. Never remove your only copy to simulate a clean environment. Use this sequence:

Follow the same download and import instructions that players will receive.
Enter as a new player and check spawn, inventory, permissions and visible instructions.
Verify custom blocks, textures, sounds and one scripted mechanic.
Die and respawn, disconnect and reconnect, then save, close and reopen the world.
For multiplayer maps, test two players progressing at different speeds and one joining late.
Reach the ending and confirm a reset or replay works if the map promises one.

Record failures against the candidate filename. “It works in my world” is not equivalent to “this download works after import.”

Publish useful compatibility information

Give the download a versioned filename, for example woodland-trial-1.0.0.mcworld. Include tested Bedrock version, player count, supported devices actually tested, required packs or experiments, credits and a short changelog. Link the map installation guide for players who need import help.

A screenshot should show the actual release map, not an unrelated render. Keep the previous release available to diagnose reports. The Iced Fox Maps section is separate from Addons because a world download and a reusable add-on solve different player needs.

When the exported map fails

Import failure: check the file downloaded completely and has the expected extension. Missing content: compare the recipient's active packs with the release inventory. Wrong starting state: revisit player setup and progression reset. A map that works only after a second join: inspect initialization order and late-join behavior before publishing another candidate.

Sources and verification

References checked on October 29, 2026. Examples were checked against these references and validated structurally; in-game acceptance checks are included above for your target version.