Local save diagnosis
Diagnose a Palworld save before changing anything.
Palworld Save Editor starts with evidence: which files you have, what format they use, what is missing, and whether the browser can safely continue. The original stays untouched while you decide the next move.
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.
Recognition in progress
Reading file headers
- Header and compression signatureWAIT
- Required file set and backupsWAIT
- Editable objects and transfer scopeWAIT
- Private receipt and WorldprintWAIT
Recognition receipt
Local save recognized
Pal Save Editor found the required records and mapped the safe next step.
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.
What the recognition receipt tells you
A useful diagnosis is more than a green check beside Level.sav. Palworld Save Editor inventories Level.sav, LevelMeta.sav, WorldOption.sav, Players/*.sav, and timestamped backups, then explains which part of the intended job can be verified from that set.
The receipt also records a SHA-256 based Worldprint, total bytes, format signals, platform clues, and an explicit capability state. A file can be recognized without being declared editable.
Why binary editing is sometimes locked
Recent Palworld saves often use the PlM container and Oodle compression. The browser ecosystem does not currently offer a mature, permissively licensed PlM write path with proven current-version round trips. Palworld Save Editor therefore stops at read-only diagnosis when it cannot prove a rebuild.
That restraint is the product. A guessed export can destroy the recovery options that still exist in the original and backup folders.
The safe route after scanning
If the set is complete and the format is supported, the next step is a scoped change plan. If files are missing, Palworld Save Editor points to the exact companion folder. If the active save looks damaged, it prioritizes recovery points before mutation. Transfer jobs move to an identity map before any conversion.
- Freeze the original input as the reference point.
- Describe every affected player, Pal, inventory group, or file.
- Block export until structure, references, identities, values, scope, and round-trip checks pass.
Task checklist
- 01Upload the complete world folder as a ZIP when possible.
- 02Keep at least one timestamped backup outside the active save directory.
- 03Treat an unconfirmed game version as unknown, not compatible.
- 04Save the Recognition Receipt before using another repair or conversion tool.
Questions people ask before touching the save
Does Palworld Save Editor upload my Palworld save?
No. The current site has no save upload API, Worker function, or database. File inspection runs in your browser.
Can it repair every corrupted save?
No. It can identify file-set problems and risky signatures. A repair export is offered only when the required parser and validation path is proven.
Why show a health score?
The score summarizes visible evidence such as missing files, tiny Level.sav files, unsupported signatures, and backup coverage. The underlying issues are always listed so the number is not a black box.