How to Host a Palworld Dedicated Server: Setup, Settings and Ports
Quick answer
To host Palworld, download the dedicated server with SteamCMD (app ID 2394010), then copy the contents of DefaultPalWorldSettings.ini into PalWorldSettings.ini under Pal/Saved/Config/WindowsServer or LinuxServer and edit it while the server is stopped. The game listens on UDP 8211 by default and takes up to 32 players. Start it with -publiclobby to appear in the community server list; Steam players can also join by IP. Back up the save folder regularly and keep the server on the same version as the game.
What do you need to host a Palworld server?
The Palworld dedicated server is a separate program that Pocketpair distributes for free, and you do not need to own the game to run it. It is available for Windows and Linux through SteamCMD under app ID 2394010. Players connect with their normal copies of Palworld. Leave a comfortable amount of disk space, because the install is several gigabytes and saves plus backups grow over time.
Memory is what sets Palworld apart from many survival games. Every base, working Pal and dropped item lives in memory, and usage creeps upward the longer the server stays online. Pocketpair's own server documentation lists 16 GB of RAM as the recommended level even for small servers. On the CPU side, a few strong cores and fast NVMe storage reduce the hitches players notice when the world saves.
- SteamCMD and Palworld Dedicated Server, app ID 2394010
- Game port: UDP 8211 (configurable)
- Optional REST API port: TCP 8212, reachable only from a trusted network
- 16 GB of RAM as a comfortable baseline, more for busy servers
- A machine that stays online around the clock, or a rented server
How do you install a Palworld dedicated server with SteamCMD?
Install SteamCMD, log in anonymously and download the server into an empty folder: set the target with force_install_dir, type login anonymous, run app_update 2394010 validate and then quit. You reuse the same command for every update, and validate re-downloads any missing or corrupted files.
On Windows the server starts with PalServer.exe, on Linux with PalServer.sh. The first launch creates the folder structure and a new world, so it is a good habit to start it once and stop it before configuring anything. On the command line, -port sets the game port, -players caps the player count and -publiclobby lists the server in the community server browser. Pocketpair's documentation also suggests -useperfthreads, -NoAsyncLoadingThread and -UseMultithreadForDS on multi-core machines.
Hosting on your own PC is fine for a test, but the world goes offline whenever you shut the PC down, and a home connection needs port forwarding. A rented server comes with the files already installed. In the TheCrewHost game panel, Palworld installs with one click, and the İstanbul location keeps ping low for players in Türkiye.
Where is PalWorldSettings.ini and how do you create it?
All gameplay rules live in PalWorldSettings.ini. On Windows it sits in Pal/Saved/Config/WindowsServer, on Linux in Pal/Saved/Config/LinuxServer. The server usually creates this file empty on first launch. To fill it, copy the contents of DefaultPalWorldSettings.ini from the server's root folder and paste them in. Do not edit DefaultPalWorldSettings.ini itself: the server does not read it, and updates overwrite it.
Every setting sits on one long OptionSettings=( ... ) line, separated by commas. Miss a bracket or a quote and the server may ignore the whole file and start with defaults, so keep a copy before you edit. Always make changes while the server is stopped, because a running server can write its in-memory values back over your edits when it shuts down.
There is one more trap. If the save folder contains a WorldOption.sav file, which happens when you move a world over from a hosted co-op game, the server prefers the settings in that file over the ini. If your ini edits seem to do nothing, check for it first and consider backing it up and removing it.
Which Palworld server settings matter most?
The ini holds dozens of options, but a handful define how your server feels. Rate settings work as multipliers of 1.0, so 2.0 means double and 0.5 means half. ExpRate controls levelling speed, PalCaptureRate the capture chance, EnemyDropItemRate what enemies drop and CollectionDropRate how much wood, stone and ore you get from gathering. Friend groups often raise experience and gathering a little while leaving capture at the default.
DeathPenalty decides what you lose on death: None drops nothing, Item drops your inventory, ItemAndEquipment adds your gear, and All also drops the Pals in your party. Base limits come from BaseCampMaxNumInGuild (bases per guild) and BaseCampWorkerMaxNum (working Pals per base). Raising the worker cap makes players happy but noticeably increases server load, since every working Pal runs its own pathing and task logic.
New keys can appear in the ini as the game evolves. After each update, comparing DefaultPalWorldSettings.ini against your own file is the easiest way to spot options you have not set yet.
| Setting | What it controls | Note |
|---|---|---|
| ServerName / ServerDescription | Name and description in the server list | Keep it short and searchable |
| ServerPlayerMaxNum | Concurrent player limit | Maximum is 32 |
| ServerPassword | Password to join | Leave empty for an open server |
| AdminPassword | Admin rights and REST API password | Make it long and unique |
| ExpRate / PalCaptureRate | Experience and capture rates | 1.0 is the default |
| EnemyDropItemRate / CollectionDropRate | Drops and gathering yield | High values speed up the economy |
| DeathPenalty | What drops on death | None, Item, ItemAndEquipment, All |
| BaseCampWorkerMaxNum | Working Pals per base | Higher values cost CPU and RAM |
| bIsPvP / bEnablePlayerToPlayerDamage | Player versus player damage | Set both to True for PvP |
| PublicPort / PublicIP | Address advertised in the list | Set by hand behind NAT |
Which ports does a Palworld server use?
Players connect on UDP 8211 by default. If you change it with -port, set PublicPort in the ini to the same value, otherwise the community list advertises the wrong port. On a home connection you need to forward this UDP port on your router to the server's local IP and allow it through the operating system firewall.
When the REST API is enabled it listens on TCP 8212 by default. Do not expose that port to the internet. The API is protected by the admin password, but it can kick, ban and shut down the server, so keep it reachable only from the machine itself or a network you trust. Some setup guides also open UDP 27015 for Steam queries, which is worth checking if the server will not show up in the list.
How do players join a Palworld server?
There are two ways in. The first is the community server list: start the server with -publiclobby and players can search for it by name in the community servers tab of the multiplayer menu. The second is a direct connection: Steam players type IP:port, for example 203.0.113.10:8211, into the field at the bottom of the same screen. If you set a password, the game asks for it either way.
If the server does not appear in the list, first confirm that the port is really open, then that -publiclobby is on the command line. New servers can take a few minutes to show up. For a private group, skipping the list entirely and sharing only the IP and password is a perfectly good choice.
Can Xbox and PS5 players join a dedicated server?
Palworld supports crossplay on dedicated servers, bringing Steam, Xbox, PS5 and Mac players into the same world. The CrossplayPlatforms setting in the ini controls which platforms may join; remove a platform from the list and its players can no longer see the server. The default template includes all four.
The practical limit is how players connect. Console players cannot type an IP address, so they can only find your server through the community server list. If you have friends on console, always start the server with -publiclobby and give it a distinctive name that is easy to search. The server itself always runs on a PC, either Windows or Linux; consoles cannot host a dedicated server. Crossplay details have shifted between patches, so check Pocketpair's server documentation after major updates.
How do you manage the server with the REST API and RCON?
The REST API is the current way to manage a Palworld server remotely. You enable it with RESTAPIEnabled=True and a RESTAPIPort, it authenticates with your AdminPassword and it returns JSON. Through it you can list players, broadcast announcements, kick or ban, save the world and shut the server down with a countdown. Many ready-made admin panels and Discord bots are built on top of it.
RCON (RCONEnabled, RCONPort) still appears in the settings file, but community and hosting documentation describe it as being phased out. If you are building a new admin setup, go with the REST API. In game, you become admin with the /AdminPassword command and then use commands such as /KickPlayer, /BanPlayer, /Save and /Shutdown. The endpoint list can change between versions, so treat the documentation for your server build as the reference.
How do you back up and update a Palworld server?
The world save lives under Pal/Saved/SaveGames/0, in a folder named after a long server-specific ID. The safest manual backup is to stop the server and copy that whole folder. Setting bIsUseBackupSaveData=True also turns on the game's own automatic backups, which pile up under the same folder and need occasional cleanup so the disk does not fill. A sensible routine adds a daily off-server copy on top of the in-game backups.
Game and server must run the same version. Palworld reached 1.0 in 2026, and after big updates players cannot join a server left on the old build. To update, stop the server, back up the save folder, run app_update 2394010 validate in SteamCMD again, then carry any new keys from DefaultPalWorldSettings.ini into your own ini. Testing that an old world loads cleanly on a copy before a major patch goes live keeps the risk of losing progress low.
| Players | Suggested RAM | Note |
|---|---|---|
| 1-4 | 8-12 GB | Small friend group, few bases |
| 5-10 | 16 GB | Pocketpair's recommended baseline |
| 11-20 | 20-24 GB | Many bases and working Pals |
| 21-32 | 32 GB or more | Schedule regular restarts |
Set up your Palworld server in 7 steps
- 1
Download the server files
Log in anonymously with SteamCMD and run app_update 2394010 validate into an empty folder, or rent a server that comes with Palworld preinstalled.
- 2
Start it once and stop it
Run PalServer once and shut it down so that the config and save folders under Pal/Saved are created.
- 3
Prepare the settings file
Copy the contents of DefaultPalWorldSettings.ini into PalWorldSettings.ini in the WindowsServer or LinuxServer folder.
- 4
Set your rules
With the server stopped, edit ServerName, ServerPassword, AdminPassword, ServerPlayerMaxNum, the rate multipliers, DeathPenalty and the PvP options.
- 5
Open the ports
Allow UDP 8211 through the firewall and forward it on your router if you host at home; keep the REST API port closed to the internet.
- 6
Get listed
If console players will join, start the server with -publiclobby and check that CrossplayPlatforms includes their platform.
- 7
Plan backups and updates
Enable bIsUseBackupSaveData, copy the save folder off the server every day and take a fresh backup before each update.
Frequently Asked Questions
How many players can a Palworld server hold?
The cap set through ServerPlayerMaxNum is 32 players, and higher values are not accepted. In practice the hardware is the real limit: a full 32-player server with many bases and working Pals needs a lot of memory. For small communities, a limit somewhere between 8 and 16 keeps both performance and the crowding in the world under control.
I changed the settings but nothing happened. Why?
There are three usual causes: editing the file in the wrong folder, saving while the server was running so it overwrote your changes on shutdown, and a WorldOption.sav in the save folder that overrides the ini. Stop the server, edit the file in WindowsServer or LinuxServer, check the brackets on the OptionSettings line and start it again.
Can I move my co-op world to a dedicated server?
Yes, by copying the save folder into the server's SaveGames folder, but the original host's character is tied to a different player ID and often breaks in the move. The community uses several conversion tools for this. Back up both the original save and the server folder first, and check the result on a test server before inviting everyone.
Why does my Palworld server get slower over time?
As bases, Pals and dropped items pile up, memory use climbs and long-running servers get heavier. A scheduled daily restart, a reasonable cap on working Pals and enough RAM go a long way. If the problem persists, make sure the server build is current, since performance fixes arrive regularly in patches.
Can I install mods?
Many Palworld mods depend on Windows-only tooling and sit outside official support. People who want those mods on a Linux machine often run the Windows server build under Proton instead. Before adding mods, back up the world, check that each mod matches your server version and expect some of them to break after every game update.
Do I need a server password?
Not strictly, but it makes sense for a friends-only server. With ServerPassword empty, anyone who finds the server in the list can join. If you would rather not use a password, keeping the server out of the list and sharing only the IP is a middle ground. AdminPassword should always be set, long and unique, and never shared, since the REST API relies on it.
Can I host a Palworld server for free on my own PC?
Yes. The server software is free and will even run on the same PC you play on. The catch is that the game and the server then compete for a lot of RAM, the world disappears whenever the PC is off, and you have to forward port 8211 on your router. That is fine for a few evenings of testing, but if friends should be able to join any time, a separate machine that stays online is easier.
