NBT & data editing · Java & Bedrock · Beginner

How to Open and Edit Any Minecraft NBT or .dat File in Your Browser

Minecraft stores almost all of its world rules, player inventories, and entity details inside Named Binary Tag (NBT) files, which normally look like unreadable gibberish in a standard text editor. With the browser-based NBT Editor on world.9minecraft.net, you can decode, navigate, and modify any .dat or .nbt file directly on your device. Because the tool runs locally in your browser, your save files are processed instantly and never upload to an external server.

Open the NBT EditorOpen and edit any NBT file: level.dat, player data, structures, schematics, Bedrock files.

What you need

  • A Minecraft Java Edition or Bedrock Edition world save folder (or an individual .dat or .nbt file)
  • A modern web browser to run the world.9minecraft.net NBT Editor
  • A backup copy of your world folder or target file before making any changes

Step by step

  1. 1Back Up Your World and Locate the File

    Before touching any internal game data, create a duplicate copy of your entire world folder and store it somewhere safe. Next, locate the specific file you want to edit inside your world directory, such as level.dat for global world settings, a player file inside the playerdata folder, or raids.dat inside the data folder. Make sure Minecraft is completely closed, as the game locks files and overwrites outside changes while a world is actively running.

    Tip: On Java Edition, player files are named using your account's UUID (like 069a79f4-44e9-4726-a5be-fca90e38aaf5.dat).

  2. 2Load Your Data into the NBT Editor

    Open the NBT Editor on world.9minecraft.net. Click to open your world folder, a .zip archive, or select a standalone .dat or .nbt file from your computer. The tool automatically detects whether the file uses GZip compression or Bedrock's little-endian header format and decompresses it in your browser memory, presenting you with a clean, expandable tree view.

    Tip: If you load an entire world folder, you can switch between level.dat and playerdata files without having to re-browse your hard drive.

  3. 3Navigate Compound Tags and Lists

    Click the arrow or plus icon next to the root folder—usually named Data in Java Edition's level.dat—to expand its contents. NBT files are organized like nested folders: Compound tags (often shown with a package or curly-brace icon) group related settings together, while List tags hold ordered collections of identical items like Inventory or Pos (position coordinates). Use the search bar in the NBT Editor if you are looking for a specific key name like allowCommands, RainTime, or Health.

  4. 4Modify Tag Values Safely

    Click on the value of any tag you want to change and type your new entry. Pay close attention to the data type icon next to the tag name: a Byte tag only accepts whole numbers from -128 to 127 (commonly used as 0 for false and 1 for true), while an Int or Long accepts much larger whole numbers, and Float or Double tags require decimal numbers. When editing Byte Arrays or Int Arrays, avoid adding or removing elements unless you know the exact array length the game expects.

    Tip: To enable cheats in an existing Java world, find allowCommands inside the Data compound and change its Byte value from 0 to 1.

  5. 5Save and Replace the Original File

    Once you finish editing, click the Save or Download button in the NBT Editor to export your modified file. The tool automatically re-applies the proper GZip compression or Bedrock binary framing so the game can read it without errors. Move the downloaded file back into its original location inside your Minecraft world folder, choosing to overwrite the existing file when prompted by your operating system.

How it works

Named Binary Tag (NBT) is a hierarchical data format designed to store complex game information in a compact binary structure. Instead of plain text like JSON, every piece of data in an NBT file begins with a single byte identifying its strict data type—such as TAG_Byte (1), TAG_Int (3), TAG_String (8), TAG_List (9), or TAG_Compound (10)—followed by the name of the tag and its raw binary payload. This strict typing is why entering a decimal number into an integer tag or exceeding a byte's numerical limit will fail.

To save hard drive space, Minecraft wraps most Java Edition .dat and .nbt files (like level.dat and structure blueprints) in standard GZip compression. If you open them in a regular text editor, you only see scrambled compressed bytes. Meanwhile, Bedrock Edition stores its level.dat uncompressed, but prepends an 8-byte header containing the file version and payload byte length, and writes all numbers in little-endian byte order (least significant byte first, opposite of Java's big-endian order).

When you open a file in our browser-based NBT Editor, the tool reads the first few bytes (the magic numbers) to identify whether the file is GZip-compressed, raw big-endian, or Bedrock little-endian. It unpacks the binary stream locally in your browser's RAM, lets you edit the tree without breaking data type boundaries, and repackages the exact compression and header structure when you save.

Common mistakes

  • Editing a file while the world is currently open in Minecraft, which causes the game to overwrite your newly replaced file the moment you pause or quit.
  • Typing a number outside a tag's mathematical limit, such as putting 500 into a Byte tag (which maxes out at 127) or entering letters into a numeric Float tag.
  • Confusing tag names between editions, since Java Edition often uses capitalized PascalCase or camelCase depending on the version (like GameType or spawnX), whereas Bedrock Edition frequently differs (like GameType or SpawnX).
  • Renaming the downloaded file to something like level (1).dat instead of keeping the exact original filename, causing Minecraft to ignore your edited file.

FAQ

Why does my .dat file look like random symbols in a regular text editor?

Most Minecraft .dat files are binary files compressed with GZip. Standard text editors try to read compressed binary numbers as alphabetical characters, resulting in unreadable symbols.

Can I edit both Java Edition and Bedrock Edition files with this tool?

Yes. The NBT Editor on world.9minecraft.net automatically detects Java's GZip-compressed big-endian format as well as Bedrock's uncompressed little-endian level.dat format.

Are my world files uploaded to a server when I use the NBT Editor?

No. Everything happens locally inside your web browser using JavaScript. Your files never leave your computer, making it completely private and instant.

Where are singleplayer inventory items stored if I don't see my UUID file?

In Java Edition singleplayer, the host player's inventory and position are stored directly inside level.dat under the Data -> Player compound tag, which overrides the matching file in the playerdata folder.

By loading your Minecraft files into the browser-based NBT Editor on world.9minecraft.net, you can safely decompress, navigate, and tweak any compound tag or value locally without installing external software.

More nbt & data editing guides

NBT & data editingHow to Edit Chest Contents, Sign Text, and Command Blocks Inside Chunk NBTEvery placed container, sign, and command block in a Minecraft Java Edition world stores its detailed state inside the region files as a block entity. When you need to clear a lag-inducing chest, edit a sign without breaking it, or disable a soft-locking repeating command block, you can modify these properties directly in the chunk data. This guide explains how to locate and edit placed block entities using our browser-based NBT Editor.JavaAdvanced5 steps
NBT & data editingHow to Inspect and Modify Structure Block .nbt FilesMinecraft Structure Blocks save custom builds as standalone .nbt files, allowing you to transfer creations between worlds or use them in custom data packs. Instead of rebuilding a structure in-game just to swap out one building material or remove accidentally captured mobs, you can directly edit the saved structure data. Our browser-based NBT Editor lets you inspect and modify these files locally on your device without uploading anything to a server.JavaIntermediate5 steps
NBT & data editingHow to Edit Objectives, Teams, and Player Scores in scoreboard.datUninstalling complex datapacks often leaves your world cluttered with hundreds of obsolete scoreboard objectives and orphaned player scores. By manually editing the scoreboard.dat file offline, you can instantly clean up your world data, modify player statistics, or tweak team settings without typing tedious in-game commands. Because the NBT Editor runs entirely inside your browser, your world files are processed locally on your device and never upload to a server.JavaIntermediate6 steps
NBT & data editingHow to Edit Villager Trades, XP, and Gossip Data via Entity NBTCustomizing villager trades, experience levels, and player reputation directly in your Minecraft Java Edition world allows you to build tailored shops or fix broken trading halls without using in-game command blocks. Since Minecraft 1.17 separated entity storage from terrain chunks, villager data lives inside dedicated entity region files that can be modified with precision. Using the browser-based NBT Editor on world.9minecraft.net, you can inspect and rewrite a villager's Offers, Recipes, and Gossips tags locally on your machine without ever uploading your world files.JavaAdvanced6 steps
NBT & data editingMinecraft NBT Data Types Explained: Byte, Short, Int, Long, Compound, and ArraysModifying Minecraft world files requires a clear understanding of the Named Binary Tag (NBT) format, as entering a value outside a tag's strict mathematical boundaries will immediately break your save. This guide breaks down all thirteen binary data types across both Java and Bedrock Editions so you can edit values safely without causing data overflow or chunk resets. You will learn how to inspect and modify these exact tag types directly inside your browser using our local NBT Editor.Java & BedrockIntermediate5 steps