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
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.
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.
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?
%LocalAppData%\Pal\Saved, and hit Enter.
SaveGames folder from that window
straight onto this page.
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.
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.
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.
SaveGames/<your steam id>/.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.
Every character has a player GUID. Co-op hosts are
stuck on 00000000000000000000000000000001; dedicated
servers generate one per Steam account. Skip the rewrite and you
log in on the beach with an empty inventory while your bases sit
untouched.
The converter unpacks your save in the browser, patches GUIDs in
Players/*.sav and Level.sav, drops
WorldOption.sav for server uploads, and zips the
result. Save parsing borrows from
palworld-host-save-fix,
palworld-save-tools,
and ooz-wasm for Oodle saves.
%LocalAppData%\Pal\Saved\SaveGames on
your PC.
SaveGames folder to this converter.
Select your world and the host character.
Pal/Saved/SaveGames/0/<world-id>/.
DedicatedServerName=<world-id> in
Pal/Saved/Config/WindowsServer/GameUserSettings.ini
(Linux: LinuxServer).
LocalData.sav from your old co-op folder if
your map overlay is missing.
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.
Beyond renaming the player file, we rewrite character entries, guild membership, pal ownership, and palbox/party slots so inventory and pals both land with you on the server.
Co-op worlds stash rate tweaks in this file. Dedicated
servers read PalWorldSettings.ini instead. We
remove it when you upload to a server.
Fog of war lives in LocalData.sav on your PC,
not in the world save. Copy it over after your first join
if the map looks blank.
File manager, save uploads, hardware that stays up. We host Palworld.
Palworld hosting at AleForge
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.
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.
Co-op host is …0001. Dedicated servers use
Steam-derived IDs. No rewrite means a fresh character.
No. It runs in your browser on your machine. We never receive your save files.
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.
Yes for a complete remap. Inventory lives in
Players/. Bases, guild membership, pal
ownership, and palbox/party slot references live in
Level.sav. We rewrite those player-ID
references so the dedicated server can still see your
character, pals, and guild after you join.
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.
Map discovery is client-side in
LocalData.sav. Join once, quit, then copy
it from your old co-op folder to the new server's local
save path under your Steam ID.