How to create a Palworld server: the complete 2026 guide

We break down each point below, with real numbers and real pitfalls to avoid.

Requirements: what you need before getting started

Minimum server specs

Palworld isn't a lightweight game on the server side. It runs on Unreal Engine and continuously handles base, Pal and persistent world logic. Concretely, you'll need:

• CPU: 4 cores minimum, 3.5 GHz or more recommended. The process can saturate two full cores under heavy load.
• RAM: 8 GB absolute minimum, 16 GB recommended. The game has known memory leaks that drive up consumption during long sessions.
• Storage: an SSD, count on 12 to 15 GB for server files, plus extra room for saves that grow fast.
• OS: 64-bit Windows or 64-bit Linux (Ubuntu 20.04 and up, AlmaLinux...).
• Bandwidth: a stable upload connection, otherwise your players will feel lag as soon as more than 4 or 5 are connected.

For a group of 4 to 8 players, 8 GB of RAM can be enough. Beyond 12 active players with several bases, plan for 16 to 32 GB instead.

Rented dedicated server vs self-hosting: the real comparison

This is THE question to settle before you start. You have two options:

Self-hosting, on your PC or an old box at home:

• Free to run, but your machine needs to stay on 24/7 if you want a permanent server.
• You alone manage port forwarding, NAT, updates and crashes.
• Your personal internet connection is the pipe: as soon as someone downloads a movie next door, everyone lags.
• If your PC turns off or crashes, the server goes down with it.

A dedicated server rented from a specialized gaming host:

• Machine running permanently, in a datacenter, with dedicated bandwidth.
• Setup in a few clicks, automatic Palworld updates.
• Technical support if something goes wrong, automatic backups.
• Monthly cost, but generally just a few euros for a small group.

A Palworld server rented from a specialized gaming host mainly avoids network headaches: NAT, port forwarding, outages tied to your home router. For a community that intends to last, it's clearly the more comfortable option.

Step by step: creating and configuring your Palworld server

1. Create or order the server

If you self-host, you need to go through SteamCMD:

1. Download SteamCMD from Valve's official website.
2. Open a command prompt and run steamcmd.
3. Log in anonymously: login anonymous.
4. Install the server: app_update 2394010 validate.
5. The PalServer folder is created automatically.

If you rent from a host, installation generally happens automatically as soon as your order is validated. You get your FTP credentials or your management panel, and PalServer is already installed and ready to configure. That's clearly the fastest path if you don't feel like fiddling with command lines on a Sunday evening.

2. Configure the PalWorldSettings.ini file

This is the heart of your server's customization. The file is located at:

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

On a rented server, it's generally accessible directly from the control panel, which avoids digging through the FTP folder tree.

Important rule: the file must contain exactly 2 lines:

[/Script/Pal.PalGameWorldSettings]
OptionSettings=(ServerName="MyServer",ServerPlayerMaxNum=32,ServerPassword="",AdminPassword="adminpassword",PublicPort=8211,PublicIP="")

The most commonly used settings:

• ServerName: the name shown in the server list.
• ServerPlayerMaxNum: max number of players (32 by default).
• ServerPassword: password to join, leave empty for an open server.
• AdminPassword: required for in-game admin commands.
• Difficulty and DayTimeSpeedRate: to adjust difficulty and the day/night cycle speed.
• bIsMultiplay: enable for a classic multiplayer server.

3. Open the right ports

If you self-host, you need to forward two ports on your router:

• UDP 8211: the main game port, handling player connections.
• UDP 27015: the Steam query port, useful for the server to show up in the list and report connection info.

This is done through your router's admin interface (often at 192.168.1.1), in the "port forwarding" or "NAT/PAT" section. With a specialized host, this step is already done: ports are natively open, you never touch it.

4. Start the server and connect to it

Once the .ini file is saved, launch PalServer.exe (Windows) or ./PalServer.sh (Linux). The server starts, loads the world, and shows its status in the console.

To join from the game:

1. Main menu > Multiplayer.
2. Join a community server or enter the public IP and port directly.
3. Enter the password if you set one.

If it doesn't connect on the first try, check ports and the Windows firewall first — that's the number one cause of connection failures.

PC/Xbox Crossplay and Server Clustering: the big novelty of version 1.0

Since Palworld's move to version 1.0, two features really change the game for anyone running a community server.

PC/Xbox crossplay enabled natively

Steam, Xbox and Game Pass players can now meet on the same dedicated server, without workarounds or third-party software. No more groups split up because one friend plays on console.

For this to work, the server needs to be set to public community mode with the right crossplay settings enabled in PalWorldSettings.ini. Nothing insurmountable, but a badly configured setup and crossplay won't activate.

Server clustering, so you're no longer bottlenecked by the CPU

This is THE novelty that changes everything for large communities. Clustering lets you link several server instances together to form a single persistent world.

Why this matters:

• A classic server quickly saturates once you go past about thirty active players, because of the load from base and Pal calculations.
• Clustering spreads that load across several machines: more connected players, without crushing a single processor.
• For a growing guild or an RP server with several active bases at once, it's the difference between a smooth world and one that lags on every raid.

This is where hosting choice really matters. Setting up clustering yourself across several machines, managing the network between instances and getting crossplay to work properly requires networking skills few players have handy on a Friday night.

A specialized gaming host, unlike a generic cloud provider, natively handles this kind of setup: network routing between instances, port opening for crossplay, cluster load balancing. That's exactly the difference between a provider that knows Palworld's specific inner workings and a generic cloud host not necessarily built for this kind of game.

If your community is aiming for scale and simultaneous PvP content, it's worth checking that your Palworld hosting natively supports clustering and PC/Xbox crossplay, rather than trying to set it up yourself from scratch.

FAQ

All the answers to frequently asked questions about creating a Palworld server are available in the FAQ box automatically generated at the top of this page. If a question is missing, contact Lordhosting support via Discord or by ticket.