Learn how to boost server FPS and optimize your Palworld Server. This guide highlights best practices that you can use as a server owner to keep your Palworld server running at peak performance, often providing noticeable improvements in many cases.
Daily Restarts
The first step is setting up an automatic daily restart schedule. This keeps your resource usage in check while giving your server a fresh load every 24 hours. Busy public servers often restart 2-4 times a day, so adjust your schedule to suit your player count.
To set up a schedule, follow this guide.
Optimize Configuration
Several Palworld server settings can negatively impact performance. Some may have a minor effect, while others create very noticeable issues.
If you're facing Server FPS problems, adjust these settings as needed. These are the most critical settings for performance, particularly if you're operating a community server.
You can change these settings in Server Options of the GhostCap Panel.
Main Settings
| Setting Name | Recommended Value | Default Value | Description |
|---|---|---|---|
| BuildObjectDeteriorationDamageRate | 1.5 or higher | 1.0 | Higher is better for performance, this should always be at least 0.1 |
| ItemContainerForceMarkDirtyInterval | 5.0 | 1.0 | Interval in seconds before an opened container is force-synced. Higher is better for performance |
| bAutoResetGuildNoOnlinePlayers | True | False | WARNING: Enables guild disbanding after the duration specified by AutoResetGuildTimeNoOnlinePlayers. This will DELETE bases if a guild goes inactive. The default grace period is 72.0 hours |
| AutoResetGuildTimeNoOnlinePlayers | 72.0 or lower | 72.0 | If bAutoResetGuildNoOnlinePlayers is enabled, this is the time limit before a guild will be disbanded |
| PalSpawnNumRate | 0.7 | 1.0 | Decrease this to spawn fewer Pals |
| DropItemMaxNum | 1000 | 3000 | Decrease this especially if you have increased Drop Rates |
| DropItemAliveMaxHours | 0.7 | 1.0 | Decrease this especially if you have increased Drop Rates or many players |
| PhysicsActiveDropItemMaxNum | 0 | - | Maximum number of dropped items that can use physics. Set to 0 to disable item physics entirely for the best performance |
| BaseCampMaxNumInGuild | 4 | 4 | Decrease this if there are many guilds |
| ServerReplicatePawnCullDistance | 10000.0 | 15000.0 | Decrease this for much better performance, officially "Pal Sync Distance" |
| BaseCampWorkerMaxNum | 15 or lower | 15 | Decrease this to lessen load |
| MaxBuildingLimitNum | ~1000 | 0 (Unlimited) | Limits total buildings. As of 1.0.4 this applies server-wide rather than per player, with MaxBuildingLimitNumPerPlayer added as a separate setting |
| MaxBuildingLimitNumPerPlayer | ~1000 | 0 (Unlimited) | Limits max buildings per player |
| bEnableInvaderEnemy | False | True | Enables invader enemy events |
| bEnableFastTravel | False | True | When a player fast travels, all connected clients briefly stop responding. This is even worse for console players |
| bIsPvP | False | False | Enabling this causes lag when players mount and dismount Pals. Only enable if you need PvP |
Secondary Performance Settings
| Setting Name | Recommended Value | Default Value | Description |
|---|---|---|---|
| BaseCampMaxNum | 100 or lower | 128 | Decrease this if you're running a popular public server with many bases |
| Auto Save Span | 420 (7 minutes) | 240 (4 minutes) | Increase this for less frequent auto save CPU spikes |
Heavy building and high player count servers will always reach a limitation at some point. Even the fastest gaming hardware isn't able to run a Palworld server at 60fps in such cases.