Save Files & Console / inZOI / Unreal Engine 5

inZOI: Save File Location, Cloud Conflicts & Console Commands

Back up and repair inZOI saves, resolve Steam Cloud version conflicts, and open the developer console or launch options with the correct argument set for Unreal Engine 5.

Cover artwork for inZOI on the GamePathHub field file.

Find the save before you repair it

inZOI stores progress and settings in different places. Confusing the two is how people delete a working profile while trying to fix a graphics problem. Locate both, copy both, then work on a copy.

Save and configuration locations

%LOCALAPPDATA%\inZOI\Saved\SaveGames\
SAVE PROFILE: %LOCALAPPDATA%\inZOI\Saved\SaveGames\
CONFIGURATION: %LOCALAPPDATA%\inZOI\Saved\Config\Windows\GameUserSettings.ini

BACKUP ORDER:
1. Copy the save folder while the game is fully closed.
2. Copy the configuration folder separately.
3. Zip both with a dated name before any repair.
Paths are verified against Early access build — live verification. A launcher update or a mod manager can move them.

Steam Cloud conflicts

A cloud conflict appears when two machines both wrote a profile and Steam cannot decide which is newer. The safe sequence is: close the game, let Steam finish syncing, note the local file timestamp, then choose the local file deliberately rather than accepting the default prompt. Never launch a second machine while a sync is in progress.

Recover a corrupted inZOI profile

Verified recovery

Work from the backup, not the original.

  1. Copy the current profile folder to a dated backup.
  2. Restore the most recent known-good backup into a clean folder.
  3. Launch with Steam Cloud disabled for this title so the restore is not overwritten.
  4. Load the save, save once manually, close the game, then re-enable Cloud.

Launch options and the developer console

Most Unreal Engine 5 builds accept a small, documented set of launch arguments. Keep the list short: a windowed or borderless flag when the display mode is stuck, a language override, and a safe-mode flag if the build provides one. Arguments that inject DLLs or disable integrity checks are not troubleshooting steps; they are a separate risk category.

If the build ships a developer console, bind it in the input settings rather than editing files. A console toggle written into the wrong configuration file can be overwritten on the next patch.

Verify the restore

Save integrity for inZOI

0 / 5 complete

The line to keep

A backup you have restored once is real. A backup you have only created is a hope. Test the restore before the patch that makes it necessary.

Did this fix work on Patch Early access build — live verification?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against Early access build — live verification. Votes are local-only telemetry.

inZOI: bench questions

2 answers
Is this inZOI fix safe for my current save?
Yes when you back up the profile first. The routine changes configuration and caches, not the save file itself. If a fix edits an active save, the file path and the backup step are called out in the guide.
How do I know the save files & console fix worked?
Repeat the same action that failed before the change and compare like for like. For crashes, that means a cold launch. For frame pacing, that means the same route with a frame-time capture. A fix you cannot re-test is not verified.
Filed under

Save Files & Console

Patch tested: Early access build — live verification

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.