Traveloot Save Backup & Cloud Guide
Export, Cloud, itch↔Steam migration, and recovery tips so guild unlocks survive patches.
Traveloot is a run-based incremental: every magnet node, guild slot, desert recruit, and Casual Mode milestone lives in a save file, not in a disposable run. Fluffy Lotus has warned that updates can occasionally wipe or break local progress, which is why the game exposes a deliberate export control on the main menu. This guide walks through why backups matter, how to use that tiny icon, how Steam Cloud fits beside manual copies, itch ↔ Steam caveats, a pre-update checklist, multi-PC / Deck / Remote Play notes, and what to try if a file looks corrupt.
Hardware and controller setup live on System Requirements. First-hour play order is in Getting Started. Co-op host rules are in Co-op Guide. Storefront links stay on the Links Hub; patch timing lives under Release Notes.
Why backups matter for incremental unlocks
Unlike a single-session arcade score, Traveloot progress stacks across hours: workstation repairs, branching upgrade tree purchases, eight adventurers, four islands, and economy multipliers. Losing that file means re-earning wood/gold/stone loops and re-triggering desert events for Knight or Druid. A two-minute export before you click Update is cheaper than a weekend of re-farming.
Browser itch builds add another risk: web uploads or cache clears can reset browser storage. Even the downloadable itch client and Steam install can change folder layouts between versions. Treat every storefront switch and every experimental patch as a backup moment.
Step-by-step: main-menu export
- Launch Traveloot and reach the main menu (quit the active run if needed so you are not mid-stage).
- Look in the bottom-right corner for a tiny white / small icon—it is easy to miss beside larger buttons.
- Click it to export / copy save data using the in-game flow the build provides.
- Move the resulting file (or paste target) to a folder outside the install directory—Documents, a cloud drive folder you control, or an external disk.
- Name the copy with a date and build hint (for example
traveloot-2026-11-18-steam) so you can roll back cleanly.
Do not leave your only backup inside steamapps\common\Traveloot or the itch install tree. An update that replaces the game folder can delete “safe” copies that lived next to the executable.
Steam Cloud vs manual export
Steam lists Steam Cloud among Traveloot’s features (app 4349140, full release November 17, 2026). Cloud sync is convenient when you alternate a desktop and a laptop on the same Steam account: quit the game fully, wait for the cloud icon to settle, then launch on the other machine.
Cloud is not a substitute for the main-menu export:
- Cloud can lag, conflict, or fail on flaky networks.
- A bad local write can sync upward and overwrite a good remote copy.
- itch browser / itch download builds do not share Steam’s cloud namespace.
Best practice: enable Cloud on Steam and keep dated manual exports before major patches, migrations, or Deck take-home sessions.
itch.io ↔ Steam migration caveats
Players who started on itch often want Steam progress. Developer guidance from the demo era still applies as a cautious template:
- Export from the itch build using the bottom-right main-menu control.
- Install the Steam build and locate its save location carefully.
- You may need to replace a version token when swapping files—historically something like changing
VERSION2.0demotoVERSION2.0. - Launch Steam Traveloot and verify guild slots / upgrades before deleting the itch copy.
Compatibility is not guaranteed across every major release. itch still hosts a browser build (community posts have mentioned builds such as 0.10d during development), while Steam carries the full retail line. If a migrate fails, restore from your dated export rather than iteratively editing both live files. Players transferring progress sometimes mention Casual Mode—confirm the mode and unlocks you expect after import instead of assuming every flag survived.
Pre-update checklist
Before you accept a Steam auto-update, itch download, or experimental build:
- Finish the current run or exit to the main menu cleanly.
- Click the tiny bottom-right export icon and store the file outside the install folder.
- If on Steam, fully quit the client so Cloud can finish uploading.
- Skim Release Notes or Steam news for save-related warnings.
- After the update, launch once, confirm adventurers and upgrades, then export again as a “known good” post-patch baseline.
Multi-PC, Steam Deck, and Remote Play
- Two PCs, one Steam account: rely on Cloud between sessions, but still keep a manual export before the first Deck or living-room move.
- Steam Deck: treat unknown verification badges as storefront labels; still export before big OS or game updates. Controllers are fine for play—use touch or a mouse on the main menu if the tiny icon is hard to hit with a stick.
- Remote Play Together / couch co-op: progression is shared on the host save. Guests do not carry a personal permanent file home. The host should export before patch nights and before lending the PC. Role tips live in the Co-op Guide; party ideas live under the Players Hub.
Recovery if a save looks corrupt
Symptoms can include missing guild slots, wiped upgrades, failing to load, or progress that reverts after quit.
- Do not immediately overwrite your last good export while testing.
- Fully quit Traveloot and Steam/itch, then restore the most recent known-good manual copy into the active save location.
- If Cloud keeps re-downloading a bad file, temporarily disable Cloud, restore local, verify in-game, then re-enable after a clean quit.
- For itch↔Steam experiments, fall back to the pre-migrate export rather than mixing half-edited version strings.
- If nothing loads, start a fresh file on the current storefront and use Getting Started to rebuild efficiently—you already know magnet-first priorities.
Hardware reminder
Save hygiene does not replace a healthy install. Confirm Windows 10+, ~300 MB free, and stable storage on System Requirements before blaming Cloud for disk errors. Official storefronts and community links sit on the Links Hub.
Export often, store copies outside the game folder, and treat Steam Cloud as a convenience layer—not the only vault for your Traveloot guild.
Frequently Asked Questions
Quick answers to the most common Traveloot questions.
Where is the Traveloot save backup button?
On the main menu, look for a tiny white or small icon in the bottom-right corner. Click it to export or copy your save data, then store the file outside the install folder.
Does Traveloot use Steam Cloud?
Yes. Steam lists Steam Cloud among the features for app 4349140. Still keep manual exports before major updates—Cloud alone is not a perfect backup.
Can I move an itch.io Traveloot save to Steam?
Sometimes. Export from itch, then carefully place the file into the Steam save location. You may need to change a version string such as VERSION2.0demo to VERSION2.0. Success is not guaranteed across every build.
Who owns co-op progress in Traveloot?
Local and Remote Play Together progression is shared on the host save. Guests should not expect a personal permanent file; the host should export before patches.
What should I do before updating Traveloot?
Exit to the main menu, use the bottom-right export icon, save the copy outside the install directory, let Steam Cloud finish if applicable, then update and verify unlocks after launch.