For a Palworld dedicated server, Pocketpair’s current Server Guide (version 1.0.4, identified in 2026) lists 16GB of memory, four or more CPU cores, and fast SSD storage as the practical baseline. An 8GB machine can boot the server but has a higher risk of out-of-memory crashes. Pocketpair recommends more than 32GB for larger cases. You need a 64-bit Windows or Linux host and must expose the server’s UDP port 8211 unless you change it.
There is no official disk-capacity minimum, CPU clock-speed target, or player-count sizing table. Those omissions matter: choose storage for performance and free space, then add memory headroom according to your world, mods and concurrency rather than treating an invented “GB per player” rule as official.
What are the official Palworld dedicated server requirements?
Pocketpair’s Palworld Server Guide version 1.0.4 gives a short hardware and operating-system list. The figures below are the owner’s published guidance, not a community benchmark.
| Component | Official guidance | How to interpret it |
|---|---|---|
| Memory | 16GB listed | Use this as the baseline. 8GB may boot but has an increased out-of-memory crash possibility; more than 32GB is recommended for larger cases. |
| CPU | Four or more cores | Pocketpair does not publish a clock-speed target on the requirements page. |
| Storage | Faster SSD recommended | Low-performance storage may corrupt saved data. No official capacity number is stated. |
| Operating system | 64-bit Windows or 64-bit Linux | Ubuntu and AlmaLinux are examples in the guide. |
| Networking | UDP 8211 by default | The port can be changed; router forwarding may be needed for outside players. |
The guide describes 16GB as the listed memory figure, while the “more than 32GB” wording is a scaling recommendation rather than a hard minimum. Likewise, a fast SSD is a reliability and performance recommendation, not a published capacity threshold.
How much RAM do I need for a Palworld dedicated server?
Plan on 16GB of RAM for a normal dedicated-server installation. That is Pocketpair’s listed memory figure. It gives the server materially more headroom than the 8GB configuration that can start but is more vulnerable to out-of-memory failure.
What happens with 8GB?
Pocketpair explicitly says: “8GB is also bootable, but increases the possibility of server crashes due to out of memory.” In practice, 8GB should be treated as a constrained test or very small, closely monitored deployment, not an equal alternative to the 16GB recommendation. The statement does not promise a particular player count at 8GB.
When is more than 32GB justified?
The guide recommends more than 32GB for larger cases. Pocketpair does not define that phrase with a player-count table, so do not convert it into a universal number such as “32GB supports X players.” Use the higher tier when you expect a larger world, more simultaneous activity, or other workload that leaves little room for the operating system and background services.
How should I allocate memory on the host?
- Reserve enough RAM for the operating system and administration tools; the server cannot use every installed gigabyte safely.
- Start at 16GB, observe whether the process approaches the limit, and increase memory before recurring out-of-memory crashes.
- For a larger deployment, select more than 32GB from the outset rather than relying on swap or page-file growth to compensate for insufficient physical memory.
Swap or a page file can prevent an immediate hard stop in some operating systems, but it does not turn an 8GB host into a 16GB machine. It is also far slower than physical RAM, so it should not be your sizing strategy.
What CPU does a Palworld server need?
Pocketpair recommends four or more CPU cores. That is the only CPU figure on the requirements page; no minimum or recommended clock speed is published.
Why core count is the safest comparison
When comparing machines, use the four-core recommendation as the documented floor and then consider the age and sustained performance of the processor. A modern four-core CPU and an old four-core CPU can behave differently, but the guide does not provide a benchmark that would support a specific model or GHz cutoff. Avoid presenting a clock-speed number as an official requirement.
What should I monitor?
- Watch sustained CPU utilization while players are active, not only when the server is idle.
- Check whether one or more cores remain saturated during movement, combat or world activity; adding memory will not cure a processor bottleneck.
- Leave capacity for the operating system, SteamCMD or Steam processes, backups and monitoring.
A four-core host satisfies the published recommendation, while additional cores provide more scheduling headroom for a busy machine. The official documentation does not state how many players a given processor can support.
Is an SSD required for a Palworld dedicated server?
Pocketpair recommends a faster SSD, and the warning is unusually direct: “Low-performance storage may corrupt saved data.” An SSD is therefore the responsible choice for a persistent world, even though the guide does not phrase it as a formal “must have” checkbox.
Why storage performance matters
The server repeatedly reads and writes world and configuration data. Slow or inconsistent storage can extend save operations and, according to Pocketpair, increase the risk of corrupted saves. A faster internal SSD reduces that risk compared with low-performance storage.
How much disk capacity is needed?
No official disk-capacity figure appears in the guide. Do not advertise a particular number of gigabytes as the Palworld minimum. Choose capacity for the server files, the operating system, free working space and the number of retained backups your administration plan requires. A “1TB internal SSD” is a reasonable product-search description, but it is not an official Palworld requirement.
Can I use a hard disk?
The documentation does not ban hard disks, but its low-performance-storage warning makes one a poor choice for a production server. If an HDD is the only available option, treat it as a risk-managed experiment: keep reliable backups, expect slower administration, and move the installation to a faster SSD if save reliability becomes questionable.
Which operating systems are supported?
The documented choices are 64-bit Windows and 64-bit Linux. The guide names Ubuntu and AlmaLinux as Linux examples. A 32-bit host is outside the stated requirement.
Windows
Windows offers the simplest route for people without game-server experience. You can install through the Steam client or use SteamCMD. After installation, start PalServer.exe from the PalServer directory.
Linux
Linux is supported through SteamCMD. It assumes familiarity with the shell and may require additional security configuration. From the PalServer directory, start the server with ./PalServer.sh.
Choose the operating system you can patch, secure and troubleshoot. A nominally compliant machine is not useful if nobody can administer its services, files or firewall.
Which installation method should I use?
Pocketpair lists four deployment paths. They install the same dedicated-server software but differ in administration effort.
| Path | Best for | Trade-off |
|---|---|---|
| Windows with Steam client | First-time administrators | Easiest documented path, with less command-line control. |
| Windows with SteamCMD | Scripted or repeatable administration | Command-line based; you manage the install and updates yourself. |
| Linux with SteamCMD | Operators comfortable with Linux | Requires Linux knowledge and may need extra security configuration. |
| Official Docker image | Advanced users already operating containers | More operational complexity. Docker Desktop is deprecated in the guide because its storage I/O can raise the risk of save corruption and malfunction. |
How do I install with SteamCMD?
Pocketpair’s deployment instructions provide this command:
steamcmd +login anonymous +app_update 2394010 validate +quitThe same package can be found by searching Steam for Palworld Dedicated Server; enable the Tools filter if it does not appear in the normal game list.
- Install SteamCMD on the 64-bit Windows or Linux host.
- Run the command exactly as shown, allowing SteamCMD to download or validate app ID
2394010. - On Windows, change to the PalServer directory and launch
PalServer.exe. - On Linux, change to that directory and launch
./PalServer.sh. - Record the install directory and startup command so you can repeat updates and recovery consistently.
Should I use Docker?
Use the official Docker image only if you already understand container storage and networking. Pocketpair marks Docker Desktop as deprecated from a storage-I/O perspective and says that path increases the risk of saved-data corruption and malfunction. That warning is about Docker Desktop’s storage behavior; it does not turn the official image into a general-purpose beginner installation.
What network settings are required?
The default game-server port is UDP 8211. You can change the port, but every client and network rule must then use the new value.
- Confirm which UDP port the server is configured to use; leave it at 8211 unless you have a reason to change it.
- Allow that UDP port through the host’s firewall.
- If players connect from outside your local network, forward the same UDP port on the router to the server’s local IP address.
- Give players the reachable address and port, and test from a network that is not the host’s own LAN.
Port forwarding is not needed for every topology. A server on a directly reachable public host may only need its host firewall rule, while a home connection behind a router generally needs forwarding. The official requirement is the UDP port; the exact router screens depend on your equipment.
How should I size a server when there is no player-count table?
Pocketpair publishes no player-count sizing chart, so capacity must be validated on your own workload rather than inferred from an unsupported formula. Use the documented baseline, then scale for headroom.
| Situation | Starting choice | What to verify |
|---|---|---|
| Small private group or evaluation | 16GB RAM, four or more cores, faster SSD | Memory use, CPU saturation and save behavior during peak activity. |
| Busy or expanding community | More than 32GB RAM, four or more cores with additional headroom, faster SSD | Whether concurrent activity exhausts memory or leaves CPU queues. |
| 8GB test host | Only as a temporary experiment | Out-of-memory events; do not treat a successful boot as proof of stable capacity. |
Measure during the busiest realistic session. If memory reaches the limit, upgrade RAM first; if a core remains saturated while memory is comfortable, move to a faster or higher-capacity CPU. If saves are slow or corrupted, investigate storage performance before increasing CPU.
What are the most common failure modes?
Out-of-memory crashes
Symptoms include the process terminating during activity or the operating system reporting memory exhaustion. Confirm installed and available RAM, close unrelated workloads, and move from an 8GB test configuration to the 16GB baseline. For larger cases, use more than 32GB as Pocketpair recommends.
Save corruption or malfunction
Check that the server is on a faster SSD rather than low-performance storage. If you selected Docker Desktop, migrate away from that deprecated path because Pocketpair links its storage I/O behavior to increased corruption and malfunction risk. Preserve known-good saves before changing the installation.
Players cannot connect
Verify that the server is running, the configured port matches the client information, the host firewall allows UDP, and the router forwards UDP 8211 when the host is behind a NAT router. If you changed the port, replace 8211 in every relevant rule.
Linux launch errors
Confirm that you are in the PalServer directory, are using the 64-bit Linux environment described by the guide, and have applied the required security configuration for your distribution. The documented launch command is ./PalServer.sh.
Is self-hosting the right choice?
Self-hosting gives you ownership of the machine, storage and network policy, but you must supply an always-available host, maintain the operating system, expose the required UDP port and protect the save files. A rented game-server host or VPS can shift hardware and uptime management to a provider, but you must verify its current Palworld support, RAM tiers, SSD type, backups, locations and terms before committing. Pocketpair’s guide does not endorse a particular provider.
For a small group with an existing 64-bit computer, self-hosting on 16GB RAM, four or more cores and a faster SSD is the documented starting point. For a larger or public world, budget for more than 32GB and for administration time, not just the purchase of components.
Pre-launch checklist
- 64-bit Windows or Linux installed; Ubuntu and AlmaLinux are documented Linux examples.
- At least 16GB RAM for the baseline; more than 32GB for a larger case.
- Four or more CPU cores; no unsupported clock-speed claim substituted for the official guidance.
- Faster SSD storage with adequate free capacity; no invented capacity minimum.
- Palworld Dedicated Server installed through Steam, SteamCMD or the official advanced-user Docker path.
- UDP 8211 allowed through the host firewall and forwarded on the router when required.
- Startup command recorded:
PalServer.exeon Windows or./PalServer.shon Linux. - Monitoring in place for memory, CPU, storage behavior and connectivity before inviting a larger group.
How current are these requirements?
The figures and commands above come from Pocketpair’s official Server Guide and deployment documentation, identified as version 1.0.4 in 2026. Server requirements, ports and container guidance can change with later releases. Check the live Pocketpair guide before a new deployment or major upgrade, especially if an update changes the startup package or networking behavior.
Frequently Asked Questions
Does a Palworld dedicated server need a graphics card?
Pocketpair’s version 1.0.4 requirements page does not publish a GPU requirement. It specifies CPU cores, memory, storage, operating system and networking, so a graphics-card specification cannot be presented as an official minimum.
Can I predict the maximum number of players from 16GB of RAM?
No. The official documentation provides no player-count sizing table. Treat 16GB as the listed baseline, then test your actual world and peak concurrency while watching memory and CPU usage.
What does “Docker Desktop is deprecated” mean for a server administrator?
Pocketpair’s warning is about Docker Desktop’s storage-I/O performance and the resulting risk of save corruption or malfunction. Advanced users can evaluate the official Docker image, but Docker Desktop should not be selected as the beginner default for a persistent world.
Do I need port forwarding if everyone plays on the same local network?
Not necessarily. Port forwarding is generally for players arriving through a router from outside the local network; local players still need the host firewall and the correct UDP port. The exact requirement depends on your network topology.