Satisfactory Dedicated Server Setup Guide (Update 1.2)

Published on | Updated

SteamCMD install, ports 7777 and 8888, claiming the server, where its settings and ini files live, launch options and a systemd service, checked for 1.2.

A Satisfactory pioneer sitting on a conveyor belt of blue FICSIT containers, with factory chimneys behind

To set up a Satisfactory dedicated server, download the free server files (Steam app 1690800) with SteamCMD onto a 64-bit Windows or Linux machine with at least 8 GB of RAM, open port 7777 over TCP and UDP plus port 8888 over TCP, and start FactoryServer. Then claim the server from the Server Manager in the game's main menu: that is where you set its name and admin password, not in a config file.

Looking for Satisfactory server hosting rather than a machine of your own to keep running? Our Satisfactory server hosting starts at 6 GB of RAM for a new save and has ports 7777 and 8888 set up for you, and our comparison of eight hosts puts the monthly prices side by side.

Everything below is checked for Update 1.2, the current version since 2 June 2026, against the official Satisfactory wiki and Coffee Stain's own patch notes.

Why a Dedicated Server

In a normal multiplayer session the host's PC simulates the factory for everyone and renders the host's own game at the same time, so one machine does two jobs and a big factory slows both down. A dedicated server only runs the simulation, with no graphics card involved, and nobody has to keep their game open for the others to play. With Auto Pause switched off in the server settings, production also carries on while nobody is online.

Hardware Requirements

The wiki lists these minimums, which it calls community recommendations, and says it is "highly recommended that servers exceed the minimum requirements, especially for CPU".

PartMinimum from the wiki
CPU64-bit x86: Intel i5-3570 or AMD Ryzen 5 3600 or better, with a single-thread rating of 2000 or higher on cpubenchmark.net. No ARM or 32-bit support
RAM8 GB. 16 GB "may be recommended for larger saves or to host more than 4 players"
Disk12.4 GB of server files on Windows. 8 GB on Linux, operating system included
Operating systemWindows 10, 11, Server 2016, 2019 or 2022, or a Linux distribution such as Debian or Ubuntu

Single-core speed matters most. The wiki says the server "heavily favors high single-core performance" and quotes a developer from November 2021: "The game loop is still fundamentally single threaded though and all multi threaded work is happening on ticks. So one core will always work harder than others as a result." For a big factory, a CPU with fast cores does more than one with many slow cores.

On a VPS or any other virtual machine, check the CPU type before you install. With the generic kvm64 type in Proxmox the server may start, but it crashes when you create a new game. The wiki's fix is the host CPU type.

How much RAM to plan for depends mostly on the size of the save. This is how we size it, building on the wiki's 8 and 16 GB:

Where your factory isRAM
A new save in the early tiers, up to four players6 to 8 GB
Mid game: trains, drones and several production lines12 GB
Late game with nuclear power, or more than four players16 GB
A megabase across several biomes with a big group24 GB

Watch the server's memory use over a few evenings of normal play and add RAM before the next big expansion, not after the first crash. Our exit code 137 guide shows how to tell whether a crash was the server running out of memory.

Installation

Linux

Install SteamCMD as described on Valve's SteamCMD page, then download the server as a normal user, not as root:

steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous +app_update 1690800 validate +quit

App ID 1690800 is the Satisfactory Dedicated Server. With the anonymous login you need no Steam account for the download.

Windows

.\steamcmd.exe +force_install_dir "C:\SatisfactoryServer" +login anonymous +app_update 1690800 validate +quit

If you own the game on Steam, you can also install Satisfactory Dedicated Server from your Library after switching the filter to Tools. On the Epic Games Store the server is a free add-on that any account can add to its library.

Experimental branch

Add -beta experimental before validate to install the Experimental branch. To go back to the normal release, use -beta public. Leaving the flag out is not always enough, because Steam can remember the branch you were on.

Ports

PortProtocolWhat it carriesLaunch option
7777TCPServer traffic and the HTTPS API-Port=
7777UDPGame traffic and the Lightweight Query API-Port=
8888TCPReliable messaging-ReliablePort=

Port 8888 arrived with Update 1.1, and Coffee Stain's patch notes sum it up in one line: "If hosting a single server, port 8888 TCP must be open by default." Ports 15000 and 15777 from older guides have not been used since 1.0.

Two rules catch people out. Port 7777 cannot be redirected, so the outside and inside numbers on your router must match. Port 8888 can be remapped, but then the server needs the outside number through -ExternalReliablePort=. When the reliable port does not reach the server, players connect and then sit on the loading screen forever.

On Linux with UFW:

sudo ufw allow 7777/tcp
sudo ufw allow 7777/udp
sudo ufw allow 8888/tcp

With firewalld (Fedora, Rocky Linux, AlmaLinux):

sudo firewall-cmd --permanent --add-port=7777/tcp
sudo firewall-cmd --permanent --add-port=7777/udp
sudo firewall-cmd --permanent --add-port=8888/tcp
sudo firewall-cmd --reload

On Windows, in PowerShell as administrator:

New-NetFirewallRule -DisplayName "Satisfactory 7777 UDP" -Direction Inbound -Action Allow -EdgeTraversalPolicy Allow -Protocol UDP -LocalPort 7777
New-NetFirewallRule -DisplayName "Satisfactory 7777 TCP" -Direction Inbound -Action Allow -EdgeTraversalPolicy Allow -Protocol TCP -LocalPort 7777
New-NetFirewallRule -DisplayName "Satisfactory 8888 TCP" -Direction Inbound -Action Allow -EdgeTraversalPolicy Allow -Protocol TCP -LocalPort 8888

At home, forward the same ports on your router to the server's LAN address, and give the server a fixed LAN IP so the forward does not break when DHCP hands it a new one. Behind carrier-grade NAT, which some internet providers use, port forwarding does not work; for hosting from home the wiki names a VPN as the alternative.

Running the Server

On Linux:

cd ~/SatisfactoryDedicatedServer
./FactoryServer.sh

On Windows:

.\FactoryServer.exe -log -unattended

On Linux the server already logs to the terminal and runs without dialogs, so -log and -unattended only matter on Windows. Started by hand, the server stops when you close the terminal and does not come back after a crash, so run it as a service for anything long term (see below).

To check that it is listening, ask its HTTPS API from the server itself:

curl -k https://127.0.0.1:7777

On Windows, run it in Command Prompt rather than PowerShell. A running server answers with this error, which here is the good result:

{"errorCode": "errors.com.epicgames.httpserver.route_handler_not_found", "errorMessage": ""}

Launch options

OptionWhat it does
-Port=7777Game port. If the number is taken, the server tries the next one up
-ReliablePort=8888Reliable messaging port. If it is taken, the server does not start
-ExternalReliablePort=The outside port number when your router maps 8888 to another number
-multihome=192.168.1.4Binds the server to one IP address instead of all of them. Only that address then works for connecting and port forwarding
-DisablePacketRoutingTurns off the packet router, which multihome already does
-DisableSeasonalEventsTurns off seasonal events such as FICSMAS
-ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8Sets an ini value from the command line
-log and -unattendedWindows only: show the log and never wait on a dialog. Both are on by default on Linux

Guides written before 1.0 often pass -ServerQueryPort=15777 and -BeaconPort=15000. Those set the query and beacon ports that 1.0 dropped: the pre-1.0 version of the wiki page still lists them, the current one does not, so leave them out.

Claiming the Server

Before the server can run a game, it has to be claimed:

  1. Start Satisfactory and open the Server Manager from the main menu.
  2. Add the server with its IP address, plus the port if it is not 7777.
  3. Give the server a name and set the admin password. Do this right after the first start, because until then the server has no admin password.
  4. Create a new game, or upload a save as described below.

A join password is off by default. Set one with the Change Password button next to Player Password Protection in the server settings. Players join by adding the server in their own Server Manager; if they use Join Game instead, they get the error "Encryption token missing".

Where the server settings live

The server name, the admin password, the player password and the session to load at startup are not in an ini file. The server stores them in ServerSettings.7777.sav, where 7777 is the server's port, one folder above its saves:

  • Linux: ~/.config/Epic/FactoryGame/Saved/SaveGames/ServerSettings.7777.sav
  • Windows: %LocalAppData%\FactoryGame\Saved\SaveGames\ServerSettings.7777.sav

The wiki's save files page is clear about it: "Using the in-game Server Manager UI is currently the only supported method for modifying this file", and the server's HTTPS API can change the same settings. An earlier version of this guide showed a ServerSettings.ini with lines such as mServerName and mAdminPassword. The current documentation has no such file, so make these changes in the Server Manager.

SettingWhat it does
Server NameThe name shown in the Server Manager
Admin PasswordLimits admin rights such as loading saves, changing options and starting new games
Player Password ProtectionA password players need to join. Off by default
Auto-Load Session NameThe session whose newest save loads when the server starts
Auto PausePauses the game while no players are connected
Auto-Save on Player DisconnectSaves the game when a player leaves
Server Restart IntervalDespite the name, the hour of a daily automatic restart
Autosave IntervalMinutes between autosaves
Network QualityHigher can shorten load times and improve network performance, at the cost of server frame rate

Forgot the admin password? Stop the server and delete ServerSettings.7777.sav. That also resets the server name, the player password, the auto-load session and the server's certificate, and on the next start you can claim the server again.

Configuration Files

The ini files live in the install folder, not in your home folder. With the install folders from the commands above:

  • Linux: ~/SatisfactoryDedicatedServer/FactoryGame/Saved/Config/LinuxServer/
  • Windows: C:\SatisfactoryServer\FactoryGame\Saved\Config\WindowsServer\

The files may only appear after the first clean shutdown, through the quit console command or SIGINT. Edit them only while the server is stopped, because the server writes them on shutdown and would overwrite your change. A game update can also reset them, so check your edits after a patch, and do not make the files read-only.

The settings worth knowing:

More than four players (Game.ini):

[/Script/Engine.GameSession]
MaxPlayers=8

The same works as a launch option: -ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8. The wiki warns that the server is tuned for the default of four, that a higher cap can cost stability and performance, and that 127 players are possible in theory only.

More autosave files (Engine.ini). The server rotates three autosaves by default, from SessionName_autosave_0.sav to SessionName_autosave_2.sav:

[/Script/FactoryGame.FGSaveSession]
mNumRotatingAutosaves=5

Longer timeouts for players with older PCs or slow connections (Engine.ini). The default is 30 seconds, and this sets 60:

[/Script/OnlineSubsystemUtils.IpNetDriver]
InitialConnectTimeout=60.0
ConnectionTimeout=60.0

No crash report uploads from a Linux server, which sends them by default (Engine.ini):

[CrashReportClient]
bImplicitSend=False

Autosave interval. The default is 300 seconds. Change it under Autosave Interval in the Server Manager, in minutes, or with the console command FG.AutosaveInterval 600, in seconds. Saving more often means more frequent short performance drops, because the server slows down while it saves.

Tick rate. Leave it at the default of 30. The wiki is blunt about it: if the hardware cannot reach 30, raising the limit will not help with lag.

Running It as a Service

On Linux, systemd restarts the server after a crash, starts it at boot and, with this unit from the wiki, runs a SteamCMD update before every start. Save it as /etc/systemd/system/satisfactory.service and change the user and paths to yours. /usr/games/steamcmd is where the Debian and Ubuntu package puts SteamCMD.

[Unit]
Description=Satisfactory dedicated server
Wants=network-online.target
After=syslog.target network.target nss-lookup.target network-online.target

[Service]
ExecStartPre=/usr/games/steamcmd +force_install_dir "/home/steam/SatisfactoryDedicatedServer" +login anonymous +app_update 1690800 validate +quit
ExecStart=/home/steam/SatisfactoryDedicatedServer/FactoryServer.sh
User=steam
Group=steam
Restart=on-failure
RestartSec=60
KillSignal=SIGINT
WorkingDirectory=/home/steam/SatisfactoryDedicatedServer

[Install]
WantedBy=multi-user.target
sudo systemctl daemon-reload
sudo systemctl enable satisfactory
sudo systemctl start satisfactory
sudo systemctl status satisfactory

Three things to know about this setup:

  • KillSignal=SIGINT lets the server shut down cleanly. Without it systemd sends SIGTERM, which ends the process at once.
  • The server does not save when it shuts down, not even cleanly. Make sure nobody is online, or save first with server.SaveGame and a save name in the Server Manager's Console tab, and turn on Auto-Save on Player Disconnect.
  • If an older machine needs more than systemd's usual 90 seconds to start the server, the service can end up restarting in a loop. Add TimeoutSec=300 to the [Service] block.

The server logs to the journal and to FactoryGame/Saved/Logs in the install folder, where FactoryGame.log is the current log. On Linux it keeps up to 15 log files.

On Windows, NSSM does the same job: create the service with nssm.exe install SatisfactoryServerService, point its Path at FactoryServer.exe and set Arguments to -unattended.

Save Migration

  1. Find the save. On Windows your saves are in %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\, in a folder named after your Steam or Epic ID; both stores use the same path. On Linux and the Steam Deck the game runs through Proton, so the saves sit in the Proton prefix under steamapps/compatdata/526870/, and the wiki's save files page lists the exact paths.
  2. Upload it. In the Server Manager, open the server's Manage Saves tab, upload the .sav file and load it.
  3. Or copy it over. A Linux server keeps its saves in ~/.config/Epic/FactoryGame/Saved/SaveGames/server, a Windows server in %LocalAppData%\FactoryGame\Saved\SaveGames\server. Stop the server, copy the .sav in, start it again and load the save in the Server Manager.
  4. Make it load after a restart. Set Auto-Load Session Name to the session's name, and the server opens its newest save on every start.

If you play on the Experimental branch, install the server from that branch too, as shown above. Blueprints live next to the saves in SaveGames/blueprints; our blueprint sharing guide covers getting them onto a server.

Updating

Stop the server, run the install command again and start it. With the service above, sudo systemctl restart satisfactory does all three, because the update runs before every start. A server installed through the Steam client gets updates from Steam like a game, though you may have to shut it down first. If SteamCMD stops with state is 0x606 after update job, the server was still running and holding its files: stop it, and reboot if it was already stopped.

Before an update, copy the whole SaveGames/server folder somewhere else, because autosaves rotate and overwrite each other. Update the server on the day your players' games update. The last two patches both fixed the server: v1.2.4.0 on 11 August 2026 stopped admins from losing their access and having to log in again every time, and v1.2.4.1 on 12 October 2026 fixed a dedicated server crash when someone placed a Conveyor Throughput Monitor on a belt.

To shut the server down cleanly, use the HTTPS API's Shutdown function, the quit command in the Server Manager's Console tab, SIGINT or systemctl stop satisfactory on Linux, or Ctrl+C in the server window on Windows. Closing that window with the X kills the process before it has finished writing its files.

Troubleshooting

Start with the basics on Linux: pgrep -f FactoryServer.sh shows whether the server runs, and ss -plnut | grep FactoryServer shows which ports it listens on. After that, these are the usual problems:

  • Players connect, then hang on the loading screen. Port 8888 over TCP does not reach the server. The server can still look fine in the Server Manager, because the game reads its status through the Lightweight Query API on UDP 7777, which does not use 8888.
  • "Encryption token missing". The player used Join Game. Add the server in the Server Manager and join from there.
  • Players time out while joining a big factory. Raise the two timeouts in Engine.ini, as shown above.
  • The server crashes when you create a new game on a VM. The CPU type is kvm64; switch it to host.
  • Two warnings at the end of the startup log. NAT Detection Failed and EOS STA Analytics disabled both concern EOS, which the wiki says the server has no interactions with. It calls them innocuous: the server is up and waiting for players.
  • Friends cannot find the server. Give them your public IP address, plus the port if it is not 7777. The game passes the reliable messaging port on by itself.

Hosting Recommendations

Running the server yourself has no monthly fee, but the machine has to be on whenever anyone wants to play, it needs 8 GB of RAM free for the server alone, and both ports have to reach it. To rent one instead, start with our comparison of Satisfactory server hosting: monthly prices and RAM at eight hosts, ours included, checked on 25 October 2026.

Our Satisfactory hosting comes in five sizes, VAT included: Starter with 6 GB of RAM for €6.00 a month, Small with 8 GB for €8.00, Medium with 12 GB for €11.80, Large with 16 GB for €15.60 and Extreme with 24 GB for €23.20. Both ports are set up for you, and every plan has NVMe storage and DDoS protection.

The plan selector offers nine regions: the Netherlands, Germany, Poland, Canada, USA (California), USA (Virginia), Singapore, India (Mumbai) and Australia (Sydney). Its United Kingdom button orders a server in the Netherlands, because there is no UK node. The CPU depends on the region, and in every region it is shared with the other servers on the node:

  • Netherlands, Germany, Poland, Canada and India: Ryzen 9 3900X-class
  • USA (California and Virginia): Ryzen 9 7950X3D with DDR5
  • Singapore and Australia: Ryzen 9 5950X

In the USA every plan costs €0.10 more per GB of RAM, so Medium is €13.00 there. At checkout one Europe product covers the Netherlands, Germany and Poland, and one USA product covers California and Virginia, so if you want Germany, Poland or Virginia, say so in live chat when you order.

FAQ

Which ports does a Satisfactory dedicated server need?

TCP and UDP 7777, plus TCP 8888 for reliable messaging since Update 1.1. Ports 15000 and 15777 from older guides have not been used since 1.0. Port 7777 must keep the same number outside and inside, so forwarding outside port 7778 to inside port 7777 does not work. Port 8888 can be remapped on your router, as long as you add -ExternalReliablePort= with the outside number to the start command, next to -ReliablePort=.

Can I run mods on a dedicated server?

Yes, if the mod supports it. The modding docs say "most, but not all, mods are compatible with dedicated servers." On a mod's ficsit.app page, look at the Latest Version section: a table with a Server column and a checkmark for your server's platform means the mod works on a dedicated server. Players need the same mods as the server to join. Satisfactory Mod Manager 3.0 or newer installs them on a server over SFTP, and our Satisfactory Mod Manager guide walks through it.

How many players can join a Satisfactory server?

Four by default, which is what the server is tuned for. Raise MaxPlayers in Game.ini for more; the wiki calls 127 a theoretical limit and warns that a higher cap can cost stability and performance.

Can PlayStation or Xbox players join a dedicated server?

Not at the moment. Coffee Stain says dedicated servers are currently only supported on PC, so they are not available during crossplay. Since patch 1.2.5.0 of 4 November 2026, PC players can play with PlayStation 5 and Xbox Series X|S players in a session one of them hosts in the game, without mods and with a free Epic Games account each. Players on Steam and the Epic Games Store can join the same dedicated server, wherever its files came from.

Does the factory keep running when nobody is online?

Only with Auto Pause off. Auto Pause is a setting in the Server Manager that pauses the game while no players are connected.

Can I run two servers on one machine?

Yes. Give each instance its own -Port and -ReliablePort, open those ports, and budget RAM for each server separately. Without those options the game port moves up to the next free number on its own, and the reliable port tries up to 512 ports from 8888.

How do I reset the admin password?

Stop the server and delete ServerSettings.7777.sav from the SaveGames folder, then claim the server again. This also clears the server name and the player password.

Related: Satisfactory server hosting compared, Satisfactory server requirements, Satisfactory Mod Manager on a server, Satisfactory blueprints on a server, game server security

Sources

All opened on 4 November 2026: