iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
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.
Fix Palworld server lag by first separating simulation overload from network trouble. Watch CPU, memory, storage activity and network reachability while players reproduce the problem. Then move the server and save files to fast SSD storage, keep the player cap realistic, apply Pocketpair’s documented threading flags, and verify UDP port 8211, firewall and port-forwarding rules. These changes address the server rather than cosmetic settings on an individual player’s PC.
Identify what kind of lag you have
“Lag” describes several different failures. A server that cannot process the world quickly enough produces delayed actions and stale world updates. A reachability or packet-delivery problem produces failed joins, timeouts or rubber-banding even when the host has unused CPU. Diagnose the category before changing settings.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Simulation overload
- Players can connect, but actions register late.
- World updates, creature behavior or building changes appear several seconds behind.
- Everyone experiences the delay at roughly the same time.
- The host shows sustained CPU, memory or storage pressure while the issue is reproduced.
Connectivity trouble
- Players outside the local network cannot join, or joins time out.
- Players are repeatedly disconnected or rubber-band to an earlier position.
- Local players are fine while remote players have problems.
- UDP 8211 is not forwarded to the correct machine, blocked by a firewall, or affected by an address or port-detection problem.
Capture evidence during a reproduction
- Ask one or more players to perform the action that normally causes lag.
- Record host CPU utilization, available memory, disk activity and network status during the event.
- Note whether the symptom is delayed simulation, rubber-banding, a timeout, or a failed join.
- Change one category of setting at a time and repeat the same reproduction so you can identify which change helped or hurt.
Do not start by lowering client graphics settings. Those settings can improve one player’s frame rate, but they do not fix a dedicated server that is out of CPU, memory, storage I/O capacity or network reachability.
Meet the documented server baseline
Pocketpair’s current Palworld Server Guide (version 0.5.0 documentation) recommends at least four CPU cores, 16 GB of memory, faster SSD storage and the default UDP port 8211. The guide says 8 GB is bootable, but increases the possibility of out-of-memory server crashes. Treat 16 GB as the practical starting point for a persistent multiplayer server, not as a guarantee of smooth play at every player count.
#1 Best Overall
- MEET THE NEXT GEN: Consider this a cheat code; Our Samsung 990 PRO Gen4 SSD helps you reach near max performance with lightning-fast speeds; Whether you’re a hardcore gamer or a tech guru, you’ll get power efficiency built for the final boss
- REACH THE NEXT LEVEL: Gen4 steps up with faster transfer speeds and high-performance bandwidth; With a more than 55% improvement in random performance compared to 980 PRO, it’s here for heavy computing and faster loading
- THE FASTEST SSD FROM THE WORLD'S FLASH MEMORY BRAND: The speed you need for any occasion; With read and write speeds up to 7450/6900 MB/s you’ll reach near max performance of PCIe 4.0 powering through for any use
- PLAY WITHOUT LIMITS: Give yourself some space with storage capacities from 1TB to 4TB; Sync all your saves and reign supreme in gaming, video editing, data analysis and more
- IT’S A POWER MOVE: Save the power for your performance; Get power efficiency all while experiencing up to 50% improved performance per watt over the 980 PRO; It makes every move more effective with less consumption
| Resource | Documented guidance | How to apply it |
|---|---|---|
| CPU | 4+ cores recommended | Watch sustained utilization while players reproduce the lag. A machine that meets the minimum on paper can still stall when its cores are saturated. |
| Memory | 16 GB recommended; 8 GB is bootable but raises out-of-memory crash risk | Leave operating-system headroom. If available memory falls sharply or the process is terminated, add RAM or reduce the player cap. |
| Storage | Faster SSD storage recommended | Place both the server installation and save data on an SSD, preferably NVMe. |
| Network | UDP 8211 by default | Forward the port to the server’s fixed LAN address and allow it through the host firewall. |
Low-performance storage is not merely a speed concern: Pocketpair warns that it may corrupt saved data. If the server is on a hard disk, USB device or a congested shared volume, moving the installation and saves to an internal SSD is the clearest physical upgrade supported by the official requirements.
Move the server and saves to fast SSD storage
Why storage affects apparent lag
World loading, save operations and other disk activity can pause server work. A slow or overloaded device can therefore look like a network problem: players see delayed updates even though their internet connection is stable. It also increases the risk to the save itself.
Recommended Free Tools
Safe migration sequence
- Stop the Palworld server cleanly.
- Make a separate backup of the complete save directory and configuration files.
- Copy the server installation and save data to an internal SSD; an NVMe SSD is preferable when available.
- Update the service, shortcut or startup script so it points to the new location.
- Start the server, confirm that the expected world and player data load, and watch disk activity during a normal save.
- Keep the old copy untouched until the new location has been verified through a restart and a successful save.
A faster drive cannot compensate for an exhausted CPU or insufficient memory, so continue monitoring all resources after the move.
Match the player cap to the machine
Pocketpair’s arguments documentation shows -players=32. This is a configurable ceiling, not a promise that every four-core, 16-GB server will remain smooth with 32 simultaneous players. The actual sustainable capacity depends on the server’s CPU behavior, memory use, storage and world activity.
Rank #2
- Ideal for high speed, low power storage
- Gen 4x4 NVMe PCle performance
- Up to 6,000MB/s read, 4,000MB/s write
- Includes Acronis cloning software
- 5-year limited warranty
Reduce pressure when the host is saturated
- Check CPU and memory while the server is busy, not only at an empty base.
- If either resource remains heavily pressured and the lag appears for everyone, lower the configured player cap.
- Restart the server and reproduce the same workload.
- Raise the cap only after the host remains stable through the busiest activity you can reliably reproduce.
A lower cap is often preferable to allowing more players into a world that cannot process them consistently. Do not advertise the documented value of 32 as a performance guarantee.
Apply Pocketpair’s documented threading options
Pocketpair documents these startup options for dedicated servers:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
-useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS
The arguments guide also documents -NumberOfWorkerThreadsServer=X and states: Maximum number of process thread is CPU thread-count – 1 .
Set X according to that rule for the host’s available CPU thread count. For example, a processor with eight CPU threads would use seven worker threads under this guidance; verify the machine’s actual thread count rather than assuming it from the model name.
Rank #3
- SPEED UP PROJECTS. Launch creator applications fast with uncompromising PCIe 4.0 read speeds up to 7,100MB/s,[2] (1TB and 2TB[1] models) and write speeds up to 6,700MB/s[2] (1TB[1]-4TB[1] models).
- CREATE AND STORE MORE. Make more room for your 4K videos and high-resolution images with capacities from 500GB[1] up to 4TB[1] on M.2 2280 built with our trusted 8th generation SANDISK BiCS QLC 3D CBA NAND.
- IT GOES WHERE YOU GO. With an all-new power efficient design, your drive delivers high performance with low power, giving you more time to be productive while on the go.
- UNCOMPROMISED RELIABILITY. With up to 1,200 TBW[3] (4TB[1] model) endurance rating, your drive is designed for creators.
- KEEP YOUR DRIVE UPDATED. Monitor your SSD’s performance and check for updates with the downloadable SANDISK Dashboard application.[5]
Change and validate the flags
- Stop the server and back up its startup script or service definition.
- Add the documented flags to the existing launch command, preserving the command’s current executable and save-path arguments.
- Set
-NumberOfWorkerThreadsServer=Xusing CPU thread-count minus one. - Start the server and confirm that it reaches the normal ready state.
- Monitor CPU utilization, memory and disk activity during the same reproduction used before the change.
- Remove or revise one option at a time if startup fails or the symptom worsens.
These are documented options, not a measured promise of a particular percentage improvement. Their effect depends on the host and workload, so keep the change only if monitoring shows a stable result.
Fix UDP reachability, forwarding and firewall rules
UDP port 8211 is the default documented port. A server can have excellent hardware and still produce failed joins or rubber-banding when packets cannot reach it consistently.
Give the host a stable local address
Reserve the server’s LAN address in the router’s DHCP settings or configure an appropriate fixed address. A forwarding rule aimed at an address that changes after a reboot will silently stop working.
Forward and allow the port
- In the router’s port-forwarding page, create a rule for UDP 8211.
- Set the destination to the server’s fixed LAN address.
- On the host, create or enable an inbound firewall rule allowing UDP 8211 for the server process or service.
- Check that another application is not using the same port.
- Test from outside the LAN, such as through a player using a different internet connection. A test from inside the same network may not exercise the router’s external forwarding path.
Use explicit public addressing when automatic detection fails
Pocketpair’s arguments documentation includes -publicip=x.x.x.x and -publicport=xxxx. Use these when the server advertises the wrong public address or port and automatic detection does not work reliably. The values must match the address and external port players can actually reach.
Rank #4
- HUGE SPEED BOOST: Get random read/write speeds that are 40%/55% faster than 980 PRO; Experience up to 1400K/1550K IOPS, while sequential read/write speeds up to 7,450/6,900 MB/s reach near the max performance of PCIe 4.0*
- BREAKTHROUGH POWER EFFICIENCY: Use less power and get more performance; Enjoy up to 50% improved performance per watt over 980 PRO, plus optimal power efficiency with max PCIe 4.0 performance**
- SMART THERMAL CONTROL: Samsung's own nickel-coated controller delivers effective thermal control; With its slim size, 990 PRO is a perfect fit for desktops and laptops that meet the PCI-SIG D8 standard***
- THE CHAMPION MAKER: Up to 65% improvement in random performance enables faster loads for an ultimate gaming experience on PS5 and DirectStorage PC games****
- SAMSUNG MAGICIAN SOFTWARE: Get the most out of your SSD with Samsung Magician's advanced yet intuitive optimization tools; Monitor drive health, protect valuable data, and receive important updates for your 990 PRO
If local players connect but remote players cannot, investigate forwarding, firewall and the internet connection before changing CPU or graphics settings. If everyone connects but all players rubber-band together, return to host-resource monitoring as well as network checks.
Choose a deployment method that protects performance and saves
Pocketpair documents several deployment paths: Windows with Steam, Windows with SteamCMD, Linux with SteamCMD and an official Docker image. Select the environment you can update, monitor and back up reliably.
| Deployment choice | What to verify | Important limitation |
|---|---|---|
| Windows with Steam | Dedicated host resources, service startup, firewall and UDP forwarding | Do not let desktop applications consume the same CPU, memory or disk during play. |
| Windows with SteamCMD | Update automation, service account, save backups and firewall rules | Startup scripts must retain the required arguments after updates. |
| Linux with SteamCMD | Service management, file permissions, firewall and external forwarding | Monitor the service after restarts and confirm the save path is writable. |
| Official Docker image | Persistent volumes, resource limits, port mapping and backups | Docker Desktop is deprecated by Pocketpair from a storage-I/O perspective because it increases the risk of saved-data corruption and malfunction. |
The Docker warning concerns Docker Desktop’s storage I/O deployment, not a blanket claim that every container arrangement performs identically. If you use containers, make sure save data is on reliable persistent storage and that the documented UDP port is exposed correctly.
Use configuration changes methodically
Pocketpair’s official operations index covers configuration parameters, commands, mods and PvP. Use that index as the reference for a specific setting instead of copying an unrelated server configuration.
Best Value
- This product has been replaced by our latest generation. Please search for the SANDISK Optimus GX 7100 NVMe SSD
- HIGH-OCTANE GAMING. Experience speeds up to 7,250MB/s read and 6,900MB/s write (1-2TB models), with up to 35% faster performance than previous generation.
- PURPOSE-BUILT. Designed for serious on-the-go gamers, with a PCIe Gen4 interface and SANDISK’s next generation TLC 3D NAND.
- MORE TIME TO CLEAR THAT CHECKPOINT. Built with laptops and handheld gaming devices in mind, with up to 100% more power efficiency over the previous generation.
- DO MORE WITH DASHBOARD. Ensure your drive is optimized for prime performance with the downloadable WD_BLACK Dashboard (Windows only).
- Back up saves and configuration before every batch of changes.
- Change one class of setting at a time: capacity, threading, gameplay configuration or networking.
- Record the old value, new value and restart time.
- Test with the same player count and activity pattern so results are comparable.
- Revert immediately when a change causes startup errors, worse simulation delay or save problems.
Mods can add their own CPU, memory and storage load. If lag began after a mod or a large configuration change, reproduce the issue on a backed-up, known-good configuration before adding more tuning variables.
Self-hosting versus managed hosting
Managed hosting is reasonable when you cannot provide the recommended resources, administer port forwarding and firewalls, or maintain backups and restarts. The official documentation establishes the server’s resource and network requirements, but it does not publish provider prices or latency benchmarks. Compare offers using the criteria below rather than assuming a package’s player count equals guaranteed performance.
| Criterion | Self-hosting | Managed hosting |
|---|---|---|
| Monthly cost | Not stated; depends on hardware, electricity and internet service. | Not stated in Pocketpair’s documentation; check the provider and region. |
| CPU | You choose the processor; verify at least four cores and observe sustained load. | Ask for the allocated CPU and its single-thread performance; no official benchmark is provided. |
| Memory | Allocate at least the documented 16 GB baseline with operating-system headroom. | Confirm the guaranteed RAM allocation, not only a shared maximum. |
| Storage | Use SSD, preferably NVMe, for installation and saves. | Confirm SSD/NVMe storage and how persistent saves are handled. |
| Geographic latency | Place the host near the players you serve. | Choose a location near most players; no official latency target is published. |
| Backups and restarts | You schedule, test and restore backups yourself. | Check backup frequency, retention, restore access and restart controls. |
| Port and firewall management | You configure UDP 8211, forwarding and host rules. | Confirm whether the port is included and whether you can change it. |
| Player cap | You control -players= and must match it to measured capacity. |
Verify whether the advertised cap is configurable and what resources are reserved. |
| Mods and migration | Full control over files and migration. | Check mod support and whether you can download complete saves and configuration files. |
Troubleshoot by symptom
Everyone rubber-bands, but the server stays reachable
- Check CPU, memory and disk activity during the event.
- Move saves to SSD/NVMe if storage is slow or saturated.
- Apply the documented threading options and worker-thread rule, then restart.
- Lower the player cap if resource pressure remains.
Only remote players fail to join
- Confirm the server’s LAN address has not changed.
- Verify UDP 8211 forwarding and the host firewall rule.
- Test from outside the LAN.
- Use
-publicipand-publicportwhen automatic address detection advertises the wrong endpoint.
The server crashes or loses progress
- Check memory first; Pocketpair warns that 8 GB increases out-of-memory crash risk.
- Move the installation and saves off low-performance storage.
- Do not use Docker Desktop for storage-I/O-sensitive deployment; Pocketpair warns of increased saved-data corruption and malfunction risk.
- Restore the latest known-good backup before testing another configuration.
Lag starts after increasing the player count
- Return to the previous cap and observe whether the symptom disappears.
- Measure CPU and memory at the higher count.
- Keep the lower cap unless the host can sustain the workload without pressure.
A practical order of operations
- Classify the symptom as simulation overload, connectivity trouble or both.
- Measure CPU, memory, storage and network behavior while players reproduce it.
- Confirm the documented baseline: 4+ CPU cores, 16 GB memory, SSD storage and UDP 8211.
- Move the server and saves to SSD/NVMe and create a verified backup.
- Lower
-players=when sustained resource pressure appears. - Add
-useperfthreads -NoAsyncLoadingThread -UseMultithreadForDSand set-NumberOfWorkerThreadsServer=Xto CPU thread-count minus one. - Verify the fixed LAN address, UDP forwarding, firewall and outside-LAN reachability.
- Review deployment choice and avoid Docker Desktop where its storage I/O creates save-integrity risk.
- Use the official operations index for further configuration, changing one class at a time and keeping rollback backups.
No official source cited here publishes a latency target, packet-loss threshold or measured percentage improvement for these fixes. Judge success by repeatable symptoms and resource observations on your own server, not by an invented benchmark.
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.
