Player identity first

Palworld Player Save Editor guide to identity-safe changes.

Player progression is only one part of the record. Transfer and host changes can fail when PlayerUID, GUID, guild membership, Pal ownership, and Level.sav references no longer agree. This page explains the required change plan; the current UI does not edit player values or parse real player identities.

Scan local files Try the safe sample

Primary keyPlayer identityName alone is never enough for mapping

CompanionLevel.savPlayer files must be checked against world references

Failure signalCharacter resetOften means the server created a new identity

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?

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.

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.

Safe player change plan

Identify the exact player through file ID, PlayerUID, GUID, and world references. List owned Pals, guild membership, and base links in the impact preview. Block export when any reference points to a missing identity.

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.

SAFE

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.

FAQ

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?

No. The current UI does not expose player fields. A future narrow change still requires preserving the rest of the record and every world reference.