Satisfactory 1.0 Dedicated Server: What You Need to Know

Satisfactory left early access with its 1.0 release, and the dedicated server component matured along with it. If you ran a server during early access, several things have changed. If you are starting fresh, this guide covers everything you need to know about hosting Satisfactory 1.0 for your factory-building group.

What changed in 1.0

The 1.0 release brought stability improvements to the dedicated server, better memory management for large factories, and refined the web-based server management API. The server now handles large save files more gracefully, which matters because late-game Satisfactory saves can exceed 100 MB. The update also introduced the final tier of research and production chains, which increase CPU load as factories grow.

System requirements

Satisfactory's dedicated server is demanding compared to most game servers:

• CPU: Strong single-thread performance is essential. The factory simulation runs on a single core for physics and belt calculations. An AMD Ryzen 9 7950X or similar is ideal.
• RAM: Minimum 6 GB for a small factory with 2 to 3 players. A mid-game factory with 4 players uses 8 to 10 GB. Late-game mega-factories can push past 12 GB.
• Storage: NVMe recommended. Save files grow large, and the server autosaves frequently. Slow storage causes noticeable stuttering during saves.
• Network: Moderate bandwidth needs. The game syncs factory state rather than streaming world data, so bandwidth stays reasonable even with large builds.

Installation and setup

The Satisfactory dedicated server is distributed through SteamCMD using App ID 1690800:

steamcmd +login anonymous \
  +app_update 1690800 validate \
  +quit

After installation, the server is configured through a web interface. On first start, it binds to port 7777 (game traffic, UDP) and port 15000 (query, UDP). The server API runs on port 15777 by default.

Open all three ports in your firewall. The web management panel is accessible from the game itself: connect to the server, and the first player to join can claim admin access and set the server name, password, and other options.

Server management

Satisfactory uses a different management approach than most game servers. Instead of editing config files directly, most settings are controlled through the in-game server manager or the REST API:

• Creating a new game: Done through the in-game menu after connecting as admin. You choose the starting location and session name.
• Loading a save: Upload save files through the in-game server manager or place them in the saves directory and load from the menu.
• Autosave interval: Configurable through the server settings. Default is every 5 minutes. For large factories, consider extending this to 10 or 15 minutes to reduce stutter from frequent save operations.

Performance tips for large factories

• Use manifold designs: Manifold (overflow) belt layouts are more efficient for the server to simulate than load-balanced designs with many splitters and mergers.
• Limit vehicle routes: Each active vehicle is a moving entity the server must simulate. Trains on fixed paths are cheaper to compute than trucks on autopilot routes.
• Clean up old builds: Deconstructing unused factory sections frees simulation resources. The server calculates every machine, belt, and pipe segment each tick.
• Monitor save file size: A save file over 200 MB indicates a very large factory. At this scale, consider upgrading your server's RAM and storage speed.

Multiplayer considerations

Satisfactory supports up to 4 players in a session. The dedicated server allows more than 4 to connect, but performance degrades beyond that. The host does not need to be online for others to play, which is the main advantage over peer-to-peer hosting.

All players need to own Satisfactory on Steam or Epic. There is no cross-store multiplayer: all players in a session must use the same platform.