---
title: "Getting started with your Satisfactory server"
description: "Navigate first boot, assign admin rights using the Administrators list, and configure AutoSave and backups to protect your builds."
url: "https://www.gameserverkings.com/knowledge-base/satisfactory/getting-started-with-your-server/"
category: "Satisfactory"
category_url: "https://www.gameserverkings.com/knowledge-base/satisfactory/"
published: "2026-06-20T19:04:11.632Z"
updated: "2026-08-16T10:55:09.072Z"
source_format: "markdown"
site: "GameServerKings"
---

# Getting started with your Satisfactory server

Satisfactory is a first-person factory builder, and since 1.0 your server keeps a persistent factory world running for the whole team. Co-op play, an always-on world, and the increasingly polished in-game Server Manager make it a great pick for engineering-focused communities.

## First Boot

1. Open [your Satisfactory game server](/games/satisfactory/) in the panel.

2. Click **Start**.

3. First boot downloads the dedicated server (about 12 GB), which takes 12 to 18 minutes.

4. The console shows `LogNet: Game session ID: ...` when the server is fully running.

To connect: in Satisfactory, **Server Manager** > **Add Server** > enter the IP and port from the **Address** at the top left of your panel.

## Initial Setup via In-Game UI

Satisfactory's dedicated server is configured almost entirely through the in-game **Server Manager**, not through config files. After first boot:

1. Connect to the server with your client.

2. The first connecting player becomes the **claimer** and sets the initial admin password.

3. Open **Server Manager** in-game.

4. Add the server, enter your admin password, and the full UI unlocks.

From the in-game UI you can:

- Set server name and description
- Create / load saves
- Configure passwords (admin and client)
- Set auto-save interval and slot count
- View logs
- Manage saves (rename, download, upload, delete)

> [!TIP] The in-game UI is the easiest way to manage the server
> This is the easiest way to manage Satisfactory dedicated servers. The config files (`ServerSettings.ini`, `Engine.ini`) cover only deeper performance tuning.

## Save Management

Satisfactory saves are at `FactoryGame/Saved/SaveGames/server/`. Files are named like `mygame_yyyy-mm-dd-hh-mm-ss.sav`.

To upload a save from your single-player game, follow [the full upload walkthrough](/knowledge-base/satisfactory/upload-your-existing-world/) — in short:

1. Locate your local save at `%LocalAppData%\FactoryGame\Saved\SaveGames\<SteamID>\`.

2. Upload the `.sav` file via SFTP to `FactoryGame/Saved/SaveGames/server/`.

3. In the in-game Server Manager, **Manage Saves** > load the uploaded save.

> [!NOTE] Co-op and dedicated saves are interchangeable
> You can convert a co-op save into a dedicated server save and vice versa without issue.

## Performance Tips

- **Enable mAutoPause**: When no players are connected, the server pauses, freeing CPU
- **Trim auto-saves**: Keep `mAutoSaveNumber` at 5 to 10; old saves are large
- **Network quality**: 2 (High) is usually fine. 3 (Ultra) doubles bandwidth use
- **Restart daily**: Satisfactory has noticeable memory creep over multi-day uptimes

## Wipe / Reset

To start fresh:

1. From the in-game Server Manager, create a new game with a new name.

2. The old save is preserved in `FactoryGame/Saved/SaveGames/server/`; delete it manually if you want to reclaim space.

> [!CAUTION] Deleting all `.sav` files is a clean slate
> Or stop the server, delete all `.sav` files, and restart for a clean slate.

## Backups

The save files are the only critical data, but they grow large (1-3 GB late-game). Use the panel's **Backups** tab daily, with weekly long-term archives. The in-game auto-save provides a second layer for in-session recovery.

## Common Issues

- **Cannot connect after update**: The game updated but the server has an older build. Restart the server; our egg pulls the latest version.
- **Mods break after game update**: Wait for SMR mod authors to push updates, then sync via SMM.
- **Save loading slow**: Large factories take time to deserialize. 1-3 minutes is normal late-game.
- **Server crash on a specific build**: A bug with a specific machine count or arrangement; restore an earlier save and rebuild the problem area differently.
- **High CPU even when paused**: Disable mods one at a time to identify a culprit. Some mods leak CPU even when the server is auto-paused.

## What to Read Next

- [Satisfactory Configuration](/knowledge-base/satisfactory/configuration-overview/)
- [Satisfactory Admin Setup](/knowledge-base/satisfactory/how-to-add-admins-and-commands/)
- [Installing Mods on Satisfactory](/knowledge-base/satisfactory/how-to-install-mods/)
- [How to Upload Your Existing World to Your Satisfactory Server](/knowledge-base/satisfactory/upload-your-existing-world/)

---

Made with 💜 by GameServerKings