Minecraft Bedrock /give Command: Copyable Item Examples & Fixes

Open controller inputs →

Copy a Bedrock /give example

• One diamond for yourself: /give @s diamond 1
• A stack of diamonds: /give @s diamond 64
• A diamond pickaxe: /give @s diamond_pickaxe 1
• A netherite sword: /give @s netherite_sword 1
• Food for everyone online: /give @a cooked_beef 32

Use these in player chat with cheats and command permission enabled. @a affects every online player; choose it deliberately. These are Bedrock examples, not Java component syntax.

Fix the error you actually received

• Command unavailable or permission denied: check cheats and your operator permissions with the world owner.
• Item not recognized: start with the plain diamond example; use an identifier without display-name spaces.
• No target: use a valid player name or player selector; a command block's @s is not the player who pressed a button.
• Copied JSON fails: remove the optional components, confirm the plain item works and then consult the Bedrock component reference.

Give yourself a basic item

In Minecraft Bedrock chat, enter /give @s diamond 1 to give the executing player one diamond. Microsoft's documented syntax is /give <player> <itemName> [amount] [data] [components]. The square brackets in documentation mean optional arguments; do not type them around an ordinary count. Cheats and appropriate command permission are required.

Read the command in order

• /give: the action.
• @s: the executing entity; in player chat, yourself.
• diamond: the item identifier.
• 1: the amount. When omitted, the documented default is one.

For a stack-sized example, enter /give @s diamond 64. For a tool, use /give @s diamond_pickaxe 1. Item identifiers use the game's names, not arbitrary display text such as “Diamond Pickaxe” with spaces.

Give another player an item

/give PlayerName diamond 1 targets a named player. Replace PlayerName with the actual recipient. @p targets the nearest living player, while @a selects all online players. Review that choice before submitting a command on a multiplayer world.

Keep advanced item data separate

The Bedrock reference includes optional data and JSON components. They are separate arguments after the amount. Do not copy Java item-data examples into this Bedrock syntax and assume they will work. For your first attempt, omit components and establish that a plain item can be delivered. If you need custom restrictions or other component behaviour, use the current official component documentation for that exact requirement.

A repeatable troubleshooting test

1. Start in a copied or test world and confirm command permissions.
2. Try one ordinary diamond with @s from player chat.
3. Read the full error if it fails: is the command unavailable, the item invalid or the target missing?
4. Change only the failed argument, then retry.
5. Increase the count or change the recipient after the basic example succeeds.

When adapting this to a command block, remember that the block is not a player. A player-chat use of @s should not be copied unchanged if the block must select someone nearby. Decide explicitly who should receive the item and what event should trigger the reward.

This guide verifies Bedrock commands. See Bedrock command setup and teleport targets. GetCheatBeacon recommends keeping experiments separate from a survival save you want to preserve.

Official sources

Checked October 9, 2026: Microsoft's give reference and target-selector documentation. Troubleshooting order is editorial advice.