The most common Minecraft file-editing mistake is opening a valid file from the wrong folder. A Java world contains metadata, player state, and chunk data in separate locations, so start by matching the problem to the file that owns it.
Which file should you open?
| File | Where to find it | What it stores |
|---|---|---|
| level.dat | The world folder root | World settings, rules, spawn, time, seed, and singleplayer Player data |
| playerdata/<uuid>.dat | The world/playerdata folder | A server player's position, inventory, health, and Ender Chest |
| region/*.mca | The world/region folder | Chunk terrain, block entities, and structures for a group of chunks |
Where level.dat lives
For a singleplayer save, open the folder named after your world inside the Minecraft saves directory. level.dat sits directly inside that folder, next to level.dat_old and directories such as region and playerdata.
.minecraft/saves/<world name>/level.datWhere playerdata/<uuid>.dat lives
On a dedicated server, each player's saved state is a UUID-named file inside the world's playerdata folder. The username is not part of the filename, so use the server's usercache.json or a trusted UUID lookup to identify the right file.
<world>/playerdata/<player-uuid>.datWhat region/*.mca files contain
Region files hold terrain chunks rather than the world's global settings. A file such as r.0.-1.mca contains a 32 by 32 chunk region. Use an MCA-capable workflow when the problem is a broken chunk, missing structure, or corrupted terrain; editing level.dat will not repair chunk data.
<world>/region/r.<region-x>.<region-z>.mcaSingleplayer versus server: the important difference
| Situation | Player data location | Important detail |
|---|---|---|
| Singleplayer | level.dat / Data / Player | Your character is stored in the world metadata file |
| Dedicated server | playerdata/<uuid>.dat | Each player has a separate UUID-named file |
| Bedrock Edition | Different save format | These Java paths and tags do not apply directly |
A safe first edit
- Close Minecraft, or stop the server and wait for it to shut down completely.
- Copy the whole world folder to a separate backup location and work on a duplicate when possible.
- Match the symptom to level.dat, playerdata, or region before opening the file.
- Open the copy in Chunkweave, inspect the tree, and export a separate edited file.
- Test the duplicate world first, then keep the original backup until the change is confirmed.
Open a level.dat file
Inspect world settings locally in your browser before you make a change.
Frequently asked questions
Do these paths apply to Bedrock Edition?
No. This guide describes Minecraft Java Edition's save layout. Bedrock uses a different storage format and should not be edited with Java level.dat or playerdata instructions.
What if my world folder is nested one level too deep?
The folder registered as the world should contain level.dat directly. If you see another folder before level.dat, move up or down until you find the actual world root, then verify it also contains region or playerdata where expected.
Do I need to back up the whole world folder?
Yes. A whole-folder backup is the safest rollback because a change to level.dat can affect loading while a region edit can affect terrain. Keep the backup outside the live saves or server directory.