Patch reference: v1.0.4 (7 September 2026). Selected roster and example builds; check current in-game values.

🖥️Hosting Options Compared

Palworld in-game screenshot
Multiplayer hosts run a server-side persistent world — same world, shared progressSource: Palworld Wiki · official media
OptionCostPlayersBest for
Official serverFreePublicCasual testing
Host multiplayer from game menuFreeUp to 4 (host must stay online)Friends' co-op
Dedicated server (self-host)Free (you run it)Unlimited-ishPersistent community servers
Rented dedicated server$$$High24/7 uptime, large groups

🔌Ports & Connection

Default ports
  • Game port: 8211 (UDP) — the main game traffic.
  • Query port: 27015 (UDP) — server browser listing.
  • REST API: 8212 (optional, admin commands).

⚠️ Open these in your firewall/router and port-forward them to the server machine for external players.

⚙️Dedicated Server Config (key settings)

PalWorldSettings.ini essentials
SettingExampleWhat it does
ServerNameMy PalworldShown in server browser
ServerPasswordsecret123Private access
MaxPlayers32Capacity cap
PlayerDrops0 (off)Death penalty toggle
ExpRate1.5XP multiplier
PalCaptureRate1.0Capture odds multiplier

💡 Edit config only while the server is stopped, then restart. Backup the file before big changes.

👥Role Division for Co-op

Divide and conquer
  • Builder: manages base layout, power, automation.
  • Farmer/Breeder: runs the food loop and breeding lines.
  • Explorer/Catcher: scouts spawns, captures new species, feeds Paldeck XP to everyone.
  • Combat lead: handles towers and world bosses with the best team.

💡 XP and progress are shared in co-op worlds — divide by interest, not by power.

🔧Common Connection Issues

Fix checklist
  1. "Connection timed out" → port forwarding / firewall rules missing.
  2. Server not in browser → query port (27015) closed.
  3. Version mismatch → update server to match client build.
  4. Lag spikes → check server CPU; Palworld is single-core heavy, more RAM ≠ smooth.
  5. Password rejected → ServerPassword must be set identically in config (no trailing spaces).

FAQ

Can console players join dedicated servers?

No — dedicated server hosting is a PC feature, and console players connect to hosted sessions instead. Crossplay pools mix console and PC players in the same session types, so a mixed group's options are: the PC member hosts, or the group rents a PC-side server everyone joins. Check the connection section below for the port and NAT settings either route needs.

The host's save is the world's save

On hosted co-op, the world lives in the host's save file: if the host cannot play, the group cannot play, and a host's corrupted save is everyone's loss. The practical rules: the host backs up saves on a schedule, the group agrees on session cadence, and if the world matters, graduate to a dedicated server before the save gets big rather than after it gets fragile.

Which hosting option fits which group

Four-player co-op through the host's game is the zero-setup default and the right choice for a one-session group; a dedicated server is the right choice once your world outlives the host's free evenings, because it keeps the world online without anyone's PC. The trade is cost and configuration time versus permanence, and the config section below covers the settings that matter on a dedicated box.

NAT, ports and the connection checklist

Most connection failures are router questions: hosted sessions need the host's ports forwarded (the port section below lists the defaults), UPnP helps where it works, and both sides should test on a fresh session before blaming the game. Dedicated servers move the port question to the host's firewall and the config file — the key settings section covers the three lines that matter.