Stardew Valley is a good example of why backing up a folder is safer than hunting for a single extension. A farm lives in its own directory, and the directory contains multiple related records. That makes the folder boundary the practical unit for backups. On Windows, macOS, and Linux the path is well documented and easy to copy once hidden application-data folders are visible. Before a major mod change or a manual save operation, copy the entire farm directory to a location outside the live Saves folder and give the copy a date.
Choose the correct backup boundary
For Stardew Valley, the researched PC save location is Windows: %APPDATA%StardewValleySaves | macOS: $HOME/.config/StardewValley/Saves/ | Linux / Steam Play: $XDG_CONFIG_HOME/StardewValley/Saves/ (normally ~/.config/StardewValley/Saves/). The known save file or folder pattern is <FarmName>_<unique-id>
SaveGameInfo. Copy the whole farm folder, not only one file. This preserves the main save, SaveGameInfo, and any paired backup files that may be useful for recovery. Copying the complete documented save boundary is safer than selecting one visually obvious file, because companion metadata, indexes, backups, or multiple slots can be required together.
Make an offline copy before changing anything
Close the game first, wait for the active launcher to finish writing, then copy the save data to a separate folder that the game and sync client do not watch. Label the copy with the game, storefront, profile, and date. Documented launcher context: Steam, GOG Galaxy, Xbox / Microsoft Store. The normal desktop save folder is shared by Windows builds that use the standard StardewValley application-data path, while Microsoft Store/Xbox packaging and cloud behavior can differ. Do not assume a console or mobile save can be copied directly into the desktop folder.
Account for cloud saves
Steam Cloud and GOG Galaxy cloud support are documented. Cloud sync is convenient but should not replace a dated offline copy before mods, save editing, or migration. Before restoring an older backup, decide which copy should win. If the game or launcher starts while an older manual copy is in place, synchronization can replace it before you confirm that it works. Keep the untouched backup outside the live save path until the restored progress has been opened and saved normally.
Restore without changing format assumptions
Each farm is stored as a folder. Standard desktop saves include the main farm save and SaveGameInfo; the main data is XML text even though the primary file normally has no conventional extension. Compatibility note: Desktop saves are structured farm folders. Modded saves may depend on content or IDs provided by installed mods, so restoring the file without the same mod set can change behavior. Restore into the matching storefront/profile context whenever possible. Do not rename a save extension, move a folder into a different container type, or assume a console/mobile copy is equivalent unless a tested migration path specifically says so.
Recovery fallback
If a farm disappears from the load menu, compare the folder name, the main save filename, and SaveGameInfo. Keep the original folder intact before trying older backup copies. If the restored copy fails, put the untouched original back first. Then compare location, account/profile, cloud state, and the full directory structure before trying a different backup. The objective is reversible recovery, not repeated destructive experiments on the only copy.
Verification context: Desktop save paths and cloud services were reviewed against current PCGamingWiki coverage. File-structure notes are limited to the standard farm-folder layout; no arbitrary XML rewrite is performed by this Game Hub.