Improve Satisfactory Server Performance

This guide shows you how to optimize your Satisfactory server performance – for fewer lags, more stable connections and a better gaming experience even with large factories.

Optimize hardware

• CPU: Satisfactory benefits massively from high single-core performance. A modern processor with high clock speed is more important than many cores
• RAM: 8 GB minimum, 16 GB for larger factories. The server gets hungrier as the factory grows and more players join
• Storage: Use NVMe SSD instead of HDD – autosaves are written much faster

Optimize Engine.ini

You'll find the file at FactoryGame/Saved/Config/WindowsServer/Engine.ini. Add or adjust the following entries:

[/Script/OnlineSubsystemUtils.IpNetDriver]
MaxClientRate=1048576
MaxInternetClientRate=1048576
NetServerMaxTickRate=30
LanServerMaxTickRate=30

[/Script/Engine.Player]
ConfiguredInternetSpeed=1048576
ConfiguredLanSpeed=1048576

[/Script/SocketSubsystemEpic.EpicNetDriver]
MaxSendBufferSize=16777216
MaxReceiveBufferSize=16777216
NetConnectionClassName="Script/Engine.NetConnection"

• MaxClientRate: Increases bandwidth per player to 1 MB/s
• NetServerMaxTickRate: 30 instead of default 60 – saves CPU with barely noticeable difference
• Increase buffers: Prevents connection drops with large amounts of data

Adjust GameUserSettings.ini

You'll find the file at FactoryGame/Saved/Config/WindowsServer/GameUserSettings.ini:

[/Script/FactoryGame.FGGameUserSettings]
mIntValues=(("FG.NetworkQuality", 3))
mFloatValues=(("FG.AutosaveInterval", 900.0))

• NetworkQuality: 0=Low, 1=Medium, 3=Ultra. Higher values put more load on the server
• AutosaveInterval: In seconds. 900 = every 15 minutes. Saving too frequently causes lags

Increase autosave interval

The autosave briefly freezes the server. The larger the factory, the longer the freeze. Set the interval to 15-30 minutes to reduce the number of interruptions.

Choose spawn area wisely

• The map is one large world – the spawn area only determines the starting point
• Northern Forest is popular for its resources, but Grasslands loads faster
• The more players explore different areas, the more of the map the server has to load

Limit player foundations

• Large foundation platforms are one of the biggest performance killers
• Build vertically rather than horizontally
• Distribute factories across different areas of the map
• Hiding conveyor belts in enclosed rooms or under the floor – the server still has to calculate everything

Reduce vehicles and trains

• Every vehicle constantly calculates its position and route
• Trains are more efficient than many tractors/trucks
• Shut down or dismantle unused vehicles

Restart server regularly

• Daily restart prevents memory leaks
• Use Windows Task Scheduler or cronjob for automatic restarts
• Always stop the server with quit, don't close the window

Quick checklist

1. Choose CPU with strong single-core performance, use NVMe SSD
2. Extend Engine.ini with optimized network values
3. Increase autosave interval to 15-30 minutes
4. Set NetworkQuality to 3 if bandwidth is sufficient
5. Avoid large foundations, limit vehicles
6. Restart server daily