Player identity first
Palworld Player Save Editor with a visible change plan.
Open a complete world and edit your character: level, experience, name, work speed, sanity, and fullness live in Level.sav, while technology points, unlocked technologies, the Paldeck, and fast travel live in your own Players/<id>.sav. Both are written with exact-path diff, validation, backup, and receipt export. Identity and ownership stay untouched: the editor matches PlayerUID across the two files but never rewrites it.
Open a save to edit a player
Choose the complete world so player ownership and Pal links can be checked together.
A real player's level, experience, name, work speed, sanity, and fullness are editable in Level.sav; technology points, unlocked technologies, the Paldeck, and fast travel are editable in their own player file. Identity and ownership stay locked.Quick answer
Palworld player save editor: what to know first
- Your character's level, experience, name, and stats are written into its record in Level.sav, with the same checks as a Pal edit.
- Technology points, unlocked technologies, the Paldeck, and fast travel are written into your own Players/<id>.sav, which is matched to Level.sav by PlayerUID.
- Level.sav alone is enough for your character's record; technology, the Paldeck, and fast travel need the matching Players folder, because identity and ownership references cross file boundaries.
- Use the co-op migration and character-reset guides for recovery planning; no identity rewrite is performed on this page.
What the browser can and cannot read today
A complete PlZ2 / 0x32 world decodes each player's character record from Level.sav and pairs it with the matching Players/<id>.sav by PlayerUID. The editor shows the player's name, level, owned Pals, inventory containers, technology points, unlocked technologies, Paldeck, and fast-travel points.
Level, experience, name, work speed, sanity, and fullness are editable in Level.sav. Technology points, unlocked technologies, the Paldeck, and recorded fast-travel points are editable in the player's own file. The PlayerUID, GUID, appearance, and ownership links are read to keep the two files together, never rewritten.
Status points spent on each stat and the points left to spend are editable in Level.sav too, ancient technology points in the player's own file, and a level change writes the experience that level starts at.
| Input | Available evidence | Player edit or export |
|---|---|---|
| Editable sample | Named fixture players and owner references | Level and technology points |
| Pal Save Editor JSON | Documented fixture model | Allowlisted fixture fields + safe pack |
| Real Players/*.sav | Technology, Paldeck, fast travel, inventory ownership | Technology points, unlocks, Paldeck, fast travel + Safe Pack |
| Real Level.sav | Named players and their character records | Level, experience, name, work speed, sanity, fullness |
Why a player file cannot be edited in isolation
Palworld stores important player relationships across the individual player save and world data. A change that preserves the file but loses the world-side mapping can look like a brand-new character at login. The complete world is required to prove which identities and ownership links belong together.
Safe player change requirements
A future change plan must identify the exact player through file role, PlayerUID, GUID, and world references; list owned Pals, guild membership, bases, storage locks, and other dependent records; and block export when an identity is duplicated, missing, or ambiguous. The editor already refuses duplicate or mismatched PlayerUIDs when it opens a world; rewriting an identity or moving ownership is not live in this release.
Host characters need special handling
A co-op host may not map like a normal client character during dedicated-server migration. Host transfer should be a dedicated mission with explicit identity confirmation, not a checkbox inside a generic level editor.
Task checklist
- 01Include Level.sav and the complete Players folder.
- 02Map by identity fields, not display name.
- 03Verify guild, base, and Pal ownership after the change.
- 04Keep the original player file and world backup together.
Questions people ask before touching the save
Why did my character reset after transfer?
The target server likely created or selected a different player identity. The old data may still exist under another GUID.
Can I edit only player level here?
Yes. Change just the level, or any other supported field, and only that field appears as a pending change with its exact path. The same works on the editable sample and a Pal Save Editor JSON fixture.