{"id":22925,"date":"2026-07-07T18:35:57","date_gmt":"2026-07-07T18:35:57","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/minecraft-give-command\/"},"modified":"2026-07-07T18:35:57","modified_gmt":"2026-07-07T18:35:57","slug":"minecraft-give-command","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/minecraft-give-command\/","title":{"rendered":"Minecraft \/give Command: Full Guide with Examples"},"content":{"rendered":"\n

Quick answer:<\/strong> The \/give<\/code> command drops one or more item stacks straight into a player’s inventory. The exact syntax in Minecraft Java Edition 26.2 is \/give []<\/code> \u2014 for example, \/give @p diamond 64<\/code> hands the nearest player a full stack of diamonds. You need operator permissions (permission level 2) or a single-player world with cheats enabled to run it.<\/p>\n\n\n\n

Below is the complete breakdown for Java Edition 26.2 (“Chaos Cubed”, released June 16 2026), including the modern data-component item format, copy-paste examples, and how Bedrock does things differently. Want to build commands without memorizing SNBT? Use our free Minecraft Give Command Generator<\/strong><\/a> to point-and-click your item, enchantments, and name, then copy the finished command.<\/p>\n\n\n\n

Syntax<\/h2>\n\n\n\n

The base command takes three arguments \u2014 two required, one optional:<\/p>\n\n\n\n

\/give   []<\/code><\/pre>\n\n\n\n
Argument<\/th>Required<\/th>What it accepts<\/th><\/tr><\/thead>
<\/code><\/td>Yes<\/td>An entity argument that must resolve to player(s)<\/strong> \u2014 a player name, a UUID, or a player-type target selector such as @p<\/code>, @a<\/code>, @r<\/code>, or @s<\/code>.<\/td><\/tr>
<\/code><\/td>Yes<\/td>An item in the form item_id[data_components]<\/code>. The bracketed components are optional; omit them for a plain item. The minecraft:<\/code> namespace prefix is optional.<\/td><\/tr>
[]<\/code><\/td>No<\/td>Integer from 1 to 2147483647. Defaults to 1 when omitted.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
The data-component item format<\/h3>\n\n\n\n
Since Java Edition 1.20.5, custom item data is written with data components<\/strong>, not the old NBT {tag}<\/code> syntax. The format is item_id[component=value,component=value]<\/code>, where each component is a namespaced ID and each value is written in SNBT. Multiple components are comma-separated inside a single pair of square brackets. You can suppress a default component with an exclamation prefix, e.g. stone[!custom_name]<\/code>. Any pre-1.20.5 guide using diamond_sword{Enchantments:[...]}<\/code> is out of date for 26.2.<\/p>\n\n\n\n
Component<\/th>Purpose<\/th>Example value<\/th><\/tr><\/thead>
enchantments<\/code><\/td>Map of enchantment ID to level<\/td>{sharpness:3,knockback:2}<\/code><\/td><\/tr>
custom_name<\/code><\/td>Anvil-renamable display name (text component)<\/td>{text:\"Magic Wand\",color:\"light_purple\",italic:false}<\/code><\/td><\/tr>
item_name<\/code><\/td>Base name that cannot<\/em> be overwritten in an anvil<\/td>\"Dirt\"<\/code><\/td><\/tr>
lore<\/code><\/td>Array of tooltip lines<\/td>[{text:\"A shiny Emerald!\",italic:false,color:\"gold\"}]<\/code><\/td><\/tr>
damage<\/code><\/td>Durability damage already applied<\/td>500<\/code><\/td><\/tr>
unbreakable<\/code><\/td>Item never loses durability (presence alone is enough)<\/td>{}<\/code><\/td><\/tr>
max_stack_size<\/code><\/td>Override max stack size (1\u201399)<\/td>64<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Need item IDs or enchantment IDs to plug in here? See our Minecraft item IDs reference<\/a> and the full enchantments list<\/a>.<\/p>\n\n\n\n
Examples<\/h2>\n\n\n\n
All of these are ready to paste into chat or a command block.<\/p>\n\n\n\n
1. A full stack of diamonds to the nearest player:<\/strong><\/p>\n\n\n\n
\/give @p diamond 64<\/code><\/pre>\n\n\n\n
2. A golden apple to every online player<\/strong> using the @a<\/code> selector:<\/p>\n\n\n\n
\/give @a golden_apple 1<\/code><\/pre>\n\n\n\n
3. An enchanted sword to yourself.<\/strong> The enchantments<\/code> component takes a map of enchantment ID to integer level:<\/p>\n\n\n\n
\/give @s wooden_sword[enchantments={sharpness:3,knockback:2}] 1<\/code><\/pre>\n\n\n\n
4. A named, unbreakable pickaxe.<\/strong> Combine multiple components inside one set of brackets, separated by commas:<\/p>\n\n\n\n
\/give @p diamond_pickaxe[custom_name={text:\"Magic Wand\",color:\"light_purple\",italic:false},unbreakable={}] 1<\/code><\/pre>\n\n\n\n
5. The full worked example<\/strong> \u2014 enchanted, named, and unbreakable in one command:<\/p>\n\n\n\n
\/give @s diamond_sword[enchantments={sharpness:5},custom_name={text:\"Excalibur\",color:\"gold\",italic:false},unbreakable={}] 1<\/code><\/pre>\n\n\n\n
Note on the enchantments value: the documented data-component format uses the flat {id:level}<\/code> map shown above. The Minecraft Wiki also shows a wrapped form, enchantments={levels:{sharpness:5}}<\/code>; if one form is rejected by your server, try the other. Our give command generator<\/a> always outputs the correct shape for you.<\/p>\n\n\n\n
Permissions, op level, and mechanics<\/h2>\n\n\n\n
\/give<\/code> is a cheat command. It requires permission level 2<\/strong> \u2014 meaning you must be an operator (op), or be in a single-player world with cheats enabled. This “permission level 2” phrasing is Java-Edition-specific. If you run a server, grant yourself op through your control panel console; on our hosting you can do this from the panel in one click. See our Minecraft server hosting<\/a> for panels with instant console and command access.<\/p>\n\n\n\n
How the items are delivered: \/give<\/code> places the requested item stack(s) directly into the target’s inventory. If the inventory is full, the overflow is dropped at the player’s feet rather than lost.<\/p>\n\n\n\n
About the target selectors: \/give<\/code> requires a player-type<\/strong> target. @p<\/code> (nearest player), @a<\/code> (all players), @r<\/code> (random player), and @s<\/code> (the executor, i.e. yourself) are all valid. A raw @e<\/code> (all entities) or @n<\/code> (nearest entity) will error unless filtered to players, because those can resolve to non-players. Learn more in our target selectors guide<\/a>.<\/p>\n\n\n\n
Version context:<\/strong> 26.2 is the first release on Mojang’s new year.drop.hotfix<\/em> versioning scheme (so “26.2” = year 2026, drop 2). Nothing in the 26.2 changelog changes how \/give<\/code> works; the command and the data-component item format are inherited unchanged from the 1.20.5+ component era.<\/p>\n\n\n\n
Java vs Bedrock<\/h2>\n\n\n\n
This is where the two editions diverge significantly. Bedrock’s \/give<\/code> does not use Java’s item_id[...]<\/code> bracket component syntax.<\/strong> Instead it uses positional numeric arguments plus a trailing JSON components object:<\/p>\n\n\n\n
give   [amount: int] [data: int] [components: json]<\/code><\/pre>\n\n\n\n
\u00a0<\/th>Java Edition<\/th>Bedrock Edition<\/th><\/tr><\/thead>
Custom item data<\/td>item_id[component=value]<\/code> brackets (SNBT)<\/td>Positional amount<\/code>\/data<\/code> ints + trailing JSON components<\/code><\/td><\/tr>
Enchanting via \/give<\/td>Yes, via enchantments<\/code> component<\/td>No full data-tag support<\/td><\/tr>
Permission<\/td>Permission level 2 (op \/ cheats)<\/td>Cheats \/ op<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
A Bedrock example that gives an item with a component looks like this:<\/p>\n\n\n\n
\/give @p diamond_sword 1 0 {\"keep_on_death\":{}}<\/code><\/pre>\n\n\n\n
Here the 1<\/code> is the amount, 0<\/code> is the data\/aux value, and the JSON object is the components field. Bedrock also uses the data value for variants \u2014 e.g. \/give @a potion 1 5<\/code> gives a specific potion type by number. Because the syntaxes are incompatible, always confirm which edition you’re on before copying a command.<\/p>\n\n\n\n
Frequently asked questions<\/h2>\n\n\n\n
How much can I give with one command?<\/h3>\n\n\n\n
The count<\/code> argument accepts any integer from 1 up to 2147483647. Items beyond a stack’s normal maximum are placed as additional stacks (or dropped if the inventory fills up).<\/p>\n\n\n\n
Why does my command say I don’t have permission?<\/h3>\n\n\n\n
\/give<\/code> needs permission level 2. Make yourself an operator on your server, or enable cheats in your single-player world. Without op or cheats, the command is blocked.<\/p>\n\n\n\n
Can I give an item to everyone at once?<\/h3>\n\n\n\n
Yes \u2014 use the @a<\/code> selector, which targets every online player, for example \/give @a golden_apple 1<\/code>. Use @r<\/code> for a single random player.<\/p>\n\n\n\n
How do I make an item unbreakable or rename it?<\/h3>\n\n\n\n
Add data components in brackets. Use unbreakable={}<\/code> for infinite durability and custom_name={text:\"...\"}<\/code> for an anvil-renamable name. Use item_name<\/code> instead if you want a name that can’t be overwritten in an anvil.<\/p>\n\n\n\n
Why won’t my old \/give command work anymore?<\/h3>\n\n\n\n
If it uses NBT {tag}<\/code> syntax like diamond_sword{Enchantments:[...]}<\/code>, it’s from before 1.20.5 and is outdated. Java 26.2 uses the data-component format item_id[component=value]<\/code> instead. Convert it, or rebuild it with our give command generator<\/a>.<\/p>\n\n\n\n
Keep exploring commands<\/h3>\n\n\n\n