Reversible editing workflow

Edit a Palworld save with backup, impact preview and validation.

The live editor completes the full loop for the sample world and Palworld Save Editor JSON fixtures. Real `.sav` output remains locked until the parser can prove unchanged round trips and current-game loading.

Scan local files Try the safe sample

OriginalImmutableEvery edit starts from an in-memory clone

DiffField-levelPaths, before values, and after values stay visible

Export gate6 checksA failed required check keeps download disabled

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?

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.

What a trustworthy save editor must prove

Changing a number in a form is the easy part. A safe editor must know which dependent fields, owner references, and companion files are affected. It also needs to prove that an unchanged file can survive decode and rebuild before attempting a modified export.

Palworld Save Editor keeps the original model frozen, records only UI-approved paths in the Change Plan, and shows a plain-English impact sentence beside the raw Expert diff.

Supported live editing in this release

The built-in sample and `pal-save-editor-world/1` JSON fixtures support Pal nickname, level, work speed, attack IV, defense IV, active skill, selected player values, inventory quantities, and technology lists. These fixtures exist to prove the safety workflow, not to masquerade as a Level.sav file.

The exported safe pack contains the modified fixture, the original backup, a machine-readable Change Receipt, and a README that explicitly says not to rename JSON to Level.sav.

Requirements before real `.sav` export unlocks

The release gate includes full input consumption, byte-stable unchanged round trips, modified reparse, non-target region checks, export re-decompression, and successful loading in the current game. PlM/Oodle licensing must also be compatible with commercial browser distribution.

SAFE

Task checklist

01Use the sample to understand the workflow before opening a real save.
02Confirm the Scope Map contains only the objects you intend to touch.
03Review every field-level diff in Guided or Expert mode.
04Keep export blocked if any reference, value, scope, or round-trip check fails.

FAQ

Questions people ask before touching the save

Is this a working online Palworld save editor?

It is a working local editor for the sample and Palworld Save Editor JSON fixture format. Real Palworld binary save writing is still locked and is not presented as complete.

Why not use an existing Oodle WASM file?

Available implementations introduce GPL or educational-use restrictions and still lack enough current-version round-trip evidence for Palworld Save Editor's commercial safety promise.

Can I inspect a real Level.sav today?

Yes. Palworld Save Editor can recognize the file set, hash it, detect common container signals, flag missing companions, and issue a read-only receipt.