You and a few friends want to roam Palpagos together without one person's PC being the bottleneck. Good call. Working out how to host a Palworld dedicated server is one of the friendlier survival-game setups out there, but there are two or three traps that will quietly eat an evening if nobody warns you first. I've stood up plenty of these. Let me walk you through both paths (a managed host and a raw SteamCMD self-host), the config values actually worth touching, and the connection errors that make people quit before they even join.
Hosted setup vs a SteamCMD self-host
Two ways to do this, and they suit different people.
Self-hosting with SteamCMD means installing the dedicated server app on a machine you own (or a VPS) and running it yourself. Free if you already have the hardware, and a genuinely good way to learn how the server behaves under the hood. Here's the catch: Palworld's dedicated server is a memory hog. A fresh world with four players sits comfortably around 8 GB of RAM, and I've watched a busy 16-player world climb past 20 GB after a few weeks of base-building. Run it on your gaming PC and you're heating your room, tying up your upload bandwidth, and pausing the world the second you shut the machine down. You're also opening ports on your home router and hoping nobody points a flood at your IP.
Managed hosting hands you a running server in about a minute. On our Palworld server hosting you pick the game, it installs, and you get a live IP plus full file access to edit configs. No SteamCMD, no port forwarding on your own router, and DDoS protection sits in front of the box. Our nodes are in Frankfurt, London, and Gravelines, so ping stays low for anyone playing across Europe. Honestly, if the goal is "friends can hop on any time without me leaving my desktop running," get a hosted slot. If the goal is learning Linux and you don't mind babysitting a process, self-host.
Still weighing it up? We wrote a longer breakdown in how to choose game server hosting that maps onto Palworld cleanly.
Self-hosting the Palworld server with SteamCMD
Going the DIY route? Here's the no-fluff version. This assumes a Windows machine or Windows VPS. Linux works through the Proton wrapper, but Windows is less fiddly for Palworld specifically, so start there if you can.
- Download and unzip SteamCMD from Valve. Drop it somewhere with a short path like C:\steamcmd. Deep nested folders cause strange failures, so keep it shallow.
- Run steamcmd.exe, then type login anonymous. The Palworld dedicated server doesn't need a paid account.
- Install the server with app id 2394010: run app_update 2394010 validate. That download is roughly 8 GB, so give it a few minutes.
- Launch PalServer.exe once. The first boot generates the config files. Let it come up, then close it.
- Open Pal\Saved\Config\WindowsServer. You'll find a nearly empty PalWorldSettings.ini. Copy the full default block from DefaultPalWorldSettings.ini (in the install root) into it, or every edit you make gets ignored. This is the single most common thing people miss.
- Forward UDP port 8211 on your router to the host machine. Add query port 27015 too if you want the server listed publicly.
One tip that saves real grief: launch the server with -useperfthreads -NoAsyncLoadingThread. It smooths the stutters that show up around six or more players. And flip RCONEnabled=True early if you ever want admin commands or automated restarts. Setting it up later means another server bounce nobody wants at 11pm.
PalWorldSettings.ini values worth tuning
This file is where a private server for friends actually gets fun. The defaults are tuned for a public grind, and you almost certainly want something friendlier. Everything below lives on one long line inside PalWorldSettings.ini, so edit carefully and keep the formatting intact. A stray missing comma and the whole line reverts to defaults on next boot.
Capture and drop rates
Nudge PalCaptureRate up to somewhere around 1.5 to 2.0 if you're sick of Pals breaking out of spheres. Early-game catching feels generous without becoming a joke. Pair it with DropItemMaxNum and the XP multipliers if you want faster progression overall. For a chill weekend group I usually set ExpRate to 1.5 and leave it there.
Day and night length
DayTimeSpeedRate and NightTimeSpeedRate control how fast time passes, and higher numbers mean shorter periods. Nights drag in Palworld, and the cold early ones are genuinely rough, so pushing NightTimeSpeedRate to about 2.0 makes nights roughly half as long. Keep day speed near 1.0 so you still have time to build something.
Player count and server slots
ServerPlayerMaxNum defaults to 32. Be honest about your hardware, though. For a group of four to eight, cap it at what you'll actually use: a lower cap reserves less RAM and keeps strangers out if you ever accidentally list the server. Set ServerName and AdminPassword here as well, and if you want it locked down, set ServerPassword so only people with the password get in.
Base and building tweaks
Groups that love sprawling bases will want to raise BaseCampMaxNum and BaseCampWorkerMaxNum (the worker Pal limit per base defaults to 15). More workers means more RAM and CPU, so don't crank it unless the host has headroom. This is exactly the spot where a managed box beats a laptop that also has to run your game client.
Saving and backups
Palworld autosaves on a timer, but the save format has bitten people, especially right after big updates. The world lives in Pal\Saved\SaveGames under a long numeric folder. Back that whole folder up on a schedule and thank yourself later. On a self-host, a scheduled task that zips the SaveGames directory nightly is plenty. If you run RCON, fire the Save command before you copy, so you grab a clean state instead of a half-written one.
Here's a real gotcha: Palworld has historically had a save-bloat problem where the world file balloons and load times crawl. Dated backups mean that if a save corrupts or swells, you roll back a day instead of losing weeks of progress. On our game server hosting you get full FTP access to pull those save folders down whenever you want, and migrations between servers are free if you outgrow your plan or decide to move regions closer to your friends.
Common connection issues (and quick fixes)
This is where most of the "it doesn't work" messages come from. Run through these in order and you'll clear nearly all of them.
- Friends can't find the server in the list. Don't trust the community browser, it's flaky. Have people use "Join via IP" with your address and port, like 1.2.3.4:8211. Direct connect is far more reliable than scrolling a list.
- Port not open. On a self-host, if UDP 8211 isn't forwarded correctly, nobody gets in. Test it from outside your network, not from a device on the same LAN, because a same-network check can pass falsely and send you chasing ghosts.
- Version mismatch. After a Palworld patch, the server has to update too or clients get kicked. Re-run the SteamCMD update, or on a hosted server, restart to pull the latest build.
- Player cap or password wrong. A "server is full" message or a silent rejection usually traces to ServerPlayerMaxNum set too low or a ServerPassword typo. Check both in PalWorldSettings.ini before blaming the network.
- Coop vs dedicated confusion. The in-game "Invite Code" coop mode caps at four and isn't a dedicated server at all. Want persistence and more slots? You need the dedicated server, which is the whole point of this guide.
Get the config file populated correctly, forward that one UDP port, and back up your saves on a timer, and a Palworld server for your friends more or less runs itself. If you'd rather skip the router wrangling and the "who left their PC on" problem, learning how to host a Palworld dedicated server on a hosted box takes about a minute and keeps the world alive around the clock. Either way, you've got what you need to go catch a few thousand Pals together.