The Forest Server Requirements Calculator

Player limit

The Forest is capped at 8 players total, whether you host peer-to-peer or via a dedicated server. The standalone dedicated server defaults to 4 slots; you raise this up to 8 by editing the serverPlayers value in the server configuration. There is no way to exceed 8 without unofficial mods, and most groups run between 2 and 6.

RAM

Memory is the most important spec and the one most worth being generous with. A fresh server idles at roughly 1.5-2 GB. In practice, allocate 3 GB for a two-player game, 4 GB for the default four slots, and around 5 GB for a full eight-player server. RAM usage is not purely a function of player count: The Forest tracks every chopped tree, placed log, built structure and saved item, so a long-running world with sprawling bases will consume noticeably more memory than a fresh save. If your group builds heavily, lean toward the higher end. Mods and quality-of-life plugins add further overhead, so budget 50% extra (roughly 6-8 GB) for a modded eight-player setup.

CPU

The dedicated server is only lightly multi-threaded and depends heavily on single-core clock speed. A modern CPU with 2 cores at 2.4 GHz or faster comfortably handles 2-3 players. For 4 or more, and especially a full server, target 4 cores at 3.0 GHz or higher. When comparing hosts, prioritise a high per-core clock (a fast Ryzen or recent Intel core) over raw core count: physics for trees, AI for the cannibal and mutant enemies, and structural simulation all benefit more from clock speed than from extra threads. Shared or heavily oversold CPU plans can cause noticeable lag spikes during combat and large base interactions.

Storage

The server install itself is small, around 1-2 GB via SteamCMD. Allow 10 GB total to cover the install, save files, logs and update staging. Save files grow with world progress but remain modest. If you run mods or keep multiple save slots and backups, add a few more gigabytes. A standard SSD is plenty fast; you do not need NVMe for this game.

Bandwidth and network

The Forest is bandwidth-friendly. Steady-state traffic is only a few KB/s per player, so a typical eight-player server uses a small fraction of a 100 Mbps line. As a planning figure, budget roughly 10-15 GB of monthly data transfer per active player slot, which covers normal play plus occasional save downloads. Far more important than total bandwidth is a low-latency connection located near your players; ping has a much bigger effect on the feel of the game than throughput.

Ports

Open the Steam server port, game port and query port (commonly 8766, 27015 and 27016 by default, configurable in the server settings). These must be reachable for the server to register with Steam and appear in the browser. On a hosted plan these are handled for you; on a self-hosted box you'll forward them on your router or firewall.

Operating system

The dedicated server runs on Windows; many hosts and self-hosters also run it on Linux (Ubuntu) under a compatibility layer. Either works, but factor a little extra RAM and CPU overhead for the host OS into your planning.

Keep your server smooth

Because The Forest leans on single-core performance, the single best optimisation is choosing a host with a fast, dedicated CPU core rather than a cheap oversold shared plan. Lag during enemy raids or while placing structures is almost always CPU-bound, not memory-bound.

Restart the server on a schedule. A daily or every-few-days automatic restart clears accumulated memory and resets any drift, which keeps a long-lived world responsive. Pair this with regular automated save backups so a crash or corrupt save never wipes weeks of progress.

Manage your build footprint. The biggest, most controllable driver of resource use is the number of placed structures and modified terrain. Tearing down abandoned half-built bases and consolidating to fewer large settlements reduces the simulation and memory load far more than any config tweak.

Match your slot count to reality. Leaving the server at a full 8 slots when only 3 friends play wastes nothing directly, but if you do open it up, the jump from 4 to 8 active players is where you'll feel the strain, so make sure your RAM and CPU headroom is in place before inviting a full lobby.

Place the server geographically close to your players. For a fast-paced survival game, a 30 ms ping feels dramatically better than 120 ms, regardless of how much bandwidth or RAM you've allocated.

What to look for in a host

The Forest is undemanding, so the deciding factors are quality and convenience rather than raw size. Focus on these points:

• CPU clock speed and dedication. Prioritise plans built on modern, high-clock processors with guaranteed (not oversold) cores. This single factor affects in-game smoothness more than anything else.
• Adequate, flexible RAM. Make sure you can run at least 4-5 GB for a full server, with the option to add more if you mod or build heavily. Avoid plans that lock you to a tiny fixed allocation.
• Server location. Pick a data-centre region close to where most players live to keep latency low. Many providers list multiple regions.
• Automated backups and easy restarts. Built-in scheduled backups and one-click or scheduled restarts protect your save and keep performance steady over weeks of play.
• Mod and config support. If you plan to use mods, confirm the host gives you file access and an easy way to edit the server configuration and slot count.
• Transparent pricing and uptime. Because the game only needs 8 slots, you should not overpay. Compare price against committed resources and look for a clear uptime track record.

Whether you self-host on a spare machine or rent from a provider, the same priorities apply: fast cores, enough memory, low latency to your group, and reliable backups.

CPU note: The Forest's dedicated server is lightly multi-threaded and leans on single-core speed. 2 cores at 2.4 GHz+ handle 2-3 players; bump to 4 cores at 3.0 GHz+ for a full 8-player slot. High per-core clock speed matters more than core count.

The Forest hard-caps at 8 players; the dedicated server defaults to 4 slots until you raise serverPlayers in the config. RAM use is modest at start but climbs as players build large bases and the world fills with saved structures and tree-cut state. These figures are conservative and include OS overhead; allocate a little headroom.