Pal SaveEditor
Runs locallyOpen a save

Evidence-based compatibility

Palworld save compatibility by version, platform and format.

Compatibility is a matrix, not a yes-or-no badge. A tool may recognize a file, decode the container, parse part of the world, and still be unable to rebuild a save that the current game will load.

Scan local files Try the safe sample
PlZRecognizeZlib-era container; safe writes still require RawData round-trip proof
PlMRecognize + blockOodle container; no permissive proven browser write path
CNKRecognizeGame Pass outer container; migration requires identity mapping

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

Recognition, reading, and writing are different claims

Recognition finds format signals and file roles. Reading turns bytes into a structured model. Writing rebuilds the file. Round-trip validation proves an unchanged model survives. Game-load confirmation proves the export works in Palworld. Palworld Save Editor reports these states separately.

02

Why PlM changes the browser equation

Palworld v0.6 introduced widespread PlM/Oodle saves. Available browser Oodle implementations carry GPL or educational-use constraints, and public tools still report serialization failures on some real files. Palworld Save Editor recognizes PlM but blocks mutation.

03

What changes after a game update

Even when the outer container stays the same, Palworld RawData structures, item IDs, map types, and dependent fields can change. A compatibility claim should include the game version, task, test fixture, parser commit, validation result, and actual load confirmation date.

SAFE

Task checklist

  1. 01Check outer format and inner GVAS separately.
  2. 02Require current-version fixtures for edit claims.
  3. 03Treat decode-only support as read-only.
  4. 04Record actual game-load confirmation separately.
  5. 05Keep unsupported versions visible instead of silently guessing.
FAQ

Questions people ask before touching the save

Does PlZ mean my save is safe to edit?

No. PlZ identifies the outer compression path. The inner Palworld data still needs current-version parse and round-trip support.

Why is PlM blocked?

The required Oodle path lacks a mature permissive browser implementation and enough proven commercial round-trip coverage.

Is Palworld 1.0 automatically compatible?

No. Version 1.0 introduced data changes. Each task and format needs evidence against current real saves.