Palworld cover

Palworld multiplayer not working? Fix it here.

Open-world creature-collecting with co-op on Steam & Xbox (crossplay).

SteamXbox32 playersCrossplay ✓
Co-op type
online + dedicated server
Invite method
Steam/Xbox friends or direct-connect IP
NAT needed
Moderate or Open (Open needed to host a public server)
Ports
Steam P2P: UDP 27015–27030 · Palworld default: UDP 8211 (dedicated) · Steam datagram relay: UDP 3478 / 4379 / 4380

Crossplay: Steam and Xbox crossplay is supported but must be enabled on both sides and on the same game version.

What's happening? Pick your symptom

All Palworld co-op fix guides

Can't join friends in Palworld

Crossplay (Steam↔Xbox) needs the same patch version and the crossplay toggle on. Version drift is the usual blocker.

  1. Make sure everyone is on the same version & region — Even a one-patch difference blocks joins. Test branches, beta opt-ins, and region settings must all match.
    • Confirm all players are on the same game version (no one on a beta/test branch).
    • Match region/server selection in the game's settings.
    • If one player is on Steam and another on a different store, check the crossplay note on the game's page.
  2. Check and fix your NAT type — Strict NAT is the #1 cause of 'can't join friends'. You need Moderate or Open to host and to receive invites reliably.
    • On Steam: Settings → In-Game → check the 'NAT' indicator, or test via Steam's network settings.
    • On Xbox: Settings → General → Network settings → 'NAT type'.
    • On PlayStation: Settings → Network → View Connection Status → 'NAT Type'.
    • If Strict: enable UPnP and/or port-forward (see those fixes). Tether to a phone hotspot once to confirm — if it works there, the issue is your home router.
  3. Use the lobby / join code instead of a friend invite — Steam and platform friend-invites fail far more often than copy-paste codes. Most co-op games have a 'share lobby code' button.
    • Host creates the lobby, then copies the lobby/join code (not the friend invite).
    • Send the code in chat; the joiner pastes it into 'Join with code'.
    • If invites still fail, this bypasses the broken invite pipeline entirely.
  4. Update the game and your platform client — Mismatched patch levels prevent you from joining. Everyone must be on the same version.
    • Update the game itself (let it fully patch before launching).
    • Update Steam / Epic / Xbox app / PlayStation system software.
    • Restart the client after updating — a pending restart silently blocks matchmaking.
  5. For a dedicated server, use 'Connect to IP' with the host's public IP and port 8211 instead of the friends list.
People also search:palworld can't join friendspalworld can't join friend serverpalworld invite not working

Palworld multiplayer not working / won't connect

  1. Power-cycle your router and relaunch the game — A 30-second router reboot clears stale NAT and UPnP leases that silently break peer-to-peer connections. Fully quit the game (don't just minimise) and reopen it.
    • Unplug the router for 30 seconds, then plug it back in and wait for full sync.
    • Completely close the game (check Task Manager / Force Quit — overlays can leave it running).
    • Relaunch the game and try joining again.
  2. Enable UPnP on your router — UPnP lets the game open its own port automatically. With it off, you'll often get Strict NAT and can't host or receive invites.
    • Log in to your router admin page (usually 192.168.0.1 or 192.168.1.1).
    • Find 'UPnP' or 'Universal Plug and Play' and turn it ON.
    • Save and reboot the router, then retry the game.
  3. Port-forward the game's ports — If UPnP alone doesn't help, forward the ports manually so your router routes game traffic to your PC/console. Use the per-game port list on the game's page.
    • Note the ports listed for your game (Steam P2P uses UDP 27015–27030 and UDP 3478 / 4379 / 4380).
    • In your router, create port-forward rules (UDP) pointing to your device's local IP.
    • Set a static LAN IP (DHCP reservation) so the rule keeps working after reboots.
    • Test again — your NAT should now read Moderate or Open.
  4. Turn off VPN, proxy, and 'kill switch' tools — VPNs and routing tools reroute P2P traffic and trigger Strict NAT or total blocks. Disable them for the session.
    • Fully quit your VPN app (not just disconnect — quit it).
    • Disable any proxy in Windows Settings → Network → Proxy.
    • Temporarily uninstall 'kill switch' / firewall-overlay tools if the issue persists.
    • Retry the join with a direct connection.
People also search:palworld multiplayer not workingpalworld coop not workingpalworld online not working

Palworld connection failed / lost connection

  1. Use a wired connection to stop lag & drops — Wi-Fi jitter causes 'connection failed' and mid-session drops. A cable removes most of it.
    • Plug in Ethernet instead of Wi-Fi for the host especially.
    • If Wi-Fi only, move close to the router and use 5 GHz.
    • Close bandwidth-heavy apps (streaming, downloads) during play.
  2. Allow the game through firewall & antivirus — Over-aggressive security software flags game executables as threats and drops the connection after join.
    • Windows: Allow the game .exe through Windows Defender Firewall (Private + Public).
    • Add the game and Steam/Epic to your antivirus allow-list.
    • On Mac: System Settings → Privacy & Security → Firewall → allow the game.
  3. Verify game files (fixes corrupted installs) — A half-downloaded or corrupted file causes 'connection failed' right after joining. Verifying redownloads the broken bits.
    • Steam: Library → right-click game → Properties → Installed Files → 'Verify integrity of game files'.
    • Epic: Library → three dots → 'Manage' → 'Verify'.
    • Console: a corrupted install usually needs a full reinstall from the store.
  4. Match server region — If players pick different data-center regions, the lobby won't appear to each other. Align regions before inviting.
    • Each player opens the game's server/region picker.
    • Select the SAME region (closest to the majority).
    • Recreate the lobby after changing region.
People also search:palworld connection failedpalworld keeps disconnectingpalworld timeout connecting

Palworld crossplay not working (Steam ↔ Xbox)

  1. Enable the in-game crossplay toggle — Crossplay is OFF by default in many games. Both players must turn it on, or a Steam player simply can't see an Xbox/PS player.
    • Open the game's multiplayer / network settings.
    • Turn ON 'Crossplay' (or 'Cross-platform play') on every player's client.
    • Restart the lobby after changing it — the setting often only applies to new sessions.
    • If your platform combo isn't supported, see the crossplay note on the game's page.
  2. Make sure everyone is on the same version & region — Even a one-patch difference blocks joins. Test branches, beta opt-ins, and region settings must all match.
    • Confirm all players are on the same game version (no one on a beta/test branch).
    • Match region/server selection in the game's settings.
    • If one player is on Steam and another on a different store, check the crossplay note on the game's page.
  3. Both players must be on the same Palworld patch — a Steam-side hotfix and an Xbox update a day apart will block crossplay until both update.
  4. Check and fix your NAT type — Strict NAT is the #1 cause of 'can't join friends'. You need Moderate or Open to host and to receive invites reliably.
    • On Steam: Settings → In-Game → check the 'NAT' indicator, or test via Steam's network settings.
    • On Xbox: Settings → General → Network settings → 'NAT type'.
    • On PlayStation: Settings → Network → View Connection Status → 'NAT Type'.
    • If Strict: enable UPnP and/or port-forward (see those fixes). Tether to a phone hotspot once to confirm — if it works there, the issue is your home router.
People also search:palworld crossplay not workingpalworld steam xbox crossplaypalworld crossplay not connecting

Palworld error codes explained

VERSION MISMATCH
Players are on different patch levels. Everyone must update the game fully.
CONNECTION TIMED OUT
The host's port 8211 isn't reachable — enable UPnP or forward it.