This guide assumes you already installed a Palworld dedicated server. It distinguishes server launch arguments such as -port= from gameplay and administration settings in PalWorldSettings.ini. Mixing up port parameters or copying old performance flags can cause trouble after Palworld 1.0.
Where is PalWorldSettings.ini?
Pocketpair documents the active configuration here:
- Windows:
steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini - Linux:
steamapps/common/PalServer/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
Directories are created once the server has run at least once. If the active INI does not exist, copy the included template.
Windows PowerShell:
Copy-Item steamapps\common\PalServer\DefaultPalWorldSettings.ini steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.iniLinux:
cp steamapps/common/PalServer/DefaultPalWorldSettings.ini steamapps/common/PalServer/Pal/Saved/Config/LinuxServer/PalWorldSettings.iniEditing DefaultPalWorldSettings.ini itself does not change the running server's settings. Modify the active copied file under WindowsServer or LinuxServer.
Palworld ports and launch arguments
The dedicated server listens on port 8211 by default. Change the actual listening port with -port=. Pocketpair also documents these options:
| Launch argument | Purpose |
|---|---|
-port=8211 | Choose the server's listening port |
-players=32 | Set maximum players using a launch argument |
-publiclobby | Make it a community-listed server |
-publicip=x.x.x.x | Specify the public IP address for a community server |
-publicport=xxxx | Describe an externally exposed community-server port; does not change the listening port |
Important: -publicport does not replace -port. To actually alter the port the process listens on, use -port.
Important PalWorldSettings.ini options
| Setting | Meaning |
|---|---|
ServerName | Server name |
ServerDescription | Server description |
ServerPassword | Password required to join |
AdminPassword | Password for administrative rights |
ServerPlayerMaxNum | Maximum joining players |
CrossplayPlatforms | Permitted game platforms; source default lists Steam, Xbox, PS5 and Mac |
bIsUseBackupSaveData | Enable world backups; increases disk activity |
RESTAPIEnabled / RESTAPIPort | Enable and configure the REST API listener |
RCONEnabled / RCONPort | Enable the legacy RCON service, which Pocketpair marks deprecated |
AllowConnectPlatform is explicitly marked unavailable in the developer documentation. Use CrossplayPlatforms for platform permissions.
REST API rather than legacy RCON
Pocketpair marks RCON deprecated and recommends the REST API for new administration tools. Its RCON reference warns that support will stop in a future update.
Do not expose the REST API directly to the public internet. Pocketpair warns this can allow unauthorized server manipulation and recommends LAN-restricted access. Use a strong admin password and narrow network access controls.
Settings that affect performance
BaseCampMaxNumInGuild: default 4, maximum 10; increasing it adds processing load.BaseCampWorkerMaxNum: up to 50 Pals per base; larger values add load.PalSpawnNumRate: higher spawn rates can degrade performance.MaxBuildingLimitNum: limits structures per player;0means no limit.
If investigating poor performance, change one value at a time and note the previous setting.
Avoid outdated performance launch flags
Older server instructions often recommend -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS. Pocketpair's updated documentation notes that for Palworld 1.0 and later, leaving these arguments out may improve performance. Do not copy them into every new launch script without testing.
Common configuration mistakes
- Changes have no effect: Confirm you modified the active
PalWorldSettings.ini, not the default template. - Connection uses the wrong port:
-publicportis not the listening port;-portis. - Conflicting player limits: Pocketpair documents
-players=andServerPlayerMaxNumbut does not specify precedence when they disagree. Avoid different values. - Outdated crossplay parameter: Replace the unavailable
AllowConnectPlatformwithCrossplayPlatforms. - Old admin integration: Plan to use the REST API rather than the deprecated RCON service.
Back up and revert changes
Before changing the configuration, copy a known-working PalWorldSettings.ini. Restore it if a new setting causes a problem. For world backups, Pocketpair documents bIsUseBackupSaveData, which creates a backup folder inside saved-game data and includes automatic backups at several intervals. Enabling it increases disk load.
For the co-op modes and platforms, see our Palworld game profile.