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. If renting is the route for your group, our best Palworld server hosting comparison covers the providers worth shortlisting. For single-host verdicts, read DatHost for Palworld or LOW.MS for Palworld.
🎮 Invite co-op
One player hosts directly from the game client and up to three friends join (four players in total). 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 can creep up in RAM over long uptimes. Pocketpair has shipped dedicated-server memory-leak fixes several times, most recently in the 1.0 release notes, but its official requirements still recommend 16GB of RAM, 32GB or more for larger servers, and warn that 8GB boots but raises the risk of out-of-memory crashes. Budget 16GB if you’re self-hosting, 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 | Pocketpair’s requirement (v1.0.4 docs) | What it means in practice |
|---|---|---|
| OS | Windows 64-bit or Linux 64-bit (Ubuntu, AlmaLinux etc.) | Windows via Steam or SteamCMD, Linux via SteamCMD, or the official Docker image |
| CPU | 4 cores or more (recommended) | A recommendation rather than a hard minimum; there is no official clock-speed figure |
| RAM | 16GB; 32GB or more for larger servers | 8GB boots, but Pocketpair warns it makes out-of-memory crashes more likely |
| Storage | Fast SSD recommended | Pocketpair warns low-performance storage may corrupt save data |
| Network | UDP 8211 (default, changeable) | The only port you need to forward for players |
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:
Prefer containers? Pocketpair also publishes an official Docker image with a sample Compose file (pocketpairjp/palworld-dedicated-server-docker on GitHub). Its docs advise against Docker Desktop because of storage performance and save-corruption risk.
Step 3 — Launch the server
Run PalServer.exe (Windows) or PalServer.sh (Linux) with the official launch options for port, player cap and community listing (the server name is set in the settings file, not on the command line):
./PalServer.sh -port=8211 -players=32 -publiclobby
-publiclobby registers the server in the in-game community server list, which Xbox and PS5 players need. Drop it for a private server that friends reach by direct IP and password. Older guides add -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS; Pocketpair’s docs now say that in v1.0 and later, leaving these unset may improve performance. 32 players is the default and the most Pocketpair supports.
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 and Pal/Saved/Config/LinuxServer/ on Linux — then stop the server and edit that copy. All settings sit inside one long OptionSettings=(...) line, so change values in place. 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”
ServerPassword=“friendsonly” // join password, empty = open
AdminPassword=“changeme” // set this before going public
ServerPlayerMaxNum=32 // default and maximum
PublicIP=“” // optional, auto-detected when blank
PublicPort=8211 // optional, advertised port only
RESTAPIEnabled=True // remote admin; keep it on your LAN
🔐 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.
📡 REST API (RCON is deprecated)
For headless admin on a VPS, Pocketpair now points to the REST API (RESTAPIEnabled=True, Basic Auth with the admin password). RCON (default port 25575) is deprecated and scheduled to stop working in an upcoming update. Pocketpair says neither is designed to be exposed to the internet, so don’t port-forward them; use them from your LAN or over a VPN/SSH tunnel.
🌍 PublicIP / PublicPort
Optional, and only used by community servers. Both are detected automatically when left blank; set them only if the community list shows the wrong address. PublicPort changes the advertised port, not the port the server listens on. Listing itself comes from -publiclobby.
👥 ServerPlayerMaxNum
The maximum number of players who can join; 32 is the default and the most Pocketpair supports. Set it lower 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 list, first check that it was started with -publiclobby; without it the server never registers. If friends can’t connect at all, it’s almost always a port issue: double-check UDP 8211 is open — not TCP — in both your OS firewall and your router (no other port is needed for the listing). If your router lacks hairpin NAT you won’t see your own community server from inside the same network even when outsiders can. Direct-connecting by IP:port bypasses the list 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’s 1.0 release notes say you can continue with your existing save data, though they recommend starting fresh with a new character to enjoy the new experience. If you carry an old world forward, keep a backup of it: the notes warn that players on saves from v0.7.3 or earlier may spawn outside the new map boundary (use Emergency Escape from the Options menu), and that saves depending on removed mods may not load.
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. 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 →