Palworld does not use one universal save folder. A Windows Steam world is normally under %LocalAppData%\Pal\Saved\SaveGames, while Microsoft Store or Xbox app data uses a different package-managed location. Dedicated servers keep worlds with the server installation or configured save directory. Identify the platform and active world before replacing files. Copy the whole candidate folder to another drive first, because a newer empty world or an incorrect cloud choice can overwrite the copy you meant to restore.
Start with the Version of Palworld You Actually Launch
Check whether the game starts through Steam, the Xbox app or Microsoft Store, or a dedicated-server executable. A shortcut alone may not answer this; open the launcher and inspect the installed library. Steam and Xbox builds can coexist on one PC, yet their storage layouts are not interchangeable. A world found under the wrong platform may be a valid save that your current installation never reads.
Also decide whether the missing progress belongs to a single-player or co-op host, a community server, or a dedicated server you control. A client that joins someone else’s server does not own the server’s complete world data. Local files may hold player-side information, but restoring them cannot replace a world that exists only on the remote host.
Before exploring hidden paths, close Palworld and its server process. Leaving either running can create a new save while you are copying files. Pause cloud synchronization only after making a protected copy of every plausible local folder.
Find a Steam World and Match Its Identifier
Press Windows+R, enter %LocalAppData%\Pal\Saved\SaveGames, and press Enter. Inside, you may see a folder associated with a Steam account, followed by one or more long world identifiers. Do not rename those identifiers. Open each candidate and compare its modified date with the last successful session.
A useful world folder normally contains more than one recognizable component. Treat the directory as a set: world-level data, player records, configuration-related files, and backups must remain associated with the correct identifier. Copying only the newest-looking file can leave a world incomplete or attach the wrong player record.
Use timestamps as evidence, not as the only rule
The most recently modified folder is often active, but an unwanted new world can be newer than the missing good one. Compare several timestamps and folder sizes. A long-running world usually has a different history and data volume from a world created during troubleshooting. Label your copies with the source path and inspection date instead of changing files inside them.
Check the built-in backup tree
Palworld save sets may contain backup directories with dated copies. Preserve the entire backup tree before selecting a version. Choose a snapshot from before the unwanted change, then copy it to a separate test area. Never paste a backup over the only live world until the candidate has been protected and its components have been checked.
Handle Xbox and Microsoft Store Saves as Package Data
The Xbox app version stores data beneath a Microsoft package location rather than the straightforward Steam tree. Package names and internal containers can change, and the visible files may not use friendly world names. Avoid renaming, moving, or mixing container files by guesswork. First confirm the signed-in Xbox account and whether cloud synchronization has completed.
If the game shows older progress, disconnecting immediately may not be the best first move. Close the game, preserve accessible local package data, and record the account and sync state. Then check whether the expected world appears on another device. A working remote copy is safer than experimenting with opaque container files.
When local package data is accessible, copy its complete relevant directory while the game and Xbox services are not writing to it. Restoring one isolated container from a different timestamp can break the relationships among files. If permissions prevent access, do not take ownership of the entire WindowsApps or Packages tree. Broad permission changes can damage app servicing and are not needed for a careful backup.
Locate Dedicated-Server Worlds Before Editing Configuration
A dedicated server usually keeps save data relative to its installation and configuration, but hosting panels, containers, command-line options, or a changed service account can redirect that location. Start with the server’s startup command and configuration. Record the working directory and any custom save path. Stop the server cleanly before copying its world.
Check whether an update script installed a second server directory. The service may now launch from the new location while the older world remains intact under the previous folder. Compare logs and modification times rather than moving the old directory into the new installation immediately.
For hosted servers, use the provider’s backup and snapshot tools before downloading or restoring individual files. A local client scan cannot recover data that was stored only on the provider’s hardware. Contact the host promptly if a remote world was deleted, because its retention policy determines which backups still exist.
Choose Between a Backup Restore and Deleted-File Recovery
If the correct world folder exists and built-in backups are present, test those copies first. Keep the live folder, selected backup, and a working test copy separate. Restore all related components from the same timestamp. Mixing a current player record with an older world can produce ownership or loading problems.
If the entire local world was deleted, check the Recycle Bin, File History, cloud version history, and any manual backup. The Windows option to restore a previous file version may expose an earlier folder snapshot. Use Open or Copy when available instead of replacing the current parent folder immediately.
Once deletion is confirmed, stop playing or installing updates on the affected drive. New world saves and downloads can overwrite recoverable space. SSD TRIM can reduce the chance of recovering deleted data, so act promptly without assuming any tool can guarantee a result. For basic path navigation, see how to open AppData.
Recover a Deleted Local Palworld World with Drecov
PandaOffice Drecov is Windows data recovery software for logical loss from PCs, hard drives, SSDs, external drives, USB devices, SD cards, and memory cards. Its read-only recovery mode uses Quick Scan and Deep Scan, then lets you filter, locate, and preview supported results before saving them to a healthy destination. Lost Partition Recovery and Crashed PC Recovery address related logical-loss conditions. For Palworld, Drecov is relevant only when locally stored world or player data was deleted or became inaccessible. It cannot retrieve a server-only world from a remote host, fix game compatibility, repair physical damage, or reconstruct overwritten data.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Step 1: Open Drecov and select the original save volume
Close the game and server, stop new writes, and prepare another healthy drive. Do not install Drecov on the partition that held the missing save. Open Drecov and select the original Windows volume containing the Steam, Xbox package, or locally hosted server folder. Stop if the device clicks, disconnects, changes capacity, or reports serious read errors.
Step 2: Run Quick Scan and inspect the platform path
Begin with Quick Scan. Browse toward the former Palworld path and compare long world identifiers, dates, sizes, and folder structure. Select complete related folders rather than a single recognizable file.
Step 3: Use Deep Scan only while the source is stable
Move to Deep Scan if Quick Scan misses the world and the storage device remains stable. Older candidates may no longer show their full original path, so use timestamps, sizes, and recognizable save components together. Stop when new read errors or disconnections appear.
Filter by former path, filename, file type, size, and date. Preview representative supported files when possible. A successful preview proves only that sample; it does not certify the consistency of a complete multi-file world. Recover several plausible versions when the destination has room.
Step 5: Recover elsewhere and verify a test copy
Recover to the healthy destination, never to the source. If the selected world is absent there, inspect Drecov Folder and Recovery Folder. Preserve the recovered set, then make a separate test copy for the live save path. Launch offline, load the world, check the player and base, create a new test save, and confirm its timestamp. Only then should you resume cloud synchronization or replace server data. General deletion cases are covered in the deleted-file recovery guide.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Verify the World Before Making It Authoritative
A world that reaches the title screen has not passed a complete test. Confirm the expected character, guild, base, inventory, map progress, and recent activity. Travel to another area and create a fresh save. Close the game normally, reopen it, and load that new save again. For a server, connect with a test client and verify that the server writes to the directory you identified.
Keep the original live folder, the chosen backup, and the recovered output until the test succeeds after a restart. When cloud sync is re-enabled, read the timestamps before choosing a side. The official Palworld news and support site is the appropriate place to check current game notices that may affect saves or server behavior.
Conclusion
The answer to “where are Palworld saves stored” depends on the platform and who hosts the world. Identify Steam, Xbox, or server storage first; compare world identifiers and timestamps; and protect complete folders before restoring a backup. If stable local save data was deleted, Drecov can scan the original volume and recover candidates to another drive. Test the recovered world offline before it replaces a live or cloud copy.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
