Where is the Voidling Bound save file?
The most useful starting point for the Voidling Bound save file is the Windows local-data area, not the game installation folder. Community reports and public Steam file references commonly point players toward AppData\LocalLow and a Conglomerate Games\Voidling Bound\Saves folder. Treat that location as a strong lead rather than an official forever-contract: folder names can change between builds, demo versions, profiles, and future updates.
Where to look for the local save file
Start with File Explorer's address bar and enter %USERPROFILE%\AppData\LocalLow. This is faster and safer than clicking through hidden folders one at a time. Look for a publisher or studio folder named Conglomerate Games, then a Voidling Bound folder and, when present, a Saves subfolder. If Windows says the location does not exist, do not create an empty replacement there yet; the game may have not written a save on that profile, or the current build may use a nearby folder name.
| Place to check | What it may contain | How to use the evidence | Do not assume |
|---|---|---|---|
| AppData\LocalLow | Local profile data and saves | Check publisher, game, and Saves folder names | Every release uses the same directory |
| Steam\userdata\<Steam3ID>\2004680 | Steam Cloud or synchronised app data | Compare timestamps and conflict copies | Cloud data is always newer |
| Game installation folder | Executables, assets, logs, or configuration | Use it only to confirm the install | The save must sit beside the EXE |
| Search by modified date | Files created after a controlled test save | Use a test state to narrow candidates | A random similarly named file is safe to restore |
How Steam Cloud changes save-file recovery
Steam Cloud can be helpful when a local file is lost, but it is not a substitute for a manual backup. Cloud synchronisation can also copy an unwanted state, preserve a conflict, or make it unclear whether the local or remote version was selected. Think of it as another evidence source that must be compared, not as an automatic undo button.
- Check the Steam clientOpen the game's properties and note the current Steam Cloud setting and any sync or conflict message.
- Preserve both candidatesCopy the local folder and any cloud-conflict files before selecting, deleting, or replacing anything.
- Compare the sessionUse mission progress, modified time, file size, and the last known play session to identify the likely state.
- Test one copyRestore only a duplicate or clearly labeled working copy, then launch once and check the result.
A safe Voidling Bound save-file backup routine
A reliable backup takes less than a minute once the folder is known. Close the game, wait for Steam to finish syncing, copy the full save folder, and add the date plus a short description to the backup name. For example, a folder named 2026-09-19-after-quackies-run tells you more than a file called final-save. Keep at least one copy outside the Steam installation directory.
Before a mod
Copy the complete save folder and note the current mod or game build. Keep the backup outside the install directory.
Before an update
Save a dated snapshot before launching the updated build so you can compare old and new states if a patch changes behaviour.
Before moving PCs
Keep a local copy even when Steam Cloud is enabled. Cloud access depends on the same account, sync state, and current client.
Before recovery
Duplicate every candidate first. Test the duplicate and keep the original untouched until the result is confirmed.
Voidling Bound save-file troubleshooting
Most missing-save reports come from checking the wrong Windows profile, looking only in the installation folder, or allowing a cloud sync to overwrite the state before a copy was made. Work from the least destructive check to the most invasive one: confirm the account, find candidate folders, copy them, compare dates, and only then test a restore.
| Symptom | Likely explanation | Next safe check | Avoid |
|---|---|---|---|
| No Saves folder | No completed save on this profile or path changed | Make a small test save and search by modified time | Creating random empty files |
| Old progress after launch | Cloud or local copy was replaced by an older state | Close the game and preserve current and conflict copies | Launching repeatedly |
| Save works on one PC only | Different Windows account, Steam profile, or sync state | Compare account, app ID folder, and dated backups | Copying another user's file blindly |
| Problem started after a mod | Mod changed data or loaded an incompatible build | Use the pre-mod backup and follow the mods guide | Deleting the original backup |
| File looks unreadable | Binary or compressed format | Copy it and use the game or official support path | Editing it in a text editor |
Safe recovery rules that prevent a worse loss
Save recovery is a file-management task, not a reason to download a suspicious executable. Avoid trainers, cracked builds, random save packs, and websites that ask you to run an installer before showing a path. The existing download guide explains the official Steam route; this page stays focused on protecting data you already own.
- Stop writingClose the game and wait for Steam to finish any visible sync before touching the folder.
- Copy, never moveDuplicate the entire candidate folder and leave the original in place until recovery is confirmed.
- Label the evidenceRecord build, date, Windows account, Steam profile, and why each copy was created.
- Restore graduallyTest one duplicate, launch once, and preserve the result before trying another candidate.
Sources and verification boundary
Public Steam and community references help identify the places worth checking, but the exact save path can change. Use the current Steam client and the files created by your own controlled test as the final evidence.
- Official Voidling Bound Steam page - Official platform, app ID, store and support context.
- SteamDB user-files record - Public Steam file metadata used as a lead for app and cloud data, not as a guarantee of every local path.
- Steam Community save discussion - Player discussion that helps compare reported save locations and recovery symptoms.
- Valve Steam Cloud documentation - First-party background on Steam Cloud behaviour and the reason to keep a manual backup.