Palworld 1.0 — Wipe or Keep Your Server's World?
Last verified: August 20, 2026. Saves carry over (one exception: v0.7.3-and-earlier save data does not) and configs need no migration. Pocketpair's community manager put it plainly: “You do not need to wipe your data for Palworld 1.0, but you should.” This guide covers the call either way.
Now that Palworld 1.0 is live with a map that roughly doubles, the server-owner decision is still the same: do you wipe, or carry the old world across? The patch notes confirm saves carry over and configs need no migration, so old worlds load and play. A fresh map may show the new regions more cleanly, while a continuing world preserves bases and community history. This guide lays out both outcomes and the middle paths so the call is made deliberately rather than during a rushed restart. For everything else in the update, see the full Palworld 1.0 guide.
The compatibility reality (what we know, what we don't)
- Known: 1.0 adds the World Tree region and the Sunreach sky island; together they roughly double the playable landmass. The breeding rework (Mutation and Awakening) is in, dedicated servers gained in-game voice chat, guild roles, and optimized processing, and — crucially for this decision — saves carry over with all 88 pre-1.0 settings intact, so configs need no migration — with one hard boundary from the changelog: save data from v0.7.3 and earlier is no longer carried over, so servers dormant since those old builds must start fresh. Server Clustering is groundwork only: the 1.0 server binary carries cluster fields, but it's absent from the changelog and PalWorldSettings, with no supported config path yet. Details: our Palworld 1.0 feature reference.
- Unknown: whether existing worlds generate the new regions fully, partially, or not at all. Palworld's track record is friendly — previous updates kept old worlds loadable — but doubling a map is a different class of change, and survival-game precedent says big new terrain favors fresh worlds.
- Planning stance: assume old worlds will load and play, and test whether the new content works for your existing world before deleting anything. A fresh map is an option, not a recovery plan.
The case for wiping
- The content is the map. 1.0's headline is geography. A world that cannot fully generate the second island misses the update's center of mass.
- A fresh world is easier to explain to new players. The 1.0 launch brought a large audience, and a listing that clearly says "Fresh 1.0 world" gives newcomers an obvious starting point. A year-old world with established empires needs stronger onboarding.
- Equal footing keeps newcomers. Veterans with end-game bases and perfect breeding lines are, to a day-one joiner, scenery. Resets are how public servers stay joinable.
The case for keeping
- The history is the product. For a closed friend-group server, the bases, the breeding projects, the shared landmarks are the game. Freshness is worth less than continuity to a community that is not recruiting.
- The friendly precedent. If 1.0 follows Palworld's own update history, old worlds will load fine and some or all new content will be reachable. Wiping preemptively could mean deleting a year for nothing.
- You can always wipe later. Keeping a verified backup and continuing for a while preserves the option to reset later; deleting the only copy of a world does not.
The middle paths (often the right answer)
- Run a second server for a trial period. Keep the old world running and open a fresh 1.0 world alongside it. After a few weeks, move the community's attention wherever it settled. This is the lowest-risk option for established communities that still want growth.
- Clustering is not an option yet. Server Clustering isn't a usable 1.0 feature: it's absent from the changelog and from PalWorldSettings, and Pocketpair hasn't published how to configure it — though the 1.0 server binary does carry cluster fields (ClusterNode, ClusterGroupIndex, connection settings), so the groundwork exists with no supported config path today. Until that changes, the realistic middle paths are the second server above and the archive below — don't promise cluster transfers to your players.
- Archive with honors. Final backup, a download link for the old world, a screenshot night before the wipe. Communities accept resets that are treated as chapter endings instead of deletions.
The post-1.0 checklist (both paths)
- Backup, restore-tested, before any new update or reset. Keep the old world and the fresh world as separate, clearly labelled backups.
- Announce the decision before you act. Whatever you choose, the community accepting it depends on hearing it in advance with reasons.
- Mods: delete, don't disable. Pocketpair's official warning is that disabling old mods "is not enough" — stale Early Access mod files can cause 1.0 crashes and corrupted saves. Re-add compatible mods one at a time after the server loads cleanly.
- Keeping the world? Check the config too. Configs need no migration, but if you have a heavily tuned pre-1.0
PalWorldSettings.ini, the free 1.0 Config Migration Doctor verifies it against 1.0 and adds the 31 new keys with sane values. - Fresh-world servers: make the promise clear. Say whether the world is fresh, what ruleset it uses, and how you handle resets. Keep the capacity sized for your expected peak and the larger 1.0 map.
Opening a fresh 1.0 world or a second server next to your old one? Rent a Palworld dedicated server with Supercraft and choose the setup that fits your community now.
Looking for managed Palworld server hosting? Supercraft runs Palworld dedicated servers with daily backups, instant setup, and 4 region options.