Inspect a Palworld save file
Older PlZ saves are read entirely in your browser. Saves from Palworld 0.6 and newer (PlM format) are first converted on LOW.MS servers, in memory and never stored, then parsed locally. Large worlds may take a few seconds.
Drop a .sav file here
Supports player saves, Level.sav, LevelMeta.sav and WorldOption.sav from co-op and dedicated servers.
Upload any Palworld .sav file to see what is inside, without installing anything. The inspector reads player saves (technology points, unlocked technologies, UID), LevelMeta.sav (world name, in-game day) and Level.sav (players, guild and base counts, and which sections take up the space).
Both save formats are supported: the zlib PlZ container and the Oodle PlM container that Palworld has used since version 0.6. PlZ files are processed entirely in your browser; PlM files are converted to zlib on LOW.MS servers in memory, never stored, then parsed locally.
Frequently asked questions
Which files can I inspect?
Player saves from the Players folder, Level.sav (the world), LevelMeta.sav (world metadata) and WorldOption.sav (world settings, which opens in our settings generator). Both co-op and dedicated server saves work.
Is my save file uploaded anywhere?
Saves in the older PlZ format never leave your browser. Newer PlM saves (Palworld 0.6 and later) use Oodle compression that browsers cannot decompress, so the file is sent to a LOW.MS conversion endpoint that turns it into the zlib format in memory, returns it immediately and stores nothing. All parsing and display still happens locally.
Why does my Level.sav show players as UIDs instead of names?
Palworld stores character names deep inside compressed world data rather than next to the player list. The UID is what you need for server administration anyway: it is the save filename in the Players folder and the id used by admin commands.