Best Palworld Server Settings

  • 8 min read
  • Updated 12 September 2026
  • ESAGAMES Team

The settings that make a Palworld server fun without wrecking performance — sensible EXP and capture rates, work speed, the player cap, and the base and Pal limits Pocketpair's own docs flag as raising processing load. Where each setting lives and what it does.

Every Palworld server setting lives in PalWorldSettings.ini, under Pal/Saved/Config/<platform>Server/. The folder only appears after the server has started once; you then copy DefaultPalWorldSettings.ini from the install folder into it, because editing the default file itself changes nothing.

Below are balanced values for a small-to-mid co-op server, plus what each does and which limits cost CPU.

On a hosted server you can change these rates from a web panel instead of digging through folders. Our Palworld server hosting includes a file manager and one-click restarts, running on NVMe storage in Frankfurt.

What you'll need

  • Access to your server files (a panel File Manager or SFTP).
  • The file PalWorldSettings.ini under Pal/Saved/Config.
  • The ability to stop and start the server.
  • At least 16 GB of RAM, per the official requirements.

Dial in your Palworld server, setting by setting

  1. Step 1: Find PalWorldSettings.ini

    All settings live in Pal/Saved/Config/LinuxServer/PalWorldSettings.ini (or WindowsServer/). Everything is on one long OptionSettings=(...) line — edit values inside the parentheses, don't break the format.

  2. Step 2: Set EXP and capture rates

    These are what players feel first. Small bumps keep a group progressing together without the lead player running away with it. 1.5-2x EXP and ~1.2-1.5x capture is a comfortable co-op pace.

    ExpRate=1.5
    PalCaptureRate=1.5
    PalSpawnNumRate=1.0
  3. Step 3: Tune work speed & drops

    Faster base work and slightly higher drops cut the grind without trivialising it. Keep collection/gather near default so the economy still means something.

    PalStomachDecreaceRate=0.7
    CollectionDropRate=1.5
    WorkSpeedRate=1.2
  4. Step 4: Set the player cap

    ServerPlayerMaxNum ships at 32, and Pocketpair advertises dedicated servers for up to 32 players. Set it to the group you actually have rather than the maximum, and size RAM for it: the official requirements list 16 GB of memory and warn that 8 GB boots but risks out-of-memory crashes.

    ServerPlayerMaxNum=32
  5. Step 5: Watch the settings the docs say cost performance

    The official configuration page flags these. PalSpawnNumRate "impacts performance". BaseCampWorkerMaxNum (Pals per base, default 15, max 50) and BaseCampMaxNumInGuild (bases per guild, default 4, max 10) both raise processing load. ServerReplicatePawnCullDistance is the Pal sync distance from players, 5000-15000 cm, and ships at the maximum. MaxBuildingLimitNum caps buildings per player (0 = unlimited).

    PalSpawnNumRate=1.000000
    BaseCampWorkerMaxNum=15
    BaseCampMaxNumInGuild=4
    ServerReplicatePawnCullDistance=15000.000000
    MaxBuildingLimitNum=0
  6. Step 6: Check the launch arguments too

    Two server options live on the command line, not in the ini: -port and -players. The multithreading flags changed in 1.0: the argument table now says leaving -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS unset "may improve performance", while older guides still recommend adding them. Test both on your hardware.

    ./PalServer.sh -port=8211 -players=32

Fun, balanced and stable

  • Edit the right file

    Only Pal/Saved/Config/LinuxServer/PalWorldSettings.ini (or WindowsServer/) is read. Changing DefaultPalWorldSettings.ini in the install folder has no effect. Edit with the server stopped, then start it again.

  • Bases cost more than players

    Pocketpair's docs say raising Pals per base or bases per guild raises processing load, and the PvP page cuts both to reduce server strain. Raise these limits in small steps.

  • Slots need real RAM

    The default cap is 32 players. The official requirements list 16 GB of memory and warn that 8 GB boots but makes out-of-memory crashes more likely.

  • Spawn rate is a performance setting

    PalSpawnNumRate is the one gameplay multiplier the docs mark as impacting performance. Keep it near 1.0 on a busy server and give it a strong CPU.

Common problems & fixes

A rate change does nothing

Check you edited PalWorldSettings.ini under Pal/Saved/Config/, not DefaultPalWorldSettings.ini, and that the OptionSettings line is intact. Save with the server stopped, then start it.

The Config folder does not exist

It is only created once the server has started. Start it once, stop it, then copy DefaultPalWorldSettings.ini into place.

Load climbs as bases grow

Pals per base and bases per guild raise processing load. Lower BaseCampWorkerMaxNum or BaseCampMaxNumInGuild, or set MaxBuildingLimitNum.

The server crashes with out-of-memory errors

The official requirements warn that 8 GB risks out-of-memory crashes. Give it at least the 16 GB the requirements list.

Frequently asked questions

Where are Palworld server settings stored?

In PalWorldSettings.ini under Pal/Saved/Config/LinuxServer/ (or WindowsServer/). Every option is on one OptionSettings=(...) line — edit the values inside the parentheses.

Why don't my settings changes apply?

Usually the wrong file was edited: only PalWorldSettings.ini in Pal/Saved/Config/LinuxServer/ (or WindowsServer/) is read, and editing DefaultPalWorldSettings.ini does nothing. Also check the OptionSettings=(...) line is still one unbroken line, then restart the server.

What are good EXP and capture rates?

For a co-op group, around 1.5-2x EXP and 1.2-1.5x capture keeps everyone progressing together without the lead player running away. 1.0 is vanilla; very high rates end the game fast.

How many players can a Palworld server hold?

Up to 32: ServerPlayerMaxNum ships at 32 and Pocketpair advertises 32-player dedicated servers. The official requirements list 16 GB of memory for the server.

Which Palworld settings affect server performance?

The official docs flag PalSpawnNumRate (impacts performance), BaseCampWorkerMaxNum and BaseCampMaxNumInGuild (raise processing load), and list ServerReplicatePawnCullDistance and MaxBuildingLimitNum under performance. Keep them near default on a busy server.

Do I need to restart after changing settings?

Yes. Stop the server, edit PalWorldSettings.ini, save, then start it again.

Fixes for when it goes wrong

Knowledge-base fixes that pair with this guide — the errors people hit after setup.

More guides

Skip the troubleshooting

Managed, protected hosting in Frankfurt — we handle the Linux, the network and the DDoS so you don't have to.