~ is where the command runs; plain numbers are absolute world coordinates (press F3 in game to read them). Leave all three as ~ to use the spot the command runs from.
Needs cheats or operator permission (level 2). The spawn is set in the dimension where the command runs and survives broken beds.
Paste into chat with cheats enabled, or into a command block without the leading slash. Targeted players are not notified; only the usual command feedback appears for whoever runs it.
/spawnpoint sets a personal respawn point for one or more players, exactly the slot a bed normally fills, but placed by command. It works in any dimension, takes effect instantly, and unlike a bed it cannot be blown up, slept away or broken by another player.
Every player carries one personal respawn point. Normally a bed or a respawn anchor writes it; the spawnpoint command writes the same value directly. From then on, dying sends the player back to that block, in the dimension where the command ran. Map makers use it for checkpoints, servers use it to bind players to hubs and arena bases, and in singleplayer it is the quickest way to make any spot home.
It is a permission level 2 command: turn cheats on in singleplayer or run it as an operator on a server. Targeted players get no message; the spawn simply changes.
1. Pick the targets in the generator above: yourself, a named player, or a selector like @a with optional filters for team, tag or distance.
2. Add coordinates if the spawn should be somewhere other than where the command runs. Press F3 in game to read exact block positions.
3. Optionally set the facing, so players respawn looking the right way, toward an arena gate or a quest board.
4. Copy the command and paste it into chat, or into a command block without the leading slash. Keep two air blocks free at the spawn position so the respawn is never obstructed.
/spawnpoint [<targets>] [<pos>] [<angle>]Each argument is optional but they nest left to right: a position needs targets, and a facing needs a position. The generator above enforces that order, validates every value, and switches between the single-angle and yaw-plus-pitch syntax based on the Minecraft version you select.
Minecraft has four ways to decide where a player respawns, and they answer different questions. /spawnpoint is the command-driven personal spawn; the other three each have a catch.
All four write to the same respawn slot for a player, so the most recent one wins. That makes /spawnpoint the cleanest option for maps and servers: it works in every dimension, costs nothing, and players cannot accidentally undo it by breaking a block, though they can still overwrite it by sleeping in a bed.
Five ready-to-paste commands covering the common jobs: personal spawns, server-wide respawns, exact checkpoints and dimension tricks. Copy one and adjust the names and coordinates.
No arguments needed: your respawn point becomes the block you are standing on. No bed required, and it cannot be lost to a creeper.
With no coordinates the command uses the spot where it runs, so standing in your base and running this points every player's respawn there.
Replace Steve with the player's name. Plain numbers are absolute world coordinates; press F3 in game to read them off the Block line.
Yaw 90 faces the player west on respawn and pitch 0 keeps the camera level. Before 1.21.9 the command takes only the yaw, so drop the trailing 0 on older versions; before 1.16.2 there is no facing argument at all.
/spawnpoint works in any dimension. Wrap it in /execute in (or run it while in the Nether) and the player respawns there with no respawn anchor or glowstone needed.
Run /spawnpoint with no arguments to set your own respawn point exactly where you are standing. With operator permission you can set other players' spawns too: /spawnpoint Steve 100 64 -200 sends that player's respawn to those coordinates. The generator above builds the full command for any target, position and facing.
/spawnpoint sets a personal respawn point for specific players, the same slot a bed fills. /setworldspawn moves the world spawn, the shared default where new players first appear and where anyone without a personal spawn respawns. A player's own spawnpoint, bed or respawn anchor always wins over the world spawn.
Yes. The command sets the spawn in whichever dimension it runs in, so /execute in minecraft:the_nether run spawnpoint @p 0 70 0 gives a Nether respawn without a respawn anchor, and the same works for the End. Beds explode in those dimensions; the command has no such limit.
It sets the direction the player faces after respawning: 0 is south, 90 west, 180 north and -90 east. The angle argument needs Minecraft 1.16.2 or newer, and from 1.21.9 the command takes a full rotation, yaw plus pitch, so the respawn camera can also be tilted up or down.
Yes, whichever spawn was set most recently wins. Using a bed after the command replaces the command spawn with the bed, and running /spawnpoint again replaces the bed spawn. Breaking the bed afterwards does not bring the command spawn back; run the command again if you need it.
Almost always the spawn block is obstructed: if solid blocks cover the position, Minecraft falls back to the world spawn and shows the missing-or-obstructed message. Keep two air blocks free at the spawn point. Also check the command ran in the right dimension, because the spawn is set in the dimension where the command executes.
Need to move the world spawn instead? Or browse more Minecraft tools: