Guide Palworld

Palworld 1.0 Dedicated and Community Server Setup

Install Palworld's Windows or Linux dedicated server using SteamCMD 2394010, enable community listings for consoles, open UDP 8211, and configure crossplay and backups.

palworld-1-0 game artwork for dedicated server instructions
Source: coop-legends.de

Overview

Palworld supports dedicated servers on 64-bit Windows and Linux. Pocketpair distinguishes an ordinary Dedicated Server, joinable by address and port, from a Community Server, which is also registered in the public server browser. This distinction matters for Xbox and PlayStation 5 players, who use the community-server list to connect. The reviewed configuration defaults to CrossplayPlatforms=(Steam,Xbox,PS5,Mac).

Self-host or rent a Palworld server?

Self-hosting allows full control over the server's ports, patches, world backups and administrator settings. Renting can remove much of that operational burden. For console groups, confirm that a host supports Community Server mode and the required crossplay platforms before paying. Also compare RAM, backups, file access, REST API options and world import. Prices and availability require a current provider check.

Hardware requirements

Pocketpair recommends a CPU with at least four cores and 16 GB RAM, with over 32 GB advised for larger communities. Eight GB can sometimes start the server but carries a higher out-of-memory crash risk. Prefer an SSD. Windows and Linux must be 64-bit.

Pocketpair provides an official Docker image too, but specifically discourages Docker Desktop for this deployment because of storage I/O performance and potential save-data problems.

Install with SteamCMD

The dedicated-server Steam App ID is 2394010. On Windows or Linux, install/update it with:

steamcmd +login anonymous +app_update 2394010 validate +quit

Start PalServer.exe on Windows, or ./PalServer.sh on Linux. Run it at least once to create the configuration directories before copying in an active settings file.

Dedicated Server versus Community Server

Both modes use the same dedicated-server executable. The difference is public browser registration: add -publiclobby to advertise a Community Server. A normal Dedicated Server is accessed with the IP address and port. Xbox and PS5 clients join via the community-server browser according to Pocketpair's documentation.

Configure network port and player slots

The default is UDP 8211. Use -port=8211 to choose the actual listening port and -players=32 to set an example 32-player limit. Allow the configured UDP port through the firewall and forward it when necessary behind a router.

For public listings, add -publiclobby. Pocketpair also documents -publicip and -publicport when automatic public endpoint discovery is unsuitable. -publicport does not change the port on which the process listens; -port does.

The example -players=32 is not stated as a universal hard capacity ceiling in the developer's arguments documentation.

Avoid copying obsolete performance flags

Older guides often recommend -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS. The current Pocketpair documentation says that since Palworld 1.0, omitting these parameters can improve performance. Do not include them uncritically in new start scripts.

Use the active PalWorldSettings.ini

Do not edit DefaultPalWorldSettings.ini in place; Pocketpair says changes there are not treated as the running server's configuration. Copy the provided template to:

  • Windows: Pal\Saved\Config\WindowsServer\PalWorldSettings.ini
  • Linux: Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

For port, INI, player limits and advanced settings, see our Palworld 1.0 settings and ports guide.

Crossplay platforms

CrossplayPlatforms configures the allowed platform types. Pocketpair lists Steam, Xbox, PS5 and Mac by default. The older AllowConnectPlatform parameter is no longer supported by the reviewed guide.

Backups and administration

Set bIsUseBackupSaveData to enable automatic world backups if desired; Pocketpair warns it increases storage activity. Admin tools can use RESTAPIEnabled and RESTAPIPort.

RCON is deprecated and planned for removal in a future update, so new automation should use REST rather than treating RCON as permanent. Do not publicly expose the REST API directly: Pocketpair recommends LAN-restricted access and a strong admin password to reduce the risk of unauthorized server control. Store independent world backups outside the active server.

Mod support

Pocketpair lists bAllowClientMod to permit clients using mods, but its current dedicated-server documentation supports server-side mods on Windows only. It warns that mods can cause crashes and corrupted saves. Make a backup before enabling mods and troubleshoot a vanilla setup first.

Connect to the server

For an ordinary dedicated server, enter its address and port in the server menu. For a Community Server, find it under the community list by server name. On a home network, missing hairpin NAT may prevent using your own public address from inside the same LAN even when remote users can connect.

Server not appearing?

Check that the process runs, client and server builds agree, UDP 8211 or your configured port is reachable, and -publiclobby is enabled for a Community Server. Also inspect public IP/port identification. Console users need the community-server listing; pure direct-IP access is not the documented Xbox/PS5 method.

Use Pocketpair's -players= launch argument; -players=32 is an example value, not a documented universal hard maximum.

It uses the dedicated-server application but is additionally listed in the public community server browser through -publiclobby.

Yes, when the server is configured for their crossplay platforms and advertised as a Community Server, which is the documented console joining method.

UDP port 8211.

PalWorldSettings.ini under WindowsServer or LinuxServer. The default template is not read as the active config.