Palworld 1.0.1 Patch Notes: Save-Data Loss Fix & World Protection Guide

One day after the massive Palworld 1.0 launch, developer Pocketpair shipped v1.0.1 (build 1.100.619) on 15 July 2026 to fix four critical bugs – headlined by a save-data loss issue that could silently wipe progress after certain operations. This guide breaks down exactly what the hotfix addresses, how to update on PC, Xbox, PS5 and dedicated servers, and the practical steps to back up your world so you’re never caught out by a bug again.

Palworld v1.0.1 is a small bug-fix hotfix released 15 July 2026 (console/store label 1.100.619), one day after the game’s full 1.0 release on 10 July 2026. Version 1.0.1 is a hotfix update focused on resolving several issues affecting save data, status effects, and game stability across multiple platforms. It contains no new content – just four targeted fixes addressing critical bugs that surfaced immediately after the launch surge. Pocketpair moved fast on this one, and for good reason: the most serious fix addresses a bug where save data could be “unintentionally discarded after certain operations.”

The patch is a small download across all platforms – PC (Steam), Xbox Series X|S, Xbox Game Pass, and PlayStation 5 – and applies automatically for most players. If you’ve been playing since 1.0 dropped, updating to 1.0.1 is critical to protect your world from silent save corruption. Pocketpair hasn’t spelled out exactly which operations triggered the loss, but the fix is live and active now, and the developer has confirmed no recovery method exists for worlds already affected by the bug.

The four fixes are: possible save-data loss after certain operations; Burning status lingering after touching a Campfire; PlayStation-only title-screen save error; and Xbox-only ~30-second freeze after fast travel. Here’s the breakdown in a comparison table:

Most players will receive the update automatically when they launch the game or restart their console. Here’s how to confirm you’re running 1.0.1 and how to manually trigger the update if it hasn’t pulled yet.

PC/Steam

Steam features automatic and manual downloading of game updates. When an update is available, Steam will usually schedule the update later. You can bypass this scheduled date by manually downloading the update from the Library Menu. Open your Steam library, locate Palworld, and press the blue Update button to start the update download and installation. If no update button appears, restart Steam entirely – the client sometimes needs a reboot to detect new patches. To enable or disable auto-updates for Palworld going forward, right-click the game in your library, select Properties, go to the Updates tab, and choose your preference.

Xbox (Console & Game Pass)

To turn auto-updates for Palworld on or off, go to the Installation Queue menu and select the Install Options button. Select the Enable automatic updates checkbox from there to turn the auto-update feature on or off. If you’ve got auto-updates enabled, the console will pull 1.0.1 overnight or when you next launch Palworld. To force the update immediately, press the menu button on Palworld’s tile, select Manage game and add-ons, then Updates – if 1.100.619 is available, it will show here and you can start the download manually. If your game hasn’t updated, restart the client/console to pull 1.100.619.

PlayStation 5

PS5 auto-updates are typically enabled by default when the console is in rest mode. If you’re playing while connected to PSN, the update will download in the background. To manually check, highlight Palworld on the home screen, press Options, and select Check for Update. The patch will appear as version 1.100.619 in the download queue. After installation, the PS5-specific title-screen save error is resolved and you should be able to return to the main menu without repeated save failures.

Dedicated Server

If you’re running a Palworld dedicated server – whether self-hosted or through a provider like DatHost or ZAP-Hosting – you need to manually update the server software. For SteamCMD-based servers, stop the server process completely, then run the update command targeting Palworld’s app ID (1623730) and restart. Most hosting providers offer a one-click update button in their control panel; check your provider’s file manager or support docs for the exact steps. Always back up your world save before applying the update – the save folder structure hasn’t changed, but any major patch carries a small risk of compatibility issues with existing worlds, especially if you’re running mods or custom configurations.

Manual backups are the only guaranteed protection against save loss – even with 1.0.1 installed, hardware failure, mod conflicts, or file corruption can still erase progress. Here’s the process for every platform.

Understanding the exact file paths helps if you need to troubleshoot save issues, transfer worlds between platforms, or recover from corruption. Here’s the breakdown by platform.

PC / Steam

Windows/Steam: C:Users(your system username) > AppData > Local > Pal > Saved > SaveGames or %USERPROFILE%/Local/Pal/Saved/Savegames. Inside the SaveGames folder, you’ll find a subfolder named after your Steam 64-bit ID – a long numeric string – and inside that, one or more world folders with alphanumeric names. Each world folder contains your character data, base structures, tamed Pals, and world state. Steam Cloud backs up your saves automatically. It’s useful against accidental deletion – but not against corruption. If a save becomes corrupted, Steam Cloud syncs the corrupted file and overwrites the clean one. A separate manual backup on local or external storage is not optional for anyone with significant playtime.

Xbox Game Pass

Xbox Game Pass: C:Users(Your system username)AppDataPackagesPocketpairInc.Palworld_ad4psfrxyesvt SystemAppDatawgs. Xbox Game Pass saves to a Windows Store packages directory – not the standard AppData path. The wgs folder contains all save files for the Game Pass version. Note that Game Pass and Steam saves are not cross-compatible by default – you cannot swap save files between the two PC versions without third-party conversion tools.

Dedicated Server

For Windows-based dedicated servers installed via SteamCMD, the save path is typically inside the server installation directory: C:Program Files (x86)SteamsteamappscommonPalServerPalSavedSaveGames. If you use a hosted provider such as DatHost or ZAP-Hosting, download your save through their file manager or via FTP on a regular schedule. Hosted servers have no automatic backup by default – if the provider has an outage, your world save is gone unless you have a local copy. Always keep a local backup of any hosted server world.

Honestly, the news here isn’t great. Pocketpair has not published an official recovery tool or documented workaround for worlds lost to the pre-1.0.1 save-data bug. If you experienced unexpected progress loss before this patch, check your most recent save file before assuming data is gone permanently. Here’s what you can try:

Check Your In-Game Backup History

Palworld automatically saves the world’s data and makes a backup every 30 seconds. The most recent backups can then be restored from the World Select Menu. To restore a save data that the game has already automatically made a backup of, select the world you want to restore data to from the World Select Menu. Then, select the Restore from Backup Data button at the bottom-left corner of the screen. This feature only exists on the Steam version – Xbox Game Pass players rely on cloud saves managed by the Xbox ecosystem.

Check Steam Cloud for an Older Sync

After a crash, Steam may ask whether to use your Cloud Save or Local Save. Choose the version with your most recent progress. If you’re unsure, make a copy of both saves before selecting one. Open the SaveGames folder, compare file timestamps, and try loading the Steam Cloud version if your local file is corrupted or missing. Be aware that if the corrupted save synced to the cloud before you noticed, both copies may be bad.

Accept the Loss and Start Fresh (With Protection This Time)

If the world is genuinely gone and no backup exists, there’s no official way to resurrect it. The best path forward is to start a new save and immediately implement a backup routine. The 1.0 full release includes a reworked story progression, rebalanced Pal spawns, and new endgame systems that make a fresh playthrough a genuinely different experience – so you’re not just replaying the same grind. For faster progression on a new save, check our Palworld 1.0 leveling guide to hit level 80 and tier 10 work suitability efficiently.

Myth: Steam Cloud Is a Full Backup

Steam Cloud is useful for syncing saves across devices and recovering from accidental deletion, but it’s not against corruption. If a save becomes corrupted, Steam Cloud syncs the corrupted file and overwrites the clean one. You need a separate manual backup stored outside Steam’s ecosystem to protect against file corruption or Steam-side issues.

Myth: The Game’s Auto-Backup Handles Everything

Palworld generates automatic in-game backups every 30 seconds, added in patch 0.1.5.0. These live inside a backup/world/ subfolder in each world’s directory, named with timestamps. That’s fantastic for rolling back the last few minutes or recovering from a bad decision, but it doesn’t protect against hardware failure, drive corruption, or a catastrophic bug that wipes the entire save directory. Manual external backups remain essential.

Myth: Dedicated Server Hosts Back Up Your World Automatically

If you use a hosted provider such as DatHost or ZAP-Hosting, download your save through their file manager or via FTP on a regular schedule. Hosted servers have no automatic backup by default – if the provider has an outage, your world save is gone unless you have a local copy. Check your provider’s backup policy and assume no automatic protection unless explicitly documented. Download your world save weekly at minimum.