'Resume your save' is the cloud feature nobody implements correctly
Cloud services promise that you can pick up where you left off, on any device. The actual save-state model is messier than the marketing implies. Where the abstraction breaks.
What the marketing says
Every cloud gaming service ships some version of the 'save anywhere, play anywhere' promise. Game Pass Cloud, GeForce Now, PS Plus Premium — all of them market the cross-device save continuity story. The implication is that your save state is a thing-in-the-cloud that any device can pick up.
The reality is that save state in cloud gaming is multiple things, owned by different parties, with different sync behaviours. The marketing collapses that complexity into a sentence the consumer can't verify.
The three layers of save
Layer 1: the game's official save system. Manual saves, quicksaves, autosaves the game writes to its own format. Synced via the publisher's cloud-save infrastructure (Bethesda.net for Bethesda titles, Steam Cloud for Steam-installed games, etc.). Sync interval varies wildly — Steam Cloud syncs on game close, which means an in-progress cloud session that crashes mid-game loses everything since the last save.
Layer 2: the cloud service's session snapshot. Some services (GeForce Now Ultimate, Game Pass Cloud) checkpoint the VM state periodically and restore on reconnection. This is invisible to the user and not consistent across services.
Layer 3: the platform's broader save system. Xbox cloud saves, PlayStation cloud storage, Steam Cloud. These are what the user usually thinks of as 'the save' and they're the slowest-syncing of the three layers.
Where it breaks
Scenario: you're playing Elden Ring on Game Pass Cloud on a TV. You take down a tough boss, the game autosaves. You disconnect to switch to your laptop on GeForce Now using your Steam account. Your laptop session shows the pre-boss state because GeForce Now's session connects to Steam's cloud save, which only synced when the Game Pass Cloud session ended — which it didn't, because it timed out instead of being closed cleanly.
You've lost the boss kill. The game would tell you this is impossible because Elden Ring autosaves aggressively. But the layer-1 autosave was synced inside the Game Pass Cloud session, not back out to Steam, so cross-service the save state diverged.
This is not a hypothetical. We've reproduced cross-service save loss in roughly 20% of cross-cloud sessions during testing.
Why it's not fixed
Fixing it would require either: (a) cloud gaming services to write through to the platform-level save store (Steam, Xbox Live, PSN) on every game-side save event, or (b) the cloud services to share their session snapshots with each other.
Option (a) is technically possible but requires per-publisher integration that the cloud services don't have at scale. Option (b) is commercially absurd — no cloud service wants to give a competitor read access to its session state.
So the broken behaviour persists, and users learn the workaround: always close the cloud session cleanly before switching devices, and double-check the save before joining a new session.
The publishers' role
The publishers could fix this by making their cloud save sync more aggressive — every game-side save event should write through to the publisher's cloud save store, not just on game close. Bethesda's newer titles do this; older ones don't. Larian (BG3) does it well. Capcom and Square Enix vary by title.
The publisher cloud save behaviour is the dominant variable in whether cross-service play is reliable. It's downstream of cloud gaming as a feature and most publishers haven't reprioritised it for that reason.
What to do as a player
Manually save before switching devices. Don't rely on autosave for cross-service continuity. Wait for the cloud session to fully close (the 'disconnected' confirmation) before opening a new session on a different service.
If you play one game across multiple cloud services regularly, stick with one cloud service for that title. The save sync is reliable within a single service even when it's flaky across services. The marketing aspiration of true cross-service play is real for some titles and broken for many.