Setup
Last updated 2026-05-29
Windrose Save File Location Guide
A Windrose save file location guide for checking Steam Cloud state, backup safety, update risk, and current-build save path evidence without publishing unverified file paths.
Quick answer
Do not move, delete, or edit Windrose save files until the exact current-build save location is verified on your PC. Start by checking Steam Cloud status, making route notes and screenshots, and backing up only after you can confirm which files belong to the world you care about.
Goal
Get the useful answer in under one minute.
Data status
Early Access values need build checks.
Best use
Pair this page with the planner and hub.
Verify the path before touching files
Save-file searches are useful, but they are also risky. A guessed path can make players back up the wrong folder or delete the wrong data, so this guide treats exact locations as current-build evidence, not evergreen facts.
- Confirm the installed game, account, and current build before searching local files.
- Do not publish an exact save path unless it was verified on the current build.
- Check whether Steam Cloud is enabled before moving or copying anything.
- Keep screenshots and route notes before changing file-level data.
Separate cloud sync from local backups
Steam Cloud support is listed for Windrose, but cloud sync and manual backup solve different problems. Players should understand which one they are relying on before a machine switch, update test, or co-op world recovery.
- Use Steam Cloud status checks before switching PCs.
- Let Steam finish syncing before closing the client or opening Windrose on another device.
- Treat manual backups as local recovery notes, not a replacement for understanding cloud state.
- Avoid overwriting a newer cloud save with an older local copy unless you know the direction of sync.
Build a safe backup note
Before touching any save-like folder, write a small note that tells future you what the files were, why they were backed up, and what game state they should restore.
- Record date, patch context, Steam account, world or route purpose, and device name.
- Add screenshots of the in-game state you expect the backup to match.
- Keep solo, co-op, test, and troubleshooting backups separated.
- Never rename or replace files while the game or Steam sync is active.
Use backups during updates carefully
Early Access updates can change save behavior, world data, balance, or bug symptoms. Backups are most helpful when they are tied to a clear update checkpoint.
- Create notes before major updates, long co-op sessions, or risky troubleshooting.
- After an update, test one low-risk solo route before trusting old backups for current advice.
- Do not use an old backup result as proof of current save behavior.
- Update the Steam Cloud and save safety pages if verified path or sync behavior changes.
Data table
Save file safety checklist
Use this before looking for, copying, moving, or editing Windrose save data.
| Check | Why it matters | Safe action |
|---|---|---|
| Exact path verified | Prevents backing up the wrong folder | Confirm current-build path before publishing or editing |
| Steam Cloud state | Cloud sync can overwrite local assumptions | Check Steam Cloud status and wait for sync |
| Game closed | Open files can be incomplete or locked | Close Windrose and avoid syncing mid-copy |
| Backup label | Restores need context later | Record date, device, account, world, route, and patch |
| Recovery test | A backup is only useful if it maps to the right state | Use a low-risk test before relying on it |
This checklist avoids naming an exact save path until that path has been verified against the current Windrose build.
Data table
Save evidence confidence table
Use these labels when deciding whether a save location or backup instruction is safe enough to publish.
| Label | Use when | Avoid |
|---|---|---|
| Current-build verified | The path was checked on the current build and device context | Assuming another account or OS matches |
| Cloud-state checked | Steam Cloud status and sync direction were confirmed | Copying files while sync is unclear |
| Reported only | A player report exists but has not been reproduced | Publishing the path as official |
| Not checked | No current local evidence exists | Guessing from another game or old build |
Verification note
Steam Cloud support and Windows PC context are based on official Steam store data for Windrose app 3041230 checked on 2026-05-28; exact save file paths, local backup folders, sync behavior, and save editing advice require current-build verification on the target PC and account.
FAQ
Where are Windrose save files located?
This guide does not publish an exact Windrose save path until current-build evidence verifies it. Check Steam Cloud status, close the game, and confirm which local files belong to the world or route before copying anything.
Should I edit Windrose save files?
Avoid editing save files unless you understand the current path, backup state, Steam Cloud behavior, and recovery risk. For normal play, route notes and verified backups are safer than manual edits.
Can Steam Cloud replace backups?
No. Steam Cloud can help with sync, but it does not replace clear local notes, screenshots, and a dated backup plan before updates, machine switches, or risky troubleshooting.
Related guides
Setup
Windrose Save Safety and Backup Guide
Setup
Windrose Save Missing Recovery Guide
Setup
Windrose Backup Before Update Guide
Setup
Windrose Reinstall Without Losing Saves Guide
Setup
Windrose Move Save to New PC Guide
Setup
Windrose Steam Cloud and Save Sync Guide
Setup
Windrose Mods and Steam Workshop Guide
News
Windrose Update Prep Checklist
Setup
Windrose Troubleshooting Guide
Setup
Windrose Crash on Startup Checklist
Setup
Windrose Family Sharing Guide
Start Here
Windrose Solo Offline Guide
Setup
Windrose Controller Support and Steam Features Guide
Gale Atlas is an independent fan-made guide site and is not affiliated with the developers, publishers, or official Windrose team. Game names, trademarks, and assets belong to their respective owners.