How to Create a Palworld Server: Complete Guide

To create a Palworld dedicated server: SteamCMD (AppID 2394010, anonymous login, free), UDP port 8211, PalWorldSettings.ini for configuration. 32 players max, Steam/Xbox/PS5/Mac crossplay since version 1.0. This guide covers Windows and Linux installation, configuration, crossplay and optimization.

Key takeaways

• The Palworld dedicated server is free and downloads through SteamCMD without owning the game (AppID 2394010, anonymous login).
• Port to open: UDP 8211.
• Since version 1.0 (July 2026), Steam, Xbox, PS5 and Mac crossplay works on dedicated servers.
• The PalWorldSettings.ini file is empty by default. You need to copy the contents of the DefaultPalWorldSettings.ini template into it before configuring.
• 16 GB of RAM recommended by Pocketpair, even for a small server. Usage grows over the course of sessions.

4-player co-op vs 32-player dedicated server

Palworld offers two multiplayer modes. The choice between them determines everything that follows.

This guide covers the dedicated server. If you just want to play with four people through an invite code, co-op in the game menu is enough.

Requirements

• RAM: 16 GB recommended by Pocketpair, 8 GB strict minimum. Memory usage grows over the course of sessions (bases, Pals, exploration), which makes 16 GB necessary on an active server.
• CPU: 4 cores at 3.5 GHz minimum. Pal and base simulation mainly puts load on the processor.
• Storage: 15 GB SSD minimum (12-15 GB for the server files + room for backups). Pocketpair explicitly links slow storage (HDD, SATA) to save corruption risks. Use NVMe.
• System: 64-bit Windows or Linux (Linux recommended for a production server).
• Network: stable upload bandwidth, UDP port 8211 open.

Installing the server with SteamCMD

Download SteamCMD then run:

steamcmd +login anonymous +app_update 2394010 validate +quit

The download uses an anonymous login: you don't need to own Palworld to host a server. Only your players need to own the game. The files install into steamapps/common/PalServer. Running the same command again later updates the server. Client and server must be on exactly the same version to connect.

First launch

Launch the server once so it generates the configuration folder structure:

Windows: .\PalServer.exe

Linux: ./PalServer.sh

Wait for the server to start completely, then stop it. The Pal/Saved/ folder has been created with the configuration and saves. Now move on to configuration.

For subsequent launches, use the full launch options:

./PalServer.sh -publiclobby -port=8211 -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS

Since version 1.0, the performance flags (-useperfthreads, etc.) have become optional: Pocketpair optimized the dedicated server's performance. They are still recommended on modest hardware.

Configuring PalWorldSettings.ini

This is the step where everybody gets caught out. The PalWorldSettings.ini file is empty by default. If you open it without filling it in, your server starts with the default settings and you can't change anything. You first have to copy the contents of the DefaultPalWorldSettings.ini template (located at the root of the server folder) into your configuration file.

File location:

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

All the options go on a single line OptionSettings=(...), separated by commas. Settings you don't define keep their default value.

Basic settings

Gameplay and difficulty

For an accessible community server, raise ExpRate to 2.0-3.0 and PalCaptureRate to 1.5-2.0. For a hardcore server, leave the default values and set DeathPenalty to All.

Enabling crossplay (Steam, Xbox, PS5, Mac)

Since version 1.0 (July 2026), a Palworld dedicated server can bring together players from every platform. Two conditions:

In PalWorldSettings.ini, declare the allowed platforms:

CrossplayPlatforms=(Steam,Xbox,PS5,Mac)

Launch the server with the -publiclobby option, which is essential for console players to find your server in the community list.

The old AllowConnectPlatform option is deprecated and ignored since 1.0: only use CrossplayPlatforms. To restrict access to certain platforms, remove them from the list (for example CrossplayPlatforms=(Steam) for a PC-only server).

Network configuration

Palworld communicates over UDP on port 8211 by default. It's the only port needed for players to connect.

Windows firewall: New-NetFirewallRule -DisplayName "Palworld Server" -Direction Inbound -Protocol UDP -LocalPort 8211 -Action Allow

Linux firewall (ufw): sudo ufw allow 8211/udp

Linux firewall (iptables): sudo iptables -A INPUT -p udp --dport 8211 -j ACCEPT

If you host at home, forward UDP port 8211 on your router to the local IP of the server machine. If your ISP uses CGNAT (Carrier-Grade NAT), port forwarding won't work. Contact your ISP to get a dedicated public IP, or go through a server host.

In-game administration

Set AdminPassword in PalWorldSettings.ini, then authenticate in game:

/AdminPassword YourPassword

Backups and updates

Backups are the most underrated part of administering a Palworld server.

• Automatic backups: enable bIsUseBackupSaveData=True in PalWorldSettings.ini so the server creates automatic rolling backups.
• Manual backups: copy the entire Pal/Saved/ folder (world, players, configuration) to a separate medium. Automate this copy with cron (Linux) or the Task Scheduler (Windows).
• Updates: stop the server and rerun steamcmd +login anonymous +app_update 2394010 validate +quit. Client and server must be on the same version.

Pocketpair explicitly links slow storage to save corruption risks. If your server runs on an HDD or a SATA SSD, saves can take too long and corrupt the data. Use NVMe.

Performance optimization

Palworld's memory usage grows over the course of sessions. This is normal server behavior, not a bug. Built bases, active Pals and explored chunks pile up in RAM and aren't always released properly.

• Scheduled restarts: schedule an automatic restart every 6 to 12 hours. It's the most effective fix for the memory leak. Warn players with /Shutdown 300 "Restarting in 5 minutes" before each restart.
• Number of bases and Pals: this is the first source of CPU load. Limit the number of bases per guild (BaseCampMaxNum) and the number of active Pals per base if your server lags with many players.
• Launch flags: -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS are still recommended on modest hardware, even though 1.0 made them optional.
• Mods (Steam Workshop): server mods currently only work on the Windows version of the dedicated server. The Linux build can accept players with client-side mods, but can't load Workshop mods on the server side.

Hosting: at home vs server host

Self-hosted: free (electricity aside), but your public IP is exposed, and you have to handle port forwarding, backups, updates and restarts. If your PC is off, the server is unreachable. Fine for testing with 2-4 friends.

Server host: dedicated IP, 24/7 availability, DDoS protection, a management panel with PalWorldSettings.ini configuration through a web interface, automatic backups and technical support. It's the recommended choice for a community server that needs to stay online around the clock.

Getting your server noticed

An online server with no players isn't much use.

Once your server is configured and stable, list it on our Palworld server list to gain visibility with players looking for a server to join.

Add a clear description, create a nice thumbnail, and choose the right tags, provide the connection IP and port, and the first players will arrive naturally

Frequently Asked Questions

Is the dedicated server free?

Yes. The server tool (AppID 2394010) downloads for free through SteamCMD with an anonymous login, without owning Palworld. Only your players need to own the game.

Why is PalWorldSettings.ini empty?

That's normal behavior. The file is created empty on first launch. You have to copy the contents of the DefaultPalWorldSettings.ini template file (located at the root of the server folder) into your PalWorldSettings.ini, then edit the values you want. Without this copy, the server starts with the default settings and you can't customize anything.

How much RAM do I need?

Pocketpair recommends 16 GB, even for a small server. Usage grows over the course of sessions: a server that starts at 6 GB of RAM in use can reach 12-14 GB after a few days without a restart. Scheduled restarts reset the usage.

Can console players join?

Yes, since version 1.0 (July 2026). Enable CrossplayPlatforms=(Steam,Xbox,PS5,Mac) in PalWorldSettings.ini and launch the server with -publiclobby. The old AllowConnectPlatform option is deprecated and ignored.

How do players connect?

From the in-game community server list (if you launched with -publiclobby), or by direct connection with the IP and port (8211 by default). Console players can only connect through the community list, not by direct IP.

Can you use mods on the server?

The Steam Workshop is supported since 1.0, but only on the Windows version of the dedicated server. The Linux build accepts players with client-side mods but can't load Workshop mods on the server side. If you want server mods and you're on Linux, you'll have to migrate to the Windows build.

Is my existing world compatible with 1.0?

Yes, existing saves are compatible. Pocketpair recommends starting a new world to fully enjoy the new content (World Tree, Sky Islands, rebalanced progression), but old worlds work without any problem. Make a backup before updating, as a precaution.