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.
Which storefront context matters
Documented Minecraft: Java Edition PC launchers/storefronts: 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. The active storefront/account should be identified before any restore because cloud and local storage may not use the same path or container across editions.
Documented cloud behavior
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. Cloud synchronization is useful for continuity, but it can also turn a restore into a conflict-resolution event. Let synchronization settle before making a manual backup, and keep an offline copy outside any folder monitored by the launcher or operating-system sync service.
Local save roots still matter
The researched local save boundary is Windows: %APPDATA%.minecraftsaves | macOS: $HOME/Library/Application Support/minecraft/saves/ | Linux / Steam Play: $HOME/.minecraft/saves/; the known file or folder pattern is <world-folder>level.dat
<world-folder>region*.mca
<world-folder>playerdata*.dat. A cloud-enabled game still has concrete local data involved in ordinary play, and that local context is what you need when identifying which copy was modified most recently.
Avoid accidental overwrite loops
Close the world/server and copy the entire world directory. For modded instances, preserve the instance/modpack and configuration alongside the world. When restoring, close the game and launcher, preserve both the current local copy and the backup you want to test, then place the intended data in the matching profile/storefront location. Do not repeatedly open the game between different copies without noting which side the cloud client selected.
Compatibility and conflict checks
Java Edition saves are not directly compatible with Bedrock Edition. Version downgrades can also damage or remove world data. If progress disappears or rolls back, 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. Resolve identity/path/cloud questions first. A cloud conflict is not proof that the save itself is corrupt, and a successful upload is not proof that files from another storefront are compatible.
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.