Evidence log

Palworld Save Editor changelog for compatibility evidence.

Every capability change should say what format, task, fixture, and game version was tested. Palworld Save Editor does not turn a parser commit into a blanket compatibility claim.

Scan local files Try the safe sample

0.1.0RecognitionLocal ZIP/file intake, format signals, receipts, Worldprint

0.1.0Fixture loopEdit, diff, 6 checks, backup, receipt, export

Known limitAll binary writesReal PlZ, PlM, CNK, GVAS, and unknown inputs are read-only

Local safety workbench

Run the same safety workflow on your local files.

Scan locally and export a receipt. Editing, diff, and validation are limited to the sample and Pal Save Editor JSON fixtures; every real binary input stays read-only.

0 B of save data uploadedLocal hashing and ZIP inspectionBlocked export on failed validation

What needs to happen?

Drop Level.sav, a world ZIP, or a Pal Save Editor JSON fixtureFor editing or transfer checks, include Level.sav and the Players folder. Choose local files

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.

July 27, 2026 - Static launch

Added local `.sav`, ZIP, and Palworld Save Editor JSON intake in an isolated Web Worker. Added Level.sav, player, metadata, backup, PlZ, PlM, CNK, GVAS, and unknown signature recognition with explicit capability states.

Added the complete sample editing loop: immutable original, field-level diff, owner and identity checks, legal-value validation, scope lock, JSON round-trip, safe-pack ZIP, redacted share card, and local Save Chronicle.

Known limitations

Real Palworld binary editing and repair exports are locked. No reviewed PlM/Oodle browser path currently meets the licensing and safety gates together. PlZ recognition does not imply Palworld 1.0 RawData compatibility.

Next evidence gates

The next parser milestone requires bounded WebAssembly memory, complete input consumption, unchanged round-trip fixtures, changed reparse, non-target hash checks, export re-decompression, and actual current-game loading across supported tasks.

SAFE

Task checklist

01State the exact task and format.
02Link parser commit and fixture version.
03Separate parse, round-trip, and game-load results.
04Keep failed fixtures and known limits visible.

FAQ

Questions people ask before touching the save

When will real PlM editing ship?

Only after the licensing route and safety test suite are both resolved. There is no date-based promise.

How can I verify a compatibility claim?

Check the task, format, game version, fixture, validation result, and any documented load confirmation. This release has no recorded real-binary game-load result.