Underkeep Demo Save Compatibility: What Carries Over?

The direct developer answer

The most important source is the developer's reply to the save-transfer question. It explicitly rejects compatibility between the demo and the full release rather than describing a missing menu option. Buying the game therefore should not be planned around continuing the exact demo save you have already created.

Treat this as a product boundary, not a puzzle to solve inside the demo. Your experience with controls, combat and party planning remains useful when starting again, but the saved state itself is a separate matter. A familiar quest or returning environment does not override the developer's compatibility explanation.

Different levels explain the incompatibility

The developer says the full game's forest and mushroom encounter placement differ from the demo. A save records progress within a particular version of that world, so it cannot simply be assumed to describe the changed release layout. The official answer connects the incompatibility to those level differences.

This also explains why a demo route should not be used as a precise guide to the full version. Knowing where a pickup appeared in an older demonstration does not establish where the release-game encounter occurs. Keep route compatibility and save compatibility together when deciding whether an old guide still applies to your playthrough.

The September demo break is a separate issue

On September 12, a player reported that saves from the earlier demo no longer worked after an update. A developer confirmed that break in the discussion about the updated demo. This concerns two versions of the demo rather than a transfer from the demo to the paid release.

The distinction matters when describing what went wrong. A failed old-demo save does not demonstrate that a newly created demo save can be imported into the full game. Conversely, the full game's incompatibility does not mean every save problem inside the demo has the same cause or appeared on the same date.

Identify which boundary your save is crossing

First identify whether you are launching the dedicated demo or the full game. Next establish whether the save was created before the September demo update discussed by the developer. Those two details place the problem within one of the confirmed compatibility boundaries instead of leaving you with the vague description that a save is broken.

Keep a note of the product and build when asking for help. A discussion about the release game is easier to interpret when readers know that the file came from a historical demo. Clear version information also prevents another player from suggesting a route or control instruction that belongs to a different product.

Steam Cloud does not change the developer's answer

The demo listing includes Steam Cloud as a feature. That establishes a cloud-storage feature for the demo, but it is not a promise that a different game product can read or convert its saves. The developer's explicit no-transfer answer remains the relevant statement for demo-to-release compatibility.

Separate the question of where a file is stored from the question of which version understands it. A synchronized file can still belong to the earlier product and world layout. Looking for a cloud setting therefore should not be treated as a documented way to continue the demo's progress in the full release.

Plan your transition to the full game

When deciding whether to play more of the demo, regard it as a self-contained introduction. Use the time to become comfortable with the party interface, exploration and turn-based encounters. The practical benefit is familiarity with the game, rather than an expectation that every completed objective will appear as completed after purchase.

When you install the full version, begin with its own opening flow and current instructions. The game's changed layout makes that a useful transition even if you remember much of the demo. Use release-specific party and exploration guidance instead of trying to force the old map to explain a new location.

Describe a compatibility problem clearly

If you report a save issue to the official community, include whether you are using the demo or full release. Add the version in which the save was created and the version in which you are trying to load it. If the problem appeared after the September update, mention that timing rather than describing it as a failed purchase transfer.

This information makes a report actionable without requiring you to guess a technical cause. It also keeps two developer-confirmed situations from being combined into a single misleading story. The useful first step is identifying the versions involved, not changing a file based on advice that never names its source build.

Separate compatibility from the decision to keep playing

The no-transfer answer tells you what to expect from the saved file, but it does not make the demo's experience irrelevant. You can still use the demonstration to learn how you feel about the turn-based pacing, party interface and exploration before deciding whether to start the full game. What changes is the expectation of continuing the same recorded world state after that decision.

If you are close to the end of a demo run, decide whether finishing its own quest is worthwhile to you as a self-contained activity. Do not treat completion as a technical requirement for unlocking a transfer that the developer has ruled out. Likewise, do not assume that skipping a demo outcome prevents a fresh start in a separately purchased release product.

This distinction keeps the practical decision straightforward. Use the demo to learn or complete its own slice, then approach the full release as a new playthrough in a changed world. That preserves the value of the time spent learning without replacing the explicit compatibility answer with an imagined conversion step.

Choose guides that match the new playthrough

The same version distinction applies to walkthroughs and quest checklists. The demo's mushroom search and the full game's altered encounters can share a theme while requiring different directions. A save-transfer answer is therefore also a reason to check the version label on the next guide you open.

For the full release, start with the beginner and party guides, then use the map to record your own progress. For an older demo run, retain the historical demo label when comparing reports about crates, rubble or quest outcomes. This preserves the useful knowledge from your first run while keeping incompatible world states separate.

Related guides