Introduction To Palworld Dedicated Server
Palworld drops you into this chaotic, wild open-world survival game where everything revolves around these weird little creatures called Pals. You collect them, fight alongside them, throw them into crafting, stick them on farms, and even make them run your machines. It is a full-on mix of survival mechanics, base building, and co-op chaos.
If you care about multiplayer, you need to Set up a Palworld Dedicated Server. The game supports up to 32 players, but trying to host from someone’s PC?
Once the host logs off, the world shuts down. That’s where dedicated servers come in. They keep the world running no matter what. No downtime, no host crashes, no random disconnects when things get busy.
What is Palworld and How Does Its Dedicated Server Work?
The Pals aren’t just cute sidekicks. You assign them jobs. Some fight, some farm, and some just carry your equipment while you loot another outpost.
A dedicated server in Palworld is exactly what it sounds like. It runs the game world on its own, without depending on anyone’s PC.
That means the world stays online all the time. No host required, no random shutdowns. Players can join and leave whenever. Nothing resets or disappears.
This kind of setup isn’t just for convenience. It’s what makes Palworld feel more like a true person.
Advantages of a dedicated server.
Dedicated servers offer a stronger, more flexible setup that actually holds up when things get busy. Here’s why they’re the better choice:
Stability and uptime
The server is independent of any PC, so it is always online regardless of the joined and the left participants. You don’t lose progress just because the host disconnected. The world keeps running and the Uptime and Reliability is great. That’s what makes it work for long term play.
Full control over game settings
When you are running the server, you choose how it works. Change the player cap, enable or disable PvP, adjust the spawn rate of stuff, provide or deny mod permissions whatever you consider appropriate to your group’s preferred play style. You make the rules.
Fast network performance and less lag
Everything goes through one central server and not between players, and you have less lag and more response times. It all is smoother and more trustworthy, especially when there is quite a lot of action at the same time.
Enhanced security and protection
Dedicated Palworld servers usually come with real security features.DDoS protection, firewalls, regular backups, These help block attacks and stop data from getting wiped.
Scalability and easy upgrades
As your world gets busier, you’ll need more power. That is easy with dedicated servers. The majority of hosts support upgrading CPU, RAM, storage or bandwidth quickly, and sometimes immediately. No downtime, no stress.
Use cases:
Dedicated servers in Palworld make a huge difference for multiplayer.
- If you’re running a private world, a dedicated server keeps it locked down. No random players popping in. No connection dies when someone logs out. Just your group, your rules, always online.
- Clans and organized teams use them for a reason. When you’re running raids, PvP tournaments, or scheduled events, you can’t have a server flaking out mid-match. You need uptime that doesn’t quit and performance that holds steady when things get chaotic.
- Want to adjust how the game works? Dedicated servers let you mess with PvP settings, tweak resource spawn rates, or fine-tune how fast stuff respawns. That kind of control matters when you’re trying to keep things fair or push a certain playstyle.
- Modded servers are a whole other beast. You can add new items, creatures, building systems, or whatever your group wants to try. This is where Palworld starts to feel like something totally custom.
- And because the server’s not tied to someone’s personal PC, mods actually run well. Less crashing, fewer weird bugs, and no one has to wait around for someone else to boot up the game.
Dedicated servers make multiplayer in Palworld feel solid. Doesn’t matter if it’s casual friends hanging out or a hardcore group chasing rankings. If you care about how the game runs, this is the way to do it.
Requirements for Setting Up a Palworld Dedicated Server
To play Palworld smoothly on a dedicated server the server has to meet a few basic requirements across the Operating System, hardware, and network.
Supported Platforms
You can host a Palworld dedicated server on a 64-bit Windows or Linux system. Supported Linux distributions include Ubuntu and AlmaLinux. On Windows, you can install it through Steam or SteamCMD, while Linux installations use SteamCMD. An official Docker image and sample Compose files are also available, although Docker Desktop is not recommended because it may cause performance issues or save-data corruption.
Recommended Hardware Specs
- CPU: Pocketpair recommends a processor with at least four CPU cores. No official clock-speed requirement is specified, but a modern CPU with strong per-core performance is preferable for maintaining stable server performance.
- RAM: The official requirement is 16 GB. A server can boot with 8 GB, but Pocketpair warns that this increases the risk of out-of-memory crashes. More than 32 GB is recommended for larger servers. Pocketpair does not provide an official RAM-to-player-count formula.
- Storage: Pocketpair does not specify a minimum storage capacity. Use a fast SSD with enough capacity for the server files, updates, saved worlds, logs, and backups. Pocketpair warns that low-performance storage may cause saved-data corruption. NVMe storage is preferable but not officially required.
- Network: The server requires a stable internet connection. Palworld uses UDP port 8211 by default, although the port can be changed. If the server is behind a NAT router, forward the configured UDP port to the server. TCP port 8211 is not listed as a standard Palworld server requirement.
- Public IP: A static public IP is recommended but not required. With a dynamic public IP, players must use the new address whenever it changes, unless you configure dynamic DNS. Also verify that the connection is not behind carrier-grade NAT, which can prevent inbound connections.
Preparing Your Environment
The first thing you should do before you begin hosting a Palworld in dedicated server is to determine how you will actually run it. It will be dependent on your comfort with the idea of administering servers, and the stability that you need the experience to be.
- Self-Hosting on Your Own PC: Running the server locally. But your PC has to stay on 24/7. Your internet needs to be stable and you’ll probably need to open router ports. It’s fine for testing or small groups, but not great for uptime or big sessions. Weak hardware or flaky Wi-Fi will cause problems.
- Renting a VPS or Dedicated Game Server: This is better if you want something stable. A VPS gives you dedicated CPU, RAM, and bandwidth. It’s more reliable than your home setup. You still install and manage the server, but once it’s up, it stays up. Great for long-term Palworld server, especially with mods or active players.
- Using Game Hosting Providers with Game Panels: ARZ host, Hostinger Game Panel, Host Havoc, DatHost, GTXGaming, they offer a Palworld dedicated server with browser-based controls. You get DDoS protection, auto-updates, backups, and mod support, all without touching code. Pay monthly, click a few buttons, and you’re live.
Installing Steam and SteamCMD
You’ll need one of two tools to install the Palworld server. Both are from Valve, and they’re used to pull the game server files from Steam’s backend. Which one you apply, is determined by your hosting.
- Steam Client: You can use Steam to download and manage the Palworld server using the standard interface in case you are on windows and have Steam installed. This is easier for beginners and works fine on personal PCs. It’s point and click. Just install it like any other Steam game.
- SteamCMD: This one’s for command line users. SteamCMD is a lightweight terminal tool that lets you install and update game servers without a GUI. You’ll want this if you’re running a headless Linux server, or if you’re automating anything. Most VPS setups use this. It’s fast and reliable, but you’ll need to type out some commands.
Set Up SteamCMD on Windows
- Download SteamCMD from Valve’s official page.
- Extract the folder and run steamcmd.exe. It’ll update itself for the first time.
- When it loads, type: login anonymous
- Set your install location:
force_install_dir C:\Palworld-Server - Download the server files:
app_update 2394010 validate - Type quit when it’s done.
Set Up SteamCMD on Linux
- Update everything first:
sudo apt update && sudo apt upgrade -y - Add 32-bit support and install SteamCMD:
sudo dpkg –add-architecture i386
sudo apt install lib32gcc-s1 software-properties-common steamcmd -y
- Start SteamCMD by just typing steamcmd
- Log in anonymously
- Set your install dir and pull the server files (same commands as above)
- Use screen or tmux if you want to keep the server running after closing your SSH session.
Running on macOS
Palworld doesn’t support macOS for server hosting.
Step-by-Step Installation Guide of Palworld Dedicated Server
Setting up your Palworld dedicated server isn’t complicated, but it does require a few technical steps.
This section guides you through the process of installing game files all the way to setting up your network, and starting the server.
Installing Palworld and the Dedicated Server
You do not need to install or launch the Palworld game client. Install Palworld Dedicated Server through Steam Tools or SteamCMD using app ID 2394010. After installation, launch the dedicated server using PalServer.exe on Windows or PalServer.sh on Linux. The first launch starts the server and generates the required configuration directories and files.
Install the dedicated server
Using Steam on Windows:
- Open Steam and sign in.
- Open Library.
- Enable Tools in the library filter.
- Search for Palworld Dedicated Server.
- Click Install.
Using SteamCMD on Windows or Linux:
steamcmd +login anonymous +app_update 2394010 validate +quit
This anonymously downloads or updates Palworld Dedicated Server, validates its files, and then exits SteamCMD.
Locate the server files
The exact location depends on your Steam Library or SteamCMD installation directory.
Typical Steam installation on Windows:
C:\Program Files (x86)\Steam\steamapps\common\PalServer
Typical Linux SteamCMD installation:
~/Steam/steamapps/common/PalServer
If you configured a custom Steam Library or used force_install_dir, use that location instead.
Start the server
Windows with Steam:
- Open Palworld in the Steam Library.
- Click Play.
- Select Play Palworld
- Windows from the installation directory:
cd /d “C:\Program Files (x86)\Steam\steamapps\common\PalServer”
PalServer.exe
Linux:
cd ~/Steam/steamapps/common/PalServer
./PalServer.sh
The first startup creates the required configuration directories. After that, stop the server, copy DefaultPalWorldSettings.ini to the appropriate configuration directory, edit the settings, allow UDP 8211 through the firewall, and configure port forwarding if the server is behind a router.
2. Generating Initial Server Configuration
Your server will require you to have default configuration files before you begin to tweak settings. All you have to do is start up the server and run it for a few minutes.
Where the configuration files live:
DefaultPalWorldSettings.ini is located in the server root directory. Copy it to Pal\Saved\Config\WindowsServer\PalWorldSettings.ini on Windows or Pal/Saved/Config/LinuxServer/PalWorldSettings.ini on Linux.
- DefaultPalworldSettings.ini: This one’s just a template. It holds the standard default settings the game comes with.
- PalworldSettings.ini: This is the actual config file the server uses when it runs. At first, it’ll be mostly empty or very basic, so you’ll need to edit this one to set up your preferred rules, options, and tweaks.
3. Configuring Server Settings
Get your config file ready:
Open DefaultPalWorldSettings.ini and the operating-system-specific PalWorldSettings.ini file in a plain-text editor. Editing DefaultPalWorldSettings.ini alone does not change the active server configuration.
Copy over the default settings:
Look at the DefaultPalworldSettings.ini file and scroll down to line 4. Copy the complete DefaultPalWorldSettings.ini file to the appropriate WindowsServer or LinuxServer configuration directory, then edit the copied PalWorldSettings.ini file. This gives you a clean, complete set of settings to start from, so you’re not building the configuration from scratch.
Key configurable parameters in PalworldSettings.ini:
| Parameter | Description | Example/Default |
| ServerName | Name players will see for your server | My Palworld Server |
| ServerPlayerMaxNum | to set the maximum number of connected players | 32 |
| bIsPvP | Toggle PvP mode on or off | True or False |
| ServerPort | Set the listening port with the -port command-line argument. PublicPort only advertises the external port for a community server. | 8211 |
| AdminPassword | Password for admin access | YourSecurePassword |
| PalSpawnNumRate | Pal spawning and CollectionObjectRespawnSpeedRate for gatherable-resource respawn timing. | Custom numeric values |
4. Editing tips:
- On windows, open the file in any plain document such as notepad. Make sure not to open Word (or any other rich-text editor) as it will resize the formatting of the whole file.
- You can stay on terminals in Linux like nano or vim. For example:
nano PalworldSettings.ini - Always keep a backup, then you begin working. Should something go wrong, you will be able to simply roll back to the original without getting into trouble.
5. Save changes and restart the server:
After making changes:
- Save the file
- Stop your server if it’s already running
- Then restart it using either PalServer.exe or ./PalServer.sh, depending on your Operating System
Your new settings will load when the server boots up again. That’s all you need to start tweaking your Palworld experience.
Network Configuration for Accessibility
In case you wish your Palworld server to be accessible outside your home network, your configuration must be airtight. It is setting up the correct ports forward, configuring the firewall and ensuring that your server is available to the outside world.
1. Port Forwarding on your Router.
If you want users outside your network to join your Palworld server, you’ll need to forward port 8211 (both TCP and UDP) to the cTo allow other people (not in your network) to be included in your Palworld Server, port 8211 (TCP and UDP) will have to be forwarded into the computer that is running the server.
In the first step, locate the IP address of your router. You can find it normally printed on the router somewhere, or you can use whatsmyip
Open a browser and enter that IP into the address bar http://your-router-ip
Enter your router user name and password (this is normally printed on the router or in the manual).
Search port forwarding or virtual Servers.
Now set up a new forwarding rule:
- Service Name: Call it something like “Palworld Server” or whatever you want
- UDP
- External Port: 8211
- Internal Port: 8211
- Internal IP: This is your server’s local IP address. Run ipconfig on Windows or ip addr on Linux to find the server’s local IP address.
After doing that, you must certainly save the changes. Some routers might just need a reboot to apply the new settings.
2. Set Up Your Firewall to Let Players In
On Windows:
- Open Windows Defender Firewall with Advanced Security
- Add an inbound UDP rule for port 8211 and allow PalServer.exe through Windows Defender Firewall.
- Also, make sure the Palworld server app (like PalServer.exe) is allowed through the firewall.
On Linux (using UFW):
- Open your terminal and run:
sudo ufw allow 8211/udp
- Then double-check that UFW is active:
Before enabling UFW on a remote server, allow the active SSH service with sudo ufw allow OpenSSH, then run sudo ufw enable.
3. Precautions When Configuring Firewalls
Do not block SSH:
If you’re managing your Palworld server on a Linux machine over SSH, do not block port 22. That is the default port that the SSH uses. And if you block that, you will end up logging yourself out. Make sure to always double-check that port 22 is still open before enabling or even updating firewall rules.
Avoid opening unnecessary ports:
The default Palworld gameplay port is UDP 8211. Open separate RCON or REST API ports only when those services are enabled and secured. No reason to leave extra ports exposed, it just increases the chances of someone messing with your server.
4. Testing Connectivity
Local check:
- First, test from the machine itself or another one on your local network. Use either the loopback address:
127.0.0.1:8211
- Or your server’s internal IP, like:
192.168.x.x:8211
Remote check:
- Now test from a completely different network using your public IP address. Just search “what’s my IP” in a browser from the server, and plug that into:
<Your Public IP>:8211
To find out whether 8211 is open, you may do something like Telnet or an online port checker. In case all the preparations have been made, you can test your server to make sure that it is accessible to the outside world. When this is effective, then the players are supposed to be able to connect anywhere without any problems.
1. Starting the Server
To get your server running, go to the Palworld install directory.
- On Windows, just double-click PalServer.exe or run it from a terminal.
- On Linux, open a terminal in the server directory and run: ./PalServer.sh
Once it starts, you’ll see a live log feed showing what the server is doing—player joins, world activity, errors, etc.
4. Restarting and Shutting Down Safely
To restart, do this:
- Authenticate with /AdminPassword, run /Save, and then execute /Shutdown [Seconds] [MessageText] for a controlled shutdown.
- Wait for the server to close and save.
- Relaunch it with your usual command or flags.
To shutdown.
Same thing, use Ctrl + C or the in-game command if supported. Avoid killing the process through Task Manager or kill -9 unless it’s absolutely stuck. Forced shutdowns can corrupt data or lose player progress.
If you’re using screen or tmux on Linux to keep the server running in the background:
- Use Ctrl + A + D to detach safely.
- Reattach later to check on the server.
- Always shut it down properly from inside th
Conclusion
Installation of Palworld onto your own server is under your control. It’s your choice what the game experiences are like, be it a relaxed co-op, a cut throat battle, or a game of your own. You are allowed to customize the rules, play around with mods and adjust everything to suit how your group plays.
FAQs
Can I run a Palworld server on Linux?
Yes. Palworld dedicated servers work fine on 64-bit Linux setups like Ubuntu or AlmaLinux. Most people use SteamCMD to install and manage it, which is solid if you’re running a headless VPS or something without a desktop. Easy to script, easy to automate. Just make sure the machine meets the basic hardware requirements, or the server’s gonna choke.
What is the max number of players on a dedicated server?
Palworld caps out at 32 players per server right now. That’s the limit. If you’re going to push it that far, you’ll want at least 16 GB of RAM and a decent CPU. Especially if the world’s got a lot going on like Pals, bases, PvP, all that. Multiplayer chaos stacks up quickly.
Do I need a separate game copy for the dedicated server?
No. The dedicated-server software can be downloaded anonymously through SteamCMD without purchasing a separate Palworld license. You’re not running the game itself; you’re running the server version that comes through Steam’s tools. Either grab it through the Steam client on Windows or use SteamCMD if you’re on Linux.
How often should I update the server software?
Check for updates anytime Palworld pushes a new patch. This is normally when bugs are resolved or new features are introduced. It prevents your multiplayer server from crashing. How you install it decides on whether to use SteamCMD or the Steam client to update. It is better to update off-hours when no one’s online. Save the world first. Always. Don’t be the guy who loses everyone’s progress because you restarted without a backup.
Read More: