Satisfactory Dedicated Server (1.0 / 1.1): RAM, Ports 7777/8888 & Save Upload

Building an automated megabase with friends in Satisfactory 1.0 or 1.1 becomes cumbersome when the host always has to keep their computer running. To automate production around the clock without tying up your PC, you can launch a Satisfactory dedicated server with automatic pausing and hourly billing.

Memory scales with your factory, not player count (8 GB vs 16 GB)

A Satisfactory dedicated server accommodates 1 to 8 players by default. While the official documentation mentions 8 GB as the bare minimum, the server binary raises an explicit warning whenever available system RAM drops below this threshold.

In practice, memory consumption is driven almost entirely by the scale of your factory rather than the number of engineers online:

• Miles of conveyor belts moving parts continuously across the map.
• Complex rail networks, freight stations, and automated delivery drones.
• Heavy fluid simulation and pipe pressure physics.

For any factory that expands beyond early tiers, we recommend stepping up to 16 GB (€0.12/h in Eco, €0.24/h in Dedicated). For a group playing 4 hours weekly (around 16 hours a month), a 16 GB Eco server costs roughly €1.92 per month — compared to the €8 to €15 monthly contracts of traditional game server hosts. When stopped, the server costs €0.

Ports 7777 / 8888 and claiming the server in the Server Manager

Starting with the 1.0 release, Coffee Stain Studios overhauled dedicated server networking:

• Port 7777 (both UDP and TCP) handles game traffic and player connections.
• Port 8888 (TCP) manages reliable state messages and administrative API calls.

A key mechanic of Satisfactory dedicated servers is that passwords are not configured in a text file before launch. Instead, configuration is handled entirely in-game. The first player to connect using the Server Manager tab claims the server:

1. Provide a server name.
2. Set the Administrator Password, required to manage saves and server settings.
3. Optionally set a Player Password to restrict access to your team.

These preferences are stored in ServerSettings.7777.sav alongside world data and persist cleanly across restarts.

Uploading an existing .sav file and automatic factory pausing

If you started your factory locally, your save files are stored at %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\.

You can import your world in two ways:

• In-game via Server Manager: open Manage Saves → Upload Save and select your local .sav file.
• Via the TickServ console: upload a .zip archive (up to 4 GiB) directly from your dashboard (/app).

By default, the server runs with automatic pausing enabled (AutoPause=True): as soon as the last player logs out, factory machines and power grids freeze. Shutting down the server stops billing completely while keeping your production lines ready for the next session.