Vanilla Item Groups

In modern Bedrock item definitions (format version 1.20.20 and later), creative inventory placement is controlled by the menu_category object inside the description block. This replaced the older, scattered creative_category properties that used to live either in description or inside components.

The menu_category object takes three optional fields: category, group, and is_hidden_in_commands. While category decides which of the four main tabs holds your item (construction, nature, equipment, or items), the group field tucks your item inside one of the collapsible vanilla stacks on that tab. If you leave group out, the item sits loose at the end of the tab.

{
  "format_version": "1.20.50",
  "minecraft:item": {
    "description": {
      "identifier": "example:ruby_sword",
      "menu_category": {
        "category": "equipment",
        "group": "itemGroup.name.sword",
        "is_hidden_in_commands": false
      }
    },
    "components": {
      "minecraft:max_stack_size": 1,
      "minecraft:icon": {
        "texture": "ruby_sword"
      }
    }
  }
}

Every vanilla item group belongs to a specific creative tab in the default UI layout. However, Bedrock does not strictly lock a group to one category in your JSON. What matters is that both the category and group values are valid strings recognized by the parser.

For the most natural player experience, you should always pair an item group with the tab where vanilla puts that group. For instance, putting a custom sword into itemGroup.name.sword while setting its category to construction will behave oddly or place the group in an unexpected tab. Keep equipment groups in equipment, plant and ore groups in nature, building block groups in construction, and materials in items.

The equipment tab is the most common place add-on creators use groups, because custom tools, armor, and food look messy when dumped loose at the bottom of the inventory. All group identifiers use the localization key format starting with itemGroup.name followed by the group name.

Below are the reliable vanilla group identifiers commonly used on the equipment and items tabs. Note the capitalization—these strings are case-sensitive and use camelCase for multi-word names.

While block items usually get their menu_category inside the block's behavior file, you also use these groups on standalone items like seeds, saplings, or custom doors that are placed via an item first.

When assigning groups for building materials or natural elements, pay attention to pluralization in the vanilla keys. Some keys like plank or fence are singular, while others like stairs or walls are plural.

Sometimes you create dummy items used only for custom UI icons, entity projectiles, or intermediate crafting steps that players should never pull from the creative menu. For these, set category to none and leave out the group field entirely.

If you also want to prevent players and command blocks from seeing the item in the autocomplete list when typing /give or /clear, set is_hidden_in_commands to true. The item can still be given via scripts or loot tables, or if a player types the full identifier manually in some versions, but it stays out of the way during normal play.

{
  "format_version": "1.20.50",
  "minecraft:item": {
    "description": {
      "identifier": "example:internal_ui_icon",
      "menu_category": {
        "category": "none",
        "is_hidden_in_commands": true
      }
    },
    "components": {
      "minecraft:max_stack_size": 1
    }
  }
}

Applies to Bedrock Edition 1.20.20 and later. Stable; no experimental toggles are required to use menu_category or vanilla item groups.

Read out of the game itself, so the ids match the version you are building for.