Warhounds Save File Location, Backup, and Restore Guide

Quick Answer

The Steam Cloud configuration for Warhounds points to this Windows folder:

%USERPROFILE%\AppData\LocalLow\EverPlay\Warhounds\Save

The configured file pattern is *.mdb. This is strong platform-configuration evidence, but it is not the same as opening the folder on every retail installation. After creating a new save, close the game and confirm that the most recently modified .mdb file is inside that directory before treating it as your active save location.

What the evidence confirms

Item	Status checked August 25, 2026	Practical meaning
Steam Cloud	Listed by Steam	The Steam build advertises cloud synchronization.
Configured root	WinMyDocuments	Steam resolves the path relative to the current Windows user profile.
Relative path	AppData/LocalLow/EverPlay/Warhounds/Save	Use the singular Save folder unless your own installation shows otherwise.
File pattern	*.mdb	Back up every matching database file and the containing folder.
Local retail test	Still needed	Match timestamps after saving and exiting the current build.

SteamDB exposes Steam’s cloud configuration in a readable form, but its own wording is intentionally cautious. A path configured for synchronization can change, and a machine may contain old, migrated, or test files. The timestamp check prevents you from backing up the wrong folder simply because its name looks plausible.

How to open the Warhounds save folder

1. Exit Warhounds normally.
2. Press Win + R to open the Windows Run dialog.
3. Paste %USERPROFILE%\AppData\LocalLow\EverPlay\Warhounds\Save and press Enter.
4. If the folder opens, sort by Date modified.
5. Confirm that one or more .mdb files changed after your most recent in-game save.

If Windows says the path does not exist, do not create an empty folder there. Start the game, create or update a save, exit cleanly, and check again. Also confirm that you are signed into the Windows account that launched the game.

Make a safe backup

Back up the whole Save directory, not just the file with the newest timestamp. Multiple database files can represent different profiles, campaigns, or supporting state, and copying only one file may produce an incomplete restore.

1. Close Warhounds and wait for Steam to finish synchronizing.
2. Copy the entire Save folder to a location outside the game directory.
3. Name the backup with the date and patch context, such as warhounds-save-2026-09-28-update-1.0.2.
4. Keep a second copy before installing an update, testing a trainer, or changing game files.
5. Open the backup and confirm that the .mdb files have non-zero sizes.

A cloud copy is useful, but it is not a substitute for a dated offline backup. A damaged or unwanted state can synchronize just as successfully as a good one.

Save/status fixes through Major Update 1.0.2

Patch 1.0.1 fixed certain statuses failing to persist across save and load cycles. Major Update 1.0.2 later lists additional status-saving bugs during save/load among its developer fixes. Neither announcement names every affected status or promises that every old save repairs itself.

Treat both as developer-listed fix scope, not independent proof that all persistence problems are gone. Before updating or restoring, keep a separate pre-change backup. After loading, verify the campaign map, current mission, roster availability, equipment, and any status that matters to the next decision. If something still fails to persist, preserve both the before-load and after-load copies and report the exact status, save option, mission, and installed patch.

Restore without creating a cloud conflict

Only restore a save after preserving the current folder as a separate backup.

1. Exit Warhounds and close Steam if it is still synchronizing.
2. Rename the current Save folder to a dated recovery name instead of deleting it.
3. Copy the backed-up Save folder into ...\EverPlay\Warhounds\.
4. Start Steam and read any cloud-conflict prompt carefully; choose the copy whose timestamp and size match the intended restore.
5. Launch the game and verify the campaign, mission state, roster, and save date before overwriting anything else.

This workflow is deliberately reversible. If the restored copy fails, you still have the folder that was active immediately before the attempt.

Steam and Epic saves are not assumed identical

The path above comes from Steam Cloud configuration. The Epic Games Store version is available on Windows, but this wiki has not verified Epic cloud-save support, its local directory, or cross-store compatibility. Do not move a Steam .mdb file into an Epic folder until both builds, folder layouts, and file versions have been checked on the same patch.

The platform and system requirements page tracks storefront-specific evidence. The trainer and cheats page explains why a save backup should be completed before testing any unsupported tool.

Mission save options are a separate question

Save location and save rules are not the same thing. A post-launch developer answer describes three options:

1. save whenever you want, except during the first tutorial missions;
2. save only at mission start and mission finish;
3. Ironman, with one save for the whole game updated each turn.

The answer does not provide the exact in-game option names, say whether they can be changed mid-campaign, or document achievement effects. See the difficulty settings guide for those boundaries.

Frequently asked questions

Why does the path use Save instead of Saves?

The Steam Cloud configuration uses the singular folder name Save. Do not substitute a common Unity folder name from another game. Your own file timestamps remain the final local check.

What files should I back up?

Copy the whole Save directory and all .mdb files inside it. A single newest file may not contain every campaign or supporting record.

Can Steam Cloud recover a deleted save?

It may synchronize an available remote copy, but it can also propagate a deletion or unwanted state. Preserve a separate local backup before testing recovery.

Can I use the Steam save in the Epic version?

Cross-store compatibility is not verified. Treat the stores as separate until the current builds, directory layouts, and database versions are compared directly.

Did the recent patches fix save problems?

Patch 1.0.1 fixed certain statuses failing to persist across save/load cycles, and Major Update 1.0.2 lists further status-saving fixes. The notes do not identify every affected status or guarantee that all older-save problems are repaired, so preserve a backup and verify important state after loading.

Conclusion

Use %USERPROFILE%\AppData\LocalLow\EverPlay\Warhounds\Save as the configuration-backed starting point, then confirm it with .mdb timestamps on your own machine. A full, dated folder copy made while the game is closed is the safest rollback point.