Palworld Dedicated Server tool: find, launch, and update it

The Palworld Dedicated Server tool is the free server application in Steam that runs a world separately from your game. It still needs a running host PC, enough resources, and a working network connection. If you found it beside your games and wondered whether clicking Install was the whole job, start here. You’ll find the correct library entry, locate its Windows files, launch a local test world, and understand how to update it safely. This walkthrough follows the official documentation; it does not claim a hands-on connection or update test on your hardware.

Find the Palworld Dedicated Server tool in Steam#

Enable Tools in your Steam library and search for Palworld Dedicated Server. It is a separate entry from the Palworld game you launch to play. Pocketpair documents this graphical Windows route in its dedicated-server deployment guide.

1. Show tools in the library

   Open Steam’s Library and use the filter near the upper-left corner to include Tools. Search for the full server name. If you only see Palworld, check the filter before assuming the server requires another purchase.

2. Install the server entry

   Select Palworld Dedicated Server, choose Install, and note which Steam library receives it. Let the download finish before trying to start the executable. The server application is app 2394010; the normal game and the server are different installations.

3. Check the machine behind the install button

   Read Pocketpair’s server requirements before making this your group’s permanent world. The requirements list 16 GB of RAM and recommend more than 32 GB; they warn that an 8 GB machine can boot but risks running out of memory. Running the game on the same PC adds another workload.

The tool supplies server software, not a rented machine, automatic backups, or a router configuration. If you’re still deciding where the world should live, compare the different dedicated-server hosting routes. For this route, the immediate checkpoint is simply that Steam shows the separate server entry as installed.

Locate the installation you actually launched#

Use Manage → Browse local files on the server’s library entry instead of copying a guessed C-drive path. That opens the installation Steam manages, including when you installed it on another drive. Valve documents this menu in its local-file instructions.

The usual directory underneath the selected Steam library is:

steamapps\common\PalServer

Treat that as a relative location. A library on D: will not share the full path of a library under Program Files on C:. Also check that you opened the server entry; browsing the game’s files takes you somewhere else.

Some saved-data directories appear only after the first server startup. Their absence before that first run does not by itself prove the installation failed. Once initialized, use the Palworld save location guide to identify the active world rather than assuming every folder belongs to your current group.

Record this installation’s full path somewhere useful. If you later install another copy with SteamCMD, both copies can have valid settings and saves. Editing one while launching the other produces a very convincing impression that the game is ignoring you. The first check is the executable’s installation, not another reinstall.

Launch a test world and prove it accepts a player#

Start with a local join before troubleshooting internet access. Steam’s Play button opens a launch dialog; Pocketpair’s normal dedicated-server instructions select Play Palworld Dedicated Server. The community-server choice serves a different joining route, covered below.

1. Start one server instance

   Use Play on the server entry and select the normal dedicated-server option. Keep the server window open. If you choose to launch directly from its installation folder instead, the Windows executable is:

   .\PalServer.exe

   Use one launch method at a time. Starting another copy while the first is running makes port and world troubleshooting harder.

2. Connect from the game client

   Open Palworld separately. In Join Multiplayer Game, use the IP-and-port connection field below the server list. On a Steam game client running on the same PC as the server, the local test address for the default port is:

   127.0.0.1:8211

   Pocketpair’s connection instructions explain the address field. The loopback address above points back to the machine using it; sending it to a friend points them at their own machine, not yours.

3. Check the world, not just the window

   Confirm that the game reaches the expected server world. A running console window only proves that something launched. A successful local join establishes a more useful first checkpoint, but it still does not test your router or outside access.

A new dedicated installation does not automatically adopt your co-op save. If it asks you to create a character in a fresh world, preserve your original save and investigate migration separately. Do not replace files just to make that prompt disappear. Likewise, a failed first join is not evidence that all of your existing world data is gone.

Set access rules before inviting friends#

Configure the active server file and the correct joining route before distributing an address. For a fresh installation, run the server once to create its directories, stop it, and follow Pocketpair’s configuration instructions to copy the shipped template into the real file:

Pal\Saved\Config\WindowsServer\PalWorldSettings.ini

Use the template from the version you installed, preserving its structure. Do not overwrite an existing customized configuration with defaults as routine maintenance. Restart after editing, then check the server’s name and password behavior from the game. The server settings guide explains the wider configuration without turning this tool walkthrough into a catalog of every key.

Home hosting also requires the appropriate Windows firewall and router rules. Use the full Palworld setup walkthrough for that work. A successful connection from the host PC does not prove those rules are correct, and a failed outside connection is not normally a reason to download the tool again.

Xbox-family and PS5 players need a community server; the Xbox family includes the Microsoft Store PC version. Pocketpair’s community-server guide documents Steam’s Open and start as a community server choice. For a direct Windows launch, it uses:

.\PalServer.exe -publiclobby

Check that configuration permits the platforms your group uses, keep a joining password, and have someone outside your network test the actual route. Community listing is not proof that every friend can reach the machine.

Save, stop, and update through the correct Steam entry#

Update the dedicated-server entry during a planned break, after saving, shutting down, and preserving its data. Updating the ordinary Palworld game entry does not establish that the separate server installation is current. Steam manages packages; it does not remove your responsibility for the world stored beside them.

1. Save and stop gracefully

   Tell players about the maintenance window. If you administer the server through in-game chat, authenticate with your configured administrator password and use the documented save and shutdown commands. For example:

   /AdminPassword YOUR_ADMIN_PASSWORD
   /Save
   /Shutdown 60 Maintenance

   Replace the password placeholder. These commands belong in game chat, not the black server window. Wait for the process to exit before continuing. The admin command guide covers permissions and syntax; do not substitute a forced exit for a normal shutdown.

2. Keep an independent pre-update copy

   Copy the complete saved-data directory below, including configuration, to a dated location outside the installation. Keep a copy on separate storage for protection against losing the host disk.

   Pal\Saved

   Open the copy and confirm it contains your files. This is a preservation step, not proof that a restore has been tested. Steam’s file verification feature is not a backup of your world.

3. Finish the download, then rejoin

   Return to Palworld Dedicated Server in Steam. Check Downloads for its pending update and allow that download to finish before relaunching. Review the tool’s update settings if downloads are scheduled for later; don’t assume a client update has updated every server you maintain.

   Launch the same installation again. Join it and confirm the expected character, base, settings, and friends’ access before ending maintenance. Keep the pre-update copy until those checks pass.

Consult Pocketpair’s patch announcements for compatibility details when clients use different storefronts. A documentation version label is not a reliable substitute for the current release notice. Avoid a blanket assumption that every platform must display an identical version string.

Keep the host available without guessing about Steam#

The server process and its host machine must remain available for friends to play. That is different from keeping your character logged into the game, and it is also different from proving a dependency on the graphical Steam client.

Pocketpair documents anonymous SteamCMD installation followed by a standalone server launch. That means “Steam must always stay logged in” is too broad. For an instance started through Steam’s GUI, test how exiting or restarting Steam affects that specific launch method during a quiet maintenance window. Do not turn an untested assumption into your group’s uptime plan.

Microsoft distinguishes locking from signing out. Its power-management documentation also explains application suspension during sleep. Turning the display off and putting the PC to sleep are different operations.

Keep the acceptance check practical: a friend stays connected after you close the game, and the expected world returns after a planned server restart. If that depends on remembering several manual steps every evening, consider a different operating arrangement.

Move to SteamCMD when the GUI becomes extra work#

SteamCMD becomes useful when you want to install and update the same server software without the graphical Steam client. It is an alternative installation workflow, not a faster world simulation or an automatic migration tool. Pocketpair’s documented anonymous install command is:

steamcmd +login anonymous +app_update 2394010 validate +quit

That command installs or updates the server application and exits SteamCMD. You still need to launch the server, maintain its configuration, preserve its world, and handle its network access. Installing another copy does not automatically choose the saves from your Steam-managed directory.

Stay with the graphical tool if a familiar Windows install and manual maintenance are enough for your group. Move toward a managed service or a properly administered server process when availability depends too heavily on your everyday desktop session. A headless installation still needs someone responsible for updates and recovery.

If the real problem is keeping a home PC available, check Game Hosting’s Palworld plans and availability. The current offering uses a waitlist, so plan around confirmed capacity rather than immediate provisioning. Renting is a decision about where the machine runs and who handles agreed maintenance; it is not the only way to avoid using Steam’s GUI.

Before changing routes, retain the working installation path and its independent backup. Your next server should prove that the correct world and characters load before you retire the old one.