Manual-first Windows server guide
Palworld Dedicated Server Setup, Ports, Saves and Cross-Play
This Windows-first Palworld server manual follows Pocketpair's current 1.0-era documentation from installation through a verified outside join. It distinguishes the active one-line INI from the reference template, protects the complete world and player-save tree, and treats Community Server discovery, REST administration and Workshop mods as separate operational choices.
Palworld is unusual because Xbox and PlayStation players cannot use the same direct-IP path as Steam players: they need a Community Server listing. Its current Windows server also has native Workshop mod deployment, a REST API that should stay on a trusted network, native rolling save copies, and a deprecated RCON interface that new integrations should not depend on.
SteamCMD App ID
2394010
Pocketpair publishes this ID in the official deployment command.
Player port
UDP 8211 by default
Change the listener with -port= and forward only the selected player port for direct outside joins.
Active Windows settings
Pal/Saved/Config/WindowsServer/PalWorldSettings.ini
DefaultPalWorldSettings.ini is a reference template, not the file read as the active Windows configuration.
Player ceiling
32 by the documented launch example
Use -players= or ServerPlayerMaxNum, then size the actual host from measured workload rather than the numeric ceiling.
Console joining
Xbox and PS5 require a Community Server listing
A direct-IP-only server is not a complete cross-platform configuration.
Remote administration
REST preferred; RCON deprecated
Pocketpair says management interfaces are not designed for direct Internet exposure.
Protect the server first: Stop the server cleanly and copy the entire SaveGames tree, active PalWorldSettings.ini and mod manifest state outside the install folder before updating, importing, changing mods or testing recovery.
Size the host before downloading
PC and capacity guidance
Pocketpair publishes 4+ cores, 16 GB RAM, more than 32 GB for greater stability and a fast SSD. Player-range labels and host-headroom advice here are conservative editorial starting points, not official capacity guarantees.
| Profile | Players | Memory | Processor | Storage |
|---|---|---|---|---|
| Private-world starting point Conservative starting point | A small regular group | 16 GB available to the server workload; a 32 GB host is the safer planning baseline | At least 4 modern CPU cores | Fast SSD with room for the installation, world growth and off-tree snapshots |
| Long-lived or busy world Conservative starting point | Growing guilds and higher concurrency | More than 32 GB is Pocketpair's stability recommendation | 4 or more cores, with observed headroom documented under real load | Low-latency SSD plus separate backup capacity |
Clean install
Install and create the active server layout
Generate Palworld's runtime directories first, then edit the active Windows INI while the process is stopped.
- 1
Install the official server package
Use SteamCMD or Steam Library > Tools. SteamCMD supports anonymous installation with the official app ID.
steamcmd +login anonymous +app_update 2394010 validate +quit - 2
Run once, then stop
Launch PalServer.exe from the installation root once so the Saved directory structure is created, then stop before configuration edits.
- 3
Create the active INI
Copy DefaultPalWorldSettings.ini to Pal/Saved/Config/WindowsServer/PalWorldSettings.ini and edit the destination copy.
The OptionSettings value is a single structured tuple; malformed punctuation can make values fall back or fail.
- Do not add the old performance flags by rote; Pocketpair warns they may make v1.0-and-later performance worse when unnecessary.
Connectivity
Choose the right join path and verify it
Direct IP and Community Server discovery serve different client groups, so test the route players will actually use.
- 1
Select direct or Community mode
Use direct IP for a private PC workflow. Add -publiclobby and accurate advertisement values when Xbox or PS5 players must discover the server.
- 2
Open the narrow player rule
Permit and, when direct public IPv4 hosting requires it, forward the configured UDP player port. Keep REST and RCON off the public player path.
- 3
Test LAN and an independent outside connection
Confirm the expected world and one existing identity locally, then test from a separate network and every platform family the page promises.
A same-LAN attempt through a public Community listing can fail because of hairpin NAT even when outside clients work.
Keep every layer consistent
Ports, firewall, and router setup
Open only the services your Palworld server actually uses. The game process, Windows Firewall rule, router forward, and player join address must all agree on the same port and protocol.
| Port | Protocol | Purpose | Exposure | Notes |
|---|---|---|---|---|
| 8211 (configurable) | UDP | Player traffic and direct-IP joining | Internet playersRequired for this use | Forward only the chosen listener. PublicPort advertises a value for the Community Server list; it does not create another listener.[pal-requirements][pal-arguments][pal-community] |
| 8212 in official examples | TCP | Authenticated REST administration | LAN onlyOptional | Keep the REST service on a trusted management network; do not publish it as a player-facing forwarding requirement.[pal-rest] |
| 25575 by default when legacy RCON is enabled | TCP | Deprecated RCON administration | Optional administrationOptional | Pocketpair has deprecated RCON. Do not design a new public-facing management path around it.[pal-rcon] |
Never expose an administration or RCON port merely so players can join. Keep remote administration private whenever possible, use a strong unique credential, and confirm the game's own security model before forwarding it.
Know what must survive a reinstall
Files, worlds, and configuration
| File or folder | Purpose | Backup | Notes |
|---|---|---|---|
| Pal/Saved/SaveGames | World, player, guild and companion save state | Critical | Copy the complete tree as one unit; the exact root is project-verified and must be recaptured on the release build.[pal-config] |
| Pal/Saved/Config/WindowsServer/PalWorldSettings.ini | Active Windows server configuration | Critical | The server reads this file, not the installation-root reference template.[pal-config] |
| DefaultPalWorldSettings.ini | Publisher-supplied configuration reference | Regenerates | Copy from it when bootstrapping, but never present edits here as active configuration.[pal-config] |
| Mods/PalModSettings.ini and Mods/Workshop | Enabled native Workshop server packages and discovery metadata | Recommended | Preserve package names and ordering with a pre-update snapshot; Workshop payload can be reacquired but state must stay explainable.[pal-mods] |
| Setting or file | Location | What it controls | Restart? |
|---|---|---|---|
ServerNameA distinctive name without an IP address or password | PalWorldSettings.ini OptionSettings tuple | Names the server in discovery and join surfaces.[pal-config] | Yes |
ServerPassword and AdminPasswordUse two different randomly generated secrets | PalWorldSettings.ini OptionSettings tuple | Separates player admission from privileged command/API authentication.[pal-config][pal-commands][pal-rest] | Yes |
CrossplayPlatforms(Steam,Xbox,PS5,Mac) | PalWorldSettings.ini OptionSettings tuple | Selects the currently allowed Steam, Xbox, PS5 and Mac platform families.[pal-about][pal-config] | Yes |
ServerPlayerMaxNumStart below 32 and raise only after load testing | PalWorldSettings.ini OptionSettings tuple | Caps concurrent players independently of what the machine can safely sustain.[pal-config][pal-requirements] | Yes |
bIsUseBackupSaveDataTrue, plus a separate off-tree snapshot policy | PalWorldSettings.ini OptionSettings tuple | Enables Pocketpair's native rolling save backups.[pal-config] | Yes |
Avoid incompatible clients and unsafe shortcuts
Players, mods, and administration
Cross-play and editions
Current official documentation lists Steam, Xbox/Microsoft Store, PS5 and Mac in the default CrossplayPlatforms value, but console players require Community Server discovery.
- AllowConnectPlatform is deprecated; do not copy that field from old guides.
- A direct-IP-only test does not validate Xbox or PS5 support.
- Record a build-matched join result for each promised platform because storefront releases can diverge.
Mods and extensions
Pocketpair now documents native Workshop server mods for the Windows dedicated server; this is different from older unofficial loader instructions.
- The server discovers eligible packages under Mods/Workshop through each package's Info.json.
- Enable packages by PackageName in Mods/PalModSettings.ini; the package name may differ from its folder name.
- Use -NoMods for a controlled vanilla diagnostic start.
- Back up before adding, updating or removing a content mod because Pocketpair warns mods can crash or corrupt saves.
Administration
Use the documented in-game commands or authenticated REST API on a trusted management network; Pocketpair has deprecated RCON.
- Players authenticate for in-game administration with /AdminPassword.
- Documented commands include ShowPlayers, Broadcast, KickPlayer, BanPlayer, Save and Shutdown.
- REST offers information, player, save and shutdown operations but is not designed for direct Internet exposure.
- Never reuse the join password as the admin or API credential.
Preserve a return path before maintenance
Updates, backups, and rollback
Update without gambling the world
Protect a matched world/config/mod snapshot, stop cleanly, update the official package, then verify identity and joining before reopening access.
- 1
Save and announce maintenance
Use /Save followed by /Shutdown with a countdown and message, then confirm the process has exited.
/Shutdown 60 Server update in one minute - 2
Capture a complete recovery set
Copy SaveGames, the active INI, launch choices and mod settings outside the installation tree before validation can replace files.
- 3
Update and test privately
Run app_update 2394010 validate while stopped, compare new defaults without overwriting active settings, then verify the expected world, guild ownership, mods and outside joining.
steamcmd +login anonymous +app_update 2394010 validate +quit
Back up and prove the restore path
Native rolling points help, but a separate complete snapshot is the dependable boundary for imports, updates and mod changes.
- 1
Enable native rotation
Set bIsUseBackupSaveData=True and confirm that the documented backup directory and rotation points are actually being created.
- 2
Copy the whole state set
After a clean stop, copy SaveGames, PalWorldSettings.ini and enabled mod metadata outside the server install folder.
- 3
Restore into quarantine first
Restore a matched copy and verify the world, one existing character, guild/base ownership and a save-restart cycle before replacing the production state.
Diagnose before reinstalling
Common Palworld server problems
Palworld settings revert or never apply
What players see
The server starts with default values even after the owner edited an INI.
Likely cause
The reference DefaultPalWorldSettings.ini was edited, the active file is in the wrong platform directory, or the one-line tuple is malformed.
- 1.Stop the server and back up both INI files.
- 2.Edit Pal/Saved/Config/WindowsServer/PalWorldSettings.ini, then compare the complete tuple punctuation with the official example.
- 3.Change one harmless value and restart to prove the active path before making a larger batch of edits.
Xbox or PS5 cannot join by direct IP
What players see
PC direct joining succeeds, but a console player has no usable direct-IP route.
Likely cause
Pocketpair requires Xbox and PS5 clients to join through a Community Server listing.
- 1.Back up launch and configuration state before changing discovery mode.
- 2.Configure -publiclobby with accurate public advertisement values.
- 3.Verify the listing and join from the actual console platform on a current build.
Remote administration fails or is unsafe to expose
What players see
A legacy RCON tool disconnects, or REST works only locally.
Likely cause
RCON is deprecated, while the REST API is intended for authenticated trusted-network access rather than direct Internet exposure.
- 1.Remove public forwarding for management ports before further diagnosis.
- 2.Test authenticated REST from the same trusted LAN and retain in-game commands as the maintenance fallback.
- 3.Migrate product automation away from RCON and record the current REST version behavior.
A native Workshop server mod is not loading
What players see
The package was downloaded but is absent after server start.
Likely cause
The package is not eligible for server installation, the wrong PackageName was enabled, or PalModSettings.ini was not regenerated/restarted.
- 1.Snapshot the world and current mod settings.
- 2.Read PackageName from Info.json and compare it with each ActiveModList entry.
- 3.Test a controlled -NoMods start, then re-enable one package at a time.
Every focused Palworld troubleshooting guide
- Palworld Community Server Not Showing →
- Palworld Server Ports and Windows Firewall →
- Update a Palworld Server Without Losing Your World →
- Palworld Server Backup and Recovery →
- Palworld Server Settings Not Applying: Edit the Active INI →
- Palworld RCON to REST Migration Without Public Exposure →
- Palworld Native Workshop Server Mod Not Loading →
Evidence stays visible
Sources and verification
Technical behavior changes with server builds. These are the references reviewed for this guide. Official documentation wins if a later patch changes a path, port, command, or compatibility rule.
[pal-about] Pocketpair
About server and current cross-play platforms ↗Reviewed 2026-08-30 · Official documentation
[pal-requirements] Pocketpair
Dedicated-server requirements ↗Reviewed 2026-08-30 · Official documentation
[pal-deploy] Pocketpair
Deploy a dedicated server ↗Reviewed 2026-08-30 · Official documentation
[pal-community] Pocketpair
Configure a Community Server ↗Reviewed 2026-08-30 · Official documentation
[pal-connect] Pocketpair
Connect to a Palworld server ↗Reviewed 2026-08-30 · Official documentation
[pal-arguments] Pocketpair
Server launch arguments ↗Reviewed 2026-08-30 · Official documentation
[pal-config] Pocketpair
Server configuration parameters ↗Reviewed 2026-08-30 · Official documentation
[pal-commands] Pocketpair
Dedicated-server commands ↗Reviewed 2026-08-30 · Official documentation
[pal-mods] Pocketpair
Installing mods on a server ↗Reviewed 2026-08-30 · Official documentation
[pal-rest] Pocketpair
Palworld REST API overview ↗Reviewed 2026-08-30 · Official documentation
[pal-rest-save] Pocketpair
REST save endpoint ↗Reviewed 2026-08-30 · Official documentation
[pal-rcon] Pocketpair
RCON deprecation notice ↗Reviewed 2026-08-30 · Official documentation
Keep learning
Related guides
Carry Palworld UDP 8211 beyond the LAN
Carry UDP 8211 through Windows Firewall, the router and a genuinely external join test.
Open guide →
When Palworld UDP 8211 is still unreachable
Find the upstream network boundary when a correct Palworld forward still cannot be reached.
Open guide →
Host a game server at home
Plan Windows, router and external-join checks before exposing a Palworld world.
Open guide →
Palworld troubleshooting
Work from symptom-specific diagnostics without risking the active save.
Open guide →
Palworld server FAQ
Get concise answers about joining, saves, cross-play and administration.
Open guide →