Guide

How to Do a Palworld Dedicated Server Setup After 1.0

Kuma
Kuma
November 19, 2026 at 12:10 AM · 6 min read
Clan MemberMajor General
Palworld battle scene with armed Pals and players in a grassy field

How to Set Up a Palworld Dedicated Server After 1.0

The fastest route to a working Palworld dedicated server setup: install Steam app 2394010 (Palworld Dedicated Server) with SteamCMD using an anonymous login, or pull Pocketpair's official Docker image on a Linux host. The game client (app 1623730) is not needed on the server machine. Boot it once so the config folder is created, stop it, then edit Pal/Saved/Config/WindowsServer/PalWorldSettings.ini (LinuxServer on Linux) instead of the default template. Open UDP 8211, not TCP, on every firewall layer. Budget 4+ CPU cores, 16GB RAM (32GB+ for larger servers) and an SSD.

Three sheep Pals manning machine guns behind sandbags
Three sheep Pals manning machine guns behind sandbags

What the server needs before you install

Pocketpair's documented baseline is a 64-bit Windows or Linux host with 4 or more CPU cores, 16GB of RAM (32GB+ once your player count climbs), and a fast SSD. An 8GB machine will boot, but it raises the risk of out-of-memory crashes, and low-performance storage may corrupt save data outright.

The dedicated server is free and separate from the game. Players need the game to join; the server does not need it installed. The server files are roughly 20 GB (PalGuide) — other guides put them at about 12 GB, so budget disk space generously.

Component Minimum Recommended (16-32 players)
Operating system Ubuntu 22.04 LTS / Debian 11 Ubuntu 24.04 LTS (64-bit)
CPU 2 vCPU (high single-thread clock) 4 vCPU, 3.0 GHz+ per core
RAM 8GB 16GB (server can use 10-14GB under load)
Storage 40GB SSD 60GB+ NVMe SSD (saves grow over time)
Network 50 Mbps up, static or port-forwarded IP 100 Mbps+ symmetrical
Server app ID 2394010 (dedicated server, free, anonymous login) -
Client app ID 1623730 (the game itself, required only to play) -

The default player cap is 32, against 4 in invite-based co-op. If your group is small, lower ServerPlayerMaxNum rather than paying for hardware you will not use.

Install the server: a numbered walkthrough

The steps below are the canonical SteamCMD path on Linux. The Steam client and Docker routes are labelled alternatives to specific steps.

  1. Update the host and install prerequisites. On Ubuntu or Debian, enable the multiverse repository and the i386 architecture, then install SteamCMD (sudo add-apt-repository multiverse; sudo dpkg --add-architecture i386; sudo apt update; sudo apt install steamcmd).
  2. Ensure you have SSH access to the machine with a user that has sudo privileges.
  3. Install SteamCMD into that user's home directory and run it once so it self-updates.
  4. Log in anonymously. Anonymous login is all the dedicated server requires; no Steam account or game purchase is needed.
  5. Install app 2394010 to a known directory, for example ~/palserver. This is the roughly 5.9 GB download.
  6. Boot the server once so it generates the config folder tree, then stop it cleanly. The INI does not exist before this first run.
  7. Copy the default config into place. Copy the contents of DefaultPalWorldSettings.ini into Pal/Saved/Config/LinuxServer/PalWorldSettings.ini.
  8. Edit the settings you need, server name, passwords, player cap, using the tables further down.
  9. Open the firewall. Forward and allow UDP 8211 at every layer, plus 27015/UDP for the server browser.
  10. Create a systemd unit so the server survives crashes and reboots, then start it and verify.

Alternative: Steam client. If you own Palworld on Steam, the server appears as a separate tool in your library. Enable tools in the library filter if it does not show, install Palworld Dedicated Server, and launch it once. Use this instead of steps 3-5; the first-boot, config and firewall steps are identical.

Alternative: Docker. Pocketpair publishes an official image and sample Compose files. Use the Compose file on a Linux host instead of steps 3-5. Docker Desktop is explicitly deprecated by Pocketpair because of storage-IO risk to save data, do not run your production server through it.

If SteamCMD throws steamclient.so: cannot open shared object file, the SDK library is not linked. Create the library directory and symlink the bundled library into it, then relaunch:

mkdir -p ~/.steam/sdk64
ln -s ~/steamcmd/linux64/steamclient.so ~/.steam/sdk64/

A minimal systemd unit keeps the server running unattended:

[Unit]
Description=Palworld Dedicated Server
After=network.target

[Service]
Type=simple
User=palworld
WorkingDirectory=/home/palworld/palserver
ExecStart=/home/palworld/palserver/PalServer.sh -publiclobby
Restart=on-failure
RestartSec=10

[Install]
WantedBy=multi-user.target
Port Protocol Purpose Required?
8211 UDP Main game port, players connect here Yes
27015 UDP Steam query, lists the server in the community browser Recommended
25575 TCP RCON, remote console administration Optional
8212 TCP REST API, programmatic admin control Optional

What 1.0 changed for server admins

Palworld left Early Access on July 10, 2026, and the fundamentals held: same app ID, same INI, same default port. Know which keys are live before you open the file.

  • RCON is deprecated in Pocketpair's documentation in favour of the REST API (TCP 8212, requires RESTAPIEnabled=True). RCON still works, but Pocketpair's docs mark it deprecated and recommend the REST API instead.
  • The old performance flags should be left unset. In v1.0 and later, leaving -useperfthreads, -NoAsyncLoadingThread and -UseMultithreadForDS off may improve performance. Older guides that tell you to set all three are out of date.
  • Crossplay uses CrossplayPlatforms (the current official default list is Steam, Xbox, PS5 and Mac, per VPSCost); AllowConnectPlatform is obsolete.
  • Server clustering arrived as the headline admin feature, alongside dedicated-server optimisations and safer saves.
  • Also shipped, though not admin-relevant: in-game voice chat, guild roles and permissions, and a default difficulty matching single-player Normal.

Migration notes if your world predates 1.0: saves carry over. A save older than v0.7.3 may spawn players outside the world boundary, and the "Emergency Escape" option in the Options menu fixes that. Delete old mod files before updating, because disabling mods is not enough, leftover loaders still get loaded. If you run mods, our How to Mod Palworld in 2026 covers the Workshop and UE4SS side of it.

Open UDP 8211 - the failure that makes servers unjoinable

The game port is UDP 8211 and can be changed with -port=. Opening only TCP 8211 produces the classic broken server: it starts cleanly, logs look healthy, and nobody can connect.

Every firewall layer must agree. That means the host OS firewall, the router port forward (if you host at home), the VPS control panel and any cloud security group. Miss one and the server stays invisible.

Open 27015/UDP as well so the server shows in the community browser. Direct-connect by IP still works if the query port is closed, but it is a fallback, not a fix.

Keep 8212/TCP and 25575/TCP closed to the internet. The REST API documentation states plainly that it is not designed to be exposed directly. If you need remote admin access, tunnel it.

Edit the right PalWorldSettings.ini

The config directory only exists after the first boot. Start the server once, let it generate the folder tree, then stop it. Copy the contents of DefaultPalWorldSettings.ini into PalWorldSettings.ini and edit that file.

Edits to DefaultPalWorldSettings.ini are ignored at runtime. The live file is Pal/Saved/Config/WindowsServer/PalWorldSettings.ini on Windows and LinuxServer on Linux. Restart after every change.

Essential settings to change first

Setting Default What it does Recommended
ServerName "Default Palworld Server" Name shown in the server browser Something descriptive
ServerDescription "" Browser description text Rules, wipe schedule, Discord link
ServerPassword "" (open) Password players need to join Always set one on a public IP
AdminPassword "" Password for in-game admin commands Set this, or admin commands are rejected
ServerPlayerMaxNum 32 Maximum concurrent players 10-20 for most groups

Difficulty and progression

Setting Default What it does Recommendation
DayTimeSpeedRate 1.0 Day length multiplier 1.0-1.5
NightTimeSpeedRate 1.0 Night length multiplier 0.8-1.0
ExpRate 1.0 XP gain multiplier 1.5-3.0 for casual servers
PalCaptureRate 1.0 Catch rate multiplier 1.0-1.5, avoid going above 2.0
PalSpawnNumRate 1.0 Wild Pal spawn density 0.8-1.2, lower on weak hardware
DamagePlayerMultiplier 1.0 Damage dealt to players 1.0 normal, raise for hardcore
DamagePalMultiplier 1.0 Damage dealt to Pals 1.0 normal, tweak for PvP balance

Base and guild settings

Setting Default What it does Recommendation
BaseCampMaxNum 3 Max bases per guild 3-5, more bases means more load
BaseCampWorkerMaxNum 15 Pals per base 15-20, higher values raise CPU usage significantly
DropItemMaxNum 3000 Max dropped items in world 3000-5000
GuildPlayerMaxNum 20 Max players per guild 4-10 for private servers

Launch arguments

Argument Effect
-players=32 Sets the maximum participant count
-port= Changes the listen port from the default 8211
-publiclobby Lists the server under Community Servers

Let Xbox and PlayStation players in

A plain server is joined by IP address. That works for Steam players and nobody else. Launching with -publiclobby lists the server under Community Servers, which is the only route in for Xbox and PlayStation players.

SteamCMD servers are Steam-crossplay only, so Game Pass players on a private server are better served by invite co-op. Confirm CrossplayPlatforms includes the platforms your group actually plays on before you advertise the server.

Admin access, backups and update hygiene

Set AdminPassword in the INI, restart, then authenticate in-game with /AdminPassword. Without that step, every admin command is rejected, which is the single most common "broken admin" complaint.

Command What it does
/Save Force-save the world immediately
/Shutdown [seconds] [message] Graceful shutdown with a warning, e.g. /Shutdown 60 "Restarting"
/Broadcast [message] Message every player on the server
/BanPlayer [SteamID] Ban a player by Steam ID
/KickPlayer [SteamID] Kick a player, they can rejoin
/TeleportToPlayer [SteamID] Teleport yourself to a player
/TeleportToMe [SteamID] Teleport a player to you
/ShowPlayers List connected players with Steam IDs and ping
/Info Server uptime, tick rate and player count
Last updated: November 19, 2026 at 12:10 AM

Comments

0 Comments

Join the Conversation

Share your thoughts, ask questions, and connect with other community members.

No comments yet

Be the first to share your thoughts!