Documentation Steamworks
Steam Cloud
In Brief
Steam Cloud automatically stores files from your game on Steam's servers so your players can log into Steam and access their saved games from any computer.
Level of integration
Configuration of file paths required on Steamworks website. Optionally, some API calls required from within game code to Steamworks for upload, download, enumerate, and delete.

Présentation de Steam Cloud

The Steam Cloud provides an easy and transparent remote file storage system for your game. Files specified in the Auto-Cloud configuration or written to disk (created, modified, deleted, etc.) using the Cloud API will automatically be replicated to the Steam servers after the game exits.

If the user changes computers, the files are automatically downloaded to the new computer prior to the game launching. The game can then access the files by reading them through the Cloud API or reading them directly from disk as usual. Avoid machine specific configurations such as video settings.

The Steam Client does the work of ensuring that the files are kept synchronized across all computers the user may be accessing.

Users can globally disable Cloud synchronization in the Steam Settings under Cloud by unchecking "Enable Steam Cloud synchronization for applications which support it."

Users can also disable the Cloud synchronization on a per game basis in each games properties.


Notes and Best Practices

It is important to remember that Steam will synchronize the user's Steam Cloud files for your game before and after every session. Any matching files which change during the session will be uploaded to Cloud storage immediately afterward. If your game writes very large files, or many small files, to Steam Cloud, then this may cause a noticeable impact on the user's internet bandwidth and also delay their ability to shut down Steam or re-launch the game.

As a general rule, smaller files will work better. If the saved state for a given user can be split up into different categories - things which may change frequently, and things which may not change often - then we recommend using separate files for those categories. That way, the un-changed state will not be re-uploaded after every session.

File Size Limits

The absolute limits on file sizes for Steam Cloud may change over time. Here are some current limits and thresholds:

100MBMaximum size for a call to ISteamRemoteStorage::FileWrite or ISteamRemoteStorage:;FileWriteStreamWriteChunk
256MBMay result in a non-optimal storage endpoint choice for the user's location, negatively impacting upload/download performance

Initial Setup

To set up Steam Cloud you must set the Byte quota per user and Number of files allowed per user options on the Steam Cloud Settings page in the Steamworks App Admin panel.

This quota is enforced on each Cloud-enabled game, on a per-user-per-game basis. It's recommended to set the values to reasonable amounts for your game title.

REMARQUE : Don't forget to click Save at the bottom of the page, and Publish your updated settings. Once published the cloud icon will be visible in the Steam client for anyone that owns your game.

If your game has already been released to the public then you can check the box labeled Enable cloud support for developers only. If developers-only mode is enabled then only the steam accounts which own a "Developer Comp" license for your title will see the cloud icon and will be able to use the Steam Cloud. This is useful to safely test Steam Cloud integration without breaking the public user experience. This has no effect on unreleased games since no one owns the game yet, they won't be able to see or access any cloud storage for the specific app ID.

You are able to share Cloud storage space between two app IDs by filling out the Shared cloud APP ID field. This is most commonly used to share saved games between a demo and a full game. A value of 0 disables this feature.

Steam Cloud API and Steam Auto-Cloud

Steam provides two different methods of utilizing the Steam Cloud, read up on how the two methods differ, and determine which would be the best for your application.

First up is the Steam Cloud API.
The Cloud API provides a series of functions which allows you to directly integrate the Steam Cloud into your game. The Cloud API isolates individual Steam users files from each other and provides a greater level of control over the Steam Cloud.

The Steam Cloud API is exposed via the ISteamRemoteStorage API interface, and you can find example usage in the Exemple d'application utilisant l'API Steamworks (Spacewar) project.

The second is Steam Auto-Cloud.
Steam Auto-Cloud was designed for legacy games where you can not easily integrate the Steam Cloud API. It provides a quick and easy way to get started but lacks the power and flexibility that is available with the Steam Cloud API.

It is generally recommended that you use the Cloud API if possible as it allows for deeper integration and customization, and it enables you to best provide the high quality experience that Steam users have come to expect from the Steam Cloud.

Steam Auto-Cloud

Steam Auto-Cloud is an alternative to the Steam Cloud API that allows apps to use Steam Cloud without writing code or modifying the game in any way. It only requires that you specify the file groups which you want persisted to the Cloud. Steam will automatically sync the groups of files when the application launches and exits. Avoid machine specific configurations such as video quality.


After completing the Initial Setup the Steam Auto-Cloud configuration section will unlock on the Steam Cloud Settings page.

Root Paths describe groups of files which will be persisted to the Steam Cloud. Each Root Path can be as specific as a single file or as wide as all files under a given subfolder. Use a new path for each group of files to sync.

A Root Path is composed of 5 parts:
  1. Racine

    Voici une liste prédéterminée de chemins où se trouvent généralement les sauvegardes de jeu.
    RacineSystèmes d'exploitation pris en chargeChemin correspondant
    Répertoire d’installation de l’applicationTous[Répertoire d'installation de Steam]\SteamApps\common\[dossier du jeu]\
    SteamCloudDocumentsTousChemin spécifique à la plateforme, par ex. sur Linux : ~/.SteamCloud/[nom d'utilisateur]/[dossier du jeu]/
    WinSavedGamesWindows%USERPROFILE%\Saved Games\
    MacAppSupportmacOS~/Library/Application Support/
  2. Sous-répertoire

    Chemin du sous-répertoire des fichiers du Cloud relatif à la racine. Utilisez « . » s'il n'existe pas de sous-dossier.

    Valeurs de chemin spécifiques à l'Auto-Cloud
    L'Auto-Cloud permet l’utilisation d’identifiants d’utilisateur Steam uniques dans le chemin d’accès du sous-répertoire. Ceci vous permet de stocker des fichiers de sauvegarde pour chaque utilisateur Steam séparément sur l'ordinateur. Vous pouvez utiliser ISteamUser::GetSteamID dans votre jeu pour obtenir le SteamID ou l'ID de compte de l'utilisateur actuel qui sera la cible de l'enregistrement et de la lecture.
    • {64BitSteamID} : utilisez cette variable dans le chemin de Steam pour insérer le SteamID 64 bits de l'utilisateur. Un ID Steam 64 bits ressemble à ceci : 76561198027391269.
    • {Steam3AccountID} : utilisez cette variable dans le chemin de Steam pour insérer l'ID de compte Steam 3 de l'utilisateur. Un ID de compte ressemble à ceci : 67125541.
    Exemple : SavesDir/{64BitSteamID}
  3. Motif

    Filtre sur le nom de fichier. Vous pouvez utiliser * comme caractère générique. Si vous voulez tous les fichiers du répertoire, utilisez seulement *.

    Exemple : *.sav
  4. Système d'exploitation

    Définit les systèmes d'exploitation depuis et vers lesquels ces fichiers seront synchronisés. Requis uniquement si les fichiers sont spécifiques à un système d'exploitation, ce qui ne devrait pas être le cas !
  5. Récursif

    Inclusion des sous-répertoires lors d'une recherche de fichiers correspondant au masque. Ceci est utile pour les sous-répertoires portant des noms non déterministes comme des noms d'utilisateur ou des ID non Steam. Si des Steam ID sont utilisés, alors il est vivement recommandé d'utiliser les valeurs de chemin spéciales dans le champ sous-répertoire.

Root Overrides

If your application is cross-platform and requires different directories for each OS. You can use the Root Overrides functionality to specify an override the Root Paths that you set above.

The root paths specified above can be overridden to correspond to a different path on another OS. If you use Root Overrides, you must specify [All OSes] in the Root OS drop down above.

A Root Override consists of 5 parts.
  1. Chemin racine originel

    Ceci correspond à l'un des chemins d'accès aux racines que vous avez défini plus haut.
  2. Système d'exploitation

    Système d'exploitation auquel appliquer la substitution.
  3. Nouveau chemin racine

    Nouvel emplacement vers lequel dirige le chemin racine originel avec le système d'exploitation spécifié.
  4. Ajouter/Remplacer le chemin

    Ceci vous permet d'ajouter éventuellement un chemin de sous-répertoire qui est inséré entre le nouveau chemin racine et le sous-répertoire original.
  5. Remplacer le chemin

    Si cette option est activée, le chemin spécifié dans « Ajouter/Remplacer le chemin » remplacera entièrement le sous-répertoire originel.

Example: Configuring Auto-Cloud for Unity Applications

The following is an example of setting up Auto-Cloud for use with Unity and the Application.persistentDataPath property where the value is different per OS. The Windows version is configured as the Root Path with the company in Unity set to DefaultCompany and the Project called AutocloudSample. On macOS and Linux/SteamOS, the alternate paths from Application.persistentDataPath are set in the Add/Replace Path field and Replace Path is enabled.

With these settings, Auto-Cloud files will be synchronized between the three folders as shown in the Preview samples.


Pre-release Testing

If you are adding Steam Auto-Cloud to a game which is already released and you have enabled developer-only mode during the Initial Setup then you must complete some additional steps to test the functionality.
  1. Connectez-vous à Steam avec un compte qui possède une licence Developer Comp pour l'application que vous testez.
  2. Ouvrez la console Steam en vous rendant sur steam://open/console dans votre navigateur.
  3. Tapez testappcloudpaths <AppId> dans la console avec l'AppID que vous testez. Ex. : testappcloudpaths 480
  4. Tapez set_spew_level 4 4 dans la console.
  5. Lancez votre application depuis Steam.
  6. Recherchez une éventuelle activité dans la console. Si des fichiers existent déjà dans les chemins de l'Auto-Cloud, vous devriez les voir en cours de téléchargement. Sinon, enregistrez quelques fichiers de votre application, puis fermez-les pour déclencher une synchronisation.
  7. Accédez à un autre PC et répétez les étapes ci-dessus pour tester le téléchargement des fichiers depuis l'Auto-Cloud Steam.
  8. Assurez-vous de faire le test pour tous les systèmes d'exploitation pris en charge.
  9. Tapez testcloudapppaths 0 et set_spew_level 0 0 pour mettre fin au test. Vous pouvez relancer le client Steam pour ne plus voir l'onglet de la console.

Don't forget to disable developers-only mode and publish the changes when you're done testing.


First, always ensure that you have published your changes on the Steam partner website and have waited up to 10 minutes or restarted your Steam client to receive the published changes.

If you run into issues with Steam Cloud you should check the log file located at %Steam Install%\logs\cloud_log.txt.

See Debugging the Steamworks API for additional information.