
NBT & data editing · Java · Intermediate
How to Inspect and Modify Structure Block .nbt Files
Minecraft 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.
What you need
- A Minecraft Java Edition world containing a saved structure, or a standalone structure .nbt file
- Access to our on-site NBT Editor
- A secure backup of your world folder or structure file before making any changes
Step by step
1Locate and Back Up Your Structure File
When you save a structure in-game using a Structure Block, Minecraft writes the data to your world directory under generated/<namespace>/structures/<name>.nbt (by default, the namespace is 'minecraft'). Before doing anything else, copy this .nbt file or your entire world folder to a safe location on your computer. Having a clean backup ensures you can instantly restore your build if a block state or tag is edited incorrectly.
Tip: If you named your structure 'my_house' without specifying a custom namespace, look for it at generated/minecraft/structures/my_house.nbt inside your world save folder.
2Load the File into the NBT Editor
Open the NBT Editor on our site and click to open your world folder, a world .zip, or the individual .nbt structure file directly. If you loaded the entire world folder, navigate through the directory tree to generated, open your namespace folder, and select your target file inside the structures folder. The tool will decompress and parse the structure data directly in your browser.
3Swap Block IDs Inside the Palette
Expand the root tag and locate the 'palette' list tag (or 'palettes' if your structure contains multiple randomized block variants). Inside 'palette', you will see a list of compound tags, each representing a unique block type used in your build via a 'Name' string tag (such as 'minecraft:cobblestone') and an optional 'Properties' compound tag. To swap a material across the entire structure at once, double-click the 'Name' value of the block you want to replace and type the new valid block ID, such as changing 'minecraft:oak_planks' to 'minecraft:spruce_planks'.
Tip: When replacing directional blocks like stairs or logs, ensure the new block supports the exact same values inside the 'Properties' tag (like 'facing' or 'axis'), otherwise the game may fail to place the block properly.
4Strip Unwanted Entities from the Build
If you accidentally saved wandering mobs, dropped items, or minecarts with your build, find the 'entities' list tag in the root of the structure file. Expand 'entities' to inspect each captured entity; each entry has an 'nbt' compound containing an 'id' string tag (like 'minecraft:villager' or 'minecraft:item') alongside 'pos' and 'blockPos' coordinates. You can delete individual entity compound entries to remove specific mobs, or empty the 'entities' list entirely so only blocks are pasted when you load the structure in-game.
Tip: Leave the 'entities' list tag itself intact as an empty list rather than deleting the main tag entirely, as Minecraft expects the list container to exist.
5Save and Replace the Structure File
Once you have finished editing the palette and entities, click the save or download button in the NBT Editor to export your modified .nbt file. Place the downloaded file back into your world's generated/<namespace>/structures/ folder, overwriting the original file. Load your world in Minecraft, set a Structure Block to Load mode with your structure's name, and trigger it to paste your newly modified build.
Tip: If your world was already open while you edited the file, run the /reload command in-game so Minecraft refreshes its cached structure files from the disk.
How it works
Structure .nbt files use a lookup system to keep file sizes small and efficient. Instead of writing full block names like 'minecraft:stone_bricks' for every single coordinate in a 3D grid, the game creates a 'palette' list. Each unique block and block-state combination in your build is listed once in the palette and assigned an index number based on its position in that list (0, 1, 2, and so on).
The actual 3D layout is stored inside the 'blocks' list tag. Each entry in 'blocks' contains a 'pos' list of three integers (X, Y, Z relative to the structure's corner) and a 'state' integer. This 'state' integer simply points to the matching index number in the 'palette' list. Because of this relational design, changing a single block ID inside the palette automatically updates every instance of that block throughout the entire structure.
Entities and block entities are stored separately from the standard block grid. Tile entities (like chests or signs) attach an 'nbt' compound directly to their respective entry inside the 'blocks' list. Free-moving entities (like mobs, armor stands, and item frames) are stored in the root-level 'entities' list with exact floating-point coordinates, allowing them to be edited or stripped out without disturbing the physical blocks.
Common mistakes
- Changing a block ID to one that does not support the existing 'Properties' compound tag (for example, changing 'minecraft:oak_stairs' to 'minecraft:stone' while leaving stair properties like 'half' and 'facing' attached, which causes the block to render as air or default states).
- Deleting an entry from the 'palette' list instead of modifying it; removing a palette entry shifts all subsequent index numbers down by one, scrambling every block in the 'blocks' list that points to those higher index numbers.
- Editing the 'size' list tag manually without adding or removing actual block entries, which can cause the structure bounding box to misalign or cut off parts of your build in-game.
- Forgetting to use the 'minecraft:' namespace prefix when typing a new block ID into the palette (for instance, typing 'glass' instead of 'minecraft:glass').
FAQ
Why do I see a 'palettes' tag instead of 'palette' in my structure file?
Some structures—especially vanilla ones like shipwrecks or ruins—use a 'palettes' list containing multiple sub-palettes. When the game generates the structure, it picks one palette at random to create visual variety (such as different wood types). If your file has 'palettes', make sure to apply your block ID changes across each sub-palette.
How can I completely remove a block type from my structure instead of swapping it?
Change that block's 'Name' tag in the palette to 'minecraft:air' (or 'minecraft:structure_void' if you do not want the empty space to overwrite existing terrain when pasted), and delete its 'Properties' compound tag if it has one.
Will removing entities also empty out the items inside my chests?
No. Chest contents are stored as block entities inside the 'blocks' list tag, not the root 'entities' list tag. Only entities that are not tied to the block grid—such as mobs, dropped items, armor stands, paintings, and item frames—are stored in the 'entities' list.
By editing the 'palette' and 'entities' tags inside a structure block's .nbt file using our browser-based NBT Editor, you can bulk-replace building materials and clean up unwanted mobs in seconds before pasting your build in-game.