Palworld 1.0 launched on 10 July 2026, and if you’re setting up a server for the first time — or updating an existing one — this guide covers everything: the three ways to play together, exactly how to install a dedicated server yourself with SteamCMD, the config settings actually worth changing, and when it makes more sense to rent a server instead of babysitting your own PC.
Three ways to play Palworld with friends
Before installing anything, it’s worth knowing which option actually fits your group, since each one trades off convenience against control in a different way.
🎮 Invite co-op
One player hosts directly from the game client, up to a handful of friends join. Zero setup, but the world only exists while the host is playing — closing the game ends the session for everyone.
🖥️ Self-hosted dedicated server
Free to run via SteamCMD, covered in full below. Gives you complete control, but your PC has to stay on 24/7 and you’re responsible for updates, backups and troubleshooting.
☁️ Rented managed server
A provider runs the server for you — always online, one-click updates, no port forwarding. Costs a small monthly fee but removes the maintenance entirely.
Quick reality check before you self-host
Palworld’s dedicated server process is known for accumulating RAM the longer it runs — an 8GB box that’s fine on day one can start struggling after a long weekend without a restart. This got more noticeable with 1.0’s larger world state (World Tree, Sky Islands, expanded Paldeck), so budget at least 16GB if you’re self-hosting for more than a couple of players, and schedule regular restarts regardless.
Self-hosting on your own PC — full SteamCMD setup
You don’t need to own Palworld to host it — the dedicated server downloads for free through SteamCMD’s anonymous login (Steam App ID 2394010), separate from the paid game client (App ID 1623730). This is standard for Steam dedicated servers.
Step 1 — System requirements
| Component | Minimum | Recommended for 1.0 |
|---|---|---|
| OS | 64-bit Windows 10/11 or Linux | Windows Server 2022 or Ubuntu 22.04/24.04 |
| CPU | 4-core, ~3.5GHz | High single-core clock — the simulation is single-thread-bound |
| RAM | 8GB | 16GB+ — memory use grows the longer the server runs |
| Storage | 15GB free | SSD or NVMe — initial download is ~12–15GB |
| Network | Open UDP 8211 | Also open UDP 27015 if listing publicly |
Step 2 — Install SteamCMD and download the server
Download SteamCMD, extract it into its own folder, then run the following command to pull the dedicated server files:
If you’d rather specify exactly where the server installs, add force_install_dir before the login step:
Step 3 — Launch the server
Run PalServer.exe (Windows) or PalServer.sh (Linux) with launch flags to set your server name, port, player cap and performance options:
Drop -publiclobby if you want a private, invite-only server. The player cap is hard-limited at 32 via ServerPlayerMaxNum in the settings file.
Step 4 — Run it as a proper service (Linux)
If you’re hosting on a Linux box or VPS long-term, wrap the server in a systemd service rather than a plain terminal session. That gives you automatic restart on boot, clean recovery after a crash or out-of-memory kill, and no dependency on keeping an SSH session open. Create a dedicated palworld user, place the server files under that account, and point ExecStart at the same launch flags used above.
PalWorldSettings.ini — the settings worth changing
The main config file starts out empty. Copy everything from DefaultPalWorldSettings.ini into PalWorldSettings.ini — found at Pal/Saved/Config/WindowsServer/ on Windows — then edit that copy. Editing the Default file directly does nothing; the server only reads from the live copy, and it needs to have been launched once already to generate the folder structure.
ServerName=“My Palworld Server”
ServerDescription=“UK community server”
AdminPassword=“changeme” // set this before going public
ServerPlayerMaxNum=32 // hard cap
PublicIP=“” // required if listing publicly
PublicPort=8211
RCONEnabled=True // remote admin without console access
🔐 AdminPassword
Set before opening your server publicly. Type /AdminPassword yourpassword in in-game chat to gain admin rights on your own server, unlocking commands like teleport, kick and ban.
📡 RCON
Enables remote administration without needing direct console access — useful if your server runs headless on a VPS. Set RCONEnabled=True and forward the RCON port too if using it remotely.
🌍 PublicIP / PublicPort
Only needed if you want your server to appear in the in-game community server browser. Skip these for a private, invite-only server where friends connect by direct IP.
👥 ServerPlayerMaxNum
The real ceiling on player count, hard-capped at 32. Set it lower than 32 deliberately if you want to keep performance headroom for a smaller, more active group.
There’s a well-known quirk worth flagging: some Palworld hosts note that once a world has been created, certain .ini changes silently stop taking effect because WorldOption.sav in the save folder can override them. If a setting change doesn’t seem to be applying, that file is the first place to check.
Connecting, port forwarding and going public
Once your server is running, launch Palworld, go to Join Multiplayer Game, and enter your address at the bottom of the screen. On the same machine, that’s 127.0.0.1:8211. For friends on your home network, use your PC’s local IP instead (find it via ipconfig on Windows).
For friends connecting over the internet, you’ll need to forward UDP port 8211 on your router to your PC’s local IP — the exact steps vary by router, but you’re looking for a “Port Forwarding,” “NAT,” or “Virtual Server” section in its admin settings. If your ISP uses CG-NAT or you share a public IP with other households, standard port forwarding won’t work — in that case a VPN tool like Radmin VPN or Hamachi, or simply renting a server, sidesteps the problem entirely.
Common connection problem
If your server isn’t showing up in the community browser or friends can’t connect, it’s almost always a port issue. Double-check UDP 8211 is open — not TCP — in both your OS firewall and your router, and that UDP 27015 is open too if you want the server to appear in the public listing. Direct-connecting by IP:port bypasses the browser entirely and is the fastest way to confirm the server itself is actually working.
Saves, backups and updating without breaking things
Your world data lives in Pal/Saved/SaveGames. Copy this folder somewhere safe before any major update or config change — it’s the single most important habit for anyone self-hosting long-term. If you’re on a VPS, back it up off the server entirely, to a cloud bucket or a separate machine, and enable rolling backups if disk space allows.
To update the server after a patch, always stop it first — never update with players online — then re-run the same SteamCMD command used for the initial install:
Restart the server and confirm clients can connect without a version mismatch error before announcing it’s back up. Pocketpair has confirmed 1.0 does not automatically wipe existing saves, though they recommend starting a fresh world to properly experience the new content — if you do carry an old save forward, keep a backup of it specifically in case older saves behave unpredictably against the new world generation.
When to rent instead of self-host
Everything above works, and it’s genuinely free if you have a spare machine and don’t mind a terminal. The catches show up over time rather than on day one: your PC has to stay on 24/7 for the world to exist, your home upload speed carries the entire server, and Palworld’s well-known memory growth issue means you’re the one who notices when performance degrades and has to restart it — often at an inconvenient time.
A rented, managed server removes all of that: it stays online regardless of whether your own PC is running, updates are handled for you or are one click away, and if something goes wrong there’s a support team rather than just you and a search engine. Given how much bigger Palworld’s world got with 1.0, that trade-off is worth it for most groups beyond two or three casual players.
See the best Palworld 1.0 hosting providers →Palworld dedicated server — frequently asked questions
Don’t want to babysit restarts? Rent a Palworld 1.0 server instead.
Compare the best Palworld 1.0 hosting providers →
