Emberville demo save transfer to Early Access was announced for the public Steam Next Fest demo. Creator & Press Preview saves were explicitly excluded. Keep those two builds separate: a general claim that every prerelease save carries over is too broad.
As of October 28, 2026, Early Access has not launched. Its planned release moved to January 7, 2027. The public-demo carryover statement predates that postponement, so it is an announced intention rather than a completed, tested import into the delayed launch build. Preserve your public demo progress, then check the launch instructions when Early Access becomes available.
Identify the build that created your progress
The important first question is which build you played. If you downloaded the public demo through Steam during the October event, that is the demo covered by the carryover statement. If you received an earlier creator or press preview, that access belongs to the excluded category.
Do not decide solely from a video's title or the word demo in a conversation. Preview coverage and public-demo coverage can describe similar opening content while referring to different builds. Your own access history is more useful: how you obtained the build, when you played it, and whether it was the public Steam demo.
The October 22 update labeled Demo Alpha 0.20.18.x belongs to the public demo line. A later public-demo patch does not turn that build into the earlier Creator & Press Preview. Conversely, having played similar content earlier does not establish that the earlier save qualifies for transfer.
If you played both versions, keep the distinction in your notes. Preserve the public demo progress separately from any excluded preview progress and seek build-specific guidance if the files or access history are unclear. Do not overwrite one with another in an attempt to make them eligible.
Identify which product created your save; separate store panels do not demonstrate save compatibility.
Understand what the announcement does and does not promise
The supported statement is that public demo progress is intended to continue into Early Access. It does not provide a verified item-by-item migration table, an import-button walkthrough, or a cross-store transfer procedure. Those missing details should not be filled with assumptions.
A promise about progress also does not automatically include every local option or control preference. Character continuity and configuration continuity are different questions. Be prepared to review settings when the next build launches rather than assuming all options will appear exactly as they did in the demo.
The creator-preview exception is equally important. Excluded preview saves should be expected to start fresh in Early Access unless the developer provides a later, specific change to that rule. Renaming a file or copying it into another folder is not an established way to convert that exception into supported progress.
| Build or transfer question | Current supported status | Practical action |
|---|---|---|
| Public Steam demo progress into Early Access | Carryover announced before postponement | Preserve it and check delayed-launch instructions |
| Creator & Press Preview progress | Explicitly excluded | Plan for a fresh start unless the rule changes |
| Public demo import into the January launch build | Not yet tested because Early Access is unreleased | Do not describe it as completed migration |
| Steam progress moved to another store | No verified procedure established | Do not buy or move files assuming portability |
| Early Access progress into final 1.0 | Separate, unconfirmed compatibility question | Wait for release-specific guidance |
Preserve progress while waiting
The safest immediate action is to keep the eligible public demo save intact. Do not reset the character, clear the entire local-data folder, or use an aggressive cleanup operation merely because the demo session has ended. Those actions can remove the progress you want to carry forward.
A backup is a reasonable precaution before you change installations or local files, but it is not an official import procedure. Keep any copy separate from the live game data and make sure you can identify which build it came from. Do not replace current files with an older copy just because both contain similar opening progress.
If you cannot confidently identify the character-save files, stop before moving them. A folder can contain both settings and progress. The fact that a language workaround targets an options file does not mean everything in the same directory is safe to delete or interchangeable.
Record a few visible details of your current character, such as the name and where you stopped, if you want a reference for later. That does not prove which fields will transfer, but it can help you recognize whether the expected character appears when the future build loads.
Keep cloud sync separate from build compatibility
Cloud synchronization and save compatibility solve different problems. A cloud service can move or retain files without proving that a different game build can interpret them correctly. Do not treat a cloud-support label as a guarantee that demo-to-Early-Access migration has already been validated.
Likewise, playing on more than one device adds another question: whether the same current progress is present on both installations. That does not establish the future import process. If you use several devices, keep track of which one has the progress you intend to preserve before making changes.
Avoid resolving a synchronization conflict by guessing which copy is newer. Check the visible character state and any client information available to you, then preserve a recovery copy before choosing between files. This is general data-preservation advice, not a tested Emberville cloud-recovery method.
There is no verified instruction here to disable synchronization, force an upload, or replace a remote save. Use build-specific guidance if such a step becomes necessary. An unnecessary change to synchronization can create an additional problem while you are trying to preserve a future transfer.
Your own character name, progression and inventory can be recorded before a future import; this is not a transfer result.
Recheck the rule when Early Access becomes available
The delay matters because the transfer has not yet happened against a released Early Access build. When that build becomes available, read the current save instructions before launching a manual file operation. The January date is a release plan, not a guarantee that every migration detail is already fixed.
Begin with the normal supported route described at launch. Do not preemptively rename folders, convert file extensions, or copy a save into an assumed location. A complete manual migration sequence is not confirmed for the delayed launch build; wait for its instructions before moving files.
After the future build loads, check whether the expected character is present and whether its recognizable progress appears. A character name alone may not confirm every aspect of continuity, so inspect the ordinary game state before deleting your retained demo copy.
If progress appears correctly, continue only far enough to confirm that the character loads and normal play works. Keep the earlier recovery copy until you are satisfied that the supported transfer has completed. Removing it before that check would discard your fallback without establishing a successful result.
If the expected character is missing after launch
First confirm that the progress came from the public demo rather than the excluded preview. That distinction should come before troubleshooting because an excluded build's failure to appear is not evidence that the public-demo promise failed.
Next, check that you are using the intended account, installation, and current release build. These are general identity and installation checks, not a tested fix. Record what the new build shows before creating replacement progress or changing local files.
Describe the problem with the build source, demo version, and visible character details. State whether the old public demo still shows the progress you expected to import and whether the new build shows no character or a different one. That is more useful than reporting only that saves do not work.
Do not overwrite the retained demo save with a fresh Early Access character while trying to diagnose the issue. A new character may be useful for testing the game itself, but it does not recover the earlier progress. Keep the two questions separate and wait for instructions addressing the actual import symptom.
Avoid unsupported cross-store and final-release assumptions
The current carryover statement should not be stretched into a promise of portability between every store, device, or future release. Windows PC availability on more than one storefront does not establish that files, account entitlements, or import paths are identical.
If store choice matters because you want to continue demo progress, wait for an explicit compatibility statement about that route. Do not purchase on the assumption that a Steam public demo save will automatically appear elsewhere. A general announcement about demo progress is narrower than a complete cross-store migration policy.
The eventual 1.0 release is another separate boundary. Early Access is expected to evolve, and future systems or platforms do not establish save compatibility today. Do not describe the public-demo promise as a guarantee that every later version will retain every character unchanged.
Keeping these questions separate makes the immediate decision clearer: preserve the public demo progress you have, identify its build correctly, and follow the next release's actual import instructions. You do not need to solve every future portability question before keeping an eligible save safe.
Decide how much demo progress to invest now
If you enjoy the public demo, the announced carryover gives a reason to preserve that progress. It does not turn the unreleased import into a certainty or require you to grind the demo solely for a presumed future advantage. Choose how much to play based on the experience available now.
Do not treat a previewer's extensive preparation as evidence of what your own public-demo character will retain. The preview exclusion makes that comparison particularly unreliable. Use your current build and the public-demo rule as the relevant boundary.
The useful completion state for now is preservation, not migration: you know which build created the progress, the character remains intact, and you have avoided unsupported file changes. The migration check becomes possible only when a supported Early Access build and its current instructions are actually available.