Save structure reference

Palworld save format: PlZ, PlM, CNK and GVAS explained.

A `.sav` extension does not describe one format. Palworld save files can contain an outer platform container, a compression layer, Unreal GVAS data, and Palworld-specific RawData that changes across game versions.

PlZZlib containerMagic appears after declared-size fields
PlMOodle containerCommon in newer saves and license-sensitive
GVASUnreal SaveGameThe decompressed structured layer

Local safety workbench

Run the same safety workflow on your local files.

Scan locally, freeze the original, preview the exact scope, run validation, and export a receipt. Unknown binary formats stay read-only.

0 B sent to a serverLocal hashing and ZIP inspectionBlocked export on failed validation
What needs to happen?
Find my save
Files never leave this tab Original input stays immutable Real binary writing is locked in this release

Local return loop

Save Chronicle

Receipt metadata lives only in this browser. Raw saves are never stored.

Your next local scan will appear here.

ReadyLocal workbench loaded.
01

The layers in a save

A common Steam or server file begins with declared sizes and a container marker such as PlZ or PlM. After decompression, the data begins with the Unreal `GVAS` signature. Palworld stores additional custom RawData inside that structure.

02

PlZ and CNK

PlZ uses zlib compression flags and is the easier container to open with permissive browser libraries. Game Pass can add a CNK-style outer wrapper before the inner Palworld container. Opening those layers still does not solve identity conversion or RawData writing.

03

PlM and Oodle

PlM uses Oodle compression. Some public implementations are GPL, lack clear licensing, or contain educational-use notices. A commercial static site distributes its WASM to every visitor, so licensing and provenance must be treated as product gates.

04

Why round-trip is the minimum write test

A parser that can display JSON may still fail to serialize nested map types or preserve unknown regions. Before editing, an unchanged parse and rebuild should reproduce the same decompressed bytes or a documented equivalent that the current game loads.

SAFE

Task checklist

  1. 01Identify the outer container marker.
  2. 02Verify declared and actual sizes.
  3. 03Confirm the inner GVAS layer is fully consumed.
  4. 04Parse version-specific RawData with limits.
  5. 05Prove unchanged and changed round trips before writing.
FAQ

Questions people ask before touching the save

Is every Level.sav a PlZ file?

No. Newer saves commonly use PlM/Oodle, and Game Pass can include an additional CNK container.

Can I edit GVAS JSON and serialize it back?

Only if the parser understands the Palworld custom data and can prove a stable rebuild. Generic GVAS support alone is not enough.