Palworld runs on Unreal Engine 5 and its dedicated server is noticeably hungrier than most survival games. A 32-player world is the default ceiling – MaxPlayers caps at 32 – and hitting that cap smoothly requires more RAM and single-thread CPU performance than the game’s minimum specs suggest. On top of that, the server process leaks memory over time, so planning restarts and backups is part of running a stable community server. This guide covers the hardware that actually handles 32 players, the SteamCMD install, the config file, and the launch flags that reduce stutter.<\/p>\n\n\n\n
If you would rather rent than maintain your own box, compare dedicated server providers on our comparison table<\/a> first – the RAM and CPU requirements below are the minimum you should filter by.<\/p>\n\n\n\n For a 32-player world the server process typically consumes 6-9 GB of RAM once bases, pals, and structures accumulate. RAM is the binding constraint; CPU matters for tick stability, and storage speed affects world saves and fast travel. Realistic sizing:<\/p>\n\n\n\n If you run Palworld alongside other games or services on the same box, add their requirements on top – do not share the headroom.<\/p>\n\n\n\n The Palworld dedicated server (app ID 2394010) installs through SteamCMD on both Linux and Windows. On a Linux host:<\/p>\n\n\n\n On Windows, download SteamCMD, run the same command with a Windows path, and launch via PalServer.exe. First boot generates the world and config files under Pal\/Saved, which can take a few minutes on a fresh world.<\/p>\n\n\n\n Open the firewall before the first connection: the server listens on UDP 8211 by default, plus the RCON port if you enable it. On a rented box you also want the game’s query traffic forwarded – check the provider’s panel documentation, since some use a proxy IP that forwards only the ports you explicitly configure.<\/p>\n\n\n\n Open Pal\/Saved\/Config\/LinuxServer\/GameUserSettings.ini (WindowsServer on Windows) and set the player cap and server details under the PalWorldSettings section:<\/p>\n\n\n\n Set MaxPlayers to 32 only if your hardware matches the recommended column above – a 32-player cap on an 8 GB box produces rubber-banding and save lag once bases grow. Also set a real AdminPassword and change RCONPort if the default 25575 is exposed.<\/p>\n\n\n\n You can also set a ServerPassword for a private community, though players must re-enter it in the server browser each time. RCON is the tool for admin actions and clean restarts without touching the console – pair it with a community dashboard like Palworld-RCON to see connected players, trigger manual saves, and broadcast warnings before a restart.<\/p>\n\n\n\n Palworld’s server benefits from three community-standard launch flags that spread work across threads:<\/p>\n\n\n\n Monitor sustained CPU usage: if the box sits above roughly 80% during peak play, the world tick slows and players see hitches. On Windows you can pin the process to physical cores via the affinity setting in Task Manager. The memory leak means a 32-player server grows by hundreds of MB per hour of uptime, so plan a restart every 6-12 hours.<\/p>\n\n\n\n Expect the world tick to dip when dozens of bases are active simultaneously – that is normal Palworld behavior. The metric that matters is whether CPU stays under about 80% at peak and whether the save interval completes without freezing gameplay. If saves stall, move the save directory onto faster NVMe or reduce autosave frequency slightly.<\/p>\n\n\n\n World saves live under Pal\/Saved\/SaveGames. A cron job that stops the server, snapshots the save directory, and restarts it keeps both memory and risk under control:<\/p>\n\n\n\n Keep at least three days of backups off-box; a corrupted save on a server without backups is how communities die.<\/p>\n\n\n\n Test a restore at least once before opening the server to players. A backup you have never restored is a guess, and Palworld save files are sensitive to version mismatches – restore with the same game version the save was created on, then update afterward.<\/p>\n\n\n\n A self-managed 32-player Palworld server is entirely feasible on a 6-core\/16 GB dedicated machine, but it assumes you handle SteamCMD updates, config tweaks, and restarts yourself. If you would rather have the provider manage the instance, see the full specs and pricing<\/a> on our comparison table and look for plans with at least 16 GB RAM and NVMe storage.<\/p>\n\n\n\nHardware Specs for a 32-Player Palworld Server<\/h2>\n\n\n\n
Component<\/th> Minimum (24 players)<\/th> Recommended (32 players)<\/th><\/tr><\/thead> CPU<\/td> 4 cores @ 3.5 GHz+<\/td> 6-8 cores @ 3.8 GHz+ (Ryzen 7 \/ EPYC 7313 class)<\/td><\/tr> RAM<\/td> 12 GB (8 GB server)<\/td> 16 GB (10-12 GB server headroom)<\/td><\/tr> Storage<\/td> NVMe, 20 GB free<\/td> NVMe, 40 GB+ for saves and future updates<\/td><\/tr> Network<\/td> 100 Mbps, 1-2 TB transfer<\/td> 250 Mbps+ unmetered or high cap<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Installing the Dedicated Server with SteamCMD<\/h2>\n\n\n\n
steamcmd +login anonymous +force_install_dir \/opt\/palworld +app_update 2394010 validate +quit\ncd \/opt\/palworld\n.\/PalServer.sh<\/code><\/pre>\n\n\n\nConfiguring GameUserSettings.ini for 32 Players<\/h2>\n\n\n\n
[\/Script\/Pal.PalGameWorldSettings]\nOptionSettings=(ServerName=\"My 32P Server\",ServerDescription=\"32-player survival\",MaxPlayers=32,PublicPort=8211,RCONEnabled=True,RCONPort=25575,AdminPassword=\"CHANGE_ME\",Difficulty=None,DayTimeSpeedRate=1.0,NightTimeSpeedRate=1.0)<\/code><\/pre>\n\n\n\nLaunch Parameters That Reduce Stutter<\/h2>\n\n\n\n
.\/PalServer.sh -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS<\/code><\/pre>\n\n\n\nBackups and Scheduled Restarts<\/h2>\n\n\n\n
0 *\/8 * * * systemctl stop palworld && tar czf \/backups\/pal-$(date +\\%F-\\%H).tar.gz -C \/opt\/palworld\/Pal\/Saved SaveGames && systemctl start palworld<\/code><\/pre>\n\n\n\nRenting vs Running Your Own Box<\/h2>\n\n\n\n