First, tell them apart: Bedrock or Java?

The first step with “my Minecraft world won’t open” is always to tell which edition it is. .mcworld, .mctemplate, and .mcpack files are basically Bedrock; if unzipping reveals a level.dat paired with a region/ folder, or the save came from a PC, it’s most likely Java. The two aren’t interchangeable — trying to open a Java world in Bedrock will naturally “fail to open.” You don’t have to guess: import the file into mcworld.app and it diagnoses the type, version, and health report for free, right on your device.

Common causes and matching fixes

The vast majority of “won’t open” cases aren’t a truly corrupted file but one of these three:

  1. Structure problems — level.dat isn’t at the root of the archive, or there’s an extra folder layer wrapped around the world. For these, the free simple structure fix is enough and outputs a new file that imports normally.
  2. Packaging errors — the wrong compression method or file extension leaves the device unable to recognize the file. The diagnosis pinpoints where the problem is.
  3. Version mismatch — the save version doesn’t line up with the game version on your device; if it’s a Java world you want to play on a phone, you’ll need to convert it first — see Java → Bedrock conversion.

Only true data corruption needs the advanced fix (pay-per-result, refund on failure).

The bottom line: free diagnosis, original file untouched

mcworld.app’s diagnosis is free and runs on your device by default; any fix never overwrites your source file — every time it creates a new version while the original is preserved along with its hash, so it’s traceable and reversible. To understand the full workflow, read the in-depth tutorial Importing and repairing worlds. If the error happens during import, see What to do when a world won’t import; if you suspect the file is genuinely corrupted, see Diagnosing and handling a corrupted .mcworld.