Palworld just crossed 40 million players on July 8, 2026, two days before the official 1.0 release on July 10. The milestone dropped on Steam in a short community update: 2.5 years of growth, a look back at every major patch, and a nudge toward the 1.0 launch trailer. If you host a Palworld dedicated server, the next 72 hours are the busiest window this game has ever seen. Here is what changed, what to expect at launch, and exactly what to do to keep your server smooth through it.
The 40 Million Milestone (July 8, 2026)
Pocketpair confirmed the number in a Steam news post at 04:57 UTC on July 8. That is roughly 8 million new players since the previous public milestone (32 million, reported earlier this year), and it lands right on top of a 30% off Steam Summer Sale discount that has been running since June 25. Both together mean a huge wave of first-time buyers is about to try multiplayer with the 1.0 build sitting one patch away.
The milestone matters for server owners because the two spikes will stack: sale buyers coming in over the weekend, then the 1.0 launch on Thursday pulling everyone back in for the new content. Pocketpair is clearly leaning into it, with the "Bucky looks back" retrospective video, a new cinematic trailer, and the Palworld × Windrose Steam bundle all live at the same time.
What Palworld 1.0 Actually Brings on July 10
The 1.0 build wraps up the early access roadmap Pocketpair confirmed back on June 5. The headline additions we already know about:
- World Tree endgame area with new boss encounters and endgame Pals
- Palworld 1.0 achievements across combat, breeding, exploration, and multiplayer
- Save version bump: 1.0 saves are not backward-compatible with 0.7.x clients, so mixed-version join attempts will bounce
- Cinematic trailer content hinted at in the June 5 reveal (final zone reveal, story bookend)
We will publish the full breakdown once the 1.0 patch notes hit on July 10, but the practical takeaway now is that this is a major-version drop, not a routine content update. Expect roughly 12 to 30 GB in new files, a mandatory dedicated server binary swap, and a first-boot delay while your Pals and bases migrate.
What This Means for Your Server
If you rent a Palworld dedicated server, you are about to hit a three-day stretch where everything is at once: bigger player counts than the game has ever seen, an unavoidable version bump, and mods breaking on day one. Here is the honest checklist we send our own customers.
Before July 10
- Take a manual backup of your world save. Do not trust auto-backups for a version bump. Grab the
Saved/SaveGamesfolder over SFTP and store it locally. - Note your active mods list. UE4SS / Unreal-based Palworld mods usually break on major-version bumps until authors update. Save your mod list somewhere you can rebuild it, then remove all mods before updating to 1.0.
- Check your RAM headroom. Palworld's memory footprint scales with the map. 8 GB is the practical floor for a 1.0 server; 16 GB is comfortable for 8 to 16 players.
- Warn your players. Post the July 10 update window in your Discord. First-boot after the update is a 5 to 15 minute save migration, so a "server is down, back at X" heads-up prevents panic pings.
On July 10
- Do not press update while players are online. Announce a wipe of active sessions 30 minutes ahead, then update. A rushed update is how corrupt saves happen.
- Update Pterodactyl egg first, then the game files, then restart. The 1.0 build likely ships as a new SteamCMD update; if the panel exposes a "reinstall" button, use it rather than incrementally patching.
- Expect a slow first startup. 5 to 15 minutes is normal for a save migration. Do not restart the server thinking it hung.
- Only re-enable mods after 24 hours. Wait for authors to confirm 1.0 compatibility on their Nexus / GitHub pages. A broken mod on launch weekend can wipe your world.
Launch Weekend Load
If you were on the smallest tier before, this is the weekend to bump one step up. 40 million players and a 30% off sale means the friends who bounced off Palworld last year are back, and they will all want to play at once. A 4 to 6 GB tier gives you the headroom to survive a full 8-player group plus a new World Tree boss without the tickrate collapsing.
Was It Worth the Wait?
The honest answer is that Palworld 1.0 is not the reveal of a brand new game. It is the version where a chaotic early access experiment finally becomes a finished product. What you get on July 10 is a survival craft game that has been iterated on 15+ times, playtested by 40 million people, and is now sitting at a stable feature set with a real endgame and a real ending. For a co-op host, that means far fewer save-breaking updates going forward, more mods that will stay compatible, and a much better first hour for your friends when they try it for the first time.
Host Your Palworld Server on DoomHosting
If you are spinning up a Palworld server for launch weekend, DoomHosting's Palworld servers are one-click ready with SteamCMD auto-updates, full FTP for your saves, DDoS protection, and instant setup. We run Ryzen 9 hardware across North America and Europe, so your friends get low ping either side of the Atlantic. Servers can be resized without wiping, so if you start small and outgrow it after the 1.0 rush, you can bump RAM in one click.
40 million players is a very good problem for Pocketpair to have. It is a slightly harder problem for anyone running a server. Get your backup done today, hold off on updating mods until authors confirm 1.0, and your Thursday launch will be uneventful in exactly the right way.
