Best Palworld Server Settings
The settings that make a Palworld server fun without wrecking performance — sensible EXP and capture rates, work-speed, player cap, and the one thing everyone trips on: why your ini edits don't apply after the world is generated. Where each setting lives and what it does.
Every Palworld server setting lives in PalWorldSettings.ini, under Pal/Saved/Config/<platform>Server/. Two things trip almost everyone up: you must stop the server before editing (or it overwrites your file on restart), and once a world is generated, most world settings are baked into WorldOption.sav — so ini edits do nothing until you account for it.
Below are balanced values for a small-to-mid co-op server, plus what each does and how to make changes actually apply.
What you'll need
A quick checklist before you begin — have these ready and the rest is easy.
- Access to your server files (a panel File Manager or SFTP).
- The file PalWorldSettings.ini under Pal/Saved/Config.
- The ability to stop the server before editing.
- Awareness that WorldOption.sav holds world settings after generation.
- A strong CPU and enough RAM for busy bases.
Dial in your Palworld server, setting by setting
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.
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
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
Set a realistic player cap
The engine accepts up to 32, but Palworld dedicated stability drops hard past 16 — TPS issues, base desync and pal pathfinding failures show up at 20+. 16 is the realistic ceiling.
ServerPlayerMaxNum=16
Leave the performance traps at 1.0
A few options look cool but double RAM use and tank performance when players roam far from base (heavy pal spawns / density). If the server lags away from base, this is usually why — keep them at default.
PalSpawnNumRate=1.0 ; avoid cranking spawn/density multipliers on a shared box
Make changes actually apply
Two rules: stop the server before editing, and remember that after world generation most world settings live in WorldOption.sav. Rates you change in the ini after that may not take — a fresh world (or removing/regenerating WorldOption.sav on a test world) is the clean way to re-tune.
Fun, balanced and stable
Stop the server before editing
Edit PalWorldSettings.ini while it's running and your changes get overwritten on restart. Stop it first, edit, save, then start — every time.
WorldOption.sav wins after world-gen
Once a world exists, most settings are baked into WorldOption.sav and the ini is ignored. If a rate change does nothing, this is why — set rates before generating, or regenerate the world.
16 players is the real ceiling
The config allows 32, but stability falls apart past ~16. For a smooth server, cap it at 16 and spend the headroom on tick-rate, not slot count.
Base density is the lag driver
Big bases with many pals and heavy spawn multipliers are what tank Palworld servers. Keep spawn rates near default and give the server a strong CPU.
Common problems & fixes
Hit a snag? These are the issues people run into most — and how to solve them.
My changes keep reverting
You edited PalWorldSettings.ini while the server was running. Stop it, edit, save, then start — it writes the file on shutdown and overwrites you.
A rate change does nothing
The world is already generated and reading from WorldOption.sav. Set rates before generating, or regenerate the world to re-apply.
The server lags when players roam
Heavy pal spawn/density multipliers. Return PalSpawnNumRate and density options to 1.0 and give the server more CPU.
Players desync or pals stop pathing
You're over the stable player count. Cap ServerPlayerMaxNum at 16 for a smooth server.
Skip the setup — host it with ESAGAMES
Want a smooth Palworld server without fighting the config? Our Palworld hosting runs high-clock CPUs on NVMe behind a multi-Tbps Frankfurt network — panel included, instant setup.
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?
Two common reasons: you edited while the server was running (it overwrites on restart), or the world is already generated and reading from WorldOption.sav instead of the ini. Stop the server first, and set rates before generating the world.
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 really hold?
The config allows 32, but stability drops hard past 16 — TPS problems, base desync and pal pathfinding failures. 16 is the realistic ceiling for a smooth server in 2026.
Why is my server laggy away from base?
Usually cranked pal spawn/density multipliers, which spike RAM and CPU as players roam. Keep PalSpawnNumRate near 1.0 and give the server a stronger CPU.
Do I need to restart after changing settings?
Yes — stop the server, edit the ini, save, then start it. Editing live gets your changes overwritten when the server writes the file on shutdown.
Keep reading
Palworld is a trademark of Pocketpair, Inc. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Pocketpair. You must own a legitimate copy of the game to play.
