How to Transfer a Silksong Save Between PCs

Quick answer

On the new PC, update Silksong and launch it once, then quit. That creates the destination account’s numeric Steam ID folder (or default for a non-Steam build). Back up anything already inside it. From the old PC, copy—not move—the complete save folder and keep that copy untouched. Put a duplicate of the intended userX.dat into the matching destination folder, open the profile, save, quit, and open it again before removing anything from the old PC.

Move the save without losing either copy

Update Silksong to the same game version on both PCs.
On the source PC, close the game and copy the entire save folder to a dated backup.
On the destination PC, launch the game once, create or identify the target slot, then close the game completely.
Open Team Cherry’s documented platform path and choose the numeric Steam ID or default folder that the destination launch just created.
Back up any existing destination userX.dat before copying the source file.
Copy—not move—the source profile, keep the intended slot number, and launch the destination game to verify it.

Steam game transfer and save transfer are different

Steam’s local network transfer can copy installed game content, but Steam Support explicitly says it excludes local save games, configuration files, Steam Cloud files, Workshop content, and shader files. A successful game installation transfer therefore does not prove the Silksong profile moved.

Silksong’s PC save is stored in the Team Cherry folder documented by the developer, with Steam users separated into numeric sub-folders. Confirm that destination folder instead of placing the file beside the game executable.

Before the first Steam Cloud decision

Preserve local copies from both devices before either one synchronizes.
Do not open the same profile on both computers during the first test.
If Steam presents a conflict, do not choose by “cloud” versus “local” alone. Compare the shown time and then verify the profile’s playtime, last bench, and inventory.
Keep the source computer untouched until the destination save opens, saves, closes, and reopens successfully.

What this guide does not promise

These steps are for PC save files. A console does not expose the same Team Cherry folder or let this browser editor select its cloud save, so do not apply the PC copy instructions to a console profile.

Moving a file between different Steam accounts can also involve ownership and cloud behavior outside the save schema. Test a copy in the destination account’s own generated folder; do not overwrite both accounts’ only local copies.

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.