How do I make a Satisfactory server? Install Satisfactory Dedicated Server files on a 64-bit Windows or Linux PC (or rent a managed host), start the server process, claim it in Satisfactory’s Server Manager, load a world, and forward the required ports. For internet play, use a stable LAN address and forward TCP/UDP 7777 plus TCP 8888 unless the current server reference for your build specifies different mappings.
This guide covers self-hosting and cloud hosting, hardware, SteamCMD installation, Server Manager setup, save migration, firewall rules, router forwarding, testing, persistence, and recovery. Dedicated servers are a PC feature; do not assume console support without checking the current console documentation.
What is a Satisfactory dedicated server, and who can use one?
A dedicated server is a separate server process that runs the world without requiring the Satisfactory game client to remain open on the same computer. Friends connect to that process while the host machine handles simulation, saves, networking, and logs. Satisfactory reached full release on September 10, 2024, and Coffee Stain’s support documentation confirms dedicated-server support.
The dedicated-server reference documents 64-bit Windows and Linux binaries. The PC listing describes online co-op and cross-platform multiplayer, but dedicated-server support is a PC capability; console players should check current console-specific documentation before planning a dedicated-server setup.
How do I choose between self-hosting and managed hosting?
Self-hosting gives you direct access to files, logs, ports, and backups. A managed host removes most router and operating-system work, but adds recurring fees and provider-specific limits that can make unusual problems harder to diagnose.
| Consideration | Self-hosted Windows/Linux PC | Managed cloud host |
|---|---|---|
| Control | Full control of binaries, launch options, saves, logs, firewall, and updates. | Controlled through the provider’s panel; advanced settings may be hidden. |
| Cost pattern | Mostly a one-time hardware and electricity cost. | Recurring rental charge; hardware is included. |
| Setup effort | You install files, secure the machine, forward ports, and maintain backups. | Usually faster to provision; the provider handles the public network endpoint. |
| Uptime | Depends on your power, broadband, router, and maintenance. | Usually benefits from a data-center connection, subject to the provider’s terms. |
| Port forwarding | Your responsibility unless everyone connects over a VPN. | Normally handled by the provider, although custom ports may still be restricted. |
| Save access | Direct access to the save directory and backup files. | Depends on the panel’s export and file-management features. |
| Troubleshooting | You can inspect every process and log. | Support can help, but provider-specific abstractions can obscure the cause. |
Choose self-hosting when you already have a spare 64-bit PC, want complete save control, or prefer a one-time hardware purchase. Choose managed hosting when you cannot configure a router, need a data-center location, or want the server to stay online while your home PC is off. Confirm the provider’s supported game branch, save access, cancellation terms, and data-center region before paying.
What hardware and network does a Satisfactory server need?
The dedicated server needs a 64-bit x86-64 CPU with good single-core performance, memory for the simulation, storage for binaries and saves, and a reliable broadband connection. These are server requirements, not the graphics requirements of the game client.
| Resource | Dedicated-server guidance | Important qualification |
|---|---|---|
| CPU | 64-bit x86-64 processor; strong single-core performance is useful. | Load rises with world complexity and player count. |
| Memory | About 8 GB is a baseline; 16 GB is advisable for larger saves or more than four players. | Leave headroom for the operating system, logs, and backups. |
| Storage | About 12.4 GB for Windows server files and about 8 GB for Linux files. | Figures exclude saves, logs, backups, updates, and temporary files. |
| Operating system | Supported 64-bit Windows or Linux distribution. | Keep the server and client on compatible branches. |
| Network | Broadband internet for remote players and a stable LAN address. | Home internet may use carrier-grade NAT, which can block inbound connections. |
The Steam client listing separately specifies a 64-bit operating system, 8 GB RAM minimum, 20 GB storage, and internet for multiplayer. It also lists graphics hardware for the playable client; do not treat those GPU requirements as dedicated-server requirements unless the same PC will also run the game.
Host-preparation checklist
- Use a wired connection where possible; a Gigabit Ethernet cable reduces local wireless variability.
- Reserve a DHCP address for the server in the router, or configure a static LAN address correctly.
- Leave additional SSD capacity for rotating saves, logs, crash reports, and future server updates.
- Keep the operating system, firewall, and server account maintained. Run the service under a non-administrator account where practical.
- Record the server’s LAN address, public address, selected branch, and external port before inviting friends.
How do I install the Satisfactory dedicated-server files?
The documented SteamCMD installation uses app ID 1690800. SteamCMD can install the server without installing the playable client.
Linux installation
- Install SteamCMD using your distribution’s supported package or the official SteamCMD procedure.
- Create a directory owned by the account that will run the server.
- Run:
steamcmd +force_install_dir ~/SatisfactoryDedicatedServer +login anonymous +app_update 1690800 validate +quitThe validate option checks the downloaded files. Repeat the command after an update when you need to repair or verify the installation.
Windows installation
- Download and unpack SteamCMD to a location such as
C:steamcmd. - Open PowerShell or Command Prompt and run the equivalent command with an absolute install path:
.steamcmd.exe +force_install_dir "C:Game ServersSatisfactory Server" +login anonymous +app_update 1690800 validate +quitKeep the server directory separate from the SteamCMD directory so updates and backups are easier to manage.
Alternative installation methods
You can install the dedicated server from Steam’s Tools category. Epic users can use the Epic Dedicated Server Tool add-on. These methods still require the same branch discipline, firewall configuration, save handling, and Server Manager claim.
What if I use the Experimental branch?
Treat Experimental as a separate beta branch. Install the matching server branch and keep every player’s client on that branch; a client and server on different branches or builds commonly fail to connect or load a save. Back up the world before changing branches, and do not move a production save to a beta branch without a rollback copy.
How do I start the Satisfactory server process?
Launch the executable from the installed server directory. On Windows, the documented command is:
FactoryServer.exe -log -unattendedOn Linux, run:
./FactoryServer.shThe terminal may stop printing frequent messages while the process is idle and waiting for a client; that does not by itself indicate a crash. A manual launch ends when its terminal closes, so use a service manager, supported wrapper, or persistent session for a server that must survive logout or reboot.
How do I claim and configure the server in Server Manager?
Server Manager is where you make the running process usable by players. The server must be claimed before it can start a game.
- Open Satisfactory and enter Server Manager.
- Add the server using its address and port. On a local network, start with the server’s LAN address.
- Set a server name that your group will recognize.
- Create an administrator password and store it in a password manager. Do not reuse a personal account password.
- Claim the server when prompted.
- Create a new world or import an existing save.
- Choose whether to require a player password. Administrator access and player access are separate decisions.
- Save the configuration and start the game session.
Useful session settings
- Auto-load: loads the selected world when the server starts, reducing manual recovery after a reboot.
- Autosave on disconnect: writes a save when the last player leaves, which can preserve recent progress.
- Pause when empty: pauses simulation while nobody is connected, reducing unnecessary progression and resource use.
- Restart interval: schedules restarts to clear accumulated issues; choose a quiet time for your group.
- Network quality: select the setting appropriate to your connection and player group, then change it only after testing.
How do I import and back up a Satisfactory save?
Back up before a migration, branch change, binary update, or major configuration change. Stop the server cleanly first so the save is not being written while you copy it.
Coffee Stain’s support FAQ places standard Windows client saves under %LOCALAPPDATA%FactoryGameSavedSaveGames and recommends copying them elsewhere regularly, especially when cloud saves are involved. A dedicated server’s save directory varies with platform and service account, so use the current dedicated-server reference for that server’s exact path rather than assuming the client path.
- Stop the server through its management interface or shut down the process cleanly.
- Copy the complete save directory to storage that is not the live server disk.
- Label the backup with the world name, date, game branch, and server version.
- Keep more than one historical copy; a newly copied corrupt save should not replace the last known-good copy.
- Import a copy into the server manager, test it, and retain the original backup until players confirm that the world is intact.
What ports does a Satisfactory server need?
The current dedicated-server reference lists standard port 7777 on both TCP and UDP, plus reliable-messaging port 8888 on TCP. Forward the external port to the same internal port on the server’s stable LAN address unless your build’s documentation says you have selected a different mapping.
| Purpose | Protocol | Default port |
|---|---|---|
| Dedicated-server standard traffic | TCP and UDP | 7777 |
| Reliable messaging | TCP | 8888 |
Port remapping behavior differs between the standard and reliable ports. Do not copy a rule from an older guide without checking the current reference. Allow the same ports through the host operating system’s firewall and any security software.
General multiplayer ports are not the dedicated-server table
Coffee Stain’s general multiplayer/NAT troubleshooting guidance also lists TCP 5222 and 6666, and UDP 5222, 6666, and 7777–7827. Treat those as general game connectivity guidance; do not silently substitute them for the dedicated-server defaults above. If troubleshooting requires those services, add only the rules relevant to the documented symptom and your current build.
How do I host Satisfactory for friends over the internet?
For internet play, friends need a reachable public address, while the router must know which local machine receives the traffic.
- Give the server PC a reserved LAN address in the router.
- Create port-forwarding rules for TCP/UDP 7777 and TCP 8888 to that address.
- Allow the same ports in Windows Firewall, Linux firewall tools, and security software.
- Check whether your ISP uses carrier-grade NAT. If it does, ordinary forwarding may not work; ask the ISP for a reachable address or use a properly configured VPN solution.
- Have a friend test from a different internet connection, such as cellular data. Testing only from inside your LAN can produce misleading results because some routers do not support hairpin NAT.
- Give friends the public IP address and standard port when it is not 7777. The game communicates the reliable port as part of the connection process.
| Play method | Reachability | Administration and risk |
|---|---|---|
| Same LAN | Usually simplest; connect to the private LAN address. | Limited to the home network and still depends on local firewall rules. |
| Internet with forwarding | Friends connect through the public address. | Requires router rules, firewall exposure, stable addressing, and CGNAT checks. |
| VPN overlay | Players connect through the virtual network. | Can avoid inbound forwarding but adds software, accounts, and another source of latency. |
| Managed host | Provider supplies a public endpoint. | Less local networking work, but recurring cost and provider-specific controls. |
How do I test the server safely?
- Connect from the host PC or another device on the same LAN.
- Confirm the server was claimed and a world is loaded in Server Manager.
- Check that the process is running and listening on the expected ports.
- Verify host firewall and antivirus allow rules.
- Check that the router forwards to the server’s current LAN address, not an old DHCP address.
- Test from an external network.
- Confirm every client and the server use the same branch and build.
- Invite additional players only after the single-player connection succeeds.
Testing in this order separates game configuration from public-network problems. If LAN access works but an outside connection fails, focus on firewall rules, forwarding, CGNAT, and the public address rather than reinstalling the game.
How do I keep the server running after reboot?
A service manager starts the server after boot, restarts it after a failure, and keeps logs outside a disposable terminal. On Linux, a systemd unit can run SteamCMD during a controlled restart, launch the server as a non-root user, and use Restart=on-failure. Adapt paths, usernames, and permissions to your installation:
[Unit]
Description=Satisfactory Dedicated Server
After=network-online.target
Wants=network-online.target
[Service]
User=satisfactory
WorkingDirectory=/home/satisfactory/SatisfactoryDedicatedServer
ExecStartPre=/usr/games/steamcmd +force_install_dir /home/satisfactory/SatisfactoryDedicatedServer +login anonymous +app_update 1690800 validate +quit
ExecStart=/home/satisfactory/SatisfactoryDedicatedServer/FactoryServer.sh
Restart=on-failure
RestartSec=10
[Install]
WantedBy=multi-user.targetTest the unit manually before enabling it at boot. Ensure the service account owns the installation and save directories, and retain logs and backups on storage that survives a failed process or update. Windows hosts can use an equivalent supported service wrapper or scheduled startup task, provided it launches the server with the intended working directory and account.
What should I check when friends cannot connect?
- Process and claim: confirm the server is running, claimed, and has a loaded world.
- Branch and build: compare the server and every player’s branch, including Experimental versus the regular branch.
- Firewall: verify TCP/UDP 7777 and TCP 8888 are allowed on the host and not blocked by antivirus.
- Forwarding: confirm the router points to the server’s current LAN address and uses the correct protocol.
- CGNAT: compare the router’s reported WAN address with the public address. A mismatch can indicate carrier-grade NAT.
- External test: test from outside the home network; internal tests cannot prove public reachability.
- Fresh save: create a temporary world. If it works while the original does not, investigate save corruption or migration issues.
- Logs and crashes: read rotated server logs and crash reports, preserving copies before an update overwrites them.
- Client-side checks: update drivers and verify game files when the failure is limited to one player’s client, following Coffee Stain’s support checklist.
Should I create a new world or import an existing save?
| Choice | Best for | Trade-offs |
|---|---|---|
| New world | Fastest connectivity test and a clean start. | Does not preserve an established factory or progression. |
| Imported save | Continuing a solo or previous co-op factory. | Requires a verified backup and carries migration or corruption risk. |
For a first deployment, test the network with a new temporary world, then import a copy of the real save after the connection and permissions are proven. Keep the original save untouched until everyone confirms the imported world loads correctly.
What maintenance does a reliable server need?
- Back up saves before every branch change, migration, and server update.
- Record the running branch and build so clients can match it after an update.
- Review disk space for saves, logs, crash reports, and downloaded update files.
- Apply operating-system and server updates during an agreed maintenance window.
- Check that the router reservation still points to the correct machine.
- Periodically test a restore from backup rather than assuming copies are usable.
- Review service logs after automatic restarts and investigate repeated failures.
Frequently Asked Questions
Can console players join a Satisfactory dedicated server?
Dedicated-server documentation covers PC Windows and Linux binaries. The PC listing mentions cross-platform multiplayer, but console dedicated-server availability is not established here, so check the current console support documentation before promising console access.
Can I change the default server ports?
Port remapping is possible only within the rules supported by the current server build, and the standard and reliable ports do not remap identically. Change the configuration and router rules together, then verify the listening ports from an external network.
Can I move a save from a hosted service to my own PC?
That depends on whether the host lets you export the complete save and whether the destination server uses a compatible branch. Stop the hosted instance, export a backup, test it on a separate local world, and keep the hosted copy until the migration is confirmed.
How can I tell whether a failed connection is a save problem or a network problem?
Load a newly created temporary world while leaving the original backup untouched. If the fresh world is reachable, compare logs and try an earlier backup of the original; if neither world is reachable from outside the LAN, return to firewall, forwarding, and CGNAT checks.