IGTAPGuide
Menu

Save safety

IGTAP Save File Location and Backup Guide

Last verified: September 27, 2026Applies to: Full release, through Hotfix 3Needs verification

Quick answer

The exact IGTAP save path for Windows, SteamOS, and Linux remains unverified, so this guide does not publish a guessed folder. Exit the game first, keep Steam Cloud state unchanged, and locate candidates by recent modification time and game-related filenames. Copy plausible save, backup, and log files into a separate dated folder; never move or overwrite the originals. Hotfix 3 confirms that the game now creates backup saves and more detailed save logs. A valid backup process is complete only when the copied files remain intact outside the live save area and can be matched to the expected play-session timestamp.

Symptoms

You may need a backup before troubleshooting lost progress, moving between systems, preserving evidence for a bug report, or testing an officially supported recovery. The exact IGTAP save-file location has not been verified for Windows, SteamOS, or Linux. Publishing a familiar-looking application-data path would create a false sense of certainty, so this guide uses a discovery method instead.

Before touching any candidate, exit IGTAP. If Steam shows a synchronization operation or conflict, let the normal operation finish only when no conflict decision is required. Do not disable Cloud, uninstall, or move folders while you are still identifying the files.

Likely causes

Players often search for the save path because different games store files under user data, engine-specific folders, Steam data, or another platform location. Install files and save files are also easy to confuse. An IGTAP executable or asset folder is not evidence that progression is stored beside it.

Hotfix 3 confirms that backup saves and more detailed save logs exist in the current release line. It does not publish their filesystem paths or naming scheme in the official material reviewed here. Steam Cloud is listed as a feature, which means a local copy operation must be planned with synchronization in mind.

Fixes in safe order

  1. Exit the game. Record the time of the final known-good play session.
  2. Create a destination first. Make a new folder outside any live game or Steam directory. Name it with the date, device, and reason for the backup.
  3. Search by recent change. Use the operating system’s file search or storage tools to inspect files modified during the final session. Narrow candidates using game-related names and nearby logs, but do not declare a path confirmed from a name alone.
  4. Compare timestamps. A plausible set should have modification times consistent with launching, saving, and closing IGTAP.
  5. Copy the whole plausible set. Include candidate primary files, backups, and logs. Preserve folder structure when practical. Never move, rename, or edit the originals.
  6. Record a manifest. Save a screenshot or text note listing the original location, filenames, sizes, and modification times.
  7. Keep Steam Cloud unchanged. A backup is preservation, not a Cloud reset. Do not use synchronization to test an uncertain file.

If you are responding to missing progress, continue with the lost progress recovery checklist only after these copies exist.

How to verify the fix

A safe backup is a separate, readable copy that remains unchanged when the live game later saves. Check that the destination contains the expected number of files and that their sizes match the source at the time of copying. Keep the manifest with the backup. Do not test validity by overwriting your only working save.

If you later receive a developer-confirmed restore procedure, make another copy of the current live state before following it. Test restoration only from a duplicate and keep the oldest preserved set untouched. For demo data, read the official transfer answer: incompatibility with the full game is expected.

When to stop and wait for a patch

Stop if recent-file search finds several indistinguishable candidates, Steam presents a conflict you cannot resolve from timestamps, or the only available copy changes while the game is closed. Do not guess which file is primary based on an extension alone.

Ask for official guidance with your operating system, game version, candidate locations, filenames, timestamps, and log files. Avoid publicly posting personal account paths or unrelated system information. Until the developer or a directly reproduced test confirms the path, label it Needs verification.

Sources and verification status

Officially confirmed: IGTAP supports Steam Cloud. Hotfix 3 added backup saves and more verbose save logging. These facts justify preserving cloud state, backups, and logs.

Needs verification: exact Windows, SteamOS, and Linux locations; filename format; automatic backup count; restore priority; and whether every installation uses the same path. This page intentionally contains no guessed directory.

Related guides

Lost Progress or Watts→Demo Save Transfer→Rare Achievements→

Source and verification notes