Human-readable change proof
Palworld save diff shows exactly what changed in a fixture plan.
A useful diff answers two questions: what will change, and what important data will stay untouched. Palworld Save Editor combines a plain-English impact summary with exact paths for technical review.
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.
Recognition in progress
Reading file headers
- Header and compression signatureWAIT
- Required file set and backupsWAIT
- Capability state and transfer prerequisitesWAIT
- Private receipt and WorldprintWAIT
Recognition receipt
Local save recognized
Pal Save Editor identified the selected files and assigned a capability state.
Inspection summary
Pal Save Editor can describe the file set and risks, but it cannot prove a safe decode and rebuild path yet. Download the recognition receipt instead of a guessed save.
Local return loop
Save Chronicle
Receipt metadata lives only in this browser. Raw saves are never stored.
Your next local scan will appear here.
Why a raw JSON diff is not enough
Palworld records contain identities and dependencies that are hard to judge from a long structural diff. Palworld Save Editor groups the change by human object, then preserves the exact field path for audit. A one-Pal edit should not hide an unrelated player or guild change in a collapsed tree.
How scope lock works
The editor exposes a finite list of allowed fields. Validation compares the frozen original and edited model recursively. If any changed path falls outside that list, export fails even when the value itself looks valid.
What the receipt should contain
A Change Receipt records the source hash, receipt ID, timestamp, changed paths, before and after values, validation results, and recovery instruction. It should never claim the game loaded unless a user actually tested that export in the game.
Task checklist
- 01Count changed objects, not only fields.
- 02Inspect unexpected identity or owner paths first.
- 03Keep source hash and validation time with the diff.
- 04Confirm game loading separately from structural validation.
Questions people ask before touching the save
Can a diff prove the save will load?
No. It proves what changed in the parsed model. Game loading is a separate confirmation step.
Why list unchanged objects?
Users need confidence that other players, bases, guilds, and Pals were not touched by a narrow change.