How to Find Your World From a Save in tModLoader's Cloud Storage
If you've been playing Terraria with tModLoader and suddenly can't locate your world after switching devices, reinstalling, or noticing your save ended up in the cloud, you're not alone. This is one of the more confusing pain points for modded Terraria players — because tModLoader handles save files differently from vanilla Terraria, and cloud saves add another layer on top of that.
Here's a clear breakdown of how the system works and where to actually find what you're looking for.
Why tModLoader Saves Files Differently From Vanilla Terraria
tModLoader runs as a separate game on Steam, not a mod layered on top of your existing Terraria installation. This means it maintains its own save directory, completely separate from where vanilla Terraria stores worlds and players.
When you enable Steam Cloud Sync for tModLoader, your save files get uploaded to Valve's cloud storage and can appear to "disappear" from your local machine — or at least become harder to find through normal file browsing.
Understanding this split is the first step to finding your world.
Where tModLoader Stores World Files Locally
By default, tModLoader saves worlds in a dedicated folder depending on your operating system:
| Operating System | Default tModLoader Save Path |
|---|---|
| Windows | %UserProfile%DocumentsMy GamesTerraria ModLoaderWorlds |
| macOS | ~/Library/Application Support/Terraria/tModLoader/Worlds |
| Linux | ~/.local/share/Terraria/tModLoader/Worlds |
Each world is saved as a .wld file, with a matching .wld.bak backup file alongside it. If you can see these files, your world is stored locally.
🗂️ Pro tip: If the Worlds folder appears empty, Steam Cloud may have replaced your local files with cloud versions, or the sync may not have completed properly.
How Steam Cloud Interacts With tModLoader Saves
Steam Cloud for tModLoader works the same way it does for most Steam titles — it syncs save files between your local machine and Valve's servers. The key behaviors to understand:
- On launch, Steam checks whether the cloud version or local version is newer and may prompt you to choose
- On close, Steam uploads any changes to the cloud
- Conflicts occur when saves exist on two different machines with no shared sync history
When Steam Cloud is active, your world file may exist only in the cloud if local storage was wiped, the game was reinstalled, or the sync hasn't fully downloaded yet.
How to Access Cloud-Saved Worlds
To retrieve a world from Steam Cloud storage, you have a few paths:
Option 1: Let Steam sync automatically Launch tModLoader through Steam on the machine where you want to play. Steam should detect the cloud save and download it before the game opens. The world should then appear in your in-game world selection menu.
Option 2: Use Steam's cloud file viewer
- Open Steam and go to your Library
- Right-click tModLoader → select Properties
- Navigate to the General tab and look for the Steam Cloud section
- Some versions of Steam allow you to view and force-download specific cloud files from here
Option 3: Access cloud files via the Steam website
- Log in at store.steampowered.com
- Go to your username → Account Details → View Steam Cloud
- Find tModLoader in the list and browse the stored files
- You can download
.wldfiles directly from here and manually place them in your local Worlds folder
What Can Go Wrong — and Why the Fix Varies
Several variables affect whether your world loads cleanly after pulling it from cloud storage:
Mod dependencies: A world saved with specific mods active may not load correctly if those mods aren't installed, are outdated, or have been removed from the mod browser. tModLoader will usually warn you, but some issues are silent.
tModLoader version mismatches: tModLoader releases separate stable versions tied to different Terraria builds. A world created on one version may have compatibility issues when opened on a significantly different version. This is especially relevant if you updated tModLoader between play sessions.
Corrupted or partial syncs: If Steam Cloud sync was interrupted — by a crash, a network drop, or a forced shutdown — the uploaded file may be incomplete. The .wld.bak backup is worth checking in these cases.
Multiple accounts or Steam profiles: If you play on more than one Steam account, or share a machine with another player, cloud saves are account-specific. A world saved under one account won't appear in another account's cloud.
Verifying the World Loaded Correctly
Once you've located and downloaded your world file and placed it in the correct Worlds directory:
- Launch tModLoader through Steam
- Click Single Player from the main menu
- Your world should appear in the world selection list
If it doesn't appear, double-check that the .wld file is in the right folder path for your OS, and that you're launching tModLoader specifically — not vanilla Terraria, which reads from a different directory.
⚠️ If the world loads but looks wrong — missing items, broken structures, or mod content not appearing — the issue is almost certainly a mod version mismatch rather than a problem with the save file itself.
The Variables That Determine Your Outcome
Finding a world from tModLoader's cloud storage is straightforward in a clean setup, but the real-world result depends heavily on:
- Whether Steam Cloud was enabled before the world was lost locally
- Which version of tModLoader the world was last saved on
- Which mods were active and whether they're still available
- Whether the sync completed fully before any reinstall or device switch
- Whether you're recovering to the same machine or a new one
Each of those factors changes what the recovery process looks like — and whether a simple sync is enough or a more manual approach is needed. 🔍