When a Steam Early Access game reaches version 1.0, Steam does not automatically carry every save forward, and it does not automatically wipe every save. The game’s developers decide whether the new build can read existing files, converts them during an update, keeps some data but changes other data, or rejects them entirely. Funguys Swarm announced that its Early Access saves and unlocks would carry into 1.0, while Foundation said its Early Access cities could not load in the 1.0 build. Abiotic Factor kept existing worlds but changed some saved items. Those different outcomes are why the only reliable answer is the named game’s latest developer announcement, migration guide, patch notes, and Early Access FAQ.
What happens to a save when Early Access becomes version 1.0?
There is no Steam-wide carryover rule. A 1.0 launch can preserve a save exactly, migrate it automatically, preserve the world while altering individual items, or make the old file incompatible with the new executable.
Valve’s Early Access guidance tells developers to explain save-breaking updates to players and to keep their Early Access questions and answers current. Its wording is explicit: “If you know your updates during Early Access will break save files, make sure you tell players up front.” Read that game-specific communication rather than relying on assumptions about Steam.
A save that “carries over” also does not necessarily produce an unchanged world. The game may convert inventories, remove obsolete objects, rebalance progression, or alter pets and food while retaining the underlying world. Conversely, an “incompatible” save normally means the 1.0 program cannot read it; it does not prove that the file was deleted from your drive.
Which outcomes are possible?
| Outcome | Published example | What it means for you |
|---|---|---|
| Full carryover | Funguys Swarm’s August 2026 1.0 announcement said, “Your save files carry over,” including unlocks. | Continue in 1.0, subject to that game’s stated limits and platform rules. |
| Carryover with changes | Abiotic Factor’s July 15, 2025 1.0 guide said existing worlds could continue but listed changes to saved food, pets and other data. | Your world may load while particular objects, values or systems are transformed. |
| Incompatible with 1.0 | Foundation’s January 31, 2025 1.0 announcement said old cities could not load in 1.0 and identified an older 1.9 Steam Beta branch. | Use a legacy branch only if the developer provides one; it is not a universal Steam feature. |
| Not decided | Witchfire’s July 2026 version 0.9 FAQ said the team hoped to preserve saves but still needed migration testing. | Treat compatibility as unconfirmed until a later announcement settles it. |
These are examples, not a cross-game percentage or prediction. Version labels such as 1.0 and 1.9 describe releases, not the likelihood of a wipe.
How can I find the definitive answer for my game?
Look for an explicit compatibility statement from the developer and check when it was published. A vague promise that progress is “safe” is less useful than a sentence saying whether the old file loads automatically, needs an import, or requires a particular branch.
Read the newest announcement and migration notes
Check the game’s Steam announcements, patch notes, migration guide and Early Access Q&A. Valve asks developers to maintain that Q&A, but plans can change between an early FAQ and the actual 1.0 build. If the announcement describes a future intention, quote it to yourself as a plan, not a guarantee.
Separate world compatibility from item compatibility
Search the notice for details about inventories, quests, research, pets, food, buildings, characters and achievements. Abiotic Factor demonstrates why this matters: “the world continues” did not mean every saved object remained identical.
Check for a required conversion step
Some games can migrate on first launch; others require selecting an import option, opening a save in a transitional build, or following a developer-provided sequence. Do not launch repeatedly while guessing. If the instructions name a backup, branch or order of operations, follow those directions before allowing the 1.0 build to rewrite files.
Look for branch and platform limits
Foundation offered its older Early Access 1.9 build through Steam Betas so players could continue old cities, while warning that the old branch might eventually disappear. A legacy branch is a game-specific accommodation, not an entitlement. Funguys Swarm’s announcement also said its saves remained platform-specific, so carryover on Steam did not imply transfer to another platform.
What should I do before the 1.0 update?
Prepare the game’s actual save files first, then let Steam finish any supported synchronization. A separate copy gives you a recovery point, but it cannot make an incompatible file readable by a new game build.
- Record the developer’s instructions. Save the URL or title of the latest compatibility announcement and note whether it describes automatic migration, changed content, a fresh profile recommendation, or a legacy branch.
- Finish a normal save and close the game. Wait for Steam Cloud to complete if the game supports it. Steamworks synchronizes configured files around game sessions, and Steam Support advises resolving a synchronization error before launching again.
- Locate this game’s real save folder. Steam Support lists common local Cloud locations: Windows
C:Program Files (x86)Steamuserdata, macOS~/Library/Application Support/Steam/userdata, and Linux~/.local/share/Steam/userdata. Those folders are not a guarantee that every game stores its saves there, because developers choose what their integration syncs. Witchfire, for example, identifiesUsersyour_usernameAppDataLocalWitchfireSavedSaveGamesfor its saves. - Make an untouched copy. Copy the identified save folder or files to another drive or a separate folder before the major update. A USB flash drive is simply one place to keep that copy; an external SSD is another option if you already maintain broader backups. Verify that the copied files exist and do not replace the active files with the backup until the developer’s migration instructions are clear.
- Prepare for a Cloud conflict. If Steam presents local and Cloud versions, compare their timestamps with your last play session. Steam says the most recently modified copy is often the one you want, not an infallible rule. Offline play can create conflicts, and Abiotic Factor specifically warned against replacing a newer save with an older Cloud copy.
- Review mods. Disable or update unsupported mods if the developer requires it. Abiotic Factor warned that unsupported mods could break a world during its 1.0 transition, while Foundation said its mods needed updates.
Is Steam Cloud a guaranteed backup or save converter?
No. Steam Cloud synchronizes the files a developer has configured; it does not convert an old save format into a new one, and some games do not use Cloud to store save games at all.
Steam Support warns that synchronization conflicts or an older upload can replace progress. A Cloud copy can therefore preserve a file that the 1.0 build still cannot read, or it can be older than the local file you meant to keep. Treat Cloud as synchronization, not as an independent archival backup. Keep a separate copy before a major version change.
Cloud also does not promise cross-platform transfer. Whether a game shares progress between PC, console or other platforms depends on that game’s implementation. Even when the same game supports Cloud, its platform-specific save format or account rules may prevent a file from moving between platforms.
What if my progress appears to be missing after launch?
Stop before repeatedly opening the game, accepting a conflict choice, or saving over the existing files. First determine whether the game migrated the file, selected another Cloud copy, or is running a build that cannot read the old format.
- Read the migration notice again. Look for a required import, a changed save location, a warning about mods, or a statement that old files only work on a legacy branch.
- Inspect conflict timestamps. Compare the local and Cloud dates with the time you last played. Do not choose a copy solely because Steam labels it “Cloud” or “local.”
- Check the older computer. Steam Support notes that an unsynchronized save may still be on the machine where you played. If it is there, allow the correct file to synchronize only after confirming it is the newer progress.
- Ask the developer about this game’s files. Request the documented save path and ask whether an import tool, migration procedure or previous-build branch exists. Steam Support says it cannot recover lost saves or resolve a game’s Cloud conflict for you.
- Use a legacy branch only when offered. Foundation’s 1.9 branch is a specific example. Do not assume another Early Access title will provide an equivalent option, or that the branch will remain available indefinitely.
Do not delete the backup while troubleshooting. If the 1.0 build has already rewritten a file, the untouched copy is the safest basis for following the developer’s next instruction.
Does choosing to start over mean the game wiped my save?
No. A fresh start can be a player choice or a developer recommendation even when technical carryover works. Witchfire’s July 2026 version 0.9 FAQ said the team hoped to preserve saves but had not confirmed 1.0 compatibility; separately, it anticipated recommending a fresh profile for the intended challenge. That is different from announcing that every existing save would be deleted or rejected.
Wait for the final 1.0 instructions before treating an early FAQ as a decision. If the developer recommends a new profile, preserve the old files so you can return to them if the game supports both profiles or later adds migration.
What does platform-specific carryover mean?
It means a save can survive the Early Access-to-1.0 update on the same platform without being transferable elsewhere. Funguys Swarm said its Early Access saves carried into 1.0 but remained platform-specific. Steam Support likewise says cross-platform Cloud integration is game-dependent.
Before buying or installing a second platform version, look for a separate cross-save statement. A Steam Cloud setting alone does not establish console transfer, and copying a file between platforms cannot overcome different formats or account systems.
How should I interpret a developer’s wording?
Prefer precise verbs over broad reassurance. “Your save files carry over” is a strong statement for the named release; “worlds continue” still calls for a list of changed objects; “we hope” or “we plan” signals an unconfirmed future result.
- Confirmed: the announcement names the release and states that existing saves load or carry over.
- Conditional: the announcement requires a migration step, a clean profile, a specific branch, or removal of unsupported mods.
- Partial: the world remains but selected items, unlocks or systems change.
- Unconfirmed: the team is still testing compatibility or says it will decide later.
- Incompatible: the new build cannot load the old format; only a separately maintained older build may open it.
There is no verified cross-game rate for carryover, wipes or Cloud recovery. The safest conclusion comes from the game’s latest dated announcement, not from what another Early Access title did.
Frequently asked questions
Can I keep playing an old save after 1.0 without updating?
Only if the developer leaves an older build available, such as a Steam Beta or legacy branch. Availability can be temporary, and the old branch may stop receiving fixes or eventually be removed, so treat it as a preservation option rather than a permanent guarantee.
Will a save backup let me downgrade if 1.0 breaks it?
A backup preserves the bytes you had before the update, but the game still needs a compatible executable to open them. If the developer does not provide a previous build or migration tool, restoring the file alone may not make it playable.
Do achievements and unlocks always follow the save?
They are separate things to verify in the announcement. Funguys Swarm specifically included unlocks in its carryover statement, but another game may handle achievements through account data, profile data or one-time progression differently.
Where should I ask when the save path is undocumented?
Use the game’s official support channel, Steam announcement comments or community hub only after checking the developer’s own documentation. Give the game version, operating system, platform, mod status and the exact symptom, but do not upload personal account files publicly.
Frequently Asked Questions
Can I keep playing an old save after 1.0 without updating?
Only if the developer leaves an older build available, such as a Steam Beta or legacy branch. Availability can be temporary, and the old branch may stop receiving fixes or eventually be removed, so treat it as a preservation option rather than a permanent guarantee.
Will a save backup let me downgrade if 1.0 breaks it?
A backup preserves the bytes you had before the update, but the game still needs a compatible executable to open them. If the developer does not provide a previous build or migration tool, restoring the file alone may not make it playable.
Do achievements and unlocks always follow the save?
They are separate things to verify in the announcement. Funguys Swarm specifically included unlocks in its carryover statement, but another game may handle achievements through account data, profile data or one-time progression differently.
Where should I ask when the save path is undocumented?
Use the game’s official support channel, Steam announcement comments or community hub only after checking the developer’s own documentation. Give the game version, operating system, platform, mod status and the exact symptom, but do not upload personal account files publicly.