What exactly is NBT

NBT stands for Named Binary Tag, a binary data format that Minecraft designed itself. The core idea is that every piece of data carries three things—“name + data type + value”—nested together into a tree structure. Common types include integers, floats, strings, lists, and the “compound tag (Compound)” that can keep nesting more inside it.

A lot of key world data is stored as NBT:

  • level.dat — World metadata: name, game mode, seed, spawn point, game rules, version, and more. It is itself an NBT file (usually gzip-compressed).
  • Entities and block entities — Data like mobs, items inside chests, and sign text is also recorded as NBT.
  • Player data — Inventory, position, status, and so on are NBT too.

If you want to dig into what level.dat contains and what happens if it goes missing, see What is a world’s level.dat.

Why it looks like garbage in a text editor

Because NBT is binary rather than plain text—it packs type markers and values directly into bytes, and level.dat is often gzip-compressed on top of that, so opening it in a text editor only shows gibberish. To read its contents you need a dedicated NBT editor, or simply let the game read it.

This also explains a common misunderstanding: when a world “won’t open,” it’s usually not that the NBT content is broken, but that the packaging structure is wrong—for example, level.dat isn’t at the root of the archive, or there’s an extra wrapping folder. These structural problems have nothing to do with NBT itself; see What is a Java Edition region/.mca file to understand how Java Edition world files are organized.

How TopoBlocks treats this NBT

When you open or diagnose a .mcworld / .zip / Java Edition world, TopoBlocks reads NBT structures like level.dat to determine the file type, version, whether the structure is intact, and whether any files are missing. For where these save files normally live and what they look like, see Where are Minecraft world saves.

A few things to be clear about:

  • Free by default, on-device. Reading NBT for diagnosis is only to pinpoint the problem; it does not require uploading your world to the cloud. Features like cloud backup require your explicit consent.
  • Never overwrites the source file. Even when repairing, it generates a new file and preserves the original file and hash for traceability—it never modifies your original NBT in place.
  • Honest boundaries. Structural repair fixes file / packaging / structure problems; if the NBT data itself is severely corrupted, a simple repair may not save it, and complex damage goes through advanced repair (¥9 per run). Before you pay it shows you the problem, success probability, and risks; if it fails you’re refunded automatically, and prices are as shown in the app.

In short: NBT is the “internal language” Minecraft uses to store world data, and understanding it helps you see why some worlds won’t open—and which layer a repair is actually touching.