01
Upload the world archive
Use one ZIP, TAR.GZ, or TGZ archive containing exactly one world folder with Level.sav and its Players folder.
Palworld server hosting
Palworld migration guide
Move your Palworld co-op world without abandoning the host character.
Copying a co-op save to a dedicated server can leave the original host looking like a new player. Metrly turns the risky part into a guided, backup-first workflow: validate the archive, install it safely, detect the host’s temporary identity, convert it, and verify the result.
Why ordinary file copying fails
The host-character trap
Palworld stores the co-op host under a special player identity. On a dedicated server, that same person joins with a normal player identity. The world, guild, Pals, and bases may be present while the host appears to start over.
The original world is preserved behind a completed locked backup.
Only a detected player save can be selected as the host’s temporary identity.
The converted world must pass save-boundary checks and server-health verification.
A failed managed change triggers an automatic rollback attempt.
The managed path
From co-op save to healthy dedicated world
These are the actual controls built into Metrly’s Palworld management flow. No live world is replaced merely because a file was uploaded.
02
Validate before touching live files
Metrly inspects the archive, identifies a co-op or dedicated source, and rejects unsafe paths, links, duplicate files, and ambiguous worlds.
03
Back up, install, and verify
After your confirmation, Metrly creates a locked safety backup, installs the validated world, restores the prior process state, and checks server health.
04
Reconnect the co-op host
The original host joins once and creates Palworld’s temporary character. Metrly detects that new player save and converts the host identity after another locked backup.
Choose the right path
What can move—and what still needs an archive
Where players can join from is not the same as where a world save can be exported from. Metrly only installs files it can inspect and validate.
Current locationInputMetrly path
Current location
World already installed on this Metrly server
Input
No upload required
Metrly path
Have the original host join once, autosave, then scan and convert the active world.
Current location
Co-op or single-player world on another computer
Input
World archive required
Metrly path
Upload for validation, install behind a locked backup, then complete host conversion.
Current location
Dedicated world from another host
Input
World archive required
Metrly path
Upload for validation and install. Host conversion is only for co-op-host identity.
Current location
Console or cloud save without accessible world files
Input
Not an import source
Metrly path
Cross-platform joining does not make a cloud-only save exportable. Do not claim a migration until you have a valid archive.
Archive checklist
Validate the package before migration day
A clean archive makes the migration reversible and keeps stray files away from the active world.
Exactly one Palworld world folder
Level.sav at the expected world boundary
The matching Players folder
ZIP, TAR.GZ, or TGZ format
No traversal paths, links, or device files
No more than 5 GiB compressed
No more than 20 GiB expanded
No more than 200,000 files
Questions before you move
Palworld migration FAQ
The visible answers below are also the answers published in this page’s structured data.
Why can the original Palworld co-op host lose access to their character after migration?
A co-op host is stored under a special player identity. On a dedicated server, the same person joins under a normal player identity, so copying files alone does not reconnect that new identity to the host character.
What does a Palworld world archive need to contain for Metrly?
The archive must contain exactly one world folder with Level.sav and its Players folder. Metrly accepts ZIP, TAR.GZ, and TGZ archives and validates the archive before replacing the live world.
Does cross-platform play mean every platform can export a world to Metrly?
No. The platforms allowed to join a server and the places from which a save can be exported are separate questions. Migration requires an accessible world archive that passes validation.
What happens if a Metrly Palworld import or host conversion fails?
Metrly requires a completed locked safety backup before installation or conversion. It verifies the changed world after startup and attempts to restore the prior world automatically if the managed operation fails.
Product behavior on this page is based on Metrly’s current validated import and conversion implementation. For dedicated-server fundamentals, see Pocketpair’s official server documentation. Palworld and Pocketpair are trademarks of their respective owners.
Keep the world. Change where it runs.
Ready to move your Palworld world?
Start the Palworld deployment path. Your source page and acquisition context are preserved so we can measure whether this guide leads to a running, paying, retained server.