Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →To host a Palworld multiplayer world from your own computer, install the separate Palworld Dedicated Server tool, start its server executable, and make the listening port reachable. Pocketpair’s current documentation lists 64-bit Windows and Linux, a recommended four-core CPU, 16 GB of RAM, and faster SSD storage. The default listening port is UDP 8211. Friends connecting from outside your home network also need a router port-forwarding rule and a matching operating-system firewall rule.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Palworld servers with free DDoS protection and up to three free backups a day.
This guide covers Steam and SteamCMD installation, first launch, launch arguments, internet access, joining, backups, updates, and the failure points most likely to prevent connections.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat a Palworld dedicated server is
A dedicated server is a separate Palworld program that runs the multiplayer world independently of the normal game client. You do not host it by simply opening the regular game and inviting people. Install the Palworld Dedicated Server tool, run its server process, and leave that process running while players connect.
The computer running the process is the host. Its processor, memory, storage performance, power state, network connection, firewall, and router determine whether the world remains available. If the host PC is shut down, asleep, disconnected, or running out of memory, the dedicated server cannot continue serving players.
#1 Best Overall
- Officially licensed Palworld merch. Join the hunt and capture all the creatures in this open world survival video game. Weaponize your creatures or put them to work in this unique collecting game.
- Perfect graphic apparel for fans of Video Games, Creature Collecting, Open World Games, Cute Animals, Funny Games, and Pocketpair.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
Pocketpair’s published requirements and commands are versioned documentation rather than a promise that every future release will behave identically. The pages consulted for this guide are marked 0.1.5.1 (requirements), 0.5.0 (deployment), and 0.6.8 (arguments), crawled in October 2026. Recheck the current Pocketpair documentation before applying an update if a command or argument has changed.
Check the PC before installing
Use the following as the starting point for a self-hosted server. The memory figure is especially important: the server can boot with 8 GB, but Pocketpair says that configuration has a greater possibility of out-of-memory crashes.
| Item | Pocketpair guidance | What it means in practice |
|---|---|---|
| Operating system | 64-bit Windows or 64-bit Linux | Use a 64-bit installation; a 32-bit operating system is not the documented target. |
| CPU | Four cores recommended | Treat four physical or logical cores as the baseline for a small private server, not as a guaranteed player capacity. |
| Memory | 16 GB recommended | Leave memory for the operating system and other services instead of assigning every gigabyte to the server. |
| Lower-memory start | 8 GB can boot, with increased out-of-memory crash risk | Use this only as a constrained setup and watch for crashes; it is not equivalent to the recommended configuration. |
| Storage | Faster SSD storage recommended | Do not put the world on slow or failing storage. Pocketpair warns that low-performance storage may corrupt saved data. |
Reserve a stable local address
For internet play, the router must always forward traffic to the same host computer. Reserve the PC’s local address in the router’s DHCP settings, or configure an equivalent static local address using your network’s documented method. If the address changes, a port-forwarding rule can silently point at another device.
Keep the host available
A home-hosted server is online only while the PC and server process are running. Disable sleep for the hosting machine or choose a power plan that keeps it awake during play sessions. This is an availability decision, not a Palworld setting: Windows or Linux power management can stop a perfectly configured server.
Self-hosting or a managed server?
Running the server on your PC gives you direct control over the executable, launch arguments, world files, and maintenance schedule. It avoids a separate hosting subscription, but your computer must remain powered on and you are responsible for networking, updates, backups, and recovery.
A managed service moves the always-on machine and much of the network setup to another provider. That can be simpler for friends in different locations, but the recurring price, storage limits, backup policy, supported Palworld version, and player capacity vary by provider and must be checked at the time you subscribe. The table describes the decision without assuming any particular company or plan.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Consideration | PC self-hosting | Managed hosting |
|---|---|---|
| Upfront hardware cost | Uses a PC that meets the requirements; buying or upgrading hardware is your responsibility. | Usually avoids buying a dedicated host, but plan terms determine what hardware is allocated. |
| Recurring cost | No separate hosting fee is established here; electricity and your existing internet service still apply. | Requires a recurring service charge whose current amount is provider-specific. |
| Configuration and saves | Direct access to launch arguments and save data on your machine. | Access depends on the provider’s control panel and file tools. |
| Availability when your PC is off | Unavailable while the host PC is off, asleep, or disconnected. | Depends on the provider’s service and maintenance policy. |
| Networking complexity | Requires a local address, firewall rule, and router port forwarding for internet players. | May reduce home-router work, but you still need to configure the game and account access correctly. |
| Updates and backups | You schedule updates and make backups yourself. | Tools and policies differ; verify whether backups are automatic, downloadable, and restorable. |
Install Palworld Dedicated Server through Steam
Steam is the graphical route. It installs the dedicated-server tool separately from the normal game.
- Open Steam on the intended host PC.
- Open the Library and switch the library filter to show Tools. Search for Palworld Dedicated Server.
- Install that tool to the SSD you intend to use for the world. Record the installation directory; you will need it to start the executable and create shortcuts or service entries later.
- After installation finishes, open the tool’s installation directory rather than launching the ordinary Palworld game.
If the tool does not appear, check that the Tools filter is enabled and that Steam has completed its library refresh. Installing the regular game alone does not install the dedicated-server executable.
Install with SteamCMD
SteamCMD is useful for a command-line Windows installation or for an automated update script. Install SteamCMD from Valve’s official distribution, open a terminal in its directory, and run Pocketpair’s documented command:
steamcmd +login anonymous +app_update 2394010 validate +quit2394010 is the Palworld dedicated-server app ID identified in Pocketpair’s deployment instructions. The validate option checks the downloaded files. Run the same update command later when you intentionally update the server, after stopping the running process and taking a backup.
Free tools Windows power users keep installed
One-click scans. No signup required.
SteamCMD does not replace the server executable. It downloads or updates the files; you still start the server from its installation directory using the platform-specific command below.
Start the server once
Change to the directory containing the installed server files. Pocketpair documents these executable names:
| Platform | Command |
|---|---|
| Windows |
|
| Linux |
|
Run it once before changing advanced settings. A first launch lets the program create its working files and confirms that the executable can start on your machine. Keep the terminal or console window open while testing. Stopping that process stops the dedicated server.
Windows start example
In Command Prompt or PowerShell, change to the server directory and run PalServer.exe. If Windows displays a firewall prompt, allow the server on the network profiles you actually use, then create or verify an explicit inbound rule for the server executable and UDP 8211. The firewall decision is separate from router configuration.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteLinux start example
In a shell, change to the server directory and run ./PalServer.sh. If the shell reports that the file cannot be executed, check that you are in the correct directory and that the file has execute permission. Configure the Linux firewall, if one is enabled, to allow the UDP port you choose for the server.
Set the listening port and player limit
The default network listening port is UDP 8211. You can state it explicitly with -port=8211. Pocketpair’s documented player-cap example is -players=32; that is an example setting, not a guarantee that your hardware or connection will support 32 active players.
PalServer.exe -port=8211 -players=32On Linux, append the same arguments to the shell command:
./PalServer.sh -port=8211 -players=32If you select another port, use that value consistently in the server command, firewall rule, router forwarding rule, and the address players enter. A mismatch is one of the most common reasons a server appears to be running but cannot be reached.
Recommended Free Tools
Publish a community server or specify public addressing
Pocketpair documents -publiclobby to publish a community server. Use it only when you want the server discoverable through the relevant community-server listing; a private group can instead connect directly using the reachable address and port.
The documented -publicip and -publicport arguments let you provide public-network values manually when automatic detection fails. These arguments do not remove the need for a working route to the host. The public address must actually lead to your network, and the public port must match the port forwarded by the router.
PalServer.exe -port=8211 -players=32 -publiclobbyFor a manually specified public endpoint, add the values required by your network:
PalServer.exe -port=8211 -publicip=YOUR_PUBLIC_IP -publicport=8211Replace the example value with your real public address; do not leave the literal text in a production shortcut. If your public address changes, update the launch configuration or use a current address-sharing method outside the Palworld server itself.
Use the documented multithreading options carefully
Pocketpair lists these options for multithreaded server operation:
-useperfthreads -NoAsyncLoadingThread -UseMultithreadForDSIt also documents an optional worker-thread count:
-NumberOfWorkerThreadsServer=XReplace X only with a value appropriate for your CPU and testing. Do not assume that a larger number is automatically faster. Add one change at a time, observe stability, and remove the option if it causes errors or no measurable benefit. These are launch-time settings, so stop the server before changing them.
Make the server reachable from the internet
Players on the same home network and players elsewhere follow different paths. A local player can often use the host PC’s private address. An internet player needs the public address of your network and a router rule that sends the chosen UDP port to the host PC.
- Confirm the dedicated-server process is running and listening on the port in your launch command.
- Reserve the host PC’s local address so it will not change.
- Create an inbound operating-system firewall rule for
PalServer.exeor the Linux server process, allowing UDP on the configured port. On Windows, allowing the executable and allowing the UDP port are separate ways to define the rule; verify that the rule actually covers the port you selected. - Open the router’s port-forwarding section and create a UDP rule from the external port to the host PC’s reserved local address and the same internal port. The default is UDP 8211.
- Save the router rule, restart the server if you changed its port, and test from a network outside your home Wi-Fi.
Pocketpair specifically identifies Windows firewall configuration and router port forwarding as separate tasks. Completing one does not complete the other. The official requirements also assume that your internet service permits the needed inbound connection; not every ISP or network design provides that capability.
Tell friends how to join
Give friends the server’s reachable address and configured port after the process is running. For players outside your home, that normally means the network’s public address plus the forwarded UDP port; for players on the same LAN, use the host PC’s local address when appropriate.
Use the exact port from the launch command. If you kept the default, that is UDP 8211. If you changed it, friends must use the changed value and the router and firewall must use that same value. A community server published with -publiclobby can be found through the game’s community-server listing when publication and network reachability are both working.
Do not send friends a private address such as a home LAN address when they are connecting from another location. Conversely, do not expose a public address in places where you do not want unsolicited connection attempts; choose direct sharing or community publication deliberately.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Troubleshoot a server that will not start
The command is not found
You are probably in the wrong directory, or the Steam/SteamCMD installation did not finish. Open the dedicated-server installation directory and confirm that PalServer.exe (Windows) or PalServer.sh (Linux) exists. Re-run the SteamCMD update with validate if files are missing.
Rank #4
- Officially licensed Palworld merch. Join the hunt and capture all the creatures in this open world survival video game. Weaponize your creatures or put them to work in this unique collecting game.
- Perfect graphic apparel for fans of Video Games, Creature Collecting, Open World Games, Cute Animals, Funny Games, and Pocketpair.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
It starts and then crashes
Check memory first. Pocketpair says 8 GB can boot but increases the possibility of an out-of-memory crash; 16 GB is the recommended starting point. Close unrelated applications, watch memory use during startup and play, and move to a machine with more available RAM if crashes continue. Also check that the server is on faster storage, because Pocketpair warns that low-performance storage may corrupt saved data.
The port is already in use
Another process may already be using the configured port. Stop the other server or select a different port with -port=NUMBER. Then update the firewall rule, router forwarding rule, and player instructions to the same number.
Troubleshoot remote connection failures
Work through the path in order rather than changing several settings at once:
- Verify that the server process is still running on the host PC.
- Verify the launch command’s port, including whether it is UDP and whether you changed the default.
- Check the Windows firewall or Linux firewall rule for the executable and port.
- Check the router’s forwarding destination: it must be the host PC’s current reserved local address, not an old address.
- Confirm that the friend is using the public address and the configured public port, not a private LAN address.
- If you used
-publicipor-publicport, confirm those values match the real reachable endpoint.
Test from outside the host’s home network. A connection attempt made from the same LAN may not prove that the router’s internet-facing forwarding works, because some routers do not support loopback testing. If all local settings are correct but inbound traffic never arrives, the ISP or upstream network may not permit inbound connections; the official requirements establish the need for port forwarding but do not guarantee support from every provider.
Operate the server safely
Stop cleanly before maintenance
Use the server’s normal shutdown method and wait for the process to exit before updating files or powering off the computer. Abruptly terminating a process while it is writing world data increases the risk of damaged saves, especially on slow or unreliable storage.
Back up before updates and experiments
Make a copy of the server’s save and configuration data before changing launch arguments, installing an update, or trying a new worker-thread setting. Keep at least one backup that is not on the same physical disk. Label copies with the date and the server version so you know which one to restore.
Update deliberately
Stop the running server, back up its data, update the files through Steam or by running the SteamCMD command again, then start the server and watch the console for errors. Do not update while players are actively writing to the world. Because launch arguments and platform behavior can change, compare your command line with the current Pocketpair documentation after each major update.
Keep launch settings reproducible
Store the exact working command in a shortcut, shell script, or written runbook. Include the port, player cap, community-listing choice, public-address arguments, and any multithreading options you have tested. A documented command makes recovery easier after reinstalling or moving the server to another PC.
Which setup should you choose?
- Choose a PC host when you already have a four-core, 16-GB machine with fast storage, can keep it powered on, and want direct control over files and arguments.
- Choose a managed service when your PC cannot remain online or your network does not allow inbound forwarding, and you accept a recurring fee and provider-specific controls.
- Start privately with direct address sharing when only a known group needs access. Add
-publiclobbywhen discoverability is more important than a private endpoint. - Use the default port first while testing. Change it only when you have a reason, and then change every dependent setting together.
The reliable self-hosted sequence is therefore: meet the hardware and storage requirements, install the dedicated tool, start it once, set a reproducible command, allow the process through the host firewall, forward UDP 8211 (or your replacement port), and test from an external network before inviting everyone.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
