The official minimum specs for The Forest dedicated server list 4GB of RAM for 3 or more players. That number is accurate as a floor - but it doesn’t tell you much about what happens after your group has been playing for a few weeks, or what changes once you add mods.
The Forest’s server process keeps the entire world state in memory: every built structure, every fallen log, every fire someone lit and walked away from. None of that clears until you restart. A server that runs comfortably at 4GB on day one can start showing strain after a month of active play, and knowing why makes it easier to plan ahead.
Player Count: The Baseline
Player count is the obvious starting point. The default maximum is 8 players, and for a vanilla server with a fresh world, 4GB is a reasonable working number across that entire range. You won’t be running hot on a 2-player survival run, but you also won’t be in trouble with a full 8-player lobby on a map that’s still early.
| Players | Recommended RAM |
|---|---|
| 1-4 (fresh world, vanilla) | 4GB |
| 5-8 (full lobby, vanilla) | 4-5GB |
| 9-16 (extended cap via config) | 5-6GB |
| 16+ (public or community server) | 8GB+ |
The default cap of 8 can be raised by editing your server.cfg. If you do that, account for both the extra player connections and any mods you’re using to enable the higher slot count - those two things together move the needle more than either one alone.
What Actually Pushes RAM Up Over Time
Player count is just one variable. The bigger factor for most groups is how long the server has been running and what’s accumulated in the world.
Three things eat RAM in The Forest that don’t get mentioned in most guides:
Fallen logs. When a tree gets chopped down, the logs stay in the world. On a server, they don’t despawn between sessions - they sit there until someone cleans them up or the server restarts. A world where everyone’s been building for a few weeks has potentially thousands of loose logs and sticks loaded into memory at any given time.
Built structures. Every platform, every wall, every rope bridge is part of the server’s object graph. A single modest treehouse isn’t much. A fortified compound with walls, multiple structures, and storage built out by 6 players over a month is a different story.
Abandoned fires. Fires left burning or smoldering around the map persist in memory the same way structures do. It sounds minor, but on an older world with multiple players who’ve been making camps, it adds up.
A pattern we see
Lag that gradually worsens over a play session - rather than spiking at login - is usually memory pressure, not a CPU or network issue. If your server feels fine for the first hour and gets progressively worse, world state accumulation is the likely cause. A restart will confirm it.
The practical takeaway: if your group plays regularly and builds actively, expect RAM usage to climb over time. The server that fit cleanly in 4GB at launch may need 5GB after a month.
Mods
The Forest’s main modding framework is ModAPI, and mods run server-side. Each mod adds to the baseline overhead, though most individual mods are fairly lightweight. The issue is stacking.
A single quality-of-life mod - synced sleep, adjusted enemy behavior, a building tweak - probably adds a few hundred MB at most. Three or four mods together on an older world with heavy construction is where you start to feel it.
A reasonable rule of thumb: if you’re running mods, add 1GB to whatever your baseline estimate would be for vanilla. If you’re running several mods on an older, well-built world, add 2GB.
Warning
If you’re raising the player slot cap past 8 using a mod or config change, factor in both the additional player connections and the mod’s overhead separately. That combination moves faster than either variable on its own.
The Quick Reference
If you want to skip straight to a number:
4GB - fresh world, vanilla, up to 8 players, and you’re planning to restart the server every week or two. This is the right place to start for most small groups.
5GB - your world is a few weeks old, you have some building done, or you’re running one or two mods. A comfortable middle ground for groups who play regularly.
6GB - older world with active building, multiple mods, or you’re pushing past 8 player slots. Worth the extra headroom if your group logs on consistently.
8GB+ - public or community server, 16 or more players, or a heavy mod stack. Plan conservatively; you’d rather have unused headroom than hit the ceiling mid-session.
Signs You’re Running Low
The most common signal is lag that gets progressively worse through a session without any obvious cause - no new players joining, no one opening a new chunk of the map. That pattern, especially on an older world, usually points to memory pressure rather than CPU or connection issues.
Other things to watch for: longer-than-usual save times, or lag spikes that coincide with the autosave interval (which you can set as low as 15 minutes in config.cfg).
If you’re seeing these on a fresh world, something else may be going on - it’s worth opening a support ticket to have someone look at the logs before assuming a RAM upgrade will fix it.
WinterNode’s Forest servers start at 4GB - $7.96/month at our flat $1.99/GB rate. If you’re not sure where to start, 4GB is the right call for most groups, and you can scale up if your world grows into something bigger. Everything’s covered by our 48-hour refund policy, so there’s no risk in testing the waters.
Got questions about your setup? Our support team responds to tickets with actual humans, and we’re on Discord if you’d rather ask there.
Frequently Asked Questions
4GB handles a fresh world with up to 8 players in vanilla. Plan for 5-6GB if your world is older, heavily built, or you're running mods.
Yes. Fallen logs, abandoned fires, and built structures all persist in memory and accumulate until the server restarts.
Add roughly 1-2GB on top of your baseline estimate. A modded server with active building on an older world should plan for at least 6GB.
Yes, the default player cap of 8 can be raised through server config. Doing so increases RAM demand - plan for 5-6GB or more depending on how high you push the slot count.