Palworld Dedicated Server Setup

Palworld’s open-world chaos is best enjoyed with friends, but public servers make that tough. Lag spikes, player limits, and random disconnects can ruin the fun fast. Your own Palworld dedicated server hosting fixes that.
Palworld Dedicated Server Setup

Summarize this blog on:

You control every setting, decide who joins, and keep your world running even when you’re offline. Private servers also unlock mods, better performance, and real data protection for long-term worlds. 

Whether you’re building a small co-op or managing a 32-player community, self-hosting gives you the stability and freedom public servers can’t. 

In this guide, you’ll learn how to install, configure, port forward, and troubleshoot your own Palworld server, so you can play without limits.

Note: PS5/Xbox players can only join Community servers. Launch with -publiclobby so your server appears in the in-game list.

Key Takeaways

  • Host your own server for full control, zero lag, and 24/7 uptime without public server limits.
  • Minimum specs: 16 GB RAM, SSD storage, 4-core CPU, and 10+ Mbps upload speed.
  • Port forward 8211 (UDP) and 27015 (TCP/UDP) through your router to allow player connections.
  • Launch with -publiclobby flag to enable cross-play and appear in community server lists.
  • Copy DefaultPalWorldSettings.ini to create your config file before editing server settings.
  • Set strong AdminPassword and ServerPassword to control access and moderate your world.
  • Console players (PS5/Xbox) can only join via the Community Servers list; direct IP entry isn’t supported on consoles.
  • Schedule server restarts every 4-6 hours to clear memory leaks and maintain stability.
  • Back up SaveGames folder and config files regularly to protect your world from data loss.
  • Use static IP or Dynamic DNS to maintain consistent connection links for your players.

Prerequisites: What You Need Before Setup

Before launching your Palworld dedicated server, make sure your system and network meet these requirements:

System Requirements

  • Windows 10/11 (64-bit) or 64-bit Linux (e.g., Ubuntu, Debian, AlmaLinux).
  • Minimum 4 cores / 8 threads (AMD Ryzen 5 or Intel i5 class).
  • At least 16 GB for stable performance; 32 GB recommended for full 32-player servers.
  • SSD required for faster world loading and autosaves.

Network Requirements

  • Rule of thumb: at least 10 Mbps upstream; 20+ Mbps recommended for busy 20–32 player servers.
  • Wired Ethernet for low latency and reliable bandwidth.
  • Public IP address, required so players can connect from the internet.
  • Router admin access, needed to set up port forwarding for UDP/TCP ports (8211, 27015, 25575 if used).

Software Requirements

  • Install and download “Palworld Dedicated Server” from Steam → Library → Tools.
  • Add inbound rules for the server ports in your firewall (Windows Defender/Linux). Avoid disabling your firewall.
  • A dedicated hosting machine or bare-metal server for 24/7 uptime and public access.

Always run the server on a clean OS environment with updated drivers and firmware to avoid crashes and packet loss.

How to Set Up Palworld Dedicated Server?

Follow these steps in order. Keep the server window open while players are online.

Install and open “Palworld Dedicated Server”

  • Open Palworld dedicated server Steam → Library → Tools. Search for Palworld Dedicated Server and install it.
  • Run it once and close it. This generates the folders you’ll edit next.
  • Go to the config path:
    • Windows: …\Steam\steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini
    • Linux: …/Steam/steamapps/common/PalServer/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
  • If PalWorldSettings.ini is missing/empty, copy defaults from DefaultPalWorldSettings.ini (don’t edit the default file directly):

Windows (PowerShell):

Copy-Item steamapps\common\PalServer\DefaultPalWorldSettings.ini `

  steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini

Linux:

cp steamapps/common/PalServer/DefaultPalWorldSettings.ini \

   steamapps/common/PalServer/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini=

Configure core server settings (edit PalWorldSettings.ini)

Set the essentials, then save:

  • ServerName=”YourServerName” – what players see in lists.
  • ServerPassword=”OptionalPassword” – keep empty for public, set for private.
  • AdminPassword=”StrongAdminPass” – enables in-game admin. In-game, run /AdminPassword YOUR_ADMIN_PASSWORD to gain admin.
  • ServerPlayerMaxNum=32 – hard cap is 32; reduce if your hardware is modest.
  • Leave cross-play as default (CrossplayPlatforms=(Steam,Xbox,PS5,Mac)) unless you need to restrict platforms.
  • For community (public) listing, you’ll also use PublicIP / PublicPort (explained below). Note: PublicPort does not change the listen port; it only advertises the external port.

Why this matters: names aid discoverability, passwords gate access, admin lets you moderate, and player cap manages load.

Find and add your IPs

  • Local IPv4 (for router mapping): open CMD → ipconfig. Note the IPv4 (e.g., 192.168.1.50).
  • Public IP (for players): search “what is my IP” in a browser.
  • In PalWorldSettings.ini, set (for community servers):
    PublicIP=”YOUR_PUBLIC_IP” and PublicPort=8211 (default). These fields help the master list point to your server.

Forward ports + Allow through Firewall (Critical)

Forward the following to your local IPv4 on your router (Advanced → Port Forwarding). Then allow the same ports in your OS firewall:

  • 8211/UDP (game listen port; default) – required.
  • 27015/TCP+UDP (Steam query) – improves server browser visibility (not required for direct connect).
  • 25575/TCP (RCON, optional)- deprecated; prefer the REST API and avoid exposing admin ports publicly.

Tips that fix most “connection timed out” issues: verify the forward target of the current local IPv4, reboot the router after saving, and ensure Windows/Linux firewall rules allow these ports.

Launch the server (private or community)

You can run from Steam or directly:

Steam GUI

  • Open Palworld Dedicated Server.
  • For a community server (shows in the in-game list and enables console players to find you), choose “Open and start as a community server.” This applies the -publiclobby flag. Keep the black console window open.

Direct (examples):

  • Windows: PalServer.exe -publiclobby
  • Linux: ./PalServer.sh -publiclobby

 

Optional performance flags you can add:
-useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS (improves performance on multi-core CPUs; test on your hardware). 

Optionally add -NumberOfWorkerThreadsServer=CPU_threads_minus_1.

You can also change the listen port or player cap at launch, e.g.:
PalServer.exe -port=8211 -players=32

Join your server (test locally first)

  • Direct connect (Dedicated): In Palworld, open Join Multiplayer Game. Enter YOUR_PUBLIC_IP:8211 in the field below the server list, then connect. Enter the server password if prompted.
  • Community list: If you launched with -publiclobby, select Community server, search your ServerName, and join. It may take a few minutes to appear after the first boot.

Cross-play note: Palworld dedicated/community servers support Steam, Xbox (and MS Store PC), PS5, and Mac. Console users rely on Community server listing rather than direct IP entry, so keep -publiclobby for mixed platforms. 

Invite friends (and avoid common join issues)

  • Share YOUR_PUBLIC_IP:8211. PC players can direct-connect; console players should find you in Community server.
  • If they can’t join, check this quick list:
    • The server console is running (and not minimized-then-closed).
    • 8211/UDP is forwarded to the correct local IPv4 and allowed in the firewall.
    • Steam query port 27015 is open if you expect listing visibility.
    • For remote admin, use RCON cautiously (default 25575); consider not exposing it to the internet. 

Troubleshooting & Common Errors

Even a well-configured Palworld server can throw connection errors or fail to appear online. Here’s how to diagnose and fix the most common issues step by step.

Connection Timed Out

Cause: The most frequent issue: your server port isn’t reachable.

Fix:

  • Make sure port 8211 (UDP) is open and forwarded to your PC or host’s local IPv4 address.
  • Forward 27015 (TCP/UDP) for Steam query visibility.
  • Check your firewall,  allow inbound rules for 8211 and 27015.
  • Confirm your PublicIP in PalWorldSettings.ini matches your actual external IP.
  • If your ISP uses double NAT, request a public IP or use a dedicated hosting provider.
  • Restart your router and launch the server again.

Because the game uses UDP, test properly: try joining from a second network, add the server in Steam → View → Servers → Favorites, or run an external UDP scan (e.g., nmap -sU -p 8211 your.ip).

Server Not Listed in Community Tab

Cause: You launched in private mode or didn’t enable public listing.

Fix:

  • Relaunch with -publiclobby in the startup command.
  • Ensure PublicIP and PublicPort are correct in the config file.
  • Keep 27015 (UDP/TCP) open; it’s required for server browser visibility.
  • Wait 5–10 minutes after launch; listings sometimes take time to sync.
  • If you still can’t find it, connect directly using your PublicIP:8211 and confirm it’s live.

Missing or Default Config File

Cause: The server never generated your configuration files properly.

Fix:

  • In Steam, right-click Palworld Dedicated Server → Manage → Browse Local Files.
  • Locate the folder Pal\Saved\Config\WindowsServer.
  • If it’s empty, copy content from DefaultPalWorldSettings.ini into PalWorldSettings.ini.
  • Save the file and restart the server once to apply settings.

Other Players Can’t Join

Cause: Network mismatch, firewall, or incorrect forwarding.

Fix:

  • Restart your router and the Palworld Dedicated Server app.
  • Verify that the forwarded IP matches your current local IPv4.
  • Ensure friends are connecting via PublicIP:8211, not your local IP.
  • Double-check that Windows Defender or third-party firewalls aren’t blocking PalServer.exe.
  • If hosting from a laptop or dynamic IP connection, assign a static local IP or use dynamic DNS for stability.
  • If you’re testing from the same network, hairpin NAT may block you from seeing your own server. Test from a mobile hotspot or an external network.

Admin or Permission Issues

Cause: The server or Steam client lacks elevated permissions.

Fix:

  • Run both Steam and PalServer.exe as Administrator (Windows) or sudo/root (Linux).
  • On Windows: right-click → Properties → Compatibility → “Run as administrator.”
  • Ensure the folder isn’t set to read-only.
  • On Linux, check ownership with ls -l and adjust with chown username:username PalServer -R.

Bonus Fix,  Random Crashes or Lag

Cause: Memory spikes or outdated drivers.

Fix:

  • Upgrade to at least 16 GB RAM and SSD storage.

Add performance flags:

-useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS

  • Keep graphics drivers, OS updates, and SteamCMD files current.
  • Restart the server every few hours if it runs 24/7; it clears cache buildup.

Performance & Maintenance Tips

A Palworld server can stay stable for months, but only if you maintain it correctly. Use these tested performance and upkeep strategies to keep uptime high and crashes rare.

Automate Restarts for Stability

Restarting your server periodically clears memory leaks and resets background processes. Schedule automatic restarts every 4–6 hours using Task Scheduler on Windows or a cron job on Linux. Choose off-peak times so players aren’t interrupted.

Back Up Everything (Not Just the World)

Your saved worlds live in PalServer\Pal\Saved\SaveGames. Back up this folder,  plus your config files and mods,  before updates or major changes.
Store backups on off-site drives or cloud storage (like Google Drive or OneDrive). Avoid over-frequent automatic backups, which can slow the game due to heavy disk writes.

Use Static IP or Dynamic DNS

If your ISP changes your IP address often, your friends may lose access.
Fix it by either:

  • Requesting a static public IP, or
  • Setting up a Dynamic DNS (e.g. yourserver.ddns.net) to auto-update your changing IP.
    This ensures your connection link stays the same even after restarts or reboots.

Keep Your Server Updated

Update regularly to match Palworld’s latest patch version. Outdated builds often cause mismatched errors between clients and servers.

  • Check Steam or SteamCMD for new updates.
  • Re-verify your files after each patch.
  • Update mods to avoid incompatibility crashes.
  • Keep your OS and network drivers current for smoother performance.

Monitor Resource Usage

Keep an eye on CPU, RAM, and disk usage through Task Manager (Windows) or htop (Linux).
High usage means it’s time to optimize or upgrade. Reducing player count, cleaning unused saves, or adding more RAM/CPU power can prevent lag and crashes.

Upgrade When Your Community Grows

Once your player base expands, local hosting may not cut it. Move to a dedicated, unmetered bandwidth server for 24/7 uptime, DDoS protection, and global reach.
This ensures your Palworld world stays online even when you’re not.

Hosting Palworld on RedSwitches

Running a local server works, but it limits uptime, bandwidth, and reach. Your PC isn’t built to handle 24/7 hosting, global players, or unexpected power drops. That’s where enterprise-grade hosting comes in.

With our Dedicated Servers, you can host your Palworld world 24/7 without worrying about port forwarding, energy costs, or lag spikes. Each server delivers 1 Gbps, 10 Gbps & 25 Gbps bandwidth options, ensuring seamless multiplayer sessions and zero packet loss.

You also get built-in DDoS protection, 20+ global data centers for low-latency access, and full root control for modding, configuration, or backups. Prefer crypto payments? They’re supported too.

Deploy your Palworld server in minutes with RedSwitches,  the easiest way to build worlds that never sleep.

FAQs 

Q. Can I host a Palworld server on Linux?

Yes. You can also use the official Docker image on Linux. Avoid Docker Desktop on Windows for heavy I/O (use native or WSL2 bind mounts instead). Palworld supports Linux through SteamCMD. You can run the dedicated server using command-line tools, but ensure you install all dependencies and open the same ports (8211, 27015). Linux hosting is stable and often uses less memory than Windows.

Q. How do I fix the “connection timed out” error?

Check if port 8211 (UDP) and 27015 (TCP/UDP) are forwarded correctly. Make sure your firewall allows inbound traffic, and your PublicIP in PalWorldSettings.ini matches your real public IP. If you use a router with double NAT, ask your ISP for a public IP.

Q. Can PS5 and Xbox players join my server?

Yes ,  but only if your server runs in community (public) mode. Use the -publiclobby flag when launching your server so it appears in the Community Servers list. Console players cannot join via direct IP.

Q. How do I upload my world save?

Find your save folder under PalServer\Pal\Saved\SaveGames. Copy your old save files into this directory and match the correct world folder name. Restart the server, and your uploaded world will load automatically.

Q. How much RAM do I need?

For small groups, 16 GB RAM works fine. For 20–32 players or modded worlds, use 32 GB or more. Also, always host on an SSD,  it improves load times and stability.

Q. Why isn’t my server showing up in the browser?

Ensure you started with -publiclobby. Forward 27015 (Steam query port) and wait a few minutes for the list to refresh. If it still doesn’t show, verify your PublicIP and restart both the server and router.

Hafsa Saim

As a seasoned content writer passionate about technology, I've spent the past five years crafting engaging and informative content that bridges the gap between complex technical concepts and everyday understanding. With a deep understanding of hosting and cloud solutions, I specialize in creating content that resonates with industry experts and non-technical persons. I aim to empower readers with valuable insights and practical guidance in the ever-evolving world of technology.