The most reliable way to host a Palworld dedicated server is to install the official server package on a Windows or Linux machine, forward its UDP port (8211 by default), and launch it independently of the game client. The official deployment routes are Steam on Windows, SteamCMD on Windows, and SteamCMD on Linux. A practical host should have four CPU cores, 16 GB of memory, a fast SSD, and a 64-bit operating system; 8 GB can boot but carries a higher out-of-memory crash risk.
Use a private dedicated server when you only need a controlled space for friends. Add -publiclobby only when you want the server listed in the in-game community browser. The steps below cover installation, startup arguments, router and firewall configuration, connection failures, and the important difference between a private server and a listed community server.
What is a Palworld dedicated server, and why use one?
A dedicated server runs the Palworld world as a separate server process instead of tying it to one player’s active game session. The host can close the game client while the server continues running, so other players do not have to wait for the host to launch the game before joining.
That arrangement also gives you a permanent machine, a fixed set of startup options, and one save location to protect. It does not automatically make the server public: a normal dedicated server can remain private, while the optional community-server setting publishes it in the in-game browser.
The official documentation describes the following supported installation paths:
- Windows with Steam: the easiest route for beginners who prefer a graphical installation.
- Windows with SteamCMD: a command-line installation that is useful for scripted or headless administration.
- Linux with SteamCMD: suitable for a Linux host, but it assumes comfort with the shell and Linux service administration.
Follow the official deployment guide for the package-specific sequence: Palworld dedicated-server deployment.
What hardware and operating system do I need?
Pocketpair’s requirements page recommends a 64-bit Windows or Linux system, four CPU cores, 16 GB of memory, and faster SSD storage. Those are vendor recommendations rather than a performance guarantee for a particular player count, mod set, or world size. The same page says 8 GB is bootable but makes out-of-memory crashes more likely, and warns that low-performance storage can corrupt save data.
Use the published requirements as a floor for planning, not as a promise that every four-core, 16-GB machine will handle every workload. More simultaneous players, background applications, slow storage, and operating-system overhead all reduce your margin.
| Resource | Official guidance | What it means in practice |
|---|---|---|
| CPU | 4 cores recommended | Reserve those cores for the server rather than running a heavily loaded desktop or other servers alongside it. |
| Memory | 16 GB recommended; 8 GB can boot | Use 16 GB when possible. Treat 8 GB as a riskier minimum because the documentation specifically warns about out-of-memory crashes. |
| Storage | Faster SSD recommended | Prefer an SSD with enough free space for the installation, updates, logs, and saves. The documentation warns that low-performance storage may corrupt saves. |
| Operating system | 64-bit Windows or 64-bit Linux | Choose the platform you can patch, secure, and troubleshoot confidently. |
| Network | UDP port 8211 by default | Internet players need router port forwarding; Windows also needs a matching firewall rule. |
Read the complete, version-labeled requirements page before buying hardware: official Palworld server requirements. The page surfaced as version 0.6.8, so check it again when the game or server package changes.
Which installation route should I choose?
Choose the route that matches your operating system and how much command-line administration you want to do. The server software is the same conceptually, but the installation and launch commands differ.
| Route | Best for | Setup profile | Network work |
|---|---|---|---|
| Windows with Steam | Beginners with a Windows desktop | Graphical download through the Steam Library; no SteamCMD syntax needed | Router forwarding plus a Windows firewall rule |
| Windows with SteamCMD | Administrators who want repeatable command-line installs | Download SteamCMD, run the anonymous app-update command, then launch the executable | Router forwarding plus a Windows firewall rule |
| Linux with SteamCMD | Linux users comfortable with shell commands | SteamCMD installation followed by the shell launch script | Router forwarding and any required Linux security configuration |
If you are new to dedicated servers, Windows with Steam is the shortest path. If the machine will run without a desktop session, SteamCMD is more practical; Linux requires additional comfort with permissions, services, and security settings.
How do I install the server with Steam on Windows?
The Steam route uses the graphical client to download the official dedicated-server tool, then starts the server using the launch option Steam provides.
- Install and sign in to Steam on the Windows host.
- Open the Library. If the tool is not visible, enable the Tools filter.
- Search for Palworld Dedicated Server and download it.
- Open the tool’s Steam page and use the displayed Launch option. Steam starts the dedicated-server process rather than the regular game client.
- Keep the installation folder identified. You will need it for later command-line launches, updates, backups, and troubleshooting.
Steam is convenient for a first installation, but a graphical client is not required for the server to keep running after the process has started. For a headless Windows machine or repeatable updates, use SteamCMD instead.
How do I install the server with SteamCMD?
SteamCMD is the official command-line route on both Windows and Linux. Download SteamCMD from Valve, open a terminal in its directory, and run the Palworld app update command with anonymous access:
steamcmd +login anonymous +app_update 2394010 validate +quitThe app ID in that command is the dedicated-server package. The validate argument checks the downloaded files, which is useful after an interrupted update or a suspected damaged installation.
Windows with SteamCMD
- Extract SteamCMD to a folder you can administer.
- Open Command Prompt or PowerShell in the SteamCMD folder.
- Run
steamcmd +login anonymous +app_update 2394010 validate +quit. - Locate the Palworld server installation directory created by SteamCMD.
- Change to that directory and launch
PalServer.exe.
PalServer.exeLinux with SteamCMD
- Install SteamCMD using your distribution’s supported package method.
- Run the same anonymous app-update command from the SteamCMD directory.
- Change to the directory containing the server files.
- Start the Linux launch script:
./PalServer.shIf Linux refuses to execute the script, check the file’s execute permission and the account that owns the installation before changing security settings. The official deployment instructions are at docs.palworldgame.com/getting-started/deploy-dedicated-server/.
How do I start the server with a custom port or player limit?
Append startup arguments to the Steam launch settings or to the executable/script command. The documented defaults are UDP port 8211 and a maximum of 32 participants.
| Argument | Default or effect | Example |
|---|---|---|
-port=8211 |
Default listening port | -port=8000 changes the listen port to UDP 8000 |
-players=32 |
Maximum participant count | -players=16 sets a 16-player cap |
-publiclobby |
Enables community-server listing | Add it only when you want browser discoverability |
Windows examples
PalServer.exe -port=8000To change the player limit, append the corresponding argument, for example PalServer.exe -players=16. You can combine arguments in one launch command, separated by spaces.
Linux examples
./PalServer.sh -port=8000Use the same argument names with the Linux script. Whichever port you choose must match the router forwarding rule and the host firewall rule. The full argument reference is maintained at Palworld server arguments.
The current v1.0-and-later argument guidance says leaving performance flags unset may improve performance. Avoid copying performance-tuning command lines from older guides unless they match the current argument reference.
How do I make the server reachable from the internet?
Internet access requires two separate layers: forward the server’s UDP port on your router to the host machine, then allow that same port through the host operating system’s firewall. The default is UDP 8211; if you changed it with -port, forward the replacement port instead.
- Give the server machine a stable address on your local network, preferably through a DHCP reservation so the forwarding target does not change.
- Open the router’s port-forwarding page and create a rule for UDP 8211 to the server machine’s local IP address. Substitute your custom port if you changed the startup argument.
- On Windows, create or approve a firewall rule for the server executable and the same UDP port. Router forwarding alone is not enough.
- On Linux, check the host firewall and any additional security framework enabled by your distribution. The official requirements page notes that Linux may need security configuration in addition to the router rule.
- Start the server and have an outside-network player test the connection. A test from the same home network does not prove that internet forwarding works.
Do not forward unrelated ports, and do not expose administrative services that the server does not require. The official networking requirements are documented at Palworld requirements.
Should I run a private server or a community server?
Both are dedicated servers. The difference is whether the server is advertised in Palworld’s in-game community browser.
| Choice | How it works | Advantages | Important limitation |
|---|---|---|---|
| Private dedicated server | Launch without -publiclobby; players connect using the server details you provide |
Less discoverable and easier to keep limited to friends | You must distribute the connection information yourself |
| Community server | Add -publiclobby to the deployed server’s launch arguments |
Appears in the in-game community-server browser | Routers without Hairpin NAT may prevent players on the same local network from connecting through the listing |
You do not need -publiclobby merely because you want a dedicated server. The official community-server instructions explicitly say that private operation can skip this step: configure a Palworld community server.
What is the Hairpin NAT problem?
Hairpin NAT, also called NAT loopback, lets devices inside your home network reach a service by using the router’s public address. If your router lacks that feature, local players may fail to join a community server through its public listing even though players outside the network can connect. In that case, test the listing with an external player and use a local-network connection method for people inside the house, or keep the server private.
Which platforms can join?
An official overview page surfaced in version 0.5.0 describes dedicated/community-server cross-play between Steam, Xbox Series, Microsoft Store Windows PC, and macOS, and says co-op cross-play is available. It lists PS5 as unsupported on that page. Because those statements come from an older versioned overview, verify the current platform notes before promising cross-play to a particular group: Palworld server overview.
Platform compatibility does not remove the networking requirements. Every participant still needs a route to the server, and a private server still requires you to provide its connection details.
How do I troubleshoot a server that friends cannot join?
Work from the server outward. The symptom usually identifies which layer is wrong.
| Symptom | Likely cause | Check or fix |
|---|---|---|
| The process starts, but nobody outside the home can connect | Missing or incorrect port forwarding | Confirm the launch port, forward that UDP port to the correct local IP, and retest from an outside network. |
| Windows clients time out while the router rule looks correct | Windows Firewall is blocking the executable or port | Add an inbound rule for the server program and the selected UDP port, then restart the test. |
| Linux starts the script but connections fail | Host security settings are still blocking traffic | Review the distribution firewall and security controls in addition to the router configuration. |
| Players on the same Wi-Fi cannot join a listed community server, but remote players can | Router lacks Hairpin NAT | Use a local connection path for local players or operate the server privately. |
| The server exits or crashes with memory errors | Insufficient available memory | Close competing applications, inspect memory use, and move toward the recommended 16 GB rather than treating 8 GB as a safe target. |
| Save data becomes corrupted or the server loads slowly | Low-performance storage | Move the installation and save data to faster SSD storage and restore a known-good backup. |
| A custom port appears ignored | Argument, forwarding rule, and firewall rule do not match | Check the exact command syntax, then make all three network settings use the same UDP port. |
When diagnosing, change one layer at a time: confirm the process is listening, confirm the host firewall, confirm the router target, and only then investigate platform or client issues. Re-run the SteamCMD update with validate if files may be incomplete.
How should I maintain and secure the server?
A dedicated server is an ongoing process, not a one-time download. Use a short maintenance routine:
- Back up saves before updates. Stop the server cleanly, copy the server’s save data to separate storage, then update. Keep more than one backup generation so a damaged or unwanted update does not erase your only restore point.
- Update deliberately. Run
steamcmd +login anonymous +app_update 2394010 validate +quit, review any errors, and start the server again. Do not replace a working installation with an unverified download. - Record your launch command. Keep the selected port, player limit, and whether
-publiclobbyis enabled in a small text file or service definition. This prevents an update or reboot from silently reverting your network settings. - Limit exposure. Forward only the required UDP port, keep the operating system patched, and avoid running the server under an account with more privileges than necessary.
- Watch resources. Check memory, CPU, disk space, and server logs after updates or when the player group grows. The official 16-GB recommendation is especially important if the machine also runs the game client or other services.
Performance flags deserve special caution: the current argument guidance says leaving them unset may be better than blindly applying older tuning recipes. Treat third-party command lines as unverified until they match the current official reference.
Is self-hosting better than managed hosting?
Self-hosting gives you control over the machine, files, launch arguments, backups, and network policy, but you are responsible for hardware, router forwarding, firewall rules, updates, and recovery. A managed service can remove much of that administration, but its Palworld support, locations, player limits, pricing, backup policy, and terms must be verified for the specific service and date; no universal provider specification applies.
| Consideration | Self-hosted machine | Managed service |
|---|---|---|
| Initial setup | Install the package and configure the operating system, router, and firewall | Usually abstracts installation, but the exact control panel and defaults vary |
| Network responsibility | You own port forwarding, public reachability, and local-router behavior | The provider normally supplies internet reachability; verify its platform and port support |
| Administration | You perform updates, backups, monitoring, and recovery | Some tasks may be automated, subject to the provider’s terms and tools |
| Control | Full access to startup arguments and files | Control depends on the provider’s interface and restrictions |
| Cost and capacity | Uses your existing hardware and internet connection | Price, location, memory, storage, player limits, and renewal terms vary and must be checked individually |
For a small group with a suitable always-on machine, self-hosting is the transparent option. Choose managed hosting only after confirming the exact Palworld version, platform support, memory allocation, backup behavior, and cancellation terms.
What should I check before inviting players?
- Confirm the server starts without errors and remains running after you close the game client.
- Confirm the selected UDP port in the launch command matches both the router and firewall rules.
- Test from a network outside the host’s LAN; a successful local test can be misleading when Hairpin NAT is unavailable.
- Decide whether the server is private or listed. Add
-publiclobbyonly for a community listing. - Tell players which address and port to use, and explain any platform limitations that apply to your game version.
- Make a backup before the first major update or configuration change.
Frequently Asked Questions
Does SteamCMD require my personal Steam account to stay logged in?
The documented installation command uses +login anonymous, so the download step does not require a personal account session. The server process can then run independently of the game client; keep the installation account and operating-system permissions under your control.
Can I change the server port after people have joined?
Yes, change the -port argument, then change the router forwarding and host-firewall rules to the same UDP port. Every player must use the new address-and-port combination, and an outside-network test is the quickest way to catch a stale forwarding rule.
Is 8 GB of RAM enough for a small Palworld server?
It may boot, but the official requirements specifically associate 8 GB with a higher possibility of out-of-memory crashes. Treat it as a tentative minimum for experimentation, not as a dependable capacity target for an always-on group.
What if an update leaves the server unable to start?
Stop the process, preserve the current save backup, and rerun the SteamCMD command with validate to repair incomplete files. If the problem began after a version change, compare your launch arguments with the current official argument reference instead of restoring old performance flags blindly.