{"id":1411,"date":"2022-01-20T08:19:38","date_gmt":"2022-01-20T08:19:38","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=1411"},"modified":"2026-06-15T17:50:49","modified_gmt":"2026-06-15T17:50:49","slug":"satisfactory-server-configuration-guide","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/satisfactory-server-configuration-guide\/","title":{"rendered":"Satisfactory Server Configuration Guide"},"content":{"rendered":"\n

Configuring a Satisfactory dedicated server is the difference between a buttery-smooth co-op factory and a stuttering megabase that drops players mid-build. This guide is the most complete, current walkthrough of every setting that matters on the live build \u2014 Update 1.2 (patch 1.2.2.2, released June 2, 2026)<\/strong>, now shipping simultaneously on PC, PlayStation 5 and Xbox Series S\/X. Update 1.2 introduced Game Modes (cost\/power multipliers, world randomization of resource node purities, and world seeds), a rebuilt vehicle path automation system, Fluid Trucks and Fluid Stations as a Tier 5 pipeline alternative, and an improved rain system \u2014 so getting your server config right matters more than ever.<\/p>\n\n\n\n

Everything below uses the current architecture. If you have read older host guides citing legacy UDP ports like 15000 and 15777, those are out of date \u2014 the live build uses the 7777 + 8888<\/strong> scheme documented here. Want to skip the manual setup entirely? Our managed Satisfactory hosting plans<\/a> handle the install, ports and config files for you.<\/p>\n\n\n\n

Installing the server with SteamCMD<\/h2>\n\n\n\n

The Satisfactory Dedicated Server has its own Steam app ID: 1690800<\/strong>. It is a separate download from the game client and installs anonymously through SteamCMD \u2014 no account login or game ownership required on the server box. A typical anonymous install looks like this:<\/p>\n\n\n\n

steamcmd +login anonymous +force_install_dir  +app_update 1690800 validate +quit<\/code><\/pre>\n\n\n\n
The base install is roughly 12.4 GB on Windows<\/strong> and 8 GB on Linux<\/strong>. Run the same command again any time you need to update the server after a new patch \u2014 validate<\/code> repairs any corrupted files at the same time.<\/p>\n\n\n\n
Claiming and managing the server (Server Manager flow)<\/h2>\n\n\n\n
Unlike many dedicated servers, Satisfactory has no admin password baked into a config file at install time. Instead you claim<\/em> a fresh server through the in-game Server Manager. The official sequence is:<\/p>\n\n\n\n
  1. Launch the Satisfactory game client and open the Server Manager<\/strong> from the main menu.<\/li>
  2. Add the server<\/strong> by its IP address (or hostname).<\/li>
  3. Set a name<\/strong> for the server.<\/li>
  4. Set the administrator password<\/strong> \u2014 this is the action that claims the server and binds it to you as admin.<\/li>
  5. Pick or create a session, or import an existing save (covered below).<\/li><\/ol>\n\n\n\n
    Once claimed, everything from save management to player limits is reachable through that same Server Manager panel. If you are running managed hosting, the claim step is the only part you do yourself \u2014 the rest is pre-installed.<\/p>\n\n\n\n
    Ports: the 7777 + 8888 scheme<\/h2>\n\n\n\n
    This is where most outdated guides will trip you up. The current architecture uses just two ports, and one of them carries both protocols. Forward these on your router or firewall:<\/p>\n\n\n\n
    Port<\/th>Protocol<\/th>Purpose<\/th><\/tr><\/thead>
    7777<\/strong><\/td>TCP and<\/em> UDP<\/td>Server traffic \/ HTTPS API (TCP) + game traffic \/ Lightweight Query API (UDP)<\/td><\/tr>
    8888<\/strong><\/td>TCP<\/td>Game traffic, Reliable messaging<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Two rules to remember. First, port redirection is not supported for the standard port<\/strong> \u2014 the external and internal port numbers must match on your router. You cannot map an external 27015 to an internal 7777, for example. Second, ignore any guide telling you to open separate 15777<\/code> query and 15000<\/code> beacon UDP ports; that was the pre-1.0 model and does not reflect the live build. Whether the launch binary still accepts legacy -ServerQueryPort<\/code> or -BeaconPort<\/code> flags is not confirmed for 1.2, so do not rely on them.<\/p>\n\n\n\n
    The config files: Engine.ini and Game.ini<\/h2>\n\n\n\n
    Two INI files hold the settings you will actually tune. Before you touch either of them, internalize the single most important gotcha:<\/p>\n\n\n\n
    Edit INI files only while the server is stopped.<\/strong> Satisfactory rewrites these files on a graceful shutdown, so any change you make to a running server gets overwritten when it next stops. Stop the server, edit, save, then start.<\/p>\n\n\n\n
    Engine.ini \u2014 networking and tick rate<\/h3>\n\n\n\n
    Engine.ini<\/code> controls how often the server simulates and replicates the world. The default tick rate is 30<\/strong>, and this is an upper limit<\/em> \u2014 the server only reaches it if the hardware has headroom. Raising it on a saturated CPU does nothing.<\/p>\n\n\n\n
    [\/Script\/OnlineSubsystemUtils.IpNetDriver]\nNetServerMaxTickRate=30\nLanServerMaxTickRate=30\n\n[\/Script\/SocketSubsystemEpic.EpicNetDriver]\nNetServerMaxTickRate=30\nLanServerMaxTickRate=30\n\n[\/Script\/Engine.Engine]\nNetClientTicksPerSecond=30<\/code><\/pre>\n\n\n\n
    Engine.ini<\/code> also holds the number of rotating autosave slots the server keeps on disk:<\/p>\n\n\n\n
    [\/Script\/FactoryGame.FGSaveSession]\nmNumRotatingAutosaves=XX<\/code><\/pre>\n\n\n\n
    Lowering mNumRotatingAutosaves<\/code> reduces disk churn from save writes \u2014 useful on a large factory where each serialization pass is heavy. Keep at least a couple of slots so you always have a rollback point.<\/p>\n\n\n\n
    Game.ini \u2014 player count<\/h3>\n\n\n\n
    The maximum player count lives in Game.ini<\/code>. The default is 4<\/strong>. The official note is blunt: “Up to 127 players are theoretically possible, but not practically.” Set a realistic number based on your hardware.<\/p>\n\n\n\n
    [\/Script\/Engine.GameSession]\nMaxPlayers=8<\/code><\/pre>\n\n\n\n
    You can also set the same value as a startup argument instead of editing the file:<\/p>\n\n\n\n
    -ini:Game:[\/Script\/Engine.GameSession]:MaxPlayers=8<\/code><\/pre>\n\n\n\n
    Autosave interval<\/h3>\n\n\n\n
    The autosave interval is not an INI key \u2014 it is a console command, FG.AutosaveInterval <\/code>, and the default is 300 seconds (5 minutes)<\/strong>. Raising this value spaces out the periodic world serialization that causes brief autosave hitching on big bases. The Advanced Game Settings toggles (no unlock cost, god mode, flight, and similar cheat-style options) are configured per-session in the Server Manager rather than in an INI file.<\/p>\n\n\n\n
    Hardware: how much RAM and CPU you need<\/h2>\n\n\n\n
    Component<\/th>Minimum<\/th>Recommended<\/th><\/tr><\/thead>
    CPU<\/td>x86-64 Intel i5-3570+ \/ AMD Ryzen 5 3600+, single-thread rating 2000+<\/td>Highest single-thread rating you can get<\/td><\/tr>
    RAM<\/td>8 GB<\/td>16 GB for larger saves or more than 4 players<\/td><\/tr>
    Storage<\/td>12.4 GB (Windows) \/ 8 GB (Linux) base install<\/td>More for save rotations and backups<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    The key insight for Satisfactory hardware is that the simulation is heavily single-thread-bound<\/strong>. A high single-thread CPU rating (the wiki specifies 2000+) matters far more than raw core count. A 16-core server with weak per-core performance will simulate a megabase worse than a 4-core box with strong single-thread speed.<\/p>\n\n\n\n
    Uploading an existing single-player save<\/h2>\n\n\n\n
    You do not transfer files by hand \u2014 the whole flow runs through the in-game Server Manager. As the server’s admin:<\/p>\n\n\n\n
    1. Main menu \u2192 Server Manager<\/strong> \u2192 select your server.<\/li>
    2. Open Manage Saves<\/strong>.<\/li>
    3. Go to the Upload Save<\/strong> tab \u2192 click Upload Game<\/strong> (bottom-right).<\/li>
    4. Switch to the Load Save<\/strong> tab, select the uploaded save, and click Load Game<\/strong>.<\/li>
    5. The server restarts automatically<\/strong> \u2014 wait about a minute before reconnecting.<\/li><\/ol>\n\n\n\n
      Your local saves live in %LOCALAPPDATA%\\FactoryGame\\Saved\\SaveGames\\\\<\/code> as .sav<\/code> files on Windows. One caveat: a Tier 0 (Onboarding) save will have Tier 0 auto-unlocked<\/strong> when loaded on a dedicated server, because the onboarding tutorial does not run in dedicated mode. For the full walkthrough with screenshots, see our dedicated guide on how to upload a game save to your Satisfactory server<\/a>.<\/p>\n\n\n\n
      Fixing lag and stutter<\/h2>\n\n\n\n
      Lag on a Satisfactory server almost always traces back to one of a handful of causes. The dominant one is simply factory size<\/strong> \u2014 high object counts saturate that single CPU thread. Insufficient RAM for a big save, autosave serialization stutter, and tick-rate pressure under load round out the list.<\/p>\n\n\n\n
      Your tuning levers, in order of impact:<\/p>\n\n\n\n