How to Set Up Cloud Save Sync Across Multiple Devices in RetroArch

Playing the same library across multiple devices — a desktop, a Steam Deck, a handheld running Batocera or RetroArch directly — only works smoothly if saves and save states actually follow you between them, which requires deliberate setup rather than happening automatically.

Step 1: understand the two distinct types of save data

In-game saves (.srm files, or memory card images for disc-based systems) are the save data games themselves create through their own save/load menus. Save states (RetroArch’s own frame-perfect snapshots) are separate and stored differently — a sync setup needs to cover both if you use both.

Step 2: locate RetroArch’s save directories

RetroArch → Settings → Directory →
  Savefile → note this path
  Savestate → note this path

By default these may be set to save alongside each ROM’s own folder rather than one central location — for cross-device sync, pointing both to a single dedicated folder makes the next steps far simpler.

Step 3: point both directories to a cloud-synced folder

RetroArch → Settings → Directory →
  Savefile → ~/Dropbox/retroarch-saves/
  Savestate → ~/Dropbox/retroarch-states/

Any sync service that maintains a regular folder on each device (Dropbox, Google Drive, Syncthing, a self-hosted Nextcloud instance) works here — RetroArch itself has no cloud integration built in; this works by pointing RetroArch’s own save paths at a folder something else keeps in sync.

Step 4: apply the identical configuration on every device

The save and savestate directory paths need to point at the same synced folder (adjusted for each device’s local filesystem conventions) on every device you use — a mismatch here means saves silently write to a folder that never syncs anywhere.

Step 5: avoid the single biggest risk: simultaneous use on two devices

Playing the same game on two devices at once — even briefly, like leaving RetroArch open on a handheld while also playing on desktop — creates a sync conflict, since both devices will try to write to the same save file with different content. Fully closing RetroArch on one device before opening it on another avoids this class of problem entirely.

Step 6: verify sync actually completed before switching devices

Check your sync client's status icon/log confirms the save
file actually uploaded, not just that RetroArch wrote it locally

A save written locally an instant before closing the laptop lid (which may pause background sync) can appear saved on-device but not yet actually be in the cloud folder when you open the next device — checking sync status, not just local save confirmation, avoids “my progress vanished” surprises.

Step 7: consider Syncthing for a fully private, serverless alternative

Syncthing folder shared directly between devices,
no third-party cloud storage provider involved at all

For anyone who’d rather not put save files through a third-party cloud provider, Syncthing synchronizes folders directly between your own devices over your local network or the internet, with no intermediate server storing the data.

Step 8: back up the synced folder independently as well

A sync folder propagates both good changes and mistakes (including accidental deletions) to every device equally — a separate, periodic backup of the synced save folder protects against the specific failure mode where a sync service faithfully replicates a problem everywhere rather than catching it.

Why RetroArch’s directory-based design makes this straightforward

Because RetroArch reads and writes saves as ordinary files in a configurable directory rather than through some proprietary save-management system, any general-purpose file-sync tool can handle the actual synchronization — the setup here is entirely about pointing RetroArch’s existing settings at the right folder, not about any retro-gaming-specific sync technology.