Eco Dedicated Server Requirements: RAM, CPU, Storage and Ports

For Eco’s default 72×72 world, plan for at least 4 GB of RAM, an Intel Core i5 or AMD-equivalent processor, and 1 GB of storage. Those figures are a floor, not a universal specification: larger worlds, more simultaneous players, complex law systems, and mods all require additional headroom. Prioritize high single-core CPU performance and an SSD, especially when the server’s law database is busy. A developer example for an 80-player, 200×200 world called for 16 GB of RAM, the fastest available single-core CPU, and a very fast SSD.

What are the minimum Eco dedicated server requirements?

The Eco Wiki lists the following minimums for its default 72×72 world. The figures were available from the wiki in 2026; the page does not state an original publication year.

Component	Published minimum	What the qualification means
Memory	4 GB RAM	A baseline for the default-size world, not a recommended amount for large communities.
Processor	Intel Core i5 or AMD equivalent	Higher frequency and stronger single-core performance matter more than simply having many cores.
Storage	1 GB	A minimum install footprint; it does not include comfortable space for backups, logs, updates, mods, or a growing world.
Operating system	Windows or Linux	Windows installations also require Microsoft .NET Framework 4.6.2 or newer and the Microsoft Visual C++ Redistributable 2019–2022.

These numbers describe a small or lightly populated server. The documentation explicitly ties requirements to world size, so treating them as a fixed specification for every map will lead to lag, failed updates, or an unstable service.

How much RAM does an Eco server need?

Use 4 GB only when you are running a default-size world with modest activity. Allocate more memory as the map, player count, law complexity, or mod load grows.

Why the 4 GB figure is only a floor

Eco continuously tracks a simulated world, player actions, inventories, laws, and persistence data. A 4 GB allocation leaves little room for an expanding world or for the operating system and other services on the same machine. The minimum is therefore useful for checking whether a small test server can start, not for guaranteeing smooth play under load.

What a large server example looks like

In a February 2021 discussion, Strange Loop Games developer SLG-Dennis advised 16 GB of RAM for an 80-player server with a 200×200 world. The same advice called for the fastest possible single-core CPU and the fastest SSD available, noting that an Intel Core i9-9900K would already struggle in that example. This is a developer sizing example from 2021, not a current minimum or a guarantee that every 80-player configuration will behave identically.

How to budget memory headroom

Start with the world dimensions and the highest number of players you expect online at one time, not the number of accounts in your community.
Leave memory for the operating system, monitoring tools, scheduled backups, and any control panel running beside the server.
Add margin for mods and extensive law systems; neither the minimum page nor the developer example supplies a universal RAM formula for those variables.
Watch actual memory use during peak play before deciding that a larger allocation solved a performance problem. If memory is not near exhaustion, CPU or storage latency is a more likely bottleneck.

What CPU do I need for an Eco dedicated server?

Choose the processor with the best single-core performance and sustained clock speed you can reasonably provide. Eco’s documentation says the process mainly uses one CPU core, so adding several slower cores does not directly address its primary bottleneck.

Frequency versus core count

The Eco Wiki’s guidance is unambiguous: “The highest the frequency the better as the process only uses a single CPU Core.” A modern processor with excellent per-core performance is generally a better fit than an older many-core chip with lower per-core speed. Extra cores can still help the operating system, backups, voice chat, or other services, but they should not be your main purchasing criterion.

What “Core i5 or equivalent” actually tells you

“Core i5” spans many processor generations and performance levels, so the label alone is not a useful guarantee. Treat it as a class of processor for the default world, then compare the candidate chip’s single-thread performance, sustained frequency, cooling, and power limits. The 2021 80-player example demonstrates how quickly the requirement rises: even a high-end 9900K was described as struggling under that particular map and population.

Diagnosing CPU-limited simulation

If players report delayed simulation, slow ticks, or actions resolving late while RAM remains available, inspect per-core utilization rather than total CPU percentage. A machine can show moderate overall utilization while one heavily used core is saturated. Moving the server to a faster single-core processor is more relevant than adding low-frequency cores.

How much storage does an Eco server need?

The formal minimum is 1 GB, but a practical installation should reserve substantially more. The extra capacity covers world growth, logs, configuration files, mods, update staging, and multiple backups.

Why an SSD is recommended

The Eco Wiki specifically recommends an SSD for complex law systems because they generate heavy database access. Solid-state storage reduces access latency for those reads and writes; it is most valuable when the law database is active or the world is busy. An SSD does not compensate for an underpowered CPU, but a slow mechanical disk can add another source of stalls.

Planning capacity instead of copying the minimum

Keep the live world and configuration data on storage with free space available for updates.
Reserve a separate area, drive, or remote destination for backups so a full live disk cannot prevent a backup from completing.
Account for retained logs and mod files, which accumulate even when the world itself changes slowly.
Before an update, copy the world and configuration data. The setup guide identifies the Storage and Configs folders as the data that should not be overwritten during version migration.

No official page in the supplied specifications gives a fixed gigabyte allowance for backups or long-term logs. Choose capacity from your retention policy and the observed growth of your own world rather than treating 1 GB as a safe operating target.

Which operating system and software are supported?

Eco’s requirements page lists Windows and Linux server support. On Windows, install Microsoft .NET Framework 4.6.2 or newer and the Microsoft Visual C++ Redistributable 2019–2022 before launching the server. The cited requirements do not state an equivalent Linux package list, so verify the dependencies for the Linux distribution and server build you select.

Windows checklist

Use a supported 64-bit Windows installation appropriate for your hardware.
Install .NET Framework 4.6.2 or a newer compatible release.
Install the Microsoft Visual C++ Redistributable package covering 2019–2022.
Give the server account permission to read and write its installation, Storage, and Configs folders.

Linux checklist

Linux is listed as supported, but the cited requirements do not name a distribution, kernel version, or package manager command. Confirm those details against the server build’s current documentation before deployment, and test updates and backups under the same account that will run the service.

How do I install an Eco dedicated server?

You have two supported distribution routes: install the server files through Steam’s Library and Tools area, or download the server package from the Eco website. Steam is not required for the server to run after you have obtained the files.

Choose a host. Select a machine whose single-core CPU, RAM, SSD capacity, and operating system match your expected world and player load.
Obtain the files. In Steam, open Library > Tools and install the Eco server tool, or download the server files directly from Eco’s website.
Install prerequisites. On Windows, install .NET Framework 4.6.2 or newer and the Microsoft Visual C++ Redistributable 2019–2022.
Launch once. Start the server to create its initial folders and configuration, then stop it before making major edits or restoring a backup.
Configure the world. Set the world dimensions, player limit, laws, and mod layout appropriate to your hardware. Larger dimensions and more players require more headroom than the 72×72 baseline.
Protect data. Back up the Storage and Configs folders before updates or migrations. Do not overwrite those folders blindly with a fresh server package.
Start and monitor. Run the server continuously, watch per-core CPU use, memory pressure, disk activity, and error logs, then adjust hardware or world settings based on peak conditions.

Which ports does an Eco server use?

The setup guide lists 3000 UDP for the game server and 3001 TCP for the web server. Allow the corresponding protocols through the host firewall and, when the machine is behind a router, forward each port to the server’s private address.

What if the client and server share one computer?

The guide advises using alternate ports when the server and game client run on the same computer to avoid conflicts. Change the server’s configured ports consistently, then use those new values in firewall rules and any router forwarding. A mismatch can look like a failed installation even when the server process is running.

Basic connectivity checks

Confirm that the server is listening on the configured UDP game port and TCP web port.
Check the operating-system firewall before troubleshooting the game itself.
If remote players cannot connect, verify router forwarding and whether the host has a reachable public address.
Test locally first, then test from an external connection so you can distinguish a server configuration error from an Internet-routing issue.

How should I size hardware for my world and player count?

There is no official one-line calculator. Use the documented baseline and scale each resource according to world dimensions, concurrent players, law-system activity, and mods.

Target	Evidence-based starting point	What to validate before launch
Default 72×72, small community	4 GB RAM, Core i5 or AMD equivalent, 1 GB listed storage minimum	Peak CPU per-core load, memory use, and enough extra disk for backups and updates.
Larger map or busier community	More than the default minimum; exact amount is not stated by the official page	World size, simultaneous players, laws, mods, SSD latency, and operating-system overhead.
80 players on a 200×200 world	16 GB RAM, fastest possible single-core CPU, and fastest possible SSD in the February 2021 developer example	This was a specific high-load example, not a universal guarantee or present-day minimum.

For a purchase or rental comparison, evaluate simultaneous players, world dimensions, single-core CPU performance, RAM headroom, SSD capacity and backup space, operating-system support, mod load, and whether the provider handles updates and backups. Provider-specific player limits and resource guarantees are not established by the general Eco documentation and must be checked in the individual plan.

Is self-hosting or renting better for Eco?

Self-hosting gives you control over hardware, storage, ports, backups, and update timing, but the machine must remain running whenever the world is meant to be playable. Eco’s server overview notes that many players rent dedicated servers because the hardware demand makes self-hosting inconvenient.

Choose self-hosting when

You already have a reliable, always-on machine with strong single-core performance and SSD storage.
You can configure firewalls, router forwarding, operating-system updates, and automated backups.
You want direct control over world files, mods, and migration procedures.

Choose rented hosting when

You do not want a home machine running continuously or exposed to inbound connections.
You prefer a provider to supply the hardware, network connectivity, and often the control panel.
You need a support path for restarts, updates, and backups, while still verifying exactly what the plan includes.

Whichever route you choose, compare the actual CPU model or guaranteed single-core performance, assigned RAM, SSD type and capacity, backup policy, supported operating system, and permitted mods. A plan that advertises many virtual cores is not automatically suitable if its per-core performance is weak.

What are the most common sizing and setup mistakes?

Buying for core count alone: Eco’s documented single-core bottleneck makes frequency and per-core performance the priority.
Running the 1 GB disk minimum: The server may install, but logs, backups, updates, and world growth can fill the volume.
Ignoring world dimensions: A 72×72 baseline does not describe a 200×200 world.
Underestimating laws and database activity: Complex law systems are the specific case where the documentation recommends an SSD.
Overwriting data during migration: Back up and preserve Storage and Configs before replacing server files.
Opening the wrong protocol: The game endpoint is UDP 3000 and the web endpoint is TCP 3001 unless you deliberately configure alternatives.
Confusing total CPU use with a healthy server: One saturated core can limit simulation while overall utilization looks moderate.

Frequently Asked Questions

Can an Eco server run on a virtual machine?

The cited requirements do not prohibit virtualization, but a virtual machine must still deliver the required single-core performance, dependable RAM, and low-latency SSD access. Check whether the host shares CPU time aggressively with other tenants, because variable per-core performance can produce inconsistent simulation.

Do I need a graphics card for the dedicated server?

The published server requirements identify RAM, CPU, storage, and operating-system software; they do not specify a dedicated GPU. A headless server installation should therefore be evaluated on those listed resources, while the separate game client has its own graphics requirements.

How often should I back up an Eco world?

The setup guidance requires backups before updates and migrations but does not prescribe an interval. Set a schedule based on how much progress your community can afford to lose, and keep at least one copy outside the live server disk so a disk failure or full volume does not remove both copies.

Can I change the world size after the server is live?

World dimensions are a core sizing variable, and the documentation does not promise that changing them preserves an existing world without consequences. Treat a dimension change as a migration: make a restorable backup, test it separately, and verify CPU, RAM, and storage capacity before exposing the changed world to players.

Eco Dedicated Server Requirements: RAM, CPU and Storage