Orc Incremental Save Location

Quick facts

Platform

Windows

Windows folder

%APPDATA%/OrcIncremental

Safety step

Copy the folder before manual file operations.

Save editing

Not advised

Back up before inspecting

The fact panel provides the official Windows location and safety boundary. The key art is generic; it does not show a filesystem, Steam Cloud state, or backup result.

Close the game before opening the folder. Create a dated copy in a separate location and confirm that the copied folder is present. Keep the original untouched. A backup on the same disk protects against a mistaken file operation, but not against disk loss, so a second device can provide additional safety.

Use the Demo save transfer guide for compatibility wording and Steam Cloud for the official backup statement. The known issues ledger should receive a reproducible symptom, not unverified file surgery.

Open the Windows environment location

Use the Run dialog or File Explorer address bar and enter the registered environment-based path exactly. An environment variable resolves per Windows user, which is safer than copying another player’s absolute username path.

If the folder does not appear, stop and record:

• Windows account used to run the game;
• Steam account and game build;
• whether the game has created progress on this account;
• the exact path entered;
• whether hidden items or permissions affected the view;
• any Steam sync prompt shown before launch.

Do not create a replacement folder merely because it is missing. A different account, uninitialized state, or version change may explain the observation.

Verify a backup without altering contents

Compare the source and copied folder names, item counts, and timestamps at the filesystem level. Store the date and game build in a note outside the folder. Do not open unfamiliar files in a program that might rewrite them automatically.

For a before-and-after troubleshooting record, preserve one copy before the symptom check and another only after the game is closed. Label both rather than overwriting the first.

Keep other platforms unknown

The checked official source supplies a Windows location. It does not establish an official macOS, Linux, Proton, or handheld path. Platform conventions and community reports may suggest places to inspect, but they are not adopted here as game facts.

If an official source later publishes another location, add it with its platform, build, and check date. Do not generalize the Windows environment variable.

Report a missing or stale save safely

Record the build, Steam account, local folder presence, file timestamps, Cloud prompt, and in-game state. Avoid repeated launches while the state is unclear, because each launch can change timestamps or sync decisions.

The purpose of this guide is recovery-safe observation: establish the official location, preserve a copy, and gather enough context for the next troubleshooting step without changing the evidence.

Know when to stop

Stop if the folder timestamps change unexpectedly, Windows requests elevated access you did not anticipate, Steam displays a conflict, or the expected account context cannot be confirmed. Preserve screenshots and the dated copy rather than trying more file actions.

A support request should say which official path was checked, whether the game was closed, when the backup was created, and which symptom prompted the inspection. It should not include personal directory names or file contents in a public post. Clear boundaries protect both the save and the diagnostic record.

Official source

Verification boundary

Build boundary

official Demo-retirement announcement

Evidence check

2026-08-28

Still unknown

official macOS path, official Linux path, internal save-file format

Frequently asked questions

What is verified about Save Location?

The official Demo-retirement announcement identifies the Windows save folder as %APPDATA%/OrcIncremental. Boundary: official Demo-retirement announcement. Checked 2026-08-28. Copy the entire folder before any manual file operation, close the game first, and do not edit save contents; no macOS or Linux path is published in the checked source.

How should a manual backup be verified?

Close the game, create a dated copy of the entire folder in a separate location, and confirm that the copy exists before touching the original. Work only with the copy for inspection.