How Much RAM Does an ECO Server Need?

ECO: Global Survival is not like most survival games when it comes to server resources. The server runs a full ecological simulation around the clock - pollution levels, climate data, wildlife populations, soil quality - whether anyone is logged in or not. That changes the RAM calculus significantly.

Most hosting guides on this topic say something like “4-8GB, it depends” and leave you to figure out the rest. This guide breaks down the actual factors so you can pick a number with confidence instead of guessing.

World Size Is the Biggest Variable

This is the factor most people underestimate. ECO’s default world is 72x72 tiles, which covers 0.52 km². The simulation tracks ecological state across every tile in that world, so RAM usage scales with the size of the map itself - independent of how many players are on.

Here are the officially supported world sizes and their areas:

World dimensions must be divisible by 4. A developer at Strange Loop Games has stated that 32GB of RAM is recommended for a full 4 km² world with 40 active players - which gives you a useful anchor point for understanding how aggressively RAM scales at the upper end.

For most community servers, the sweet spot is somewhere between 100x100 and 140x140. Larger worlds look appealing, but ECO’s pollution and ecological mechanics are designed around a specific player-to-world-size ratio. A 200x200 map with 10 players often means the ecology never responds meaningfully to what those players do - which defeats part of the point.

Player Count Matters, But Less Than You’d Think

Each additional player adds a relatively small amount of direct RAM overhead - estimates put it around 50MB per active player for their data, inventory, and session state. On a default world, jumping from 5 to 20 players isn’t going to double your RAM usage.

Where player count actually matters is in what players do. More players means more buildings constructed, more crafting chains running, more government laws enacted, and more economic contracts tracked. All of that accumulates in the simulation state over time, and that’s where RAM creep comes from on active servers.

A quiet 20-player server where half the group logs in once a week will be much lighter than an active 10-player server where everyone is online daily building infrastructure and passing legislation.

World Age and Simulation Complexity

This is the variable that catches most server operators off guard, and it doesn’t show up in any hosting FAQ.

ECO’s simulation doesn’t reset between sessions - it accumulates. Every structure built, every law passed, every crafting station placed persists in the world state. Strange Loop Games explicitly calls out “sophistication of play” as a RAM driver, specifically citing law complexity as an example. A server with an elaborate government system, active trade networks, and a heavily developed map will use noticeably more RAM than a fresh world with the same player count and world size.

In practice, this means you should size your RAM for where the server will be in a month or two, not where it is at launch. A world that runs comfortably on 4GB in week one may start showing strain by week six or sooner if the civilization is active and building.

Mods

ECO mods are generally lighter than what you’d see in something like a Minecraft modpack - there’s no JVM overhead, and the mod ecosystem is smaller. That said, mods that expand wildlife, add new biomes, or introduce complex economic systems do add to the simulation load.

A reasonable buffer for a moderate mod list is 1-2GB on top of your base estimate. If you’re running a heavily modded server with expanded ecology or large wildlife populations, treat it like bumping up a world size tier.

ECO mods are installed server-side and automatically downloaded by clients when they join, so there’s no manual distribution headache.

RAM by Scenario

Use this as a starting point. Your actual usage may vary based on how active your players are and how far into the playthrough you are.

A Note on CPU and Storage

RAM gets most of the attention, but ECO is worth understanding on the CPU side too. The server runs its simulation on a single core, so clock speed matters far more than core count. A high-frequency CPU will handle ECO’s tick calculations better than a many-core server with lower per-core speed.

For storage, ECO worlds can grow to 10GB or more per save file once you factor in backups - especially on long-running servers. Make sure your host doesn’t charge for or strictly cap disk space. WinterNode doesn’t meter CPU usage or disk space, so neither will sneak up on you as your world develops.

If you’re looking for an ECO server, WinterNode charges $1.99/GB RAM with no separate fees for CPU, storage, or bandwidth. At that rate, the difference between a 4GB and 6GB plan is $3.98/month - usually an easy call if you’re planning a world larger than the default. Everything’s backed by a 48-hour refund policy if it’s not the right fit.

Got questions about your specific setup? Our support team responds to tickets with actual humans, and we’re on Discord if you’d rather chat in real time.