What is confirmed about saving support
The official Steam page lists Steam Cloud as a feature. The app-details response corroborates that same declared capability. This establishes a platform feature associated with the game rather than a directly observed save operation.
The two representations share their Steam provenance, so they do not amount to separate playtests. Their agreement is useful for checking that the feature is declared consistently. It still leaves the operational question of how and when progress is written inside the game unanswered.
Cloud support is not a save command
A player asking how to save usually needs an action they can perform or a state they can recognize. The storefront’s cloud-support label supplies neither a menu sequence nor a verified save indicator. It cannot by itself identify the moment at which a particular piece of progress is preserved.
That distinction prevents an unsafe shortcut in the answer. This guide does not tell you that opening a menu, reaching a landmark or exiting the game necessarily creates a save. None of those procedures was established by the collected sources.
No manual or automatic method was verified
The available research contains no authenticated screen showing a manual-save control. It also contains no independently checked account establishing an autosave interval or a particular checkpoint rule. The correct scope is therefore a confirmed feature with an unverified procedure.
This is not a claim that the game lacks either method. It is a statement about what this article can support from the supplied material. Assigning a likely method because other adventures use it would replace evidence with a guess.
Keep the demo and full game separate
The store distinguishes the demo from the full game’s product information. That does not establish that the two share a save format or that progress moves from one to the other. No verified migration or demo-persistence procedure was collected for this page.
A successful demo session should therefore not be interpreted here as proof of a transfer feature. The demo guide focuses on official access and published preview observations. It does not turn the existence of the trial into an unsupported guarantee about campaign continuity.
Save-file locations require their own evidence
The research did not establish a complete current local save-file path in a running copy. An indexed configuration lead cannot supply the missing operational confirmation. This article consequently avoids presenting an untested backup, replacement or deletion procedure.
That limit matters because a path and a save behavior answer different questions. Even a correctly identified directory would not automatically establish a safe moment to quit or the availability of multiple slots. The page keeps those separate details out rather than making one unsupported statement depend on another.
Where to check the confirmed product feature
The official Steam page remains the source for the cloud capability recorded in this article. Use it for the current declared feature list while using the game itself for any save controls visible in your installed build. This page does not claim that the latter were captured and tested during the research.
The controls article follows the same approach for input mappings, distinguishing supported actions from unverified keys. The walkthrough likewise avoids using a story landmark as a fabricated save checkpoint. Together those boundaries give a narrower but more reliable answer than a step-by-step saving instruction unsupported by the supplied evidence.