Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Games & Saves›.nbt
THE FILE FIELD GUIDE
.nbt

Minecraft tag data

Games & Saves

NBT stores typed hierarchical tags used in Minecraft-related data. Distinguish Java/Bedrock variants, compression and byte order. Inspect copies and preserve tag types and game-version requirements.

Main use
Handling hierarchical Minecraft tag data
Data type
Binary data / document
All sections, questions and sources

Content reviewed： · Editor：Kai

Example: a practical checking sequence

Example: check edition, game version and encoding conditions for a rejected structure NBT. Close the game, back up the world and inspect a copy with compatible tools. Preserve types and hierarchy; renaming to another structure suffix does not fix compatibility.

Opening steps

Choose your environment or purpose to see its steps.

Inspect with a compatible NBT tool

Check support for the specific variant.

  1. Close the game and back up the world or source dataset.
  2. Open a copy in a tool supporting the variant.
  3. Inspect names, types, lists and version information.
For structure data

The suffix alone does not determine placement or compatibility.

  1. Ask about edition, version and intended import workflow.
  2. Use supported structure/data workflows for that version.
  3. Test in a copy and inspect blocks, position and state.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Tool rejection: inspect compression, byte order and edition variant.
  • Unreadable as text: use a typed NBT tool.
  • Failure after editing: check types, hierarchy and required tags.
  • Version differences: check data version and content compatibility.
  • Renaming to MCSTRUCTURE does not convert structure or edition differences.

Use variant-aware NBT conversion

  1. Identify edition, variant and compression.
  2. Use a documented compatible converter on a copy when required.
  3. Inspect types and values and test in an isolated copy.

JSON conversion does not automatically preserve every NBT type or compatibility condition; retain source and world backups.

Preserve types, not just values

Byte, int and long are distinct types even for the same numerical value; preserve strings, lists and compound structure.

Source for these steps：Saicone NBT project · NBT library

Java versus Bedrock variants

NBT-related variants differ in byte order, compression and surrounding formats; a general support claim does not cover everything.

  • Close the world before copying.
  • Separate backups and working copies.
  • Verify target edition and purpose.

Source for these steps：NBTExplorer project · NBTExplorer / Saicone NBT project · NBT library

Related-format differences

Related-format differences
Format / purposeUse and preserved information
NBTTyped hierarchical data.
JSONText structure with different type representation.
MCWORLDWorld distribution package.

Handling and security

Never edit the sole world source directly; check distribution rights and avoid unknown bundled executables.

Questions and answers

Is NBT plain text?

It is typed binary data.

Are Java and Bedrock variants identical?

No; compression and byte order can differ.

Can I change type if the value is the same?

No; follow the required tag type.

Can renaming transfer structures between editions?

No; actual format and version compatibility are required.

What should I back up first?

Source data and the complete related world.

Format facts: name, steward and MIME type
Formal name
Named Binary Tag
Steward / specification
Mojang ecosystem / implementation-specific
MIME type
Check the producer or implementation; do not assume a single universal MIME value.

Primary and official sources

  • Project documentationNBTExplorer

    An editor for hierarchical NBT data

    NBTExplorer project · Link checked：
  • Project documentationNBT library

    Tag types, compression and byte order

    Saicone NBT project · Link checked：