NBT editor for Minecraft Java and Bedrock files. Open level.dat, player data and .nbt structures, edit tags in a tree or as SNBT, then save. No upload.
Also known as: nbt editor · nbt editor online · minecraft nbt editor · nbt viewer · level.dat editor · minecraft dat file editor · snbt converter · nbt to json · bedrock nbt editor · edit minecraft player data
NBT editor for Minecraft Java and Bedrock files. Open level.dat, player data and .nbt structures, edit tags in a tree or as SNBT, then save. No upload.
Is NBT Editor free to use?
Yes. NBT Editor is completely free with no usage limits, and there is no paid tier required to use it.
Do I need an account to use NBT Editor?
No. NBT Editor works immediately in your browser with no signup, login, or email address required.
View and explore JSON data in an interactive collapsible tree structure. Search, filter, and navigate nested objects and arrays. Free online JSON viewer with no signup required.
CSV viewer online: open a CSV from a URL, upload a file, or paste data, then search, sort, and filter it in a clean table. Shareable ?url= links, custom delimiters, large files.
Share code snippets, logs, and text with a shareable link. Syntax highlighting for 30+ languages, expiration controls, and password protection for Pro users.
Drag and drop level.dat, a player .dat, .nbt, .schem or .mca file
or click to browse. The file is read in your browser and never uploaded.
NBT Tree Output
Open a Minecraft NBT file to browse and edit its tags here as a tree.
About NBT Editor
An NBT editor is used to read and change the binary data files Minecraft keeps for worlds, players and structures. This one opens Java Edition and Bedrock Edition files in your browser, shows every tag in a tree you can edit, renames, adds and deletes tags, converts the data to SNBT or JSON, and saves a file in the same format Minecraft wrote, without uploading anything.
Key Features
Detects gzip, zlib or uncompressed files and Java (big-endian) or Bedrock (little-endian) byte order on its own
Reads Bedrock level.dat with its 8-byte header and writes the header back with the new length
Edits values inline with type checks, so a Byte stays in -128 to 127 and a Long keeps all 64 bits
Keeps floats and doubles bit for bit, including negative zero and NaN payloads, when you save
Edits the whole file as SNBT text using the Java syntax: 1b, 2s, 3L, 4.5f, [I; 1, 2] and quoted keys
Browses Anvil .mca region files on a 32 by 32 chunk map and exports any chunk as .nbt, SNBT or JSON
Use Cases
Fix a broken level.dat after a mod removal, for example turning off a corrupted game rule or resetting the spawn point
Edit a player's position, health or inventory in playerdata/<uuid>.dat when a server admin in Texas needs to rescue a stuck player
Convert a structure block .nbt or a Sponge .schem file to SNBT to review it in a pull request for a datapack
Check DataVersion and Version tags before upgrading a Realm or a Paper server to a newer Minecraft release
Inspect a chunk from a region file to debug why entities or block entities disappeared
Export NBT to JSON to feed a script that audits items across many player files
Supported Formats
.dat
.dat_old
.nbt
.schem
.litematic
.mcstructure
.mca (read-only)
SNBT
JSON export
Related Keywords
nbt editor
nbt editor online
minecraft nbt editor
nbt viewer
level.dat editor
minecraft dat file editor
snbt converter
nbt to json
bedrock nbt editor
edit minecraft player data
What is the difference between Java and Bedrock NBT files?
Both editions use the same 13 tag types, from TAG_Byte to TAG_Long_Array, but they lay the bytes out differently. Java Edition writes numbers big-endian, stores strings in Java's modified UTF-8, and usually gzips files such as level.dat and player data. Bedrock Edition writes numbers little-endian, stores strings as plain UTF-8, leaves level.dat uncompressed, and puts an 8-byte header in front of it: a storage version and the length of the NBT that follows. A tool that assumes one layout reads the other as garbage. This editor tries both byte orders and keeps the one that parses the whole file, then saves with the same order, compression and header, so a file you open and save without edits comes back with identical NBT bytes. Region files (.mca) pack up to 1,024 chunks, each compressed on its own, behind a 4 KiB location table; chunks here are read-only because rewriting a region also means repacking its sectors.
Is my world file uploaded anywhere?
No. The file is read with the browser File API, decompressed with the built-in Compression Streams API and parsed in your tab. Saving builds the new file in memory and downloads it. Nothing is sent to a server. Keep a backup of your world before replacing level.dat, as you would with any editor.