How to Fish Game Guide Hub
Menu

How to Fish Steam Cloud & Save Not Showing: Safe Checks

Updated 2026-09-06

Upload an existing How to Fish save to Steam Cloud safely, diagnose a missing world, and preserve native backups without overwriting the only good copy.

The Island 2 cabin area in How to Fish
Official How to Fish screenshot from the Steam store.

Quick answer: stop before another save

If the expected world is missing, older or rejected as corrupt, stop before creating a replacement world or repeatedly pressing Save. Patch 1.0.12 now supports Steam Cloud, but the developer's upload instruction starts on the PC that still has the correct existing save: update the game, play that world, then exit once so Steam can upload it. Do not open a blank or older copy on another device first. Patch 1.0.11 also added native backups, but Dazed Games still has not published a manual restoration procedure.

What Dazed Games officially says about saving

Patch 1.0.6 added save-file validation and says Save, Main Menu and Quit trigger saves, with autosaves continuing every minute; the application no longer writes server or local state specifically when it crashes. Patch 1.0.11 adds a corruption check before loading and native backups. Patch 1.0.12 adds Steam Cloud and tells players with an existing world to play and exit once on the PC where it is saved. These changes improve validation and availability, but they do not guarantee recovery of progress lost before the features existed.

What is confirmed about native backups

The confirmed fact is narrow: the current Patch 1.0.11 game creates backups natively. The official announcement does not state a folder path, extension, naming scheme, number of copies, backup timing, in-game recovery screen or supported restore sequence. If the game exposes a backup or recovery prompt, photograph it and keep the original data unchanged before asking Dazed Games what to select. If no prompt appears or the world still will not load, stop there rather than experimenting with file names.

Missing on the same computer

First confirm that Steam is using the expected account and that the game is fully updated. Photograph or screenshot the visible world list, then restart Steam and the game once. If the world appears, load it only long enough to compare the island, objective and inventory before making another save. If it remains absent, stop. Verifying installed files through Steam is a reasonable program-file check, but Valve's verification does not reconstruct save progress. Do not create a new world with the same name while evidence is still missing.

Missing after switching PC or Steam Deck

Patch 1.0.12 changed the old boundary: How to Fish now supports Steam Cloud. On the computer that still contains the correct world, restart Steam to receive the update, confirm the world and inventory are correct, use the game's normal Save or Main Menu flow, then exit the game once and allow Steam to finish synchronizing. Only after that should you open the game on the destination PC or Steam Deck. If Steam shows a conflict, stop and preserve both copies; the developer has not documented a merge rule or a safe way to reconstruct two diverged worlds.

Steam Cloud still looks disabled or the save does not upload

First confirm the game is on Patch 1.0.12 or later and restart Steam, as the developer requests. Valve's support guidance also requires Steam Cloud to be enabled globally in Steam Settings > Cloud and for the game in Library > How to Fish > Properties > General. Reopen the known-good source world, exit normally once, and wait for Steam's sync status to finish before testing another device. File verification can repair installed game files, but it cannot manufacture missing save data. Do not force a cloud overwrite when you cannot identify which copy is correct.

GeForce NOW save is missing after exit

A current GeForce NOW Reddit thread contains multiple players asking about lost or non-persistent sessions, and its comments predate or overlap the Steam Cloud patch. Patch 1.0.12 is the official change that can make future saves available through the Steam account, but it does not promise recovery of a world already lost inside an earlier cloud-streaming session. If you have a correct copy on a local PC, seed Steam Cloud from that PC first. If no known-good copy remains, record the account, build and session time and contact official support instead of creating replacement data or following deletion advice.

After a crash or forced close

Write down whether the game closed to desktop, froze until terminated, returned to the menu, or the whole system restarted. Patch 1.0.6 intentionally avoids a save triggered by the application crash, so compare the world against the last deliberate Save, Main Menu or Quit action rather than the exact crash moment. Patch 1.0.9 described its corruption fix as hopeful, not guaranteed. If the world loads but inventory, objectives or server entries are wrong, exit without another save and move to the deeper save-protection checklist.

Do not use unverified recovery instructions

Patch 1.0.11 confirms native backups, but it does not say they use a .bak extension or that removing an extension restores a world. It also does not support running Steam as administrator as an autosave fix. Do not disable antivirus protection, force an upload or download, overwrite a folder from a stranger, install a save editor, or choose a file solely because its timestamp is newer. Those actions can destroy the only useful copy or mix data from different world states.

Preserve evidence before developer help

Keep the affected computer available and avoid cleanup tools. Record the game version, operating system, Steam account change if any, single-player or co-op, host/client role, last known-good time, last deliberate save action and the first wrong screen. Patch 1.0.10 prints the game version in player.log for easier debugging, but remove personal paths or identifiers before sharing logs. Ask Dazed Games for the current native-backup recovery procedure and report the exact symptom rather than claiming a cause.

How to confirm the save is healthy

A world merely appearing in the list is not enough. Load once and confirm the expected island, current quest, inventory or equipped gear, and co-op host state. If those match, use the in-game Save button, wait for completion, return through Main Menu, then reopen the world once. If anything is still wrong, do not continue progression or overwrite more slots. Keep the comparison notes and follow the recovery checklist, which separates corrupt data from missing ground items, lobby state and quest-item loss.

How to apply this guide safely

Begin with “Quick answer: stop before another save” and compare it with the objective, inventory, and controls shown by your installed build. Do not change several variables at once. If the guide concerns progression, complete one dialogue or hand-in and confirm the objective changed before sailing away. If it concerns combat, test the control or equipment choice on an ordinary encounter before spending a boss trigger. If it concerns troubleshooting, preserve the save and start with reversible checks such as restarting the session and verifying files.

Keep a short run record with the game version, solo or co-op state, host identity, starting objective, relevant equipment, steps taken, and outcome. Physics, network state, and retail patches can make two attempts look different even when both players describe them honestly. A controlled record lets you identify which condition changed. It also gives the developer a useful reproduction if the result points to a defect rather than a missed quest step.

Evidence and version check

This article uses Dazed Games — Patch 1.0.12 Steam Cloud upload instruction, Steam Support — Steam Cloud settings and troubleshooting, Reddit r/GeForceNOW — How to Fish availability and save-persistence discussion, Reddit r/HowToFish — single corrupt-save report (deletion advice not adopted), Dazed Games — Patch 1.0.11 native backup and corruption-check announcement, Dazed Games — official announcements (Patch 1.0.6 through 1.0.11), Steam Store — How to Fish current feature list, Steam Support — Verify Integrity of Game Files, Steam Discussions — current missing-save and cross-device question index. Official store text and developer announcements establish supported features and broad progression. Steam achievement wording establishes that a named action exists, but it does not prove an exact coordinate, probability, price, damage value, or hidden timer. Community discussions can reveal a repeated problem and possible workaround, but one reply is not treated as a universal mechanic. Where evidence stops, the guide uses cautious testing steps instead of inventing a precise answer.

Before relying on an older route, check the Steam news and discussion dates against the updated date at the top of this page. Prefer the current in-game objective when it conflicts with a video or forum post. Avoid unknown executables, replacement saves, cheats, or destructive file edits offered as shortcuts. A legitimate workaround should be explainable, reversible, and testable without surrendering account credentials or deleting the only known-good save.

Completion check

Finish with “How to confirm the save is healthy,” then verify the result in the system that matters: quest log for progression, inventory for items, Steam for achievements, or a repeatable symptom check for a technical fix. Do not treat a visual animation alone as proof that the save registered the event. Wait for a normal transition and inspect the state before selling items, changing hosts, or starting another objective. If the result differs from this page, send the URL, build number, exact steps, and observed result through the contact page; that evidence is how we correct guides without turning uncertain reports into false facts.

Did this guide solve your problem?

Your answer tells us which fixes need clearer evidence or another troubleshooting path.

Sources & Evidence

Claims are backed by the following sources. Unknowns are marked explicitly.

Related guides

Frequently asked questions