Cloud sync is not a versioned backup
Cloud synchronisation can copy a mistake or a damaged save to another device. A useful recovery backup is a separate copy you can identify and restore, not just the current cloud version. Make one before an editor session, game update or platform transfer.
Finish saving in game, close the game and wait for the launcher to finish syncing. Copy the complete accessible save set or use the supported backup workflow; do not copy files while the game is writing them. Container-managed Xbox data requires its own compatible workflow.
Make the backup identifiable
Keep the original backup outside the active save folder. Use a folder name containing the platform, player and your own creation date. Record whether it was made before a game update. If several people use the same PC, identify the player rather than relying on similar filenames.
- Keep one untouched pre-edit copy. Work on a separate copy where possible.
- Check that the backup exists and contains the expected files; a shortcut is not a backup.
- Keep more than one known-good version instead of overwriting your only recovery point.
Use Studio safeguards as an additional layer
Starlight Studio provides backup and Save Health tools alongside its staged editing workflow. Review any warnings before saving, and keep your independent original even when an automatic backup was created. Validation cannot guarantee every possible future game interaction.
After saving, launch the correct player profile and check the result in game before treating it as your new recovery baseline. If anything looks wrong, stop and use the restore guide rather than repeatedly saving over the original.