Minecraft: Java Edition makes the strongest case in this batch for treating a save as a directory tree. A world contains metadata, chunk regions, player records, dimensions, data packs, and potentially mod-specific data. Copying only level.dat is not a world backup. Close the world or server cleanly, then archive the entire world directory. If you use Prism Launcher, MultiMC, or another instance manager, find the actual instance path first because the default `.minecraftsaves` directory may not be the one in use.
Choose the correct backup boundary
For Minecraft: Java Edition, the researched PC save location is Windows: %APPDATA%.minecraftsaves | macOS: $HOME/Library/Application Support/minecraft/saves/ | Linux / Steam Play: $HOME/.minecraft/saves/. The known save file or folder pattern is <world-folder>level.dat
<world-folder>region*.mca
<world-folder>playerdata*.dat. Close the world/server and copy the entire world directory. For modded instances, preserve the instance/modpack and configuration alongside the world. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Minecraft Launcher, Prism Launcher, MultiMC and other instance managers. Alternative launchers can use separate instance directories. The default .minecraft path is not guaranteed to contain a world launched from a custom instance.
Account for cloud saves
Local Java Edition worlds do not become generic cloud saves simply because the player uses a Microsoft account. Realms worlds are service-hosted and can be downloaded separately through supported game workflows. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
A Java Edition world is a directory tree. level.dat stores world metadata, region files use the Anvil .mca format, and player data is stored separately. The world folder, not one file, is the correct backup unit. Compatibility note: Java Edition saves are not directly compatible with Bedrock Edition. Version downgrades can also damage or remove world data. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
If a world is missing from the default saves folder, check the active launcher instance directory. If level.dat is damaged, preserve the whole world before considering level.dat_old or any repair step. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Default Windows/macOS/Linux paths, server world location, launcher-instance behavior, Realms distinction, and Java-versus-Bedrock incompatibility were reviewed against current PCGamingWiki coverage.