A rented Palworld server is worthwhile if your group needs a permanently reachable world with controllable configuration, predictable restarts, and traceable operation. Enough RAM, a cleanly maintained PalWorldSettings.ini, and a short function test after every change are crucial before you invite friends or define larger PvE or PvP rules.
Requirements for a Stable Start
Pocketpair specifies 16 GB RAM for operation. Its official documentation says 8 GB can boot but increases OOM/crash risk; larger setups are recommended to use more than 32 GB. There is no substantiated RAM-per-player mapping: bases, worker Pals, buildings, spawn rate, mods, settings and distributed active world areas also drive load.
At game-serverhosting, a Palworld server is especially suitable if you do not only want to start an instance, but also want technical control, support, and transparent operating processes. Before setup, note down IP, port, admin password, desired player limit, and whether the world should be more PvE, PvP, or a private co-op server.
Classify PalWorldSettings.ini Correctly
The most important file is PalWorldSettings.ini. The official Palworld server documentation explains that you should not permanently edit DefaultPalWorldSettings.ini, but copy the configuration into the correct server file and change it there: documentation at docs.palworldgame.com. The configuration folders are also only created after the server has been started once.
For Linux with SteamCMD, the official documentation names this target path:
steamapps/common/PalServer/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini
For Windows servers, the file is correspondingly located under:
steamapps\common\PalServer\Pal\Saved\Config\WindowsServer\PalWorldSettings.ini
When working with a managed host, you usually open the same file through a file manager, SFTP, or a configuration panel. The important part is the process: stop server, edit file, save, restart server, test result.
Basic Configuration for Player Count, Pals, and PvP
The existing example block remains as a compact starting point. It shows typical values that you should check deliberately:
ServerPlayerMaxNum=32
PalCaptureRate=1.0
bIsPvP=False
bDropItemsOnDeath=False
NightTimeSpeedRate=3.0
ServerPlayerMaxNum sets the player limit. A value of 32 only fits if RAM, CPU reserve, and world activity fit as well. PalCaptureRate changes the capture rate and therefore directly affects the game feel. bIsPvP=False is the calmer start for most private groups because progress, bases, and resources remain less conflict-heavy. bDropItemsOnDeath=False reduces frustration after deaths, but can lower the survival challenge. NightTimeSpeedRate=3.0 significantly speeds up the night; that is practical, but changes balance and atmosphere.
Do not change such values randomly in large batches. A short change note is better: date, previous value, new value, reason. This helps you find out later more quickly which setting caused a problem.
Secure the Server and Invite Friends
For private worlds, you should set a server password:
ServerPassword=YourPassword
Do not use a password that you also use for accounts or payment services. Share IP, port, and password only in a trusted channel. Your teammates then connect in Palworld through the multiplayer section using the server IP. If the server is not visible immediately, first test direct connection by IP and then check firewall, port, server status, and typos.
If you are comparing other survival servers, the guide on renting a Valheim server with mods and configuration and the guide on renting and setting up a Satisfactory Dedicated Server are suitable internal additions. Both topics help classify how much server load and configuration discipline vary by game.
Admin Commands During Operation
Admin commands are important for maintenance, moderation, and controlled restarts. Keep the existing commands unchanged:
/ShowPlayers
/KickPlayer {SteamID}
/Save
/Shutdown 60 Restart in 60 seconds
With /ShowPlayers, you check who is connected. /KickPlayer {SteamID} removes a specific player. /Save is useful before maintenance or configuration work so the current world state is written. /Shutdown 60 Restart in 60 seconds gives players a short warning instead of ending the server abruptly.
Check the Result
After every change, you should not only check whether the process is running. Connect yourself, check joining the world, test the password, verify the displayed player count, and confirm a changed rule in-game. For PvP/PvE rules, a short test with a second player or a test account is enough. For capture or time rates, you need a concrete game situation so you confirm not only the file content, but also the effect.
A short restart test is also useful: stop server, start server, connect again. If the values are reset afterward, you probably edited the wrong file, the syntax is invalid, or a panel is overwriting manual changes.
Troubleshooting
The Server Does Not Start After a Change
First check the line you edited most recently. Common causes are missing commas in the full OptionSettings format, wrong quotation marks, or values that do not match the expected type. Temporarily revert the last change and start again.
Changes Do Not Take Effect
Do not edit DefaultPalWorldSettings.ini as the permanent configuration. According to the official documentation, changes take effect in the active PalWorldSettings.ini in the Saved/Config directory. Restart the server after saving.
Players Cannot Connect
Check IP, port, password, and server status. If only individual players are affected, check for typos and client version. If nobody can connect, check firewall, port forwarding, and whether the server has fully started.
The Server Seems Unstable
Compare the current player count with the RAM table, temporarily reduce the player limit or especially load-intensive values, and check logs around crashes. Large worlds with many active bases need more reserves than a small private test world.
Checks, Limits, and a Safe Way Back
The guide “Rent a Palworld Server: Configuration, Pals & Multiplayer 2026” applies to the server type described in the article and the version status visible at the time of checking. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values to another game, loader, or server version without checking them.
Before changing the world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.
| Checkpoint | Expected Result | Abort and Rollback |
|---|---|---|
| Server start | The server reaches the operational state without a new error message. | If startup errors occur, undo the change and restore the last backup. |
| Connection test | A test account can connect through the address shown in the panel. | If version or connection errors occur, compare version, port, and openings again. |
| Function test | The specifically changed function works without damaging existing world or game data. | If side effects occur, stop the server and restore backed-up files. |
A successful individual test is not a performance or availability guarantee. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document version, change, and test result so you can understand later deviations.
FAQ
How Much RAM Does a Palworld Server Need?
Where Do I Change the Palworld Server Settings?
The central file is PalWorldSettings.ini in the server's Saved/Config directory. Start the server once so the folders are created, edit the active file, and then restart.
Should I Enable PvP Right Away?
For private groups, PvE is usually the better start. Only enable PvP once all players accept the consequences for combat, bases, and progress and you have a backup or a clear recovery plan beforehand.
How Do I Invite Friends to the Server?
Give them the server IP, port, and, if set, the ServerPassword. They then connect in Palworld through the multiplayer section using the server IP.
What Should I Do Before a Planned Restart?
Inform active players, run /Save, and then use, for example, /Shutdown 60 Restart in 60 seconds. This reduces the risk of progress loss and surprising disconnections.