Existing saves can continue
Pocketpair's official Version 1.0 changelog says players can continue their adventures with existing save data. A mandatory wipe is not part of the official release guidance.
That confirmation does not guarantee that every MOD-dependent item, Pal, quest state, base layout, or server tool will behave exactly as it did in Early Access. Back up first. Old-world behavior after the reworked systems needs in-game verification.
Pocketpair recommends a new character
Pocketpair recommends starting fresh to experience the Version 1.0 changes more fully. The main story, mission flow, world progression, Pal balance, capture systems, bases, raids, and other systems were revised together, so a new character encounters those changes in their intended order.
This is a recommendation, not a requirement. Players who value an established collection or shared world can preserve it and decide after testing a backup.
When to keep your old save
- You want to preserve long-built bases, collections, breeding work, or multiplayer history.
- Your save did not depend on unsupported MOD content, or you have a safe test copy.
- Your group understands that missions, rewards, Pal skills, base work, map boundaries, and raid behavior changed.
- You are willing to inspect the world carefully before making irreversible changes.
When to start fresh
- You want to follow the reworked story and progression from the beginning.
- You have not played for a long time and want to relearn combat, capture, Pal, and base systems.
- Your old save contains MOD-created Pals, items, structures, quests, or other dependencies.
- Your multiplayer group wants one clear ruleset and equal progression from the start.
What server owners should do before updating
- Stop the server cleanly and copy the full save and configuration to a separate backup location.
- Record the current game build, server build, world settings, startup arguments, MODs, plugins, and management tools.
- Remove old MOD files and loaders rather than only disabling them.
- Update the server and confirm that clients use the matching Version 1.0 build.
- Test login, saving, restart persistence, one base, and one multiplayer session before reopening the main world.
MOD warning
Pocketpair warns that old MOD files can cause crashes, save corruption or loss, failed loading, and blocked quests or events. Disabling a MOD in a manager may leave files or loaders in the game directory, so the official pre-update guidance calls for manual removal and a clean, unmodded launch test.
Save data containing MOD-dependent content may not work correctly after those MODs are removed. Only reinstall a MOD after its creator confirms Version 1.0 compatibility, then test one MOD at a time.
Backup checklist
- Create a backup before the first Version 1.0 load, not after a problem appears.
- Keep at least one copy outside the active game or server folder.
- Label the backup with the date, platform, world name, and pre-update version.
- For servers, save the world data, player data, configuration, startup command, and MOD list together.
- Confirm that the backup is present and readable before updating.
- Do not overwrite the only backup during early testing.
Source note
This guide is based on Pocketpair's official Palworld v1.0 Steam changelog and official Version 1.0 MOD warning. It separates the confirmed ability to continue existing saves from recommendations that still depend on a player's platform, MOD history, and world state. Those practical outcomes need in-game verification.