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.
Known Minecraft: Java Edition save-file structure
The researched filename or folder pattern is <world-folder>level.dat
<world-folder>region*.mca
<world-folder>playerdata*.dat. File-extension context: .dat, .mca The documented format notes are: 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.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. Java Edition saves are not directly compatible with Bedrock Edition. Version downgrades can also damage or remove world data. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: Windows: %APPDATA%.minecraftsaves | macOS: $HOME/Library/Application Support/minecraft/saves/ | Linux / Steam Play: $HOME/.minecraft/saves/. Storefront 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. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
Close the world/server and copy the entire world directory. For modded instances, preserve the instance/modpack and configuration alongside the world. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: 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. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: 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. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
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.