Add an existing world to Bedrock Dedicated Server

Bedrock Dedicated Server can run an existing Bedrock world when its complete world folder is placed under the server's worlds/ directory and server.properties points level-name to that folder exactly. Do the change while the server is stopped, preserve both the current server and source world, and test privately before normal players join.

Confirm this is the official Bedrock server workflow

This guide covers the official Bedrock Dedicated Server package on supported Windows or Ubuntu systems. It does not describe Java server software, Realms, a third-party hosting control panel, or Java-to-Bedrock conversion. A MapMC Bedrock .mcworld must first be imported or unpacked into a valid Bedrock world folder for this server workflow; an ordinary Java ZIP is not compatible.

Check that server and client versions are compatible. Microsoft notes that protocol versions can change between releases, so an “Outdated Client” or “Outdated Server” message requires version alignment rather than a world-folder rename.

Start the server once, then stop it cleanly

Install the official server in its own folder and start it once so it creates the expected files and directories. Confirm that a client can join the default test world. Then use the server console's stop command and wait for shutdown to finish before touching world files.

The first run creates worlds/ along with top-level behavior_packs and resource_packs directories. Do not copy an existing world while the server is still writing to the active one.

Back up the server and prepare the world

Copy the whole server directory or at minimum the current active world and configuration files to a dated backup outside the installation. Separately preserve the original world export. Never use the only playable local world as the server's working folder.

Prepare one verified Bedrock world folder. It should be the actual folder containing the world's data, not a wrapper directory and not an unopened .mcworld sitting inside another folder. Open the source locally first and confirm spawn and known landmarks. If the world uses behavior or resource packs, record them and verify their compatibility before server launch.

Copy the folder into worlds/

Place the complete prepared world folder inside the server's worlds/ directory. Give the folder a simple, unique name without special characters, for example mapmc-london. Avoid reusing the active world's folder name unless you deliberately archived the original and can restore it.

The resulting structure should resemble BedrockServer/worlds/mapmc-london/ followed by the world data files. A doubled wrapper such as worlds/mapmc-london/mapmc-london/... can prevent the server from locating the intended data.

Set level-name to the exact folder name

Open server.properties in a plain-text editor while the server is stopped. Set:

level-name=mapmc-london

The value must match the folder name exactly, including letter case. Microsoft Learn states that multiple world folders may be installed, but only the world named by level-name is active at one time. Save the file without changing its format or adding extra quotation marks.

Start privately and inspect the result

Restart the server and watch its console output. Stop and restore the backup if the server creates a new blank world, reports damaged data, or cannot load required packs. A newly generated world usually means the configured name and available folder do not match as expected.

Join first with an administrator or allowlisted test account. Verify spawn, known buildings, boundaries, game mode, permissions, inventory behavior, and any required packs. Save, stop, and restart once more to confirm the server reopens the same world.

Separate world packs from shared server packs

Microsoft documents both world-level and top-level behavior_packs and resource_packs directories. Packs stored inside a world apply when that world runs; packs in the server's top-level folders can be available across worlds. Do not move packs blindly between these scopes. Preserve their manifest and dependency files, and test a copy after every version change.

MapMC's normal world delivery does not promise bundled Mods, Add-ons, behavior packs, or resource packs. Add them as a separate, backed-up change after the plain imported world works.

Complete the server handoff safely

• The official Bedrock Dedicated Server has run once and was stopped cleanly.
• A dated backup of the old server world and configuration exists.
• The prepared source is a verified Bedrock world folder.
• That folder sits directly under worlds/ with a simple unique name.
• level-name matches the folder name exactly.
• Logs, spawn, landmarks, permissions, packs, save, and restart were tested privately.

Only after those checks should you open the server to regular players or remove the former test world.