Palworld already runs on DirectX 11 by default — DirectX 12 is the opt-in mode, enabled with the -dx12 launch argument — so if a guide told you to "switch to DX11" to fix crashes, it was telling you to do nothing.
Launch options that are actually documented
| Argument | What it does | Status |
|---|---|---|
-dx12 | Runs the game on DirectX 12 instead of the DX11 default | Documented |
-ngxdisableota | Disables DLSS over-the-air updates; documented fix for black screen at startup on older Nvidia GPUs | Documented |
-dx11 | Would force DX11, which is already the default | Not documented for Palworld — community-reported |
-force-d3d11 | Nothing. This is a Unity engine flag; Palworld runs on Unreal | Incorrect advice |
To set one on Steam: right-click Palworld → Properties → General → Launch Options, and type the argument.
Add -dx12, play the same 10 minutes of a busy base with the same settings, and compare. If it stutters or crashes, remove the argument to return to DX11. There is no official Pocketpair recommendation for which renderer to use, so ignore anyone who states one as fact.
Crashes: work through this order
1. Remove mod residue (the biggest single cause)
Pocketpair's advisory before 1.0 named the symptoms directly: crashes when launching or playing, corrupted or unloadable save data, and quests or events becoming impossible to progress. The critical detail is that disabling mods does not help — leftover mod files and loaders still get loaded. Delete them manually, unsubscribe from Workshop items and delete their leftovers too.
2. Verify integrity of game files
Steam Library → right-click Palworld → Properties → Installed Files → Verify integrity of game files. This is Pocketpair's own recommended step and it repairs partial or interrupted updates.
3. Check whether your crash is a known, already-fixed bug
| Patch | Date | Crash or hang fixed |
|---|---|---|
| v1.0.1 | 15 Jul 2026 | Save data could be unintentionally discarded after certain operations |
| v1.0.2 | 29 Jul 2026 | All players disconnecting, and player crashes, during the Panthalus battle on dedicated servers; crash on Japanese text input in fullscreen |
| v1.0.2.101103 | 30 Jul 2026 | Infinite loading screen after defeating the World Tree boss |
| v1.0.3 | 12 Aug 2026 | Unintended Fast Travel activation during Tower Boss fights; Pals appearing to vibrate on client screens |
If your crash matches one of these, updating is the fix. As of 13 August 2026 the current build is v1.0.3.
4. Confirm you meet the requirements — they are steeper than people assume
| Spec | Minimum | Recommended |
|---|---|---|
| OS | Windows 10 (64-bit) | Windows 11 (64-bit) |
| CPU | Intel Core i5-9400F | Intel Core i5-12400 / AMD Ryzen 5 5600X |
| RAM | 16 GB | 32 GB |
| GPU | GeForce GTX 1660 | GeForce RTX 3060 Ti / Radeon RX 6700 XT |
| Storage | 40 GB, SSD required | |
Pocketpair adds a note to both tiers: performance varies depending on the number of active Pals. That is the studio telling you the simulation, not the renderer, is the bottleneck.
Stutter and low FPS
Version 1.0 shipped meaningful optimisation work. Per the official changelog, Pocketpair optimised high-load processes to reduce temporary stuttering, optimised memory-related processing, optimised data search for items and work states, and fixed crashes and memory leaks on PS5, Xbox and dedicated servers.
The same changelog names the two graphics settings the team itself adjusted, which is a strong hint about where the cost lives:
- Grass and tree draw distance at High graphics and above
- Shadow density across the field
Lower those two first. Community reports consistently point at grass detail and shadows as the settings that clear up stutter while exploring and flying — labelled here as community-reported because Pocketpair publishes no official settings guide.
The non-graphics causes
- Base size and Pal count. Working Pals are simulated. Bigger bases with more Pals cost more, permanently.
- Dropped items. Version 1.0 added a Maximum Number of Dropped Active Items world setting precisely because loose items are a measurable cost. Lower it.
- Placed structures. Every building part is persistent state.
- Storage speed. An SSD is a stated requirement, not a suggestion.
Dedicated server performance
Official requirements: 4+ CPU cores recommended, 16 GB RAM recommended. Pocketpair notes 8 GB will boot but increases the chance of out-of-memory crashes, and that low-performance storage may corrupt saved data. The default port is UDP 8211.
Palworld's official arguments documentation states that for version 1.0 and later, leaving -useperfthreads, -NoAsyncLoadingThread and -UseMultithreadForDS unset may improve performance. Those three flags were standard community advice for two years. If you copied them from a 2024 guide, remove them and re-test.
Config levers worth knowing, with their exact names:
| Setting | Effect |
|---|---|
ServerReplicatePawnCullDistance | How far away Pals are replicated to clients. Range 5000–15000 |
PhysicsActiveDropItemMaxNum | Cap on physics-active dropped items |
BaseCampWorkerMaxNum | Working Pals per base, maximum 50 |
MaxBuildingLimitNum | Structure cap; 0 means unlimited |
BaseCampMaxNumInGuild | Bases per guild. Default 4, maximum 10 |
Fixes we could not verify
Rolling GPU drivers back or forward, disabling Steam, Discord and GeForce overlays, enlarging the Windows page file, and disabling XMP memory profiles are all widely recommended for Palworld crashes but appear in no Pocketpair or vendor documentation for this game. They are cheap to try and harmless; they are not verified fixes.
What to read next
- Modding guide — the deletion routine that prevents most post-patch crashes
- Save files and settings — backing up before you experiment
- Crossplay and servers — server sizing and config file locations