
Player data & inventories · Java & Bedrock · Beginner
How to Teleport an Offline or Stuck Player by Editing Their Pos and Dimension NBT
Getting trapped in a corrupted chunk, falling into the void, or being caught in an infinite portal trap can lock a player out of a Minecraft world. Because the game cannot load the area safely, you cannot simply use in-game commands to teleport them away. This guide shows you how to rescue a stuck or offline player by directly editing their coordinate and dimension data using the browser-based NBT Editor on world.9minecraft.net, where your files are processed locally and never uploaded.
What you need
- Access to your Minecraft world save folder or a .zip archive of the world
- The stuck player's UUID (for multiplayer worlds)
- A set of safe X, Y, and Z coordinates to teleport the player to
- A complete backup copy of your world folder before making any edits
Step by step
1Back Up Your World and Ensure the Player is Offline
Before altering any game files, make a full copy of your world folder and store it in a safe location. If you are editing a single-player world, completely exit to the main menu; if you are managing a multiplayer server, ensure the stuck player has disconnected. Minecraft overwrites player files the moment a player disconnects, so editing the data while they are still logged in will cause your changes to be lost.
Tip: If you are rescuing yourself in a single-player world, you must edit data in two places: your playerdata file and the main level.dat file.
2Open Your World in the NBT Editor
Open the NBT Editor on world.9minecraft.net and click Open world folder or .zip to load your save directly into the browser. In the file tree, navigate to the playerdata folder and select the .dat file matching the stuck player's UUID (for example, playerdata/<uuid>.dat). If this is a single-player world, you should also inspect level.dat, as the game stores the local host's state inside the Data -> Player compound tag.
Tip: If you do not know the player's UUID in a multiplayer world, check the server console logs from when they last attempted to join, or open the usercache.json file in your server directory.
3Change the Pos List Tag to Safe Coordinates
Inside the expanded player file, locate the Pos list tag, which contains three double-precision floating-point values representing the X, Y, and Z coordinates in exact order. Expand the Pos tag and change these three numbers to a known safe location, such as your world spawn point (for example, X: 0.5, Y: 100.0, Z: 0.5). Make sure the second number (Y, which controls vertical height) is high enough that the player will not spawn inside solid stone and suffocate.
Tip: If you are not sure what the safe ground level is at your target X and Z coordinates, you can check your world's spawn height inside level.dat under the SpawnX, SpawnY, and SpawnZ tags.
4Update the Dimension and PortalCooldown Tags
Locate the Dimension tag to ensure your new coordinates match the realm the player is actually in. In modern Java Edition, set this string to minecraft:overworld (or minecraft:the_nether or minecraft:the_end); in Bedrock Edition or older Java versions, this tag is an integer where 0 represents the Overworld, -1 (or 1 in Bedrock) is the Nether, and 1 (or 2 in Bedrock) is the End. Next, find the PortalCooldown tag and set its value to 300 so that if the player is rescued from a broken portal, they have fifteen seconds to walk away before the portal can trigger again.
Tip: Also check the Motion list tag (set all three values to 0.0) and the FallDistance tag (set to 0.0) so a player rescued from falling into the void does not instantly die of kinetic energy upon landing at the new coordinates.
5Save and Replace the Modified File
Once you have updated Pos, Dimension, and PortalCooldown, use the tool's save or download button to export your modified .dat file. Place the downloaded file back into your world's playerdata folder (and replace level.dat if you edited a single-player host), overwriting the original file. Start your world or server and have the player log back in at their new, safe location.
How it works
Minecraft tracks every entity and player using the Named Binary Tag (NBT) format. When a player logs out or the server saves, their exact state is serialized into a compressed file inside the playerdata/<uuid>.dat directory. Because chunk loading is centered around a player's immediate coordinates, a player positioned inside a corrupted chunk or a lag machine will instantly trigger a crash the moment the server reads their Pos tag and attempts to load the surrounding terrain.
By editing the Pos and Dimension tags while the player is offline, you alter where the game engine places the player before a single chunk is loaded. The Pos tag is strictly a list of three 64-bit floating-point numbers (Doubles) indexed as 0 (X, East/West), 1 (Y, Vertical), and 2 (Z, North/South). When the player reconnects, the server reads the modified NBT data, loads the safe chunks around the new coordinates instead, and completely bypasses the corrupted area.
In single-player Java Edition worlds, the game engine keeps a duplicate copy of the host player's NBT data inside the root level.dat file under the Player compound tag. When a single-player world loads, it prioritizes this embedded Player tag over the individual file in the playerdata folder. In Bedrock Edition, offline player records are stored inside the world's db folder using a key-value database rather than loose .dat files, though our browser tool parses and exposes those exact same Pos and Dimension tags for you automatically.
Common mistakes
- Only editing playerdata/<uuid>.dat in a single-player world without also updating the Player compound tag inside level.dat, causing the game to ignore your changes and spawn you back in the trap.
- Mixing up the order of coordinates inside the Pos list by putting the Z coordinate in the second slot instead of the vertical Y height, which usually teleports the player deep into the void or underground.
- Changing the Dimension tag back to the Overworld without changing the Pos coordinates, which can leave a player stranded thousands of blocks up in the air or buried inside bedrock.
- Editing the file while the player is still connected to the server, or while the single-player world is merely paused, which results in the game overwriting your newly saved file the moment they log out.
- Leaving FallDistance at a high number after rescuing someone from the void, causing them to instantly die of fall damage the moment their feet touch the safe ground.
FAQ
Why did my player snap right back to the crashing location in single-player?
In single-player worlds, Minecraft reads the host player's location from the Player compound tag inside level.dat first. Open level.dat in the NBT Editor and apply the exact same Pos, Dimension, and PortalCooldown changes there.
How do I stop a player from dying immediately after rescuing them from lava or the void?
In addition to changing their Pos tag, look for the Fire tag and set it to 0 (or -20) to extinguish flames, set FallDistance to 0.0 to cancel accumulated fall damage, and set the three values inside the Motion list tag to 0.0 to stop their momentum.
What should the Dimension tag look like if my world is an older version or Bedrock Edition?
Modern Java Edition (1.16 and newer) uses namespaced strings like minecraft:overworld. Older Java versions and Bedrock Edition use whole numbers (Integers): 0 is the Overworld, -1 is the Nether in old Java (1 in Bedrock), and 1 is the End in old Java (2 in Bedrock). Look at the existing tag type in the NBT Editor before typing your new value.
By using the browser-based NBT Editor to update the Pos, Dimension, and PortalCooldown tags in a player's data file while they are offline, you can safely move any trapped or crashing player back to solid ground without losing their inventory.