Transfer a Bedrock World Between Phone, PC, Xbox and PlayStation: What Actually Works

Buying Minecraft again on a new device and moving a Bedrock world are separate jobs. Your account can restore access to the game while the world still lives only in the old device’s storage. The safest transfer route depends on the source device, the world’s storage location, and whether you can use a Realm as a private relay.

This guide uses current official Minecraft Help and Realms pages checked on August 25, 2026. MineBrush did not access a phone, console, PC, platform cloud, or Realm. The bundled fixture is an invented route matrix that keeps backup and readback gates explicit; it is not a world archive or transfer result.

Quick answer: copy first, verify second, delete never

Use this order:

1. confirm the source world still opens on the old device;
2. make a second copy or backup before changing storage or accounts;
3. choose one supported route: direct file copy, platform cloud/physical storage, or Realm upload/download;
4. import or download a copy on the target device;
5. open, save, exit, and reopen the target copy; and
6. keep the source untouched until the target passes.

A world appearing in the target list is progress, not proof. Check the spawn, player inventory, builds, packs, and one named piece of recent progress after a full reopen.

License transfer is not world transfer

The current Install or Transfer Minecraft to a New Device guide separates game installation/account access from moving world files. It says available routes depend on device and platform and can include cloud storage, physical storage, or Minecraft Realms.

Do not assume a Microsoft sign-in automatically downloads every local world. Account-linked purchases, Realms content, platform cloud saves, and worlds stored only on a device are different data lanes.

Before transfer, record the Microsoft account and platform account used on both devices without storing credentials in the article or support log. If the accounts differ, stop and resolve ownership before you move or overwrite anything.

Route one: Android External storage

The current Android Bedrock backup guide says worlds created while File Storage Location was set to External can be copied to a computer or another Android device. It provides the current external path under the Android app data tree and instructs users to copy the minecraftWorlds folder or an individual world folder.

That route is not a universal Android rule. The same official page directs players to the Realms transfer route when the world is in Application storage. Android versions, device vendors, file-manager permissions, and future storage policies can change direct visibility. Recheck the help page on the day you act.

When direct copy is available:

1. close Minecraft on the source device;
2. copy, do not move, the world folder;
3. preserve every file and subfolder;
4. store the first backup outside the game’s active directory;
5. copy a working duplicate into the supported target location; and
6. open the duplicate only after the file operation completes.

MineBrush does not claim the path is visible on your exact Android build or that USB/MTP permissions work. Those are device tests.

Route two: Realm as a cross-device relay

The current Minecraft Realms page says Bedrock Realms support cross-device play among Bedrock platforms and sync content through the Microsoft-account ecosystem. The current Change Your Realm Worlds guide documents downloading a Realm slot to the local worlds list and replacing a slot with a local world.

That creates a practical transfer model:

1. on the source device, upload or replace a Realm slot with the source world copy;
2. wait for completion and reopen the Realm;
3. on the target Bedrock device, sign in to the intended Microsoft account;
4. download the active or selected Realm world into the target’s local world list; and
5. verify the downloaded copy before touching the source.

Replacing a Realm slot can destroy the progress currently stored there. Minecraft’s official guide recommends downloading the slot first and warns that Realm backups are not kept forever. A transfer relay is not permission to skip the destination backup.

Route three: platform cloud or physical storage

Minecraft Help recognizes cloud and physical storage as platform-dependent transfer methods. The exact buttons, subscription requirements, save-data boundaries, and cross-generation rules belong to the platform holder and can change independently of Minecraft.

Use the console or device vendor’s current documentation for:

• which account owns the cloud save;
• whether an online-service subscription is required;
• whether the entire Bedrock save container or one world can be moved;
• source-to-target console generation rules;
• overwrite prompts; and
• rollback or version-history availability.

Do not use a phone-file path on a console or assume a platform cloud backup creates a portable .mcworld file. Those are different systems.

Phone, Windows, Xbox and PlayStation are not one filesystem

Bedrock can play across these devices, but storage access is not symmetrical. Android External storage can expose individual world folders under the official conditions. Windows can support file-oriented workflows when current documentation and permissions allow. Consoles usually route save data through their platform storage and account services, with Realms serving as the edition-level bridge for a playable world copy.

The safe statement is “choose the source-supported route,” not “copy this folder everywhere.” If a device-specific guide is missing or no longer current, hold instead of improvising in an application directory.

Keep Add-Ons and Marketplace content in a separate checklist

A world can transfer while a required resource pack, behavior pack, script, or Marketplace entitlement does not behave the same way on the target. Record which content is embedded, activated from the player’s library, downloaded from a Realm, or licensed to the source platform/account.

Do not redistribute third-party Add-On archives to “complete” a transfer. Use the creator’s official project or Marketplace entitlement. After the world opens, verify one behavior and one visual that actually matter to that world, then save and reopen.

Original MineBrush route fixture

The private fixture maps four invented source states:

• Android External storage can consider direct copy after a current path/permission check;
• Android Application storage routes to Realms or another current official method;
• console storage routes to platform documentation or Realms; and
• unknown device/storage state stays blocked.

Every route requires a source backup, exact account boundary, target copy, and save/reopen readback. The validator rejects delete-instead-of-copy, guessing an Android path, treating a license sign-in as world sync, replacing an unbacked Realm slot, cross-edition transfer, auto-success without readback, creator bytes, and a fake runtime pass.

This static matrix proves the decision logic only. It contains no storage path scraped from a device, no account identifier, no world data, and no screenshot.

Target readback checklist

1. Identity: world name, seed if known, last-played date, and expected spawn/build landmark.
2. Player state: inventory, position, permissions, and personal progress for the intended account.
3. World state: recent builds, containers, entities, scoreboard/quest state, and dimension access as applicable.
4. Content: required resource/behavior packs, scripts, Marketplace entitlements, and experiments.
5. Persistence: make a harmless change, save, exit, fully close, reopen, and confirm it remains.
6. Isolation: verify the source world and first backup still exist unchanged.

If the target copy opens with missing content, do not keep saving over it. Close, preserve logs/screenshots privately, and return to the source and backup. A partial load can become a destructive save.

Common transfer mistakes

• Moving instead of copying: removes the only working source before verification.
• Wrong account: restores the game but not the expected purchases, Realm, or player state.
• Wrong world folder: random directory names make display-name guessing unreliable.
• Application versus External confusion: applies the Android direct-copy path to an inaccessible storage mode.
• Unbacked Realm replacement: overwrites a slot that held progress.
• Edition mismatch: treats a Bedrock transfer route as a Java conversion.
• No reopen test: declares success before persistence is checked.

Evidence boundary

Official sources support separating game/account setup from world transfer, platform-dependent cloud/physical/Realms routes, Android External-storage copying, the Application-storage Realms boundary, Bedrock cross-device Realm access, Realm slot download, and the backup-before-replacement warning.

MineBrush has not accessed, copied, uploaded, downloaded, imported, opened, saved, or restored any world. Exact Android path visibility, Windows export, console cloud behavior, subscription, account ownership, world size, upload time, Add-On rights, Marketplace entitlement, multiplayer, performance, persistence, and screenshots remain action-time gates. Use Minecraft Guides for device-specific backup routes and Minecraft Maps for creator-source records.

The transfer is complete only when the target copy survives readback and the source is still safe.