Palworld Server Setup Guide 2026 — Dedicated, Hosted & Self-Hosted

1. Palworld Servers Are Resource-Hungry

A Palworld dedicated server with 4–8 players needs at minimum 8 GB of RAM and a 4-core CPU. For 16+ players, plan for 16 GB RAM and 6+ cores. The game simulates every Pal, base, and world interaction server-side — it's not a lightweight process. If you're renting a VPS, budget at least $15–$25/month for a machine that won't lag during peak hours.

2. You Need to Open Ports (Unless You Use a Host)

For anyone outside your home network to connect, you must forward UDP port 8211 on your router. If you're using a third-party host like GPortal or Nitrado, they handle this for you — no router configuration needed. Self-hosting or running your own dedicated server? Port forwarding is mandatory, and we cover it in detail below.

3. Server Progress Is Tied to the Server, Not Your Account

Unlike many games, Palworld server saves are world-level — the map, bases, and Pal data live on the server machine. If the server goes down without a backup, progress is lost for everyone. Set up automatic backups (covered in each option below) before you invite anyone.

4. 32 Players Is the Default Cap

Palworld's official dedicated server supports up to 32 concurrent players by default. You can lower this in the config to reduce resource usage, or raise it if your hardware can handle the load. Most community servers run comfortably with 10–20 players on mid-range hardware.

5. Crossplay Is Limited (as of 2026)

Steam players can connect to any dedicated server. Xbox/Game Pass players have more restrictions — check Pocketpair's latest crossplay status before inviting console friends. As of the 1.0 release, crossplay support is improving but not yet seamless across all platforms.

Step 1: Install SteamCMD

Windows: Download SteamCMD from Valve's official CDN. Extract it to a folder like C:\steamcmd. Run steamcmd.exe once — it will update itself and drop you into the Steam> prompt.

Linux (Ubuntu/Debian): SteamCMD is available via multiverse repo:

Step 2: Download the Palworld Server

From the SteamCMD prompt (Steam>), run these commands:

The server files are roughly 20 GB. Download time depends on your connection. App ID 2394010 is the official Palworld Dedicated Server — it's free and does not require owning the game.

Step 3: Configure the Server

Navigate to palworld-server/Pal/Saved/Config/WindowsServer/ (or LinuxServer/ on Linux). Find or create PalWorldSettings.ini. This is your main configuration file. Start with the defaults and tweak as needed — every setting is explained in the Server Settings section below.

Step 4: Start the Server

Windows: Run PalServer.exe from the server folder. A console window opens — leave it running. The server is ready when you see "Server is up and running" in the log.

Linux: Run ./PalServer.sh from the server directory. For background operation, use:

The flags -useperfthreads and -UseMultithreadForDS improve performance on multi-core machines — always include them.

Step 5: Set Up Automatic Backups

The server world save is at Pal/Saved/SaveGames/0/. Set up a scheduled task or cron job to copy this folder every hour:

Linux cron (hourly backup):

Step 6: Connect to Your Server

Launch Palworld, click "Join Multiplayer Game", and enter your server's public IP address followed by the port: 123.45.67.89:8211. If you're playing on the same machine as the server, use 127.0.0.1:8211. Set a server password in PalWorldSettings.ini if you want to keep randoms out.

Why Use a Game Server Host?

Third-party hosts provide a managed Palworld server on their hardware. They handle: automatic updates when Pocketpair patches the game, DDoS protection, automated backups, and a web-based control panel where you change settings without touching config files. The trade-off is cost — typically $5 to $20 per month depending on player slots and RAM.

GPortal — Official Palworld Partner

GPortal is Pocketpair's official hosting partner for Palworld. Their Palworld plans start around $5.60/month for 4 slots and scale up to 32 slots. Key features:

• One-click install — server is live within 2–3 minutes of purchase
• Built-in automatic backups with restore from any save point
• Web interface for all server settings (no INI file editing)
• Automatic updates when Pocketpair releases patches
• DDoS protection included on all plans
• Server locations in North America, Europe, and Asia-Pacific

Setup process: Sign up at gportal.com → Select Palworld → Choose your plan and region → Pay → Server auto-deploys. You'll get an IP address and port. Share it with your friends — they connect the same way as any multiplayer game.

Nitrado — Strong Alternative with Global Coverage

Nitrado is another major host with extensive Palworld support. Plans start around $7.99/month for 4 slots. Their advantages:

• Wider global server location coverage than GPortal (including South America and Middle East)
• Dynamic switching — change your server location without losing save data
• Mobile app for server management on the go
• Advanced scheduling — auto-restart your server daily at a set time
• Mod support via their control panel (workshop mods, config mods)

Setup is nearly identical: sign up → pick Palworld → configure slots/region → deploy. Both GPortal and Nitrado give you a public IP immediately after deployment.

Other Reputable Hosts

• Shockbyte — Budget-friendly, often runs promotions. Good for small groups. Plans from ~$7/month.
• Nodecraft — Strong UI/UX, good for admins who want an easy control panel. Plans from ~$10/month.
• GTXGaming — Higher price point but includes 24/7 live support chat. Good if you want someone to call when things break.

How to Choose a Host: 4 Questions

1. Where are your players? Pick a host with a data center near your group. Latency matters — connecting from Asia to a US server adds 150–250ms ping.
2. How many slots? Don't overpay. A 10-slot server is plenty for most friend groups. Only go to 32 if you're running a public community.
3. Do they auto-update? Palworld patches frequently. A host that doesn't auto-update means your server is offline until you manually trigger it.
4. What's their refund policy? Most hosts offer a 24–72 hour refund window. Test server performance before committing.

Requirements

Running the server and the game client simultaneously on the same machine is demanding. You'll want:

• 16 GB RAM minimum (32 GB recommended for smooth gameplay + server)
• 6-core CPU or better (the server uses 2–4 threads by itself)
• SSD with 40+ GB free (server files + game client + world saves)
• Stable internet — upload speed matters more than download for hosting

Method A: Dedicated Server Tool (Steam)

The easiest self-host method available since the 1.0 update:

1. Open Steam → Library → Use the dropdown above your game list to enable "Tools"
2. Find "Palworld Dedicated Server" in the list and install it
3. Launch it from Steam — a console window opens
4. Wait for "Server is up and running" in the console
5. Launch Palworld normally → Join Multiplayer Game → Enter 127.0.0.1:8211 (for you) or your public IP for friends

Method B: In-Game Co-op Mode (No Setup)

Palworld also has a built-in co-op mode that doesn't require any server setup at all:

1. Start a single-player world normally
2. Open the menu → Options → "Multiplayer Settings"
3. Toggle "Enable Multiplayer" to ON
4. Set the max players (up to 4 for co-op mode)
5. Share your invite code (generated in the pause menu) with up to 3 friends

Co-op mode is the fastest option for 2–4 friends. No config, no commands, no port forwarding. The downside: the host must be online and in-game for anyone else to play — it's not a 24/7 server.

Step 1: Find Your Local IP Address

Your server machine needs a static local IP so the port forward rule doesn't break when your router reassigns IPs. On Windows:

1. Open Command Prompt → type ipconfig
2. Find your "IPv4 Address" — usually something like 192.168.1.xxx
3. Go to your router's admin panel (typically 192.168.1.1 or 192.168.0.1)
4. Find DHCP settings → Reserve/assign a static IP for your server machine's MAC address

Step 2: Forward UDP Port 8211

Palworld uses UDP 8211 by default. TCP is not required — UDP only.

1. In your router's admin panel, find "Port Forwarding" (sometimes under Advanced → NAT → Port Forwarding)
2. Create a new rule:
   • Service name: Palworld Server
   • Protocol: UDP
   • External port: 8211
   • Internal port: 8211
   • Internal IP: (your server's static local IP from Step 1)
3. Save and apply. Some routers need a reboot.

Step 3: Configure Windows Firewall (or Linux iptables)

Windows:

1. Open "Windows Defender Firewall with Advanced Security"
2. Inbound Rules → New Rule → Port → UDP → 8211 → Allow the connection
3. Apply to all profiles (Domain, Private, Public)
4. Name it "Palworld Server" and save

Linux (ufw):

Step 4: Verify the Port Is Open

Use an online port checker like canyouseeme.org or portchecker.co. Enter port 8211. If it shows "open" or "success," your friends can connect. If it shows "closed" or "timed out," check:

• Is the server actually running?
• Did you forward UDP (not TCP)?
• Did you set a static local IP for the server machine?
• Does your ISP use CGNAT? (Many mobile/5G home internet providers do — you can't port forward through CGNAT. In this case, use a third-party host or a VPN tunnel like Tailscale.)

The PalWorldSettings.ini file controls everything about your server world. On a third-party host, you'll configure these through a web panel (same settings, different interface). Here are the settings grouped by what you'll actually want to change:

Essential Settings (Change These First)

Difficulty & Progression Settings

Base & Guild Settings

Performance-Related Settings

RCON Settings (Remote Admin)

RCON allows you to send admin commands remotely without being in-game. Essential for dedicated servers:

With RCON enabled, you can use tools like rcon-cli or Palworld-specific RCON web panels to manage your server from any device.

To use admin commands in-game, press Enter to open chat, then type:

This grants you admin privileges for the session. Once authenticated, you have access to these commands:

How to Find a Player's SteamID

Use /ShowPlayers to list everyone on the server. Each entry shows the player's name and a long numeric SteamID. Copy the SteamID for use with /KickPlayer, /BanPlayer, or teleport commands.

Setting Up Moderators

Palworld's dedicated server doesn't have a built-in moderator role — only full admin access. If you want to give someone limited moderation powers (kick only, no server shutdown), you'll need a third-party RCON tool that supports role-based permissions. Most community servers run a lightweight RCON bot (like palworld-rcon-bot on GitHub) that adds moderator roles on top of the base game's admin system.

"Connection timed out" — Friends can't join

Cause: Almost always a port forwarding or firewall issue. Fix: Verify UDP 8211 is open (use canyouseeme.org while the server is running). Check Windows Firewall isn't blocking PalServer.exe. If you're behind CGNAT, switch to a VPN tunnel or third-party host.

Server lags or rubberbands with 8+ players

Cause: CPU bottleneck. Palworld servers are heavily CPU-bound — each base, Pal, and wild spawn eats cycles. Fix: Reduce PalSpawnNumRate to 0.8, disable raids (bEnableInvaderEnemy=False), lower BaseCampWorkerMaxNum to 10, and reduce the player cap. If the problem persists, upgrade to a machine with faster single-core CPU performance (Palworld server doesn't scale perfectly across many cores).

Server keeps crashing after a few hours

Cause: Memory leak. The Palworld dedicated server has a known slow memory leak — RAM usage gradually climbs until it crashes. Fix: Set up a scheduled restart every 6–12 hours. On Linux, use a cron job: 0 */6 * * * /path/to/restart-server.sh. Most third-party hosts have an "Auto-Restart" option in their control panel. This is the single most effective fix for server stability.

World save corrupted / rollback

Cause: Server crashed or was force-killed during a save operation. Fix: This is why backups matter. Navigate to Pal/Saved/SaveGames/0/ on your server. There should be a backup subfolder with timestamped world saves. Copy the most recent backup's contents into the main 0/ folder (overwriting the corrupted one). Restart the server. If you're on GPortal/Nitrado, use their built-in backup restore feature — no manual file copying needed.

Server not showing up in community server list

Cause: The community server browser only shows Steam servers that have registered with the Steam master server. Registration can take up to 15 minutes after startup and requires port 27015–27016 UDP to be open in addition to 8211. Fix: Open UDP 27015 and 27016 in your firewall. Wait 15 minutes after starting the server before checking the list. If it still doesn't appear, use direct connect (IP:8211) — it works regardless of the server list.

Pals frozen or not working at base

Cause: Server-side pathfinding bug — Pals get stuck on terrain, structures, or each other. Fix: This is a game bug, not a server config issue. Workarounds: assign and unassign the affected Pal via the Palbox to reset its position. Build bases on flat terrain with wide pathways. Avoid placing structures too close together. Restarting the server also resets all Pal positions.