Palworld has enough configuration options to make it tempting to change everything before anybody joins. That usually makes troubleshooting harder.
Begin with the settings that affect who can connect, whether the world is recoverable, and how well the game runs during real sessions.
Start with access, player count, saves, and stability.
Configure the server's listen port and player limit for your hosting environment, decide whether it should be discoverable publicly, secure admin access, and enable a backup strategy. Change performance arguments only after measuring a real problem.
Palworld dedicated server administrationPorts and player counts
The server supports a command-line listening port option, typically shown as -port=8211 in the official guide, as well as a player-count setting. Your hosting provider may assign a different port; use that assigned value rather than forcing the example.
Choose a realistic maximum player count for the hardware and expected activity. More slots do not guarantee better performance. Test during exploration, base-building, and combat rather than only when the server is empty.
Private server or community listing?
A community server can use the public lobby startup option and associated public address settings. A direct-connect server may not need community listing settings. PublicPort is distinct from the actual listening port in the official documentation.
Plan access controls around your audience. Protect administration credentials and do not publish tokens, admin passwords, or remote administration secrets.
Protect the world save
Palworld documents an option to enable backup save data; enabling it adds disk activity. Regardless of the in-game mechanism, keep separate versioned backups and periodically test restoring a copy.
Before patches, mods, or configuration migrations, stop or safely snapshot the server using your provider's supported procedure. Retain a known-good copy until you have confirmed that the updated world loads.
Change performance options carefully
The official server documentation notes that threading-related startup arguments can have version-dependent behavior. Do not blindly copy old startup flags from videos; compare against the version you are actually running.
Record CPU, memory, player count, and any repeatable lag when deciding what to change. Adjust one variable at a time, then retest the same scenario.
A couple more questions
Should I set the default port manually?
Use the port your host assigns. The documentation's example port is not a universal requirement for every managed server.
Do the game's own backups replace offsite backups?
No. Independent backups are still important for recovery from disk loss, accidental deletion, and failed upgrades.
Sources & useful links
The technical details behind this guide, if you want to dig further.
Keep reading
Ready to start your Palworld journey?
Put what you learned into action with a server built for your next adventure.
View Palworld plans