Palworld 1.0 — Wipe or Keep Your Server's World?
Last verified: June 12, 2026. Palworld 1.0 launches July 10; world-compatibility specifics are part of the unreleased patch notes — this guide is built to survive either answer.
Every Palworld server owner has the same conversation scheduled for the next four weeks: 1.0 lands July 10 with a map that roughly doubles — do we wipe, or do we carry the old world across? Pocketpair has not published world-compatibility details (the patch notes are literally labeled "Top Secret"), so this guide does what a server owner actually needs: lays out the decision under both outcomes, the honest arguments each way, and the middle paths — so the call gets made calmly in June, not in a Discord argument on launch night.
The compatibility reality (what we know, what we don't)
- Known: 1.0 adds the World Tree region and a second major island; together they roughly double the playable landmass. Genetic Recombination (new breeding) and Server Clustering (linked dedicated servers) are confirmed. Details: our 1.0 confirmed-facts page.
- 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 assume the new content will be at its best on a fresh map. Both halves of that have been true for nearly every comparable launch.
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.
- Launch day is the recruiting event of the year. The 1.0 wave will be the biggest player influx since January 2024, and those players search for fresh worlds. A "Fresh 1.0 — started July 10" listing fills itself; a year-old world with established empires does not.
- 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. A keep decision is reversible in August; a wipe is not. When genuinely torn, the asymmetry favors keeping — if you are willing to give up the launch-wave recruiting window, which does not come back.
The middle paths (often the right answer)
- Run a second server for launch month. Old world keeps running; a fresh 1.0 world opens July 10 and catches the wave. After a month, merge the community's attention wherever it settled. Lowest-risk option for established communities that still want growth.
- Cluster them. 1.0's confirmed Server Clustering may make "old world + new world, one community" a supported configuration rather than two separate servers. Mechanics are unpublished — if clustering allows character or Pal transfer, this becomes the best of both worlds. Decision point: read the actual patch notes July 10 before promising it 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 pre-launch checklist (both paths)
- Backup, restore-tested, before the June 25 Tides of Terraria patch and again before July 10. Two update events in fifteen days means two chances for a bad migration.
- Announce the decision by early July. Whatever you choose, the community accepting it depends on hearing it in advance with reasons.
- Mods: expect two breakage windows. The 1.0 one will be bigger. Critical-mod servers should plan to run vanilla-ish for launch week rather than delay the update.
- Fresh-world servers: be live by launch morning. The wave hits immediately. Settings dialed, listing written, capacity sized for double your usual peak.
Opening a fresh world for the 1.0 wave — or a second server next to your old one? Rent a Palworld dedicated server with Supercraft and be listed before July 10.
Looking for managed Palworld server hosting? Supercraft runs Palworld dedicated servers with daily backups, instant setup, and 5 region options. Plans from $5.99/mo.