Palworld Dedicated Server: Windows Setup and Connection Checklist

Check that the machine is suitable

Pocketpair lists a 4-core-plus CPU recommendation, 16 GB memory with more than 32 GB recommended, an SSD, and a reachable UDP port (8211 by default). Its documentation warns that an 8 GB server can start but is more exposed to out-of-memory crashes. Those are server requirements, not a promise of capacity for your particular world.

If you also play on the same PC, the game client competes with the server for resources. Decide who will maintain updates and backups before inviting a group. Renting may simplify networking, but you still need access to the world files and a restore process.

References: Pocketpair: server requirements

Install and perform the first launch

In Steam, enable Tools in the Library filter, find Palworld Dedicated Server and install it. Start the dedicated-server option once so it creates its folders, then stop it before editing configuration. This is the simplest route for a first Windows host.

For administrators already using SteamCMD, the official download command is below. It installs the server tool, not the paid game client. Use your chosen installation directory; do not paste an example path over a different live server.

steamcmd +login anonymous +app_update 2394010 validate +quit

References: Pocketpair: deploy a dedicated server

Edit the active configuration, not the template

For a new installation only, copy DefaultPalWorldSettings.ini from the PalServer directory to Pal/Saved/Config/WindowsServer/PalWorldSettings.ini. If that destination already contains your settings, back it up and edit it instead of overwriting it. Editing the Default file alone does not configure the running world.

Within the supplied settings structure, set a recognizable ServerName, a private ServerPassword and a different AdminPassword. Keep RCON and the REST API disabled unless you have a reason to operate them securely. Do not forward their ports as part of ordinary player access. Leave gameplay multipliers at defaults until the first connection and save are proven.

The official 1.0.4 reference uses CrossplayPlatforms for permitted platforms; the older AllowConnectPlatform parameter is not available there. PublicPort describes a community-server address and does not change the listening port. Follow the documentation for your installed version rather than copying an old all-in-one configuration.

References: Pocketpair: configuration parameters

Test in layers before troubleshooting the internet

Start the server again. On a client, use the IP-and-port field below the server list. A client on the same Windows host can try 127.0.0.1:8211; another device on your home network needs the server PC's local address. These are address examples, not addresses for a public GamerWin server.

Only after local access works, configure the firewall and router for the game UDP port to this server machine. Reserve the machine's local address so forwarding does not drift. Friends outside your network use your public address. A private shared world should also have a strong game password.

References: Pocketpair: connect to a server · Pocketpair: server requirements · Pocketpair: configuration parameters

Make a restore plan and a buying decision

Stop the server cleanly before a manual copy, retain the relevant Saved data and configuration, and keep a dated copy away from the server disk. Test restoring to a separate instance before relying on the backup. A successful file copy is not the same as a usable restoration.

For a rented plan, ask for the CPU allocation and memory limit, the exact region, backup retention, download access to saves, renewal price and cancellation terms. '32 slots' describes an admission limit, not measured performance. A host that will not explain world export makes leaving more difficult. We have not benchmarked or ranked providers; these are procurement questions, not endorsements.

Before you play

• First launch completed; active configuration backed up.
• Different game and admin passwords set.
• Local connection works before port forwarding.
• Only required game access exposed.
• A separate restore test and world-export plan documented.

Frequently asked questions

Sources & revision notes

Editorial revision: September 11, 2026. Source notes give the scope of each reference; the revision date is not a gameplay test date. Official documentation describes the publisher's system; community sources can contain errors. Use your installed game's own descriptions when they disagree.

1. Pocketpair: server requirements (Official)

   Reference checked on September 11, 2026.

2. Pocketpair: deploy a dedicated server (Official)

   Reference checked on September 11, 2026.

3. Pocketpair: configuration parameters (Official)

   Reference checked on September 11, 2026.

4. Pocketpair: connect to a server (Official)

   Reference checked on September 11, 2026.