World won't open? Import and repair guide

← All guides

The most common reason a world "won't import" usually isn't a corrupted file at all, but a wrong folder structure—the world is wrapped in an extra layer of folders, and Minecraft can't find level.dat at the root of the archive. Problems like this can often be fixed for free in seconds.
Diagnosis is free and runs entirely on your device.Opening a file uploads nothing; an upload only happens, with your explicit consent, when a task genuinely needs cloud processing.

Step-by-step process

  1. Open the file and run a local diagnosis.Pick a .mcworld, .zip, or Java world from Files. The app copies it into its sandbox and scans it on your device, giving you a free report on file type, version, and health—no upload required.
  2. See exactly what's wrong.The diagnosis pinpoints the specific issue, such as a missing level.dat at the archive root, an extra wrapping folder, or an incomplete structure.
  3. Try the free simple fix.If the problem is the folder structure (the most common cause of import failures), the simple fix is free and produces a new .mcworld.
  4. Use advanced repair only when you need it.Complex corruption is handled by advanced repair on a per-job basis. Before you pay, you'll see the problem, the success probability, the expected output, the risks, and the refund policy; pricing is whatever's shown in the app.
  5. Verify the result.After a repair, the app checks that the structure is readable and that no files are missing, then gives you a human-readable report. Your original file stays unchanged, hash and all.

Free fix vs. advanced repair

The free simple fix handles structure and repackaging problems (a missing root file, an extra outer folder, an incorrect ZIP layout). Advanced repair is paid per job and tackles deeper corruption, such as region- or chunk-level structural problems; before you pay you'll see the success probability and a risk assessment, with pricing as shown in the app.

Your original file is always safe

A repair always produces a new file. The original stays unchanged along with its hash, so the result is always traceable back to the file you started with. “Never overwrite by mistake” is a release red line. If it's a Java world and you want to play it on iPhone, see Java to Bedrock.

Related: Import FAQ · What to do when a world fails to import

Get it all done in one place at mcworld.app

Create, repair, convert, protect, and deploy your worlds—free diagnosis, and we never overwrite your originals.

Get the App
Get the app