Game Install Folder vs. Save Folder: Know the Difference

Moving or reinstalling a game becomes less confusing when you separate three things: the files that run the game, the settings that configure it and the progress you want to preserve. They may not all live in the same directory. A successful copy of the installation is not proof that your latest checkpoint was included.

Installation files are not a universal save archive

The installation folder contains the files used to run the game. Save data may instead live under the active user’s Documents, Saved Games or AppData locations. The official Hades and Cyberpunk 2077 support guides provide examples of user-data paths distinct from a generic installation directory. 1 2

Use the exact game’s documentation rather than assuming that every title follows those examples. Some setups use custom profiles or other storage methods, so verify the active location before making a backup plan.

Settings and progress can be separate too

A configuration file may control display or input preferences without containing the checkpoint you want to transfer. Supergiant’s Hades technical guide discusses configuration troubleshooting separately from progress recovery. Do not substitute a similarly named settings file for the full save data. 1

Conversely, a complete routine backup may preserve companion files that are useful for identifying or restoring the save. Keep the documented structure intact until you understand what each file does.

Confirm what your backup tool includes

Read the scope of a launcher or installation-backup feature before relying on it. Steam’s backup documentation is the appropriate reference for that feature; it should not be treated as a guarantee that every game’s independent save location is preserved. 3

The practical question is simple: can you identify the archived progress files and restore the intended checkpoint? A large archive or successful backup message does not answer that question by itself.

Prepare before uninstalling or moving a game

1. Identify the exact installation and active save profile.
2. Find the documented save path and verify it against a recognizable recent save.
3. Close the game and copy the relevant save directory outside the installation and active save locations.
4. Record the build, storefront, dependencies and checkpoint in a separate note.
5. Confirm that the independent backup contains the expected files before changing the installation.
6. After reinstalling or moving, verify the destination path and test loading, saving and reloading.

Do not delete leftover directories simply because they look untidy. First determine whether they hold the only copy of an old profile or progress you still need.

Keep the two troubleshooting questions separate

When a game fails to start, installation or configuration checks may be relevant. When a save is missing or fails to load, the active path, file structure and compatibility deserve their own investigation. Reinstalling the game is not a universal method for restoring deleted progress.

A clear backup note records both the installation you used and the save location you verified. That small distinction makes a later migration far easier to understand and avoids relying on assumptions about what a launcher copied.

Frequently asked questions