Host save fix
Most failed migrations stop here. Swaps the host's
…0001 ID for the one tied to your Steam account —
including the player filename Linux dedicated servers expect.
Palworld Tools
Palworld Save Converter
Move a co-op or single-player world to a dedicated server, or pull a server world back to local. Full player-ID remap — character, inventory, party, palbox, guild, bases, and pal ownership. Runs in your browser; files stay on your PC.
🔒 Your save stays on your PC - nothing uploads
Co-op → dedicated usually keeps your bases and pals, but the
host character wipes. Co-op hard-codes the host as
…0001; dedicated servers give each Steam account its
own ID. This tool does the host save fix: it rewrites those GUIDs
in your files.
Drop your SaveGames folder, pick the world and
character, add your SteamID64, download the zip. Nothing installs,
nothing uploads. You don't need a blank character on the server
first if you're on Steam.
Conversion direction
How do I migrate a dedicated server world back to local co-op play?
- Choose Dedicated Server → Co-op.
-
Add the server world from
Pal/Saved/SaveGames/0/. -
Pick the character who should become the co-op host. The
converter remaps that player ID to
00000000000000000000000000000001. - Create a new co-op world in Palworld, load in once, and quit so the game writes a blank folder.
-
Download the ZIP and copy
Level.savandPlayers/into that new world folder under%LOCALAPPDATA%\Pal\Saved\SaveGames\<steam id>\. - Launch that world. Other player files in the ZIP keep their IDs.
1. Add your save files
Drag & drop your save folder here
Tip: drop the whole SaveGames folder so we can
list worlds by name. A single world folder or loose
.sav files work too.
Where do I find my save?
-
Press Win+R, paste
%LocalAppData%\Pal\Saved, and hit Enter. -
Drag the
SaveGamesfolder from that window straight onto this page. - Worlds show up by in-game name. Pick the one you want.
On a dedicated server the world lives in
Pal/Saved/SaveGames/0/.
You can also upload a single world folder, or
Level.sav plus Players/ files.
2. Select a world
3. Choose which character to move
Pick who becomes the co-op host. We'll remap their ID to
…0001 and bundle every other player file from
this dedicated world into the download.
Pick whose progress should carry over. On co-op worlds that's
almost always the host (…0001). Step 4 can remap the
whole party.
4. Prepare your new co-op slot
Co-op worlds reserve 00000000000000000000000000000001
for the host. Create a fresh local world first so Palworld
writes a blank folder, then replace its files with this package.
- Create a new co-op world in Palworld, load in once, and quit.
- Click below to download the converted save for your picked host.
- Copy the ZIP contents into that new world's folder under
SaveGames/<your steam id>/. - Launch Palworld — your party's player files travel with the world.
4. Map your character to the server (Co-op → Dedicated Server)
Dedicated servers key off your Steam account, not the co-op host slot. Look up your Steam profile, pick your SteamID64, and we'll show the player ID the server will use.
Same Steam account you'll use to join the server.
Target player ID
Search and select a SteamID64 to preview the new player ID
Already joined the server? Paste an existing player ID
For when you already joined the server once and have a
player file or GUID to merge into.
How the Palworld save converter works
The AleForge Palworld Save Converter moves a co-op host save to a
dedicated server by replacing the co-op host GUID,
00000000000000000000000000000001, with the player ID
derived from the selected Steam account. The converter runs in your
browser, patches player GUID references in
Players/*.sav and Level.sav, removes
WorldOption.sav for server uploads, and downloads the
converted files as a ZIP. Without the GUID rewrite, a dedicated
server can create a fresh character with an empty inventory while
the original bases remain in the world save. AleForge maintains this
converter. Save parsing borrows from
palworld-host-save-fix,
palworld-save-tools,
and ooz-wasm for Oodle saves.
How to migrate Palworld co-op to a dedicated server
-
Back up
%LocalAppData%\Pal\Saved\SaveGameson your PC. -
Upload your
SaveGamesfolder to this converter. Select your world and the host character. - Enter your SteamID64. The tool computes your server player GUID automatically.
-
Download the converted ZIP and extract it on your dedicated
server at
Pal/Saved/SaveGames/0/<world-id>/. -
Set
DedicatedServerName=<world-id>inPal/Saved/Config/WindowsServer/GameUserSettings.ini(Linux:LinuxServer). -
Start the server and join with the same Steam account. Copy
LocalData.savfrom your old co-op folder if your map overlay is missing.
Palworld save migration guide
Full Level.sav remap
A full AleForge Palworld Level.sav remap updates
more than the player filename: it rewrites character entries,
guild membership, pal ownership, and palbox and party slots that
reference the former co-op host ID. Inventory is stored in
Players/, while these world-level references in
Level.sav help the dedicated server continue to
associate your character with its pals, guild, palbox, party,
and bases.
- Character entries
- Guild membership
- Pal ownership
- Palbox and party slots
WorldOption.sav
Co-op worlds stash rate tweaks in this file. Dedicated
servers read PalWorldSettings.ini instead. We
remove it when you upload to a server.
Map & waypoints
If the Palworld map is dark after migrating to a dedicated
server, the missing discovery data is stored locally in
LocalData.sav, not in the world save. Join the
migrated server once, quit Palworld, then copy
LocalData.sav from the old co-op folder to the new
server local-save path under your Steam ID
(%LOCALAPPDATA%\Pal\Saved\SaveGames\<your steam id>\<server world id>\)
to restore the map overlay and discovered areas.
Need a Palworld server?
File manager, save uploads, hardware that stays up. We host Palworld.
Palworld hosting at AleForgePalworld save converter FAQ
How do I move my Palworld co-op world to a dedicated server?
Upload the save here, pick world + character, enter
SteamID64, download the zip, put it in
Pal/Saved/SaveGames/0/, and set
DedicatedServerName to the folder name. On Steam
you do not need a blank character on the dedicated server
first: SteamID64 is enough, and the converter derives the
server player ID.
Do I still need a throwaway character on the server?
Not if you're on Steam. Your SteamID64 is enough — we
derive the server player ID. Paste a GUID manually for
Xbox, PlayStation, Mac crossplay, or -nosteam.
Why does my character reset on a dedicated server?
A Palworld character resets when a co-op world is moved to a
dedicated server because the co-op host GUID is always
00000000000000000000000000000001, while the server
assigns a player ID from the Steam account. Without that GUID
rewrite, the server can create a fresh character with an empty
inventory while the original bases remain in the world save.
Is my save file uploaded anywhere?
No. It runs in your browser on your machine. We never receive your save files.
What is the Palworld host save fix?
Remaps the co-op host GUID to what your dedicated server
expects for your Steam account. A full migration also
rewrites that ID everywhere it appears in
Level.sav — character entries, guild data, pal
ownership, and palbox/party slots — not only the player
filename.
Will my inventory, pals, party, palbox, guild, and bases survive the migration?
Yes for a complete remap. Inventory is stored in
Players/. A full Level.sav remap
rewrites character entries, guild membership, pal ownership,
and palbox and party slots that referenced the co-op host ID,
so the dedicated server can still associate your character
with its pals, guild, palbox, party, and bases.
How is this different from a partial host-GUID rename?
Renaming only Players/…0001.sav (or rewriting a
few labeled GUIDs) often leaves guild, ownership, and
container-slot IDs pointing at the old co-op host. That can
load your inventory while leaving the party and palbox empty.
A full conversion remaps the player ID across character
entries, guild blobs, pal ownership, and
CharacterContainerSaveData slots in
Level.sav.
Why is the map dark after migrating a Palworld save, and how do you fix it?
The missing discovery data is stored locally in
LocalData.sav, not in the world save. Join the
migrated server once, quit Palworld, then copy
LocalData.sav from the old co-op folder to
%LOCALAPPDATA%\Pal\Saved\SaveGames\<your steam id>\<server world id>\
to restore the map overlay and discovered areas.