Palworld Tools
Estimate RAM and CPU for a Palworld dedicated server from your player count, active bases, automation level, and mods.
Most guides just multiply players × some number. That ignores bases, working Pals, mods, and RAM creeping up over long uptimes.
Slide the controls — the breakdown shows the math. Numbers assume an AleForge box (we run tuning that shaves a bit off baseline use).
Each base with Pals on work tasks adds to server memory, even when nobody is online.
| Plan | RAM | From | |
|---|---|---|---|
| Loading plans… | |||
100% = 1 dedicated thread.
Estimates only. Real usage varies with base layout, Pal count per base, mod quality, and player activity. Model last calibrated July 2026.
There is no single answer. It depends on your sliders. A few friends on vanilla with small bases often land around 4GB on AleForge (Apprentice plan). More players, automation, and mods push that up. Use the sliders above instead of a random "16GB minimum" forum post.
Working Pals, conveyors, and structures stay loaded on the server whether anyone is logged in. Two players with full production lines can beat eight players with tents.
RAM usage tends to rise the longer the server process runs. The memory leak line in the breakdown adds headroom for that. AleForge hosts get a small credit in the model for our server tuning.
Yes, mostly single-thread performance. Pal AI, breeding timers, and base logic run on one core. The CPU % above can exceed 100% when automation, players, and mods stack up — that means you need more than one thread's worth of headroom.
Depends on the pack. A couple of QoL mods are minor; larger overhauls can cost 1GB or more. Use the mod tier slider to ballpark it, then watch actual usage after you install.
File manager, save uploads, boxes that stay online.
Palworld hosting at AleForge