> For the complete documentation index, see [llms.txt](https://gamelauncher.cloud/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamelauncher.cloud/help/add-ons/cloud-saves.md).

# Cloud Saves

<figure><img src="/files/UaokJJ20EFHkXhdfqUqX" alt=""><figcaption><p>Launcher Desktop - Cloud Saves</p></figcaption></figure>

## What is Cloud Saves?

The **Cloud Saves** add-on automatically backs up and synchronizes your players' save files across their devices. It follows the Steam Auto-Cloud model: you tell the launcher where your game stores its saves, and the launcher handles the rest. No game code changes are required.

* The launcher **downloads** the latest cloud save before your game launches
* The launcher **uploads** changes after your game exits
* Every upload is stored as a **new version**, so the server never overwrites a save

{% hint style="info" %}
**Cloud Saves Addon** is a separate subscription service. **14 DAYS FREE TRIAL AVAILABLE**\
See plans [here](https://app.gamelauncher.cloud/choose-plan)
{% endhint %}

***

## Requirements

| Requirement                                                             | Why                                                                         |
| ----------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Enable [**Authentication System**](/help/add-ons/login-system.md) addon | Saves are stored per player, so each player needs an account                |
| **Players signed in**                                                   | Guest sessions do not sync (there is no player identity to attach saves to) |

{% hint style="warning" %}
Cloud Saves requires the **Authentication System** addon to be enabled on the same launcher. Players who continue as **guests** will play with local saves only.
{% endhint %}

***

## How It Works

### The Sync Lifecycle

1. **Before launch**: when a player presses **Play**, the launcher checks the cloud for a newer save version and downloads it into the configured save folder
2. **While playing**: the launcher does not touch the save folder
3. **After exit**: the launcher scans the configured save paths and, if anything changed, uploads the files as a **new version**
4. **Version history**: the last N versions (you choose 1 to 10) are kept per player, per app, and can be restored at any time

### Conflict Resolution

<figure><img src="/files/KprbKYNgFKmNBeYJWMHn" alt=""><figcaption><p>Launcher Desktop - Cloud Save conflict</p></figcaption></figure>

If both the local save and the cloud save changed since the last sync (for example, the player played offline on another PC), the launcher shows a **conflict dialog** before launching:

* **Local save**: last modified date, machine name, and size
* **Cloud save**: last modified date, machine name, and size

The player picks which one to keep. Nothing is lost either way: the cloud side keeps its version history, and the chosen save is uploaded as a new version.

### Versions and Restore

Every upload creates a new version, and the server **never overwrites** existing data. Players can open the **Cloud Saves panel** in the launcher (right-click the app) and restore any of the stored versions, for example to recover from a corrupted save.

***

## Save Paths

For each app you configure where the saves live, **per platform** (Windows, Linux, macOS). A save path is made of three parts:

1. A **base location token** (a well-known folder on the player's machine)
2. A **relative subpath** inside that base location (for example `MyStudio/MyGame/Saves`)
3. Optional **include/exclude patterns** (glob patterns, one per line)

### Base Location Tokens

| Token            | Windows                             | Linux                       | macOS                       |
| ---------------- | ----------------------------------- | --------------------------- | --------------------------- |
| **AppData**      | `C:\Users\<player>\AppData\Roaming` | `~/.config`                 | `~/.config`                 |
| **LocalAppData** | `C:\Users\<player>\AppData\Local`   | `~/.local/share`            | `~/.local/share`            |
| **Documents**    | `C:\Users\<player>\Documents`       | The user's Documents folder | The user's Documents folder |
| **SavedGames**   | `C:\Users\<player>\Saved Games`     | `~` (home folder)           | `~` (home folder)           |
| **UserProfile**  | `C:\Users\<player>`                 | `~` (home folder)           | `~` (home folder)           |
| **InstallDir**   | The app's install folder            | The app's install folder    | The app's install folder    |

### Example

Base location **AppData** with subpath `MyStudio/MyGame/Saves` resolves to:

* **Windows**: `C:\Users\<player>\AppData\Roaming\MyStudio\MyGame\Saves`
* **Linux**: `/home/<player>/.config/MyStudio/MyGame/Saves`

{% hint style="warning" %}
The relative subpath is **required**: you cannot sync an entire base folder such as `Documents`. Absolute paths and `..` segments are rejected for safety.
{% endhint %}

### Include and Exclude Patterns

Fine-tune which files are synced with glob patterns (one pattern per line). The default include pattern is `**/*` (everything under the save folder).

| Pattern    | Type    | Effect                                   |
| ---------- | ------- | ---------------------------------------- |
| `**/*`     | Include | Sync every file (default)                |
| `**/*.sav` | Include | Sync only `.sav` files, in any subfolder |
| `cache/**` | Exclude | Skip everything under the `cache` folder |
| `*.tmp`    | Exclude | Skip temporary files in the root folder  |

{% hint style="success" %}
Keep the synced set small: exclude caches, logs, screenshots, and anything the game can regenerate. Smaller saves sync faster and use less of your storage pool.
{% endhint %}

***

## Quotas and the Storage Pool

| Tier             | Storage pool | Max per-player quota (per app) |
| ---------------- | ------------ | ------------------------------ |
| **Free Trial**   | 5 GB         | 200 MB                         |
| **Essential**    | 50 GB        | 200 MB                         |
| **Professional** | 250 GB       | 500 MB                         |
| **Studio**       | 1 TB         | 1 GB                           |

Cloud Saves uses two limits that work together:

* **Storage pool**: the total cloud storage for your **entire launcher**, shared across all apps and all players. Its size depends on your tier.
* **Per-player quota**: how much storage a single player can use **per app**. You configure it in MB for each app (default **200 MB**), up to the maximum allowed by your tier.

Stored versions count toward both limits: keeping fewer versions or excluding regenerable files frees up space. You can watch the pool usage meter and per-app usage from the dashboard at any time.

***

## How to Enable

1. Go to your **launcher** in the dashboard and open the **Add-ons** tab
2. Select **Cloud Saves**
3. Accept the **Cloud Saves feature terms**
4. Start the **14 day free trial** or choose a tier (Essential, Professional, or Studio)
5. Make sure the [**Authentication System**](/help/add-ons/login-system.md) addon is enabled on the same launcher
6. Configure each app that should sync saves (see below)

Once an app is configured, players' launchers start syncing automatically: no new launcher build is needed.

***

## Per-App Configuration

Open the app's settings in the dashboard and go to the **Cloud Saves** tab:

| Setting                | Default | Notes                                                                 |
| ---------------------- | ------- | --------------------------------------------------------------------- |
| **Enable Cloud Saves** | Off     | Turns sync on for this app                                            |
| **Per-player quota**   | 200 MB  | In MB, up to your tier's maximum                                      |
| **Versions to keep**   | 5       | Between 1 and 10 versions per player                                  |
| **Save paths**         | (empty) | Base token + subpath + patterns, per platform (Windows, Linux, macOS) |

Configure a save path for every platform your app ships on. A platform without a save path simply does not sync on that platform.

***

## Player Experience

For players, Cloud Saves is invisible when everything goes well:

1. Sign in to the launcher and press **Play**
2. The latest cloud save is downloaded before the game starts
3. Play normally
4. When the game exits, changed save files are uploaded in the background

### The Cloud Saves Panel

Players can right-click an app in the launcher and open **Cloud Saves** to:

* See their **quota usage** and **last sync time**
* Browse the stored **versions** and **restore** any of them
* Trigger a manual **Sync now**
* **Disable Cloud Saves on this machine** (local saves only on that PC; other machines keep syncing)

### Offline Play

Playing offline just works: the game uses the local saves. The next time the player launches online, the launcher reconciles. If the cloud also changed in the meantime, the player resolves it through the conflict dialog.

***

## Dashboard Monitoring

The launcher's **Cloud Saves** addon tab shows:

* **Storage pool usage** meter (how much of your pool is used)
* **Per-app usage** breakdown
* **Monthly transfer stats** (uploads and downloads)

***

## Troubleshooting & FAQ

**What happens when a player plays offline?**\
The game runs with local saves. On the next online launch the launcher syncs normally, and shows the conflict dialog only if both sides changed.

**What happens when a player exceeds their quota?**\
The upload is skipped and the player sees a notice in the Cloud Saves panel. Local saves are never touched. Free up space by raising the per-player quota, upgrading your tier, or keeping fewer versions.

**What happens when the launcher storage pool is full?**\
New uploads pause across the launcher until space is freed or the tier is upgraded. Existing saves and versions stay available for download.

**If I disable the addon, are player saves deleted?**\
No. Syncing stops, but the stored versions remain until you delete them. Re-enabling the addon resumes syncing where it left off.

**Do guest players get Cloud Saves?**\
No. Saves are tied to a player account, so guests play with local saves only.

**What if the save folder does not exist yet?**\
Nothing is uploaded until the game creates its first save files. This is normal for brand-new players.

***

## Need Help?

If you have questions about Cloud Saves or need a larger storage pool, [contact our support team](mailto:support@gamelauncher.cloud).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gamelauncher.cloud/help/add-ons/cloud-saves.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.