A Factorio server needs enough RAM to load the save and mods, but an established factory is often limited by how quickly the CPU can process the simulation.
Use the ranges below as starting points, then test the actual save. A new empty map cannot show how a mature factory will perform.
Factorio Server RAM Starting Points
Small Private Factory
2–4GB
A few players, a fresh save and limited mods.
Growing or Modded Save
4–8GB
More explored map, trains, logistics and a deliberate mod set.
Large Established Factory
8GB+
A large save, overhaul mods or several active factory areas.
These are planning ranges, not fixed limits. CPU performance may force an upgrade before RAM is full.
CPU Is Usually the First Limit
The server processes one shared simulation for every connected player. Inserters, belts, bots, trains, machines, pollution, enemies and mod scripts all add work. As the factory becomes more complex, each update can take longer.
More RAM helps only when memory is actually running short. When RAM remains available but the simulation slows down, look at CPU demand and the factory itself.
RAM Loads the Save and Mods
- The current save and explored map data
- Entities, trains, logistics and active surfaces
- Installed mods and their runtime data
- Connected players and network state
- Autosaves and temporary work during updates
Leave enough memory for Linux and monitoring as well as Factorio. Do not allocate the full hosting-plan total to the game process.
A Larger Factory Needs More CPU Time
New Factory
Few entities, limited exploration and simple production. A modest VPS is usually a sensible starting point.
Growing Rail and Logistics Network
More trains, bots, production blocks and active areas increase simulation work.
Large Megabase
CPU time becomes the main question. Free RAM does not guarantee that the server can maintain smooth updates.
Mods Can Change the Requirement
A small interface mod may have little effect. An overhaul pack can add recipes, surfaces, machines and scripts throughout the game. Test the exact save with the exact mod set you intend to run.
A new map is not a useful benchmark for a long-running factory. Upload a recent copy of the live save and check it during normal activity.
Player Activity Changes the Workload
There is no fixed amount of RAM per player. Several people building in separate areas can keep more of the map active and expand it faster than a larger group working together in one location.
Plan Storage for Saves and Backups
The live save is only part of the storage requirement. Allow space for several autosaves, manual backups, mods, logs and temporary update files. Keep at least one backup away from the live VPS or VDS.
Choose VPS or VDS
A Factorio VPS is a practical starting point for a new private server. Choose VDS when the real save is repeatedly CPU-limited and predictable dedicated vCPU resources matter more than simply adding memory.
Test the Real Save Before Upgrading
- Load a recent save with the intended mods.
- Connect the normal number of players.
- Visit busy production and train areas.
- Check CPU load, memory use and save time.
- Repeat the test during an autosave.
- Upgrade only after identifying the actual limit.
Those steps are kept in the separate setup guide so this page stays focused on CPU, RAM and storage.
Open the Factorio setup section →