Palworld Multiplayer Won't Connect? Here's the Fix
In 2026 most Palworld 'can't join' issues come down to a version mismatch, a crossplay setting difference, or a blocked port on a dedicated server. Fastest fix for co-op: the host opens the world, everyone confirms they're on the exact same game version and the same platform's crossplay setting, then friends join via the in-game Invite Code (or Steam invite). For a dedicated server, forward UDP 8211 and connect by direct IP:8211.
Palworld dedicated server — exact port, config file & save path
- Game port (UDP)
8211- Config file
PalWorldSettings.ini (copy from DefaultPalWorldSettings.ini)- Save path
Pal\Saved\SaveGames\0\<WorldID>- RCON port (optional)
25575- Common cause of failed join
Edited DefaultPalWorldSettings.ini instead of PalWorldSettings.ini (game ignores the template), or 8211 not forwarded as UDP
Last verified: September 2026
Error codes
Can't join friend's co-op session
The invite/join attempt times out before entering the world
Cause: Version mismatch or a crossplay platform difference (Steam vs Game Pass vs Xbox).
- Both players confirm the same game version (a Steam/Xbox update on one side blocks the join).
- Match the platform: Steam and Xbox/Game Pass builds don't always co-op together — both on Steam is most reliable.
- Host: raise the co-op player limit and re-open the world after the friend has fully launched the game.
- Use the in-game Invite Code or Steam overlay invite rather than searching.
Failed to connect to dedicated server / connection timeout
The client can't reach the dedicated server process
Cause: UDP 8211 not forwarded, server on a different build, or wrong IP.
- Host: forward UDP port 8211 to the server's local IP and allow PalServer.exe through the firewall.
- Update the dedicated server (SteamCMD) to the same build as clients after every game patch.
- Join via 'Join Multiplayer (Dedicated Server)' and enter the public IP:8211.
- Check ServerPassword in PalWorldSettings.ini matches what players type.
Fixes that work for most Palworld errors
- Match versions: host and every player on the identical Palworld build.
- Match platform: prefer everyone on Steam; cross-platform (Steam <-> Xbox/Game Pass) co-op is fragile.
- Co-op: host uses Invite Code / Steam invite instead of the server browser.
- Dedicated server: forward UDP 8211 and allow PalServer.exe through the firewall.
- Keep the dedicated server updated to the same build as clients after each patch (SteamCMD app 2394010).
- Verify game files (Steam > Properties > Installed Files > Verify integrity) on both sides.
- Restart the world/server after everyone has finished updating to the same version.
FAQ
Why can't I join my friend in Palworld?
Usually a version mismatch or a crossplay platform difference. Confirm you're both on the exact same game version and, ideally, both on Steam, then have the host re-open the world and send an Invite Code.
What port does a Palworld dedicated server use?
UDP 8211 by default. Forward it to the server's local IP and allow PalServer.exe through the firewall, then connect via the dedicated-server option using the public IP:8211.
Can Steam and Xbox/Game Pass players play Palworld together?
Cross-platform co-op between Steam and Xbox/Game Pass is unreliable and often fails to connect. The most dependable setup is everyone on the same platform, preferably Steam.
Other games
- No Man's Sky Errors — No Connection to Matchmaking, Failed to Join Lobby & Fixes
- ARC Raiders Error Codes — AREX0024, ARMR0002 & Connection Fixes
- Battlefield 6 Error Codes — 1:85008S, 1:85009S, 1:8600 Connection Fixes
- Hollow Knight: Silksong Crash & Error Fixes — Won't Launch, Startup Crash
- War Thunder Error Codes — 81110013, 80130182, 80022B0F Connection Fixes
- Clair Obscur: Expedition 33 Errors — Fatal Error, LowLevelFatalError & Crash Fixes
- Deadlock Error Codes — Failed to Connect to Match, Matchmaking Stuck & Fixes
- Diablo 2 Resurrected Errors — Failed to Connect, Connection Interrupted & Fixes