Supports Minecraft Bedrock Edition and Java Edition — and every server core for both, popular or obscure: Vanilla, Paper, Spigot, Purpur, Folia, Fabric, Forge, NeoForge, Mohist, Sponge, Bedrock Dedicated Server, PocketMine-MP, Nukkit, PowerNukkitX, Cloudburst, Dragonfly, Endstone, LeviLamina and the rest. Full list.
Need to look inside a Minecraft file rather than change it? Drop any .nbt, .dat, .mcstructure, .schem or raw NBT dump below to see its full tag tree with types and values, search it by name or value, and export the whole thing as SNBT text. Nothing is uploaded and nothing is written unless you click save.
Half the reason to open an NBT file is diagnosis: what version wrote this, why does this world refuse to load, what is actually inside the schematic somebody sent you. The viewer shows every tag with its exact type, so you can tell a TAG_Byte of 1 from a TAG_Int of 1 — a distinction that matters to Minecraft and that text dumps usually lose.
Type badges on every row — Byte, Short, Int, Long, Float, Double, Byte[], String, List, Compound, Int[], Long[].
Full 64-bit longs shown exactly, so seeds and UUID halves read correctly instead of being rounded.
Search across the whole tree by tag name or value, with a jump straight to the match.
Detected format shown in the file bar: edition, byte order, compression and Bedrock storage version.
SNBT export to get the whole document as text you can diff, paste into a command or hand to another tool.
NBT versus SNBT
SNBT is the text form of NBT — what /data get prints and what commands accept. It keeps type information as suffixes: 3b is a byte, 3s a short, 3L a long, 3.0f a float, 3.0d a double, [I;1,2,3] an int array. The export button produces exactly that, so a binary file becomes something you can paste into a command block or check into git and diff line by line.
JSON is not a substitute: it has one number type and no byte arrays, so converting NBT to JSON silently loses the distinctions Minecraft cares about. That is why this tool exports SNBT rather than JSON.
Files that open here
Anything whose payload is a single NBT document: Java and Bedrock level.dat, playerdata, servers.dat, hotbar.nbt, idcounts.dat, raids.dat, scoreboard.dat, map data, structure .nbt, .schem and .schematic, .mcstructure, .litematic, extracted chunk payloads and packet dumps. Containers such as .mca regions, .mcworld archives and LevelDB folders need one document extracted from them first.
Frequently Asked Questions
Can I view an NBT file without editing it?
Yes. The editor only writes a file when you click Save & Download, and it never touches the file you dropped in.
Can it convert NBT to JSON?
It exports SNBT, which preserves tag types. JSON would flatten bytes, shorts, ints, longs and floats into one number type and lose byte arrays, so it is the wrong target for round-tripping Minecraft data.
Why does my file show as a different edition than I expected?
The format is detected from the bytes, not the extension. A file reported as Java when you expected Bedrock is usually a file from the other edition, or a fragment that happens to parse — check the offsets reported if it warns about trailing bytes.
How big a file can it open?
Multi-megabyte documents are fine: arrays are kept in typed arrays and the tree renders lazily, so only the rows you expand exist in the page.