Quick answer
Back up the whole save folder, then compare the game version on the machine that last opened the profile with the version installed now. Update the older installation or return to the same newer branch. Open the profile without editing its data, save normally, quit, and open it a second time. Silksong Save Editor can show values, but it does not convert a newer save into a safe older-format save.
Why changing a version number is not a downgrade
A newer build may write a field for an item, quest state, or system the older executable has never seen. The visible version value is only a label; changing that label does not teach the old executable how to handle the newer data.
Deleting every unfamiliar field is equally unsafe. The file may still decode as JSON while two values that are supposed to agree no longer do. Team Cherry blocks the older build from opening it to avoid that partial read-and-write cycle.
Safe recovery order
- Copy the incompatible userX.dat and the full save folder before experimenting.
- Check which game build last opened the profile and which build is installed now.
- Update the current installation or switch back to the matching newer build.
- Open the profile without editing it, make a normal save, close the game, and launch again.
- If you intentionally use multiple branches or devices, keep separate dated backups for each build.
- Use an older Auto Save only if you understand that restoring it replaces current progress.
Common ways version mismatches happen
- Switching from a beta or newer branch back to an older public build.
- Opening the same cloud-synced profile on devices with different update states.
- Restoring an old game installation while retaining a save written by a newer one.
- Moving a save to another PC before that PC finishes updating the game.
Use Advanced Mode to inspect, not to force the file open
The editor may display a version value when the uploaded save exposes one, but that value is not a downgrade button. Changing the visible string cannot remove every piece of newer data or add the code that exists only in the newer game build.
Use Advanced Mode for inspection only until the file opens in the correct game build. Do not force a version number, delete objects, or copy fields from another player’s save to bypass the message.
Preserve the original before testing
Work on copies, change one thing at a time, and keep the original until the chosen save opens, saves normally, closes, and opens again.
How to Fix a Silksong “Version Incompatible” Save FAQ
Is “Version Incompatible” the same as corruption?
No. It can be a healthy save written by a newer build that the older build deliberately refuses to open.
Can I change the version field in Advanced Mode?
Changing a label does not remove newer schema data or add missing game logic, so it is not a verified downgrade.
Will updating the game delete the save?
Updating is the official direction for a newer save, but preserve the entire folder first so you still have a rollback copy.
Sources and evidence
Official guidance defines the safe baseline. Community links document real player cases, but a successful report is not a universal or version-independent fix.
Official: Team Cherry: “Version Incompatible” explanation