One of the best things about a Steam Deck running EmuDeck is that it turns retro gaming back into something frictionless. You can chip away at a PS2 game on the couch, move to a desktop later, pick up a different handheld tomorrow, and not feel like your progress is trapped in one little Linux box under your TV stand.
That only works if your saves follow you.
And honestly, this is why EmuDeck cloud saves are so good when they are set up correctly. They solve a genuinely annoying problem instead of dressing up a fake one. The useful part is simple: a reliable way to keep emulator saves moving between devices without manually copying folders like it is 2007.
If you are already living in Google Drive, that route is easy. If you self-host and want your save pipeline under your own roof, Nextcloud is the better answer. Either way, the result is the same: your Steam Deck stops being an island.
Why this setup is worth doing
The obvious reason is convenience. If you bounce between a Steam Deck and a desktop, syncing saves means you stop asking annoying questions like “wait, which machine has the real save?”
The less obvious reason is resilience. EmuDeck also supports cloud backup, which means your save files are not living one SSD failure, one bad SD card, or one careless reinstall away from disappearing. That matters more than people admit. Retro saves are weirdly sentimental. Losing a hundred-hour RPG run because you kept telling yourself you would back it up later is exactly the kind of avoidable loss modern hardware should help prevent.
EmuDeck’s official docs split this into two ideas:
- CloudSync is for keeping saves aligned across devices. EmuDeck describes it as downloading saves when you start a game and uploading changes automatically afterward, so the useful mental model is launch/close sync and managed background updates rather than instant real-time mirroring.
- CloudBackup is for pushing saves to a provider so your progress survives device problems, even if you are not trying to keep multiple systems perfectly in step.
If your goal is “I want to keep playing the same save on multiple systems,” CloudSync is the feature you care about. If your goal is “I never want to lose my saves again,” CloudBackup still matters even if you only use one machine.
One caveat worth saying out loud: feature tiers and labels in EmuDeck move around enough that you should check the current app and docs at install time instead of trusting an article forever. Historically, the fuller two-way CloudSync path has often been treated as a supporter feature, so verify what your current build actually offers before you expect cross-device magic.
Google Drive or Nextcloud?
This is the easy fork in the road.
Use Google Drive if you want the least resistance
If you already use a Google account everywhere, Google Drive is the path of least resistance. You log in, let EmuDeck create the save structure, and move on with your life. That is the appeal. It is boring in the best possible way.
For most people, especially if the goal is just “make my Deck and PC stop fighting over save files,” Google Drive is the faster setup.
Use Nextcloud if you want control
If you are already self-hosting, Nextcloud is the more satisfying option. Your saves live on infrastructure you control. You are not stuffing emulator progress into yet another Google silo. It also fits nicely with the broader self-hosting mindset: if the point of the Steam Deck is to make your game library more portable and flexible, then having your save sync ride on your own storage stack is an unusually clean little win.
The tradeoff is predictable: Nextcloud is usually a little more fiddly. Still worth it, but not exactly “click button, receive enlightenment.”
What you need before you start
- A Steam Deck with EmuDeck already installed and updated.
- Your cloud provider choice: Google Drive or Nextcloud.
- If you are using Nextcloud, your server URL and preferably an app password.
- A Chromium-based browser set as the default browser in SteamOS desktop mode before you start the cloud setup.
That last point matters because EmuDeck’s official docs explicitly warn that Firefox has a bug that can prevent Cloud Saves from installing correctly on Linux and SteamOS. So if you normally live in Firefox, great, congratulations on your taste. Temporarily make Chrome or another Chromium-based browser the default anyway so the setup does not fail for a browser-specific reason.
How to set it up on Steam Deck
1. Switch to Desktop Mode and open EmuDeck
Do the setup from Desktop Mode. Open the EmuDeck app and head for the cloud save section. Depending on the version you are on, the wording may show up as Cloud Saves, CloudSync, or similar. If EmuDeck moved the label around again, that is the menu you are hunting.
2. Decide whether you want backup, sync, or both
If you only care about recovery, set up CloudBackup. If you want real cross-device continuity between the Deck and something else, use CloudSync. For most people reading this article, that second option is the whole point.
3. Authenticate with your provider
For Google Drive, sign in through the browser flow EmuDeck launches and approve the access it needs.
For Nextcloud, use your server details. If EmuDeck asks for a WebDAV endpoint rather than just a normal site URL, the standard Nextcloud format is:
https://your-domain.example/remote.php/dav/files/USERNAME/
That URL format matches Nextcloud’s official WebDAV documentation. If you are self-hosting, use an app password instead of your normal account password. It is cleaner, safer, and easier to revoke later if you need to.
4. Let EmuDeck create its save structure
Once the provider is connected, let EmuDeck create the folder structure it expects. Official troubleshooting guidance references saves landing under paths like EmuDeck/saves/your_emulator in the cloud provider, which gives you a good place to verify whether things are actually moving.
5. Test with one game before you trust it with everything
This is the part people skip right before they discover three days later that their “working backup” was mostly wishful thinking.
Pick one emulator and one game you do not mind poking at. Make a save. Watch for CloudSync notifications. Then check the cloud provider directly and confirm that the expected save files actually appeared.
If you are syncing between devices, launch the same game on the second machine and verify that the save comes down cleanly there too.
What can go wrong
Most save-sync problems are not mysterious. They are just annoying.
- Missing cloud tooling: EmuDeck’s troubleshooting docs say to confirm that the Rclone binary and
Emulation/tools/rclone/rclone.confexist in the expectedEmulation/tools/rclonepath. If those files are missing, reinstall CloudSync from the EmuDeck app. - Bad DNS: EmuDeck’s docs also call out DNS problems more than once. If setup hangs, downloads fail, or cloud components refuse to install, switching DNS to something sane like
1.1.1.1or8.8.8.8is worth trying. - Firefox weirdness on SteamOS: Again, use a Chromium-based default browser for setup. This is one of those deeply annoying issues that is easy to dodge if you know it exists.
- Nextcloud login errors: Double-check the URL format and use your actual username, not an email alias. If your Nextcloud instance supports app passwords, use one. If the connection still fails, the Nextcloud Files web interface usually exposes the exact WebDAV path in its settings, which is the fastest way to catch a bad base URL.
- Manual backup confusion: EmuDeck’s save-management docs warn that some save paths in
Emulation/savesare symlinks. If you ever need to manually inspect or back up save data, use the real target location, not just the symlink folder, or you may back up a shortcut instead of the actual save.
The part I like most about this
This is the kind of feature that makes a Steam Deck setup feel grown up.
It is not flashy. It is not the sort of thing that gets turned into a YouTube thumbnail with glowing arrows and a shocked face. It just removes friction from real use. You stop babying one device. You stop treating emulator progress like fragile state that only exists if you remember where the folders are. You stop rebuilding the same trust every time you switch machines.
And if you are using Nextcloud, it gets even better: now your retro saves are just another thing quietly living on infrastructure you own. That is catnip if you are the kind of person who self-hosts on purpose.
My recommendation
If you want the fastest path to “this works and I can stop thinking about it,” use Google Drive.
If you already run Nextcloud or want your save pipeline under your own control, use Nextcloud and do it properly with WebDAV and an app password.
Either way, set it up now, test it with one game, and stop leaving your emulator saves to chance. EmuDeck already did the hard part by organizing the mess. You might as well take the win.
If you want the official docs before you start, read EmuDeck’s Cloud Saves guide, their CloudSync troubleshooting page, and the save management reference. For Nextcloud users, the official WebDAV documentation is the right sanity check if the URL format gets weird.