You reinstall a game, Steam Cloud proudly pulls down your 80-hour save, and then your carefully tuned modpack is nowhere to be found. The game boots anyway. You load the world anyway. Then it starts yelling about missing content, broken references, or a farm animal that has apparently become a void in space. So, does Steam Cloud save mods? Usually, no. It may save the save file that depends on those mods, which is not quite the heroic rescue Steam’s little cloud icon suggests.
Steam Cloud is useful, but it is not a complete backup of your game, your mod manager, and every sketchy-but-beloved texture replacement living in a folder three drive letters deep. Whether it saves anything mod-related depends on the individual game and what its developer told Steam to synchronise.
Does Steam Cloud save mods or just your saves?
Steam Cloud only synchronises the files a game’s developer has configured it to watch. There is no universal Steam rule that says every file connected to a game gets vacuumed into the cloud. A developer may include save data, settings, keybinds, screenshots, or local mod configuration. They may include none of those. Steam follows the rules it was given and politely ignores the rest.
For most games, Steam Cloud is intended to move your core progress between PCs: campaign saves, character data, world files, and perhaps a few preferences. Mods often live elsewhere. They may be installed through Steam Workshop, placed in a game’s installation folder, managed through Vortex or Mod Organizer 2, stored in a separate launcher directory, or generated by the game itself in an obscure AppData cave.
That means the answer has three flavours:
- The save may sync, while the mods do not. This is the usual and most dangerous arrangement for modded games.
- Workshop subscriptions may return, but not necessarily the exact installed state. Steam can re-download subscribed Workshop items after you sign in, but that is different from preserving the version, load order, settings, and dependent files your save expects.
- A few games may cloud-sync local mod data. If the developer explicitly included the relevant directory, some configuration or locally installed content may survive. Do not assume this without checking.
Steam Cloud is a courier for selected files, not a time machine for your entire mod setup.
Why a synced modded save can still break
A modded save is rarely just one file. It is a little ecosystem with opinions. The world file may record items, NPCs, buildings, quests, scripts, custom maps, mod IDs, and version-specific data. Remove the mod that created any of those things and the game has to decide what reality looks like now. Games are not always graceful about it.
Some titles simply omit missing objects. Others replace them with blanks, reset parts of the world, or refuse to load. The less lucky ones load successfully, save over the affected world, and turn a recoverable missing-mod problem into permanent save soup.
Load order matters too. Two players can have the same mods installed but still be running different versions, dependencies, configuration files, or plugin orders. This is especially common in Bethesda games, Stardew Valley setups with framework mods, Minecraft instances, and heavily customised survival games. Steam Cloud might deliver the save perfectly. It cannot tell you that a dependency updated on Tuesday and now the save was built against a different script.
There is also the quota problem. Steam Cloud storage is set by each developer, and save-heavy games can produce enormous worlds. If cloud sync fails, pauses, hits a limit, or creates a conflict after you played on two PCs, Steam may ask which version to keep. That prompt is not version history. It is a coin toss wearing a dialogue box.
Steam Workshop is not a full mod backup
Workshop makes this confusing because it feels like Steam owns the whole setup. In practice, Workshop handles subscriptions and downloads for supported games. That is helpful, but it is not the same as backing up your playable modded state.
If you reinstall Steam, your subscribed mods can often download again. But the Workshop item may have been updated, removed, made private, or replaced. Your local configuration might be elsewhere. A manually installed dependency definitely is not guaranteed to come back just because its Workshop neighbour did.
Think of Workshop as a list of boxes you ordered, not a photograph of the exact pile on your desk. The mod version you used, where it sat in the load order, what it was configured to do, and whether it worked with the rest of the pile are separate questions.
For a long-running world, preserve the modpack or instance alongside the save. In practical terms, that means keeping a copy of the mods folder, mod manager profile, config files, load order, and any launcher-specific settings. If a game uses a dedicated modpack export, make one before a major update. Future You will be less smug if Past You did it first.
How to check what Steam Cloud actually saves
The fastest answer comes from the game itself, not Steam’s general settings. First, confirm Steam Cloud is enabled globally and for that particular game in its properties. Then look for the cloud status beside the game in your library. A green cloud only means Steam believes its configured files are synced. It does not mean every mod-related file is aboard the lifeboat.
Next, identify where the game keeps four things: the save, the mods, the configuration, and the load order or profile. These may all be in one place, but usually they are not. PCGamingWiki-style folder lists and a game’s modding community documentation are useful for this investigation, but the final proof is to inspect the folders yourself.
A safe test is wonderfully unglamorous. Back up the folders manually, make a harmless setting change or new test save, let Steam sync, then check what changed on a second machine or after a controlled reinstall. Do this with a throwaway save, not the 300-hour co-op world your mate hosts from a laptop balanced on a radiator.
If the game uses Workshop, check whether the mods are subscribed, whether there are local files outside Workshop, and whether the game exposes a load order. If you use Vortex, Mod Organizer 2, Prism Launcher, r2modman, or another manager, treat its profile and instance as part of the save’s survival kit.
The safer way to protect a modded world
For small experiments, Steam Cloud plus Workshop may be enough. For a serious modded run, it is a convenience layer, not your only defence. You want restore points that predate the bad update, accidental overwrite, corrupt session, or enthusiastic friend who said they were just checking something.
Keep copies at meaningful moments: before adding or removing mods, before game updates, before converting a world, and before handing a co-op save to someone else. Crucially, retain older versions rather than overwriting one backup with the next. A backup that faithfully captures corruption is technically a backup. It is also deeply unhelpful.
Co-op creates an extra trap. Steam Cloud can sync a host’s world between that host’s own machines, but it does not solve ownership or handoff. If Jordan hosts the Valheim world and Jordan is away for the weekend, everyone else still needs the actual world files, matching mods, and a clear rule about who is allowed to advance the save. Passing folders around in Discord works right up until two people play separate timelines and one overwrites the other.
This is the problem tools such as Checkpoint64 are built for: automatic versioned copies of save folders, plus controlled co-op handoff, rather than pretending a single synced file is a backup strategy. The useful bit is not merely having a copy. It is being able to restore the copy from before the mod update ate your village.
Before you load that missing-mod warning
Stop. Do not save over the world yet.
Take a copy of the current save immediately. Then restore or reinstall the missing mods, matching versions where possible, and check the load order and configuration against the machine that last played successfully. If the warning appeared after an update, try rolling the affected mod back rather than charging ahead with the latest release. Newer is not always safer when a save was built on an older stack.
If you must remove a mod, look for that game’s recommended removal process. Some mods include cleanup commands or uninstall instructions; others explicitly warn that removal is unsafe mid-save. Believe the warning. A mod author has already watched someone turn a functioning world into abstract art so you do not have to.
Steam Cloud can save plenty of pain when your PC changes or a drive dies. Just do not ask it to remember a modded world’s entire history, every dependency, and the exact moment your group should roll back to. That is a bigger job than a little cloud icon was ever hired to do.