Pal SaveEditor
Runs locallyOpen a save

Co-op identity migration

Move a co-op world to a dedicated server without resetting characters.

The world files are only half the migration. Palworld Save Editor treats the co-op host, client players, guilds, bases, and Pal ownership as one identity map before any target folder is touched.

Scan local files Try the safe sample
Most fragileCo-op hostHost identity often needs explicit confirmation
Move togetherLevel + PlayersCopying only one side breaks cross-file references
Success checkActual loginStructural validation cannot replace in-game verification

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

Why characters reset on a dedicated server

The target server can assign a different player identity even when the world loads correctly. The old character data may remain in the Players folder while the login selects a new GUID.

02

Build an identity map before copying

List every source player file, known display name, PlayerUID, GUID, guild membership, and target identity. Mark the co-op host as unresolved until the mapping is explicitly confirmed. The dry-run should show how many players map automatically and which records need a decision.

03

Verify the migrated world

After starting the dedicated server, each player should verify level, inventory, Pals, guild, bases, technology, and map progress. Keep the source and target backups until all important accounts have logged in successfully.

SAFE

Task checklist

  1. 01Stop both source game and target server.
  2. 02Back up the full source world and target slot.
  3. 03Map all player identities, with the host handled separately.
  4. 04Verify each migrated account in game before retiring backups.
FAQ

Questions people ask before touching the save

Why does the world load but my character starts at level 1?

The server loaded the world but selected a new player identity. Restore the backup and fix the identity mapping before continuing.

Can I migrate only Level.sav?

No. The Players folder and metadata must travel with the matching world state.