Short answer

As of September 1, the developers have not publicly explained Frostrail's manual-save controls, autosave timing or beta carryover. A new Steam thread asks the question and has no answer. Official news only confirms that development added progression between levels.

Manual save
Not publicly documented
Autosave trigger
Not publicly documented
Between-level progression
Mentioned in May development news
Beta-to-Early-Access carryover
Not promised
Report route
In-game bug report button

Leave a session with the least avoidable risk

  1. Finish the current interactionClose inventory, crafting and dialogue screens and avoid quitting during a visible transition.
  2. Watch for game feedbackIf the UI shows a save or transition indicator, wait for it to clear. This is a precaution, not a published save trigger.
  3. Use the in-game quit pathPrefer the game's own menu over Task Manager, Alt+F4 or shutting down Steam.
  4. Record what returnsOn the next launch, note the host, level, quest, train state and inventory that returned. That evidence makes a report useful.
  5. Report losses in the betaUse the in-game bug report button and include whether you were host or client and exactly how the session ended.

Progression between levels is not the same as a save promise

The official Spring Development Update says progression now carries between levels. That describes the game's level structure during development, not the storage rules for closing the application. It does not identify a save slot, cloud-sync behavior, host ownership or a rollback window.

For that reason, this page does not label a bed, train station, tunnel or menu action as a save point. None of those triggers appears in the public developer material reviewed on September 1.

What the unanswered Steam thread tells us

The public question is only one sentence—“How do you save in game progress”—and currently has zero replies. It proves the task is unclear to at least one tester, but it does not supply an answer.

If a developer reply or repeatable in-game observation appears, this guide can be updated with the exact trigger and build date. Until then, concise uncertainty is safer than inventing a solution.

Host and client details to capture

Co-op games can attach world state to the host, a shared session or a service account. Frostrail has not publicly described which model the beta uses. When reporting lost progress, include who hosted, whether the same person hosted again, and whether all players closed normally.

Also include the last completed objective, current level or exit, changes made to the Eden Engine and any inventory difference. Avoid deleting local files while investigating because that removes evidence and may make recovery harder.

Sources and context

Official material establishes game facts. Community threads are labeled because a player report is evidence of a question or workaround, not a developer guarantee.

  1. OfficialSpring Development Update — Frostrail official Steam news. Accessed 2026-09-01.
  2. OfficialFrostrail Closed Beta Launched! — Frostrail official Steam news. Accessed 2026-09-01.
  3. CommunitySave progress — Steam Community. Accessed 2026-09-01.