Pal SaveEditor
Runs locallyOpen a save

Local save diagnosis

Palworld Save Doctor diagnoses files before anything changes.

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.

Scan local files Try the safe sample
First answerUnder 3 secFor normal local file sets on a modern desktop
Server upload0 bytesInspection, hashing, ZIP reading, and receipts run in-browser
DecisionEdit / repair / transferChosen from evidence instead of a beginner or expert label

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?
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

What the recognition receipt tells you

A useful diagnosis is more than a green check beside Level.sav. Palworld Save Editor inventories active world files and files found under backup paths, 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.

Palworld Save Doctor recognition receipt showing local file classification, format evidence, Worldprint, and read-only capability status
The Recognition Receipt separates file evidence from editing permission, so a recognized binary can remain explicitly read-only.
02

Why all real Palworld binary editing is locked

All real PlZ, PlM, CNK, raw GVAS, and unknown inputs remain read-only in this release. PlM adds Oodle licensing and decompression questions, while every binary format still needs complete Palworld-specific parsing, stable round trips, scoped change proof, and current-game loading before writing can unlock.

That restraint is the product. A guessed export can destroy the recovery options that still exist in the original and backup folders.

03

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 names the companion class to locate. If the active save looks damaged, preserve and compare recovery points manually before mutation. Transfer jobs need 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.
SAFE

Task checklist

  1. 01Upload the complete world folder as a ZIP when possible.
  2. 02Keep at least one timestamped backup outside the active save directory.
  3. 03Treat an unconfirmed game version as unknown, not compatible.
  4. 04Save the Recognition Receipt before using another repair or conversion tool.
FAQ

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 an evidence score?

The score summarizes visible issues such as missing files, tiny Level.sav files, unsupported signatures, and whether backup-folder files were included. The underlying issues are always listed.