Transferring and “syncing” are not the same thing
What many people call “multi-device sync” is, in most cases, really “I want to keep playing the same world on another device.” The most direct approach is to use mcworld.app to export the world as a .mcworld, then transfer it to another device via the system share sheet—save it to the Files app, use AirDrop, or simply send it to yourself. On the target device, Bedrock can import the .mcworld just by opening it; this path doesn’t depend on any account and works offline. The trade-off is that it’s manual: every time you want to carry your progress over, you have to export again.
Restoring across devices with cloud backup
If you want to skip the manual export each time, you can subscribe to World Pro and enable automatic cloud backup with version history. This way, the world is backed up to the cloud periodically, and when you switch devices or lose your local save, you can simply pick a point in time from the version history to restore on another device—turning “transferring a Minecraft save” into “retrieving any version at any time.” It’s worth emphasizing that this is closer to “cross-device restore” than real-time two-way sync—you decide which version to restore, and restoring by default creates a new copy rather than overwriting a world that already exists on that device. For details about backups themselves, see How to back up a Minecraft world.
Check the format first when crossing editions
Before transferring, always distinguish the edition: Java Edition and Bedrock are two different save formats. Bedrock can open and import a .mcworld, but a Java world can’t be used as a .mcworld directly. If you want to migrate from Java to a Bedrock phone, you first need to do a Java Edition to Bedrock conversion, which outputs an importable .mcworld, then send it over; the conversion is one-way, provides a compatibility score and an item-by-item change report, and does not promise 100% lossless results. Whichever path you take, mcworld.app follows the bottom line of never overwriting the source file—it creates a new version each time, keeps the original file and its hash traceable, and runs diagnostics on-device by default. To confirm where your world actually lives and what you’re transferring, see Where are Minecraft saves located. Diagnostics are free, you pay by results, refunds are issued on failure, and prices are as shown in the App.