Tags are the backbone of Minecraft's data-driven systems. They group blocks, items, entities, biomes, and other game objects into named sets that the game engine, commands, and datapacks all reference. This browser lets you explore every tag and its full contents, or reverse-lookup which tags contain a specific entry.
If you have ever wondered why a 
wooden sword works as furnace fuel, or why certain blocks break faster with an 
axe, the answer is tags. The #minecraft:planks tag tells the game which blocks count as planks for crafting. The #minecraft:mineable/axe tag determines what an axe can break quickly. Tags run through the game logic everywhere.
For datapack creators and command builders, tags are indispensable. Instead of listing 20 different log types in a command, you write #minecraft:logs and the game handles the rest. This tool shows you exactly what is inside each tag so you can use them with confidence.
1. Browse by category. Select a tag category (blocks, items, entity types, biomes, and more) to see every tag in that group.
2. Search tags by name. Type part of a tag name to filter the list. Searching "logs" shows #minecraft:logs, #minecraft:acacia_logs, and related tags.
3. Reverse lookup. Turn on Reverse Lookup, then enter a block, item, or entity to find every tag that contains it. This is useful when writing predicates or advancement conditions.
4. Expand tag contents. Click any tag to see its full list of entries, including nested tag references (tags that include other tags).
Minecraft organizes tags into categories based on what they group. Here is what the main categories are used for:
| Category | Common Uses |
|---|---|
| Blocks | Tool effectiveness, redstone behavior, mob spawning rules |
| Items | Recipe ingredients, fuel sources, enchantment applicability |
| Villager Trades | Trade pool definitions and item eligibility |
| Biomes | Structure placement, mob spawning, climate grouping |
| Entity Types | Mob categories, damage immunity, targeting rules |
| Damage Types | Protection enchantment grouping, death message types |
| Enchantments | Exclusive sets, treasure enchantments, slot grouping |
| Structures | Structure grouping for /locate and exploration maps |
| Banner Patterns | Pattern availability by crafting method |
| Fluids | Water and lava grouping including flowing variants |
| Game Events | Sculk sensor detection, vibration grouping |
| Instruments | Goat horn sound grouping |
| POI Types | Villager job site detection |
Block and item tags make up the bulk of the system. They control everything from what a pickaxe can mine efficiently to what ingredients a recipe accepts. The category tabs in the browser show the live tag count for each group.
Use tags in recipes instead of specific items. When defining custom recipes, reference a tag like #minecraft:planks instead of individual plank IDs. Your recipe then works with all current and future plank types, including any added by other datapacks.
Nested tags. Tags can reference other tags with the # prefix. For example, #minecraft:logs includes #minecraft:oak_logs and #minecraft:spruce_logs. The browser shows these nested references so you can trace the full structure.
Appending vs replacing. When creating custom tags, set "replace": false to add entries to an existing vanilla tag without removing its current contents. Setting it to true wipes the vanilla entries and uses only yours.
Tags are named groups of game objects (blocks, items, entities, biomes, and more) that share a common property. For example, the #minecraft:logs tag contains all log blocks like oak_log and spruce_log. The game uses tags for mechanics like tool effectiveness, fuel acceptance, and recipe ingredients, and datapack creators use them for conditions and commands.
Reference a tag with the # prefix. For example, /clear @s #minecraft:logs removes all log-type blocks from your inventory. Tags work in selectors, /give, /clear, loot tables, advancements, and predicate conditions.
Yes. Place a JSON file in your datapack at data/namespace/tags/blocks/ (or items/, entity_types/, and so on). Custom tags can reference vanilla entries, other tags using the # prefix, or your own content. Set "replace": false to append to a vanilla tag without wiping its current contents.
Reverse lookup lets you enter any block, item, or entity ID and instantly see every tag that contains it. For example, searching oak_log shows that it belongs to #minecraft:logs, #minecraft:oak_logs, #minecraft:mineable/axe, and more. This is useful when writing predicates or advancement conditions.
A tag can reference other tags using the # prefix. For example, #minecraft:logs includes #minecraft:oak_logs, #minecraft:spruce_logs, and so on. The browser shows these nested references so you can see how a tag is built up from smaller tags.
Browse more Minecraft tools:
