How to Back Up Visual Novel Saves on Windows and Steam Deck

By NeonCritic Editorial · Save-preservation guide · Checked 10 October 2026

Back up visual-novel progress by identifying the actual save directory, closing the game, copying the complete relevant data, and testing a restoration from a separate copy. Keep the original untouched until the test succeeds. Windows, native Linux, and a Windows build through Proton can use different locations, even for the same title.

Scope: We consulted Ren’Py and Valve documentation. We have not inspected your files or tested a title-specific migration. There are no affiliate links. The cover is conceptual AI-generated artwork.

Identify the game and its save system

Record title, edition, storefront, game version, operating system, and compatibility tool if used. Start with the creator’s save-location instructions. Do not assume every visual novel uses Ren’Py or that every Ren’Py project uses the default configuration.

Separate the installed application from progress data. Copying the game directory may preserve the executable while missing external saves. Conversely, preserving saves alone does not preserve the compatible game build needed to load them.

Write down which directory you identified and why. A location supported by creator documentation is stronger evidence than a folder selected because its name looks familiar. Keep uncertain candidates separate until a controlled save check resolves them.

Use Ren’Py defaults as a starting point

The official configuration documentation describes default user-save roots based on the configured save-directory name. On Windows the root is %APPDATA%/RenPy/; on native Linux it is ~/.renpy/. The game-specific subdirectory and configuration still matter.

Those paths are starting points, not a universal promise. A project can use a different configuration, including a saves folder associated with the game. The runtime’s actual path is represented by config.savedir; readers should normally use creator instructions rather than modify game code.

A Windows build through Proton uses a Windows environment inside its compatibility arrangement. Do not assume its save resides in native Linux’s Ren’Py root. Identify the particular game’s environment and preserve its data before changing tool or shortcut settings.

Confirm the directory with a controlled save

If the game permits manual saves, create a uniquely labeled one and close the application normally. Inspect which candidate directory changed at that time. Correlate filenames and timestamps with the action without deleting anything.

Keep the check narrow. A folder containing old data from another edition can look convincing but still be wrong. Record the source build and the time of the new save so the evidence is understandable.

If the title does not expose a useful manual-save option, consult its creator’s documented location. Do not force an unsupported console or edit configuration just to match a generic guide. The correct method depends on the actual product.

Copy the full relevant data

Close the game before copying. Preserve the entire identified save directory, including persistent or profile files when relevant. An individual slot may not capture unlocked galleries, preferences, or other progress stored separately.

Place the copy in a dated folder outside the working installation. Include a small text record of title, version, platform, and original path. Keep the archive somewhere that will not be overwritten by the update or reinstall you are preparing.

Use copy rather than move. Check that the destination contains the expected files and can be opened. A folder name that says “backup” is not evidence that the operation completed correctly.

Keep cloud synchronization separate

Valve’s Steam Cloud guidance explains that integration is game-specific and lost saves may not be recoverable. A synchronized file is not an independent history of every earlier state.

Before testing restoration, inspect the game’s cloud arrangement and any conflict prompt. Preserve both local candidates independently before choosing one. Do not resolve a conflict by guessing from a timestamp without considering where you last played.

Playing on another device before synchronization completes can complicate the state. Keep a clear record of which copy you intend to preserve. Use the current platform instructions for managing the specific conflict rather than deleting every cloud-related folder.

Test restoration without sacrificing the original

Use a compatible installation and a separate copy of the backup for the test. Preserve the current working saves first. Restore according to the creator’s instructions, then launch and load a known slot.

Check the expected scene and progress, not merely whether the slot appears. If persistent unlocks matter, inspect those too. Quit without overwriting your only verified copy, and retain the original archive afterward.

Ren’Py’s save documentation warns that compatibility is not guaranteed between every release. If a save fails after an update, the backup may be intact while the new build is incompatible. Keep the matching lawful game files where permitted.

Maintain a modest archive

Take a new dated copy before changing edition, applying a significant patch, or moving devices. Keep more than one known-good generation instead of replacing the previous archive immediately. Choose a retention routine that matches your available storage.

Do not load arbitrary saves from strangers to test your installation. Use your own known files or a trusted creator-provided source. A technical save format can contain executable state, so source trust matters independently of story progress.

Caveats

• Default engine paths do not cover every title or Windows-through-Proton arrangement.
• Cross-edition and cross-version save compatibility must be verified with a preserved copy.
• Cloud synchronization and an independent, tested backup serve different purposes.