How to Make a Palworld Dedicated Server (2026)

There are two ways to run a Palworld dedicated server: install and maintain it yourself with SteamCMD on your own hardware, or rent a pre-configured dedicated server and deploy it in about 30 seconds. This guide walks through both so you can pick the right path, then covers the ports, config, and admin tasks every Palworld server owner needs.

Why run a dedicated server instead of hosting from the game?

Palworld lets you host a co-op session directly from the game client, but that mode is capped at 4 players and only stays online while the host is in the game. A dedicated server is a separate always-on process that keeps your world running 24/7, supports up to 32 players, and gives everyone a persistent world they can join at any time — even when you are offline. If you want a community server, a friends group larger than four, or a world that keeps progressing while you are away, you need a dedicated server.

A dedicated server also unlocks full administrative control: you can edit every value in PalWorldSettings.ini (XP rate, gather and damage multipliers, day/night length, death penalty, PvP), run the REST admin API, kick or ban players, and take backups. None of that is available from the in-game 4-player co-op host.

Method 1 — Self-host with SteamCMD (manual)

The manual route installs the Palworld Dedicated Server tool from Steam onto a machine you own and manage. It is free of hosting fees but you are responsible for the hardware, the operating system, port forwarding, updates, and uptime. Here is the full process on Windows or Linux:

1. Install SteamCMD, Valve's command-line tool for downloading dedicated server files. On Windows download the SteamCMD zip and extract it; on Linux install the steamcmd package for your distribution.
2. From SteamCMD, run login anonymous, then app_update 2394010 validate to download the Palworld Dedicated Server (app ID 2394010). On Linux you will also need the 32-bit and 64-bit compatibility libraries and, in most cases, Proton or the Windows build under a compatibility layer.
3. Launch the server once (PalServer.exe on Windows, PalServer.sh on Linux) to generate the default configuration files, then shut it down.
4. Open DefaultPalWorldSettings.ini, copy the settings block into Pal/Saved/Config/<Platform>/PalWorldSettings.ini, and edit the values you want (server name, password, player count, XP and gather rates).
5. Forward the required ports on your router and firewall: UDP 8211 for game traffic, and optionally TCP 8212 for the REST admin API. Without the UDP 8211 port open, players will not see or be able to connect to your server.
6. Restart the server. Share your public IP and port (for example 203.0.113.10:8211) so players can add it as a community server or connect directly.

The manual method works, but the ongoing burden is real: you keep the host machine powered and online, patch it whenever Pocketpair ships an update, secure the box, and troubleshoot your own networking. A home connection also exposes your IP address and offers no DDoS protection, which matters for a public community server.

Method 2 — Deploy a managed Palworld server on Flux (30 seconds)

The faster path skips the installation entirely. A managed Palworld dedicated server on the Flux decentralized cloud is pre-built with the correct SteamCMD image, the right ports already exposed, and DDoS protection on by default. Instead of an afternoon of setup, deployment takes about 30 seconds:

1. Create a free account with Google or email.
2. Choose a plan sized to your group — 5GB RAM for small co-op groups up to 4 players, 8GB for up to 8, 12GB for up to 16, or 16GB for a full 32-player server.
3. Pick a server region close to your players from 50+ countries to keep latency low.
4. Click deploy. Your Palworld dedicated server is provisioned, the game port is opened, and it comes online in under 30 seconds.
5. Open the web dashboard to edit PalWorldSettings.ini, browse files, take backups, and use the console — no SSH or port forwarding required.

Because the server runs on Flux's distributed network rather than your home connection, your personal IP is never exposed, the server stays online 24/7, and enterprise-grade DDoS protection is included at no extra cost. Updates and the base image are handled for you.

Ports and configuration every Palworld server needs

Whichever method you choose, two ports define a Palworld dedicated server. UDP 8211 is the game port players connect through — it must be open and reachable or the server will not show up. TCP 8212 is the optional REST admin API used to query players, save the world, broadcast announcements, and shut down gracefully. If you rent on Flux both are handled for you; if you self-host you must forward them manually.

Core settings live in PalWorldSettings.ini. The most-changed values are ServerName, ServerPassword, AdminPassword, PublicPort (default 8211), ServerPlayerMaxNum (up to 32), and the multipliers for experience, gathering, and damage. See our dedicated guide to the best Palworld server settings for a full breakdown of every option and recommended values.

Next steps

Once your server is live, point your friends to it. If they are on the same platform they can add it as a community server or connect by IP and port; cross-platform play between Steam and Xbox/Game Pass has specific caveats covered in our guide on how to join a friend's Palworld server. To fine-tune the experience — faster leveling, harder bosses, longer days — head to our best Palworld server settings guide.