01First decide which of three problems you have
The first case is an old save that still opens on the original PC but has not reached a second device. The second is a conflict: two devices show different progress or Steam asks which copy to keep. The third is a missing local save on the original device as well. These cases need different next checks, so note which screen and device first showed the problem before trying anything else.
Write down the Steam account, game version, device names and one visible progress marker such as an unlocked island or achievement. Do not rely on a remembered item alone, because dropped-item persistence and Cloud synchronization are separate systems. Keep the game closed on the destination device while you confirm the source copy. A screenshot of each device’s current menu is more useful than repeatedly loading and saving uncertain progress.
- Original PC still shows expected progress → follow the initial upload route below.
- Devices disagree or Steam presents two copies → pause at the conflict route below.
- Original PC is missing the save too → preserve the local state and use the loss route below.
02If the original PC still has the save, upload from there
Patch 1.0.12 says to play and exit How to Fish once on the PC where the save already exists to upload it to Steam Cloud. Open that device, confirm the expected progress in game, then leave through the normal exit flow. Give Steam time to finish any visible synchronization before launching the game elsewhere. The patch note does not supply a fixed upload duration or claim that every device pair behaves identically.
Only after the source PC is settled should you open the destination device and compare the same progress marker. If the second device remains behind, stop before it makes another save and capture its Steam Cloud status or error text. Check that both devices use the same Steam account and current game build, because a different account or outdated client changes the diagnosis. A second attempt should change one condition at a time rather than producing more competing copies.
03If Steam shows a conflict, preserve both sides
A conflict prompt means there are competing states, not that the newest timestamp necessarily contains your best progress. Photograph the prompt, including the device name and any dates or sizes it displays, before selecting a side. Compare those details with the last device where you personally saw the wanted save open. If you cannot identify that copy, cancel or postpone the choice if Steam allows it and gather more evidence first.
Do not alternate launches between two devices while a conflict is unresolved. Each new exit can create another save state and make the history harder to reconstruct. If you have an independent backup made before the issue, keep that copy untouched while you inspect the live states. This guide does not claim a universal conflict-button choice because the game’s official note does not publish one.
04If the original device is missing progress too
Treat this as possible local loss, corruption or wrong-save selection rather than a simple first-upload delay. Stop making fresh progress on that installation and record what the game shows now. Patch 1.0.11 says the game checks saves for corruption and creates backups when corruption occurs, but it does not document a manual restoration path. Do not rename, replace or test files based on a generic guide while you are still locating the good copy.
You can inspect your Steam account’s Remote Storage page to see whether How to Fish files are listed there, without treating that list as proof a particular save can be restored. Record file names, dates and sizes if they appear, then compare them with your device notes. If no file appears, that alone does not establish why the game is missing progress. Keep screenshots and account details private when requesting developer or Steam support.
05Report the symptom with enough detail to reproduce it
State whether the original PC still has the save, whether another device differs, and whether Steam displayed a conflict. Include the patch number, Steam client state, platform and the last time the expected progress was visible. Attach the wording of any Cloud error and a redacted screenshot of the relevant screen. This gives support a concrete sequence rather than a broad claim that Steam Cloud erased everything.
Recent player discussions include failed cross-device uploads and missing collection progress, so the problem deserves active monitoring. Those posts document symptoms, not a verified recovery procedure for every player. If the save opens but one carried or dropped item is absent, use the Lost Items guide instead of assuming a full Cloud rollback. Recheck official patch notes when a later update publishes a specific fix or new recovery instruction.
Next verified routes
Continue with the exact next question
Evidence boundary
What this guide can confirm
- Patch 1.0.12 explicitly instructs players to play and exit once on the PC holding the existing save for the first Cloud upload.
- Patch 1.0.11 says the game checks saves before loading and creates backups for corruption, without publishing a manual recovery procedure.
- Steam Community posts describe cross-device sync failures and missing progress after Cloud support, but are symptom evidence rather than a proven fix.
Sources
Sources for this guide
- Official How to Fish Patch 1.0.12 announcement
Primary source for Steam Cloud and the first upload instruction.
- Official How to Fish Patch 1.0.11 announcement
Primary source for save checks and corruption backups.
- Steam Community search for How to Fish Cloud reports
Dated player symptoms, not a recovery guarantee.
- Steam account Remote Storage
Official account page for read-only inspection of listed Cloud files.