House Flipper 2 Save File Location and Backup Guide

The House Flipper 2 save file location on Windows is the folder below. Close House Flipper 2 before working with it, then paste the path into File Explorer's address bar. The developer's PC recovery instructions identify Profiles as the current saves folder and Profiles.backup as its neighboring backup folder.

%appdata%\..\LocalLow\Frozen District\House Flipper 2

Before replacing anything, copy the entire House Flipper 2 folder to a separate location. That is an additional preservation step recommended by this guide, so your original profiles, backups and logs remain available if a recovery attempt fails. The following procedure is based on the official PC recovery article, not a recovery performed on your files.

Identify the two folders before making changes

Inside the game data folder, find Profiles and Profiles.backup. The first contains the profiles the game currently reads; the second contains saved backup versions. Do not assume that the newest-looking folder is automatically the right recovery source, or that the two folders are interchangeable.

The official article explains that profiles are identified numerically, starting with 0 for the first created profile and increasing for later ones. Those numbers matter when choosing a destination. Restoring one profile means matching its number between the backup and current folders, rather than placing one player's progress over a different profile.

Preserve the complete current state first

Keep the game closed while copying the whole game data folder somewhere outside the live location. Give that copy a name that makes it easy to recognize as the state before recovery. Check that the copied folder contains both profile folders before proceeding, rather than assuming a completed copy operation preserved the intended files.

This extra copy is separate from the game's own rotating backups. It lets you preserve the current evidence while following the developer's replacement procedure, without depending entirely on the same backup set you are about to inspect. Do not delete Profiles, Profiles.backup or the whole game data directory as a general troubleshooting experiment.

Understand the backup schedule and its limits

Developer support says the game creates backup saves during play sessions lasting more than 60 minutes. It describes three retained backups: two refreshed hourly during gameplay, plus one associated with the previous day of play. That is the documented condition, rather than a promise that a fresh backup exists after every short session.

The recovery article presents this schedule as protection against lost progress, but it cannot prove the condition of an individual player's files. A recent interruption may still leave you choosing between older checkpoints, and a dated folder is not evidence that every file inside is healthy. Inspect the backups actually present before deciding how much progress may be recoverable.

Choose a checkpoint for the correct profile

Look inside Profiles.backup for the profile you need and the available dated backup folders. The dates and times identify checkpoints to compare with your last known working session. Keep the profile number with that information so you do not choose a plausible date from the wrong profile.

Support notes that the top-level folders can share modification dates, while the files inside have dates reflecting activity in the game. If the folder listing is confusing, inspect the relevant contents instead of relying on one timestamp alone. The useful question is which backup contains the state you intend to recover, not simply which item sorts last.

Restore contents into the matching live profile

The developer's full-profile method copies the contents of a chosen backup into the live profile with the same number. For example, a backup belonging to profile 0 must go into live profile 0. Do not paste it into another profile number or replace the whole Profiles directory with a dated backup container.

Use this sequence only after preserving the complete game data folder elsewhere:

Confirm that House Flipper 2 is closed.
Open the selected dated backup for the affected profile.
Copy all of that backup's contents.
Return to Profiles and open the live profile with the identical number.
Preserve that live profile's existing contents outside the game folder, then replace its contents with the copied backup contents.
Launch House Flipper 2 and inspect the restored profile.

The official article describes clearing the destination contents before pasting the backup. Keeping those contents elsewhere first makes that replacement reversible at the file level. Do not mix files from unrelated profiles or improvise a merge when you cannot identify the intended source and destination.

Check the result before continuing a long session

Open the expected profile and inspect the progress or property that prompted the recovery attempt. Confirm that you selected the intended checkpoint before treating the game as restored. A successful launch alone does not establish that the particular house or task you wanted has returned.

If the result is wrong, close the game before making further file changes. Keep your preserved original copy and note which backup you tested so the next attempt is deliberate. Avoid a long troubleshooting play session while undecided about recovery, because the documented hourly backup rotation can change the backup set.

Use individual-house recovery only when you can identify it

The support article also allows copying only the affected files for a Sandbox or Story house. That is a narrower alternative to restoring a complete profile, but it depends on recognizing the specific files involved. The acquired documentation does not supply a universal filename-to-house map in this guide.

If you cannot identify the correct files confidently, do not guess or delete neighboring files to see what happens. Preserve the current folder and ask official support which files are relevant. The Sandbox guide covers building and sharing workflows separately from this save-recovery procedure.

Keep console recovery separate from Windows folders

Developer support says it does not store console player saves. Its console advice points players to PlayStation Plus or Xbox cloud saves for reloading progress or a profile. The Windows Profiles.backup procedure therefore should not be presented as a console file-management method.

This guide has not verified a platform-specific cloud restoration sequence or the availability of a particular player's cloud copy. Use the instructions for your actual console and account, and check the dates of any available saves. Do not assume that having an online account establishes that a usable older checkpoint exists.

Treat old Documents migration errors as a separate issue

The developer has a separate support article about older saves migrating from Documents to the LocalLow game data location. It concerns that historical migration problem, rather than every case of missing progress. Finding old instructions that mention Documents does not make that directory the current default path for this Windows recovery guide.

Match the error you see to the relevant official article before moving files. If the problem remains unclear, preserve the game data folder and include its Player.log and Player-prev.log files when official support requests them. Those logs can provide diagnostic context; their existence does not itself prove that the saves are recoverable.