launch radar
Palworld 1.0 (July 10, 2026): Full Launch and What It Means for Dedicated Servers
After two and a half years in Early Access, Palworld hit 1.0 on July 10, 2026. Pocketpair calls it the biggest update ever - the World Tree, the new floating island of Sunreach, 72 new Pals, and reworked power progression through the new Mutation and Awakening systems. For server owners there is real news too - and one widely reported feature that quietly never shipped. Here is what actually landed, what didn't, and what to do with your server before you hit update.
What 1.0 actually is
Palworld launched into Early Access in January 2024 as the strangest success story of the decade: 25 million units in a month, a lawsuit from a Japanese rights-holder, and a long run of "can Pocketpair keep shipping" doubt-cycles. The answer arrived on July 10, 2026, when the game left Early Access. Pocketpair confirmed the date at Summer Game Fest 2026 and framed 1.0 as the largest content drop in the game's history. By launch Palworld had passed 40 million players; 1.0 is free for existing owners (the game stays $29.99). A correction to our earlier version: no paid game DLC is announced - the "Dawn of Palpagos" product dated July 30, 2026 is the first booster set of the physical Palworld trading card game, and a farming spin-off (Palfarm) is in development.
The headline additions, confirmed in the official 1.0 changelog:
- The World Tree. A mystical new region and the story heart of 1.0, home to a new endgame - and the place you gather Radiant Gems for the new Awakening system.
- Sunreach. A mysterious new island floating in the sky, reached with the new Wing Pack glider that lets you fly freely, no flying Pal required.
- 72 new Pals. The roster grows to 287 in total.
- Mutation and Awakening. Two new ways to push Pals past their old ceiling - a breeding rework plus a gem-fuelled Awakening path (more below).
- PvP mode. You can now progress main missions in PvP, a first for Palworld, and Pocketpair adjusted dedicated-server default settings to suit it.
- Dedicated-server changes. In-game voice chat, improved guild roles, and optimised multiplayer performance all shipped for hosts - and, notably, the widely reported "server clustering" did not (covered next).
With the 1.0 build now live, the full patch notes are public - so the list above is what actually shipped, checked against the official changelog rather than pre-launch speculation. That distinction matters this time, because one of the most-repeated pre-launch claims did not survive contact with the changelog.
Dedicated servers at 1.0: what shipped (and what didn't)
Start with the myth, because it is the one server owners kept asking about. In the run-up to 1.0, multiple outlets - Dexerto among them, echoed across hosting blogs - reported that Palworld would add ARK-style server clustering: linked dedicated servers, cross-server travel, a shared Pal Box across worlds, and a combined population above a single server's cap. It was the single most requested feature for community admins.
It isn't usable. The official 1.0 changelog contains no clustering, no linked servers, and no cross-server transfer - and no player-cap change either, and it was never on Pocketpair's published roadmap. One caveat an evidence-first site should note: the 1.0 server binary does carry cluster-related fields (ClusterNode, ClusterGroupIndex), so the groundwork exists - but it's absent from PalWorldSettings with no documented way to configure it, so there's no supported way to run a cluster today. If you have been sizing a cluster topology or budgeting a hub-and-worlds layout, stop: a Palworld dedicated server in 1.0 is still a single self-contained world, exactly as it was in Early Access.
What 1.0 did ship for dedicated servers is smaller but real, and genuinely useful if you run a community:
- In-game voice chat. Voice chat you switch on in the dedicated server's world settings. Note the platform caveat: it is unavailable on the Microsoft Store / WinGDK build.
- Improved guild features. Guilds now support multiple roles with per-role permissions - real moderation and delegation tooling for a community server, instead of one flat member list.
- Optimised dedicated-server processing. Pocketpair reworked server-side performance for better behaviour with many players and improved overall stability - the change most likely to matter on a full box.
- PvP-ready defaults. With main missions now playable in PvP, the dedicated-server default settings were adjusted for PvP play, so decide your ruleset before you open the doors.
None of that changes the fundamental sizing math. One server is still one world, so if you want to host more people you scale the box, not a cluster - the per-instance numbers in our Palworld dedicated server requirements guide still apply, and the 32-player default cap is unchanged.
Crossplay and platforms at 1.0
1.0 launched simultaneously on PC (Steam and Microsoft Store), Xbox Series X/S, Xbox One, and PlayStation 5. For server owners, the platform story is the usual Palworld nuance rather than a clean "everyone plays together."
PC and Xbox have supported crossplay through dedicated servers; PS5 is part of the launch line-up, but PlayStation cross-platform behaviour historically depends on the platform-holder agreements, so it is the detail most likely to carry platform-specific caveats. If crossplay is core to your community, read our crossplay dedicated server setup piece - the PC and Xbox path is well-trodden, and we will fold in the PS5 specifics as they settle.
Mutation and Awakening
Breeding has already been through one rework. The original "shake the box" RNG gave way in 2025 to explicit trait inheritance, where each parent carries up to four traits and IVs that pass to offspring on weighted odds. 1.0 adds Mutation on top of that: breeding now carries a low chance of producing a Pal stronger than the parents would normally allow - a mutated egg - alongside better inheritance when you are stacking multiple passive skills. It rewards deliberate breeding programs rather than replacing them.
Running parallel to breeding is Awakening, a separate strengthening path. You gather Radiant Gems in the new World Tree region and spend them to push a Pal further past its normal limits - an endgame sink that gives the World Tree a mechanical reason to exist beyond the story.
For multiplayer specifically, the thing to watch is shared breeding infrastructure on dedicated servers: communal breeding farms where several members contribute parents and harvest offspring. That pattern predates 1.0, and Mutation only makes a well-run community breeding operation more valuable, since a lucky mutated line is now something worth chasing together.
What server owners should do before you update
A full launch is a player-count event first and a technical event second. Both matter for hosts.
- Delete your old mods first - this one is not optional. Pocketpair explicitly warns that you must manually delete old mods before updating to 1.0; disabling them is not enough. Skip this and you risk crashes and corrupted, unloadable saves. Archive the previous build, remove the mod files, then update - and assume a heavily-modded server needs a maintenance window while authors recertify for 1.0.
- Back up, then decide fresh-or-keep. Existing saves carry over, so you will not be wiped, but Pocketpair recommends a fresh world to see the World Tree, Sunreach and the rest cleanly. Take a known-good backup before the build updates, and do not auto-update a server people care about.
- Expect a surge, size for it. Full launches pull lapsed players back and bring new ones in. If your server runs near its slot or RAM ceiling today, 1.0 week is when it tips over. Build in headroom or be ready to upgrade.
- Set your new server policies. 1.0 hands you real knobs: in-game voice chat to enable in world settings, per-role guild permissions to hand out, and adjusted PvP defaults to review. Decide your ruleset before you open the doors rather than after the first complaint.
Self-host or rent
The decision does not change much at 1.0; the load profile does. A populated Palworld server wants roughly 16-20 GB of RAM, NVMe storage, and - the real bottleneck - strong single-thread CPU, because the simulation does not parallelise well. Self-hosting on a home box is viable up to around 8 players; above that, the cost-per-player math and the uptime expectations push most communities to rented hardware.
For the per-game numbers and the host-by-host breakdown - including where Supercraft, DatHost, GPortal, BisectHosting and the budget tier each fit - see our honest Palworld hosting comparison and the requirements guide. We rate hosts on evidence, not affiliation. Pocketpair's official Palworld site remains the primary source for launch specifics as patch notes drop.
FAQ
- When does Palworld 1.0 release?
- July 10, 2026. Pocketpair confirmed the full launch at Summer Game Fest 2026, exiting Early Access on PC (Steam and Microsoft Store), Xbox Series X/S, Xbox One, and PlayStation 5.
- Does Palworld 1.0 have server clustering?
- No. It was widely reported before launch - Dexerto and various hosting blogs ran with it - but server clustering is not in the official 1.0 changelog. There are no linked servers, no cross-server transfer, and no player-cap change, and it was never on Pocketpair's published roadmap. A dedicated server is still a single self-contained world.
- How many players can join a Palworld dedicated server?
- The default cap stays 32 per server (co-op host-and-play caps at 4), unchanged in 1.0. The real ceiling is single-thread CPU, RAM and network, not the config value.
- Will Palworld 1.0 wipe my existing dedicated server save?
- No - existing saves carry over. Pocketpair recommends a fresh world to see the new content cleanly, but it will not wipe you. One catch for modded servers: delete old mods manually before updating (disabling is not enough) or you risk crashes and corrupted saves. Back up first.
- Does Palworld 1.0 support crossplay?
- PC and Xbox crossplay works through dedicated servers. PS5 is part of the launch, but its cross-platform behaviour depends on platform agreements and remains the detail most likely to carry platform-specific caveats.