First: back up the save
- Copy the save folder somewhere else and name the copy with today's date and time. Do it before every fix you try.
- Don't start a new character on the broken world while you're figuring it out.
- Try fixes on a copy of the save when you can, not the original.
- On a dedicated server: run
/Saveas admin, shut the server down cleanly (/Shutdown), then copy the whole save folder and the config (admin commands).
Where saves live
- Steam (PC)
%LOCALAPPDATA%\Pal\Saved\SaveGames\<your SteamID>\<world ID>\
Paste the path into File Explorer's address bar. Steam Cloud is on for Palworld, but keep your own copy before big updates.- Xbox app / PC Game Pass
%LOCALAPPDATA%\Packages\PocketpairInc.Palworld_…\SystemAppData\wgs\
These files are encrypted. Rely on Xbox cloud saves; you can still copy the folder as a safety net.- Dedicated server
- Copy the server's whole
Pal\Savedfolder: it holds both the saves andConfig\WindowsServerorConfig/LinuxServer. - Xbox and PS5 consoles
- Saves are managed by the console and its cloud. Use the game's own Restore from Backup Data option when offered (see below).
Crashes, black screen, low FPS (PC)
- Crash on start, black screen or “corrupted data”: back up your saves first. Restart Steam, verify the game's files (how to verify on Steam), then check the game reaches its title screen before you load a world.
- Low FPS or stutter: test the same spot with the same resolution and graphics settings. Change one option at a time, and note whether it's slow everywhere or only in a busy base.
- Blurry textures: write down your texture, resolution and upscaling settings. Check whether it also happens in a second world or another graphics preset. If textures look missing, verify the game's files on Steam (how).
Missing or rolled-back saves
- Steam error, then the save is gone: check you're on the same Steam account and game version as before, copy both the local folder and anything in Steam Cloud, then look at the game's own backups. One player got a similar save back by updating the game; the original reporter was already up to date, so it's not a sure fix.
- PS5 save went back in time Unresolved: compare the times of the local save, the game's Restore from Backup Data entries and the console cloud before picking one. Progress after the newest good copy may be gone.
- Xbox autosave keeps failing Unresolved: keep any world that still works, write down the platform, game version and exact error, and test a small new world to see whether autosave fails there too.
Co-op and invites
Co-op means joining a friend's world with an invite. That's different from a dedicated server, so router port settings don't apply here.
- Invite times out (for example Steam and Xbox): check both players are on the same game version, turn on multiplayer in the host's world settings, make a fresh invite code, and try a brand-new world. If a third player can test, even better.
- Only some Xbox players time out on a server others can join: compare their game version with the server's, then try one affected player on a different network to see whether the problem follows the player, the console or the network.
Dedicated and community servers
From Pocketpair's official server settings and requirements:
- Settings seem ignored? Edit the copy at
Pal/Saved/Config/WindowsServer/PalWorldSettings.ini(orLinuxServer), with the server stopped.DefaultPalWorldSettings.iniis only a template: changing it does nothing. The folder only appears after the server has started once. - Port: UDP 8211 by default (you can change it). Your router must forward it to the server.
PublicPortsets the port shown to players, not the port the server listens on. - Consoles can see the server but can't join: 1.0.4 uses
CrossplayPlatforms, default(Steam,Xbox,PS5,Mac); the oldAllowConnectPlatformsetting is from before. Then check the port, the public address, the firewall and the router. Showing up in the list only means it was found. - Friends outside can join but players at home can't: your router probably doesn't support hairpin NAT. Pocketpair says routers without it can't connect players to a community server hosted on the same network (community server docs).
- Turn on backups:
bIsUseBackupSaveDatamakes abackupfolder and keeps 5 copies every 30 seconds, 6 every 10 minutes, 12 every hour and 7 per day. It adds disk load. - Bases disappearing?
bAutoResetGuildNoOnlinePlayersdeletes the buildings and base Pals of guilds nobody logs into, afterAutoResetGuildTimeNoOnlinePlayers. Check it on shared servers. - More workers or bases:
BaseCampWorkerMaxNum(up to 50 Pals per base) andBaseCampMaxNumInGuild(default 4, up to 10). Both raise the server's processing load. - Memory: Pocketpair recommends 16 GB; 8 GB can start but is more likely to crash from running out of memory.
- Admin: set
AdminPasswordin the settings, then type/AdminPassword yourpasswordin game. Useful commands:/Save,/Shutdown [seconds] [message],/ShowPlayers,/Broadcast message(all commands). - Community server (listed publicly): start with
PalServer.exe -publiclobby(Windows) or./PalServer.sh -publiclobby(Linux).
This is an unofficial fan page. For account or purchase problems, contact Pocketpair or your platform's support.
Last checked November 8, 2026. Unofficial fan guide, not made or endorsed by Pocketpair.