First things first: garbled usually means just the “name”

When a world name turns into garbled text, a string of question marks, or little boxes, it looks alarming — but the real world data (chunks, blocks, entities) is usually fine. The problem is almost always with the encoding of the world name string:

  • levelname.txt — a plain-text file that holds the world’s display name. If it isn’t saved as UTF-8, or if its encoding got changed while being moved between different systems (Windows, Android, iOS), the name shows up garbled.
  • level.dat — the world’s metadata (NBT binary), which also stores a copy of the world name. If these two don’t match, or if either one has the wrong encoding, the name displays incorrectly.

So this is usually a minor issue, not a corrupted save. To understand what each of these files does, see What is the level.dat file and Where are Minecraft saves located.

Run a free diagnosis with TopoBlocks first, to see if it’s just the name

The safest approach is to run a free on-device diagnosis first, confirm the scope of the problem, and then decide how to fix it:

  1. Open and diagnose. Open the world file in TopoBlocks. The free diagnosis runs on your device by default, reading the actual name, version, and structure from levelname.txt / level.dat without uploading your save.
  2. Confirm whether it’s purely a name issue. If the report shows only the name is garbled and everything else is normal, it’s basically a levelname.txt encoding problem; if it also reports structural or chunk issues, that’s a different kind of problem — follow the guidance.
  3. Rename when it’s a name issue, repair when it’s a structure issue. For a pure display issue, the simplest fix is to re-save levelname.txt yourself (see the next section); if the diagnosis reports a broken archive structure / hierarchy (for example, level.dat not being at the root of the archive), you can run the free simple structure repair to produce a new .mcworld that imports correctly.

Any repair follows one product rule: never overwrite your source file — every run produces a new, traceable version, so if you are not happy with the result, the original is still there untouched.

Want to fix the name yourself? You can, and it’s often the fastest way

levelname.txt is plain text, so for a pure garbled-name issue you can absolutely fix it yourself: use a UTF-8-capable editor to re-type the world name and save it with UTF-8 encoding. level.dat also stores a copy of the name, but it is an NBT binary structure and easy to break by hand, so editing it directly is not recommended; usually you just correct levelname.txt, then rename the world once more in the in-game settings so the two places match.

We should also be honest about the limits: the steps above only solve problems with the name display/encoding and file packaging. If the world itself won’t open because of missing chunks, a damaged archive structure, or some deeper problem, that’s a different situation — simple structure repair can handle packaging/hierarchy issues, but more complex corruption may require advanced repair (¥9 per run, price shown in the app, with the problem and success probability displayed before payment, and an automatic refund on failure). For that kind of case, see What to do when a .mcworld file is corrupted.