{"id":1325,"date":"2022-01-04T12:23:45","date_gmt":"2022-01-04T12:23:45","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=1325"},"modified":"2026-06-15T17:50:46","modified_gmt":"2026-06-15T17:50:46","slug":"how-to-upload-game-save-to-your-satisfactory-server-xgamingserver","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/how-to-upload-game-save-to-your-satisfactory-server-xgamingserver\/","title":{"rendered":"How to Upload game Save to Your Satisfactory Server |XGamingServer"},"content":{"rendered":"\n

You have poured dozens of hours into a single-player Satisfactory factory, and now you want to keep building it with friends on a dedicated server that stays online around the clock. The good news: on Update 1.2 (live patch 1.2.2.2, released June 2, 2026) you do not need to manually move .sav<\/code> files over FTP or SFTP at all. Satisfactory ships with a built-in Server Manager<\/strong> that uploads your save straight from the in-game menu and loads it onto the server for you. This guide walks through that flow end to end, shows you where your local saves live, and covers the one quirk that surprises everyone the first time: Tier 0 onboarding behavior on dedicated servers.<\/p>\n\n\n\n

What you need before you upload<\/h2>\n\n\n\n

Uploading a save is done entirely through the game client, but you must already be the administrator<\/strong> of the target server. If you have not claimed your server yet, do that first. The claim and management flow from the official wiki is short:<\/p>\n\n\n\n

    \n
  1. Launch Satisfactory and open the Server Manager<\/strong> from the main menu.<\/li>\n
  2. Add the server<\/strong> by its IP address or hostname.<\/li>\n
  3. Set a name<\/strong> for the server.<\/li>\n
  4. Set the administrator password<\/strong> to claim it. The first person to set the admin password becomes the admin.<\/li>\n
  5. Pick or create a session, or import an existing save (the focus of this guide).<\/li>\n<\/ol>\n\n\n\n

    If you are still standing up the server itself, our full Satisfactory server configuration guide<\/a> covers SteamCMD install (app ID 1690800<\/code>), ports, and the key INI files. With XGamingServer, claiming is the only step you really need before uploading, because the install and port forwarding are handled for you on managed Satisfactory server hosting<\/a>.<\/p>\n\n\n\n

    Where your local single-player save lives<\/h2>\n\n\n\n

    Before uploading, it helps to know exactly which file you are about to send. On Windows, Satisfactory stores save games here:<\/p>\n\n\n\n

    %LOCALAPPDATA%\\FactoryGame\\Saved\\SaveGames\\\\<\/code><\/pre>\n\n\n\n
    Paste %LOCALAPPDATA%\\FactoryGame\\Saved\\SaveGames\\<\/code> into the Windows Run dialog (Win + R) or the File Explorer address bar and press Enter. Inside you will find one or more folders named after your Steam ID (or common<\/code>), and each holds your .sav<\/code> files. Each .sav<\/code> is one save slot. You do not strictly need to dig these out by hand for the upload itself, because the Server Manager reads your local saves directly. But knowing the path is useful for backups, for confirming you are about to upload the right world, and for copying a save off a friend’s machine if they are the one with the megabase.<\/p>\n\n\n\n
    Step-by-step: upload your save with the Server Manager<\/h2>\n\n\n\n
    This is the core of the whole article. The entire process happens inside the game; there is no manual file transfer. Make sure you are logged in as the server’s admin first.<\/p>\n\n\n\n
      \n
    1. From the main menu, open the Server Manager<\/strong> and select the target server<\/strong>. You must be its administrator to manage saves.<\/li>\n
    2. Click Manage Saves<\/strong>.<\/li>\n
    3. Open the Upload Save<\/strong> tab. You will see your local single-player saves listed here.<\/li>\n
    4. Select the save you want, then click Upload Game<\/strong> (bottom-right). The client transfers the .sav<\/code> file to the server.<\/li>\n
    5. Switch to the Load Save<\/strong> tab. Your freshly uploaded world now appears in the list.<\/li>\n
    6. Select it and click Load Game<\/strong>.<\/li>\n
    7. The server restarts automatically<\/strong> to load the new session. Wait roughly one minute before you try to connect.<\/li>\n<\/ol>\n\n\n\n
      That is it. Once the server comes back up, join it from the server browser as you normally would, and your single-player factory is now a persistent, always-on multiplayer world. The same Manage Saves panel is also where you download a server save back to your machine, so the workflow runs in both directions.<\/p>\n\n\n\n
      The Tier 0 onboarding quirk you must know about<\/h2>\n\n\n\n
      Here is the one behavior that trips up new server admins. If you upload a save that is still in Tier 0 (the Onboarding tutorial)<\/strong>, the game will auto-unlock Tier 0<\/strong> when that save is loaded on the dedicated server. The reason is simple: the onboarding tutorial sequence does not run in dedicated-server mode, so the server cannot have you complete it interactively. Instead, it just marks Tier 0 as done and drops you straight into the game.<\/p>\n\n\n\n
      For most people this is exactly what you want. But if you specifically intended to experience the tutorial as a group, upload the save only after you have already finished onboarding in single player, or accept that the server will skip it. It does not corrupt anything or skip later tiers; it only short-circuits the very first onboarding step.<\/p>\n\n\n\n
      Why the in-game method beats manual file transfer<\/h2>\n\n\n\n
      On many other games you would SFTP a save into a specific directory, match a filename, and edit a config to point at it. Satisfactory’s Server Manager removes all of that friction. It handles the file copy, places the save in the right location, registers it as a loadable session, and triggers the restart. There is no filename to guess and no path to memorize on the server side.<\/p>\n\n\n\n
      Task<\/th>Manual transfer (other games)<\/th>Satisfactory Server Manager<\/th><\/tr><\/thead>
      Move the save file<\/td>SFTP\/FTP upload to a precise folder<\/td>Click Upload Game<\/strong> in-client<\/td><\/tr>
      Make the server use it<\/td>Edit config \/ rename file<\/td>Click Load Game<\/strong> on the Load Save tab<\/td><\/tr>
      Apply the change<\/td>Manually restart the server<\/td>Server restarts automatically<\/td><\/tr>
      Admin requirement<\/td>Panel \/ FTP credentials<\/td>In-game admin password<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      After the upload: a few things worth checking<\/h2>\n\n\n\n
      Once your world is live on the server, take a moment to confirm the basics are tuned for a shared session. A migrated single-player save keeps its game settings, but the server has its own player cap and performance configuration.<\/p>\n\n\n\n