Satisfactory Server Hosting: Complete Setup Guide

Satisfactory supports dedicated servers that let you run a persistent factory world accessible to all players at any time. This guide covers everything from initial installation to ongoing maintenance and performance tuning for larger factories.

Server requirements

Satisfactory dedicated servers are demanding on both CPU and RAM, especially as factories grow:

• CPU: strong single-threaded performance is critical. The game simulation runs primarily on one core. AMD Ryzen 9 or Intel i9 with high clock speeds recommended.
• RAM: 4 GB minimum for a fresh world. 6 to 8 GB recommended for mid-game factories. Late-game megabases with 500+ buildings can use 10 to 12 GB.
• Storage: 5 GB for the server files. Save files grow with factory complexity and can reach 500 MB or more. NVMe storage reduces save and load times significantly.
• Network: 1 Mbps upload per player. Ports 7777 (UDP, game), 15777 (UDP, query), and 15000 (UDP, beacon) must be open.

Installing via SteamCMD

The dedicated server is distributed through SteamCMD with app ID 1690800:

# Install SteamCMD if not present
sudo apt install steamcmd

# Create a directory and install
mkdir -p /opt/satisfactory
steamcmd +force_install_dir /opt/satisfactory \
  +login anonymous \
  +app_update 1690800 validate \
  +quit

The server does not require a Steam account to download or run. Anonymous login works.

First launch and claiming

Start the server with:

cd /opt/satisfactory
./FactoryServer.sh -unattended

On first launch, the server generates its configuration files and waits for a player to claim it. Open Satisfactory, go to Server Manager, add your server IP, and click "Claim Server". Set an admin password during this process. The server is not joinable until claimed.

Configuration files

The main configuration is in FactoryGame/Saved/Config/LinuxServer/GameUserSettings.ini:

[/Script/Engine.GameSession]
MaxPlayers=8

[/Script/FactoryGame.FGServerSubsystem]
mAutoPause=true
mAutoSaveOnDisconnect=true

Key settings:

• MaxPlayers: default is 4. Increase to 8 or 16, but monitor server performance as each player adds CPU load.
• mAutoPause: pauses the game when no players are connected. Set to false if you want the factory to produce while everyone is offline.
• mAutoSaveOnDisconnect: saves when the last player leaves. Keep this enabled.

Save file management

Saves are stored in FactoryGame/Saved/SaveGames/server/. The server creates autosaves at a configurable interval (default: 5 minutes). Back up your saves regularly:

# Daily backup script
SAVE_DIR="/opt/satisfactory/FactoryGame/Saved/SaveGames/server"
BACKUP_DIR="/opt/backups/satisfactory"
mkdir -p "$BACKUP_DIR"
tar czf "$BACKUP_DIR/save-$(date +%Y%m%d-%H%M).tar.gz" "$SAVE_DIR"
find "$BACKUP_DIR" -name "*.tar.gz" -mtime +14 -delete

Performance tuning

Factory complexity is the main performance bottleneck. Tips for keeping the server responsive:

• Limit conveyor belt spaghetti: every belt segment is a separate actor that the server must simulate. Use manifolds instead of balancers where possible.
• Build vertically: compact vertical factories reduce the number of entities in each area, which helps with network streaming to clients.
• Reduce vehicle count: vehicles with autopilot paths are expensive. Prefer trains and conveyor belts for long-distance transport.
• Restart periodically: after 24 to 48 hours of continuous runtime, a restart clears accumulated memory and resets the entity streaming state.

Updating the server

Satisfactory receives regular updates. Keep your server current:

# Stop the server first, then:
steamcmd +force_install_dir /opt/satisfactory \
  +login anonymous \
  +app_update 1690800 validate \
  +quit

All players must run the same game version as the server. After a game update, update the server before players try to reconnect, or they will see a version mismatch error.

Running as a systemd service

Create a service file for automatic restarts and boot-time startup:

[Unit]
Description=Satisfactory Dedicated Server
After=network.target

[Service]
Type=simple
User=satisfactory
WorkingDirectory=/opt/satisfactory
ExecStart=/opt/satisfactory/FactoryServer.sh -unattended
Restart=on-failure
RestartSec=10

[Install]
WantedBy=multi-user.target

How much RAM does a Satisfactory server need?

Start with 4 GB for a new world with 1 to 2 players. Upgrade to 6 to 8 GB once you reach tier 5 or 6 and your factory has hundreds of machines. Late-game megabases with multiple production lines and many vehicles may need 10 to 12 GB.

Can I use mods on a dedicated server?

Yes. Satisfactory Mod Manager (SMM) supports dedicated servers. Install mods in the server directory the same way as on a client. All connected players must have the same mods installed, and the mod versions must match exactly.

Why does the server lag when nobody is building?

The factory simulation continues even when players are idle. Every machine, belt, splitter, and merger runs its production cycle. The more production lines you have, the more CPU time each tick consumes. If you see consistent lag with a large factory, consider disabling auto-pause and restarting the server during off-peak hours.

Can I transfer a single-player save to a dedicated server?

Yes. Copy your save file from the local Satisfactory save directory to the server save directory (FactoryGame/Saved/SaveGames/server/). Load it from the Server Manager in-game. The world, research progress, and all buildings transfer intact.