How to Fish Save Location and Autosave Guide

Current Windows guides place local How to Fish data under %USERPROFILE%\AppData\LocalLow\Dazed Games\How to Fish\. Close the game, copy that whole folder to a dated backup location and leave the original structure untouched. Do this before deleting files, starting repeated new games, moving items or testing an unofficial repair.

Official Patch 1.0.6 says the game checks a save before loading, writes when the player presses Save, writes when leaving through Main Menu or Quit, continues to autosave every minute, and does not write a new local or server state when the application crashes. Patch 1.0.10 adds persistence for up to 64 items dropped on the ground, with weapons, tools, quest items and creatures given priority. Priority is not unlimited storage and does not prove that inventory, equipped items, a boat and loose ground objects share one save path.

Close How to Fish normally and exit Steam if you are about to compare files across devices. Open File Explorer, paste %USERPROFILE%\AppData\LocalLow\Dazed Games\How to Fish\ into the address bar and copy the entire How to Fish folder to a safe location. Add the current date and time to the backup folder name so the copy cannot be confused with live data.

Do not edit the only copy. Do not move individual files out of the live folder while the game is running. Preserve the complete directory because a save system can depend on more than one file, and a partial copy may omit settings or state needed to understand the problem.

After the backup exists, record the game version, operating system, Steam account, solo or co-op role and the last known good action. Note whether you pressed Save, returned through Main Menu, used Quit, experienced a crash or force-closed the process. This timeline is more useful than saying only that “autosave failed.”

If comparing a Steam Deck and Windows PC, preserve both local folders independently. The Steam store feature list inspected for this task does not expose a Steam Cloud feature entry, and current players report missing Deck-to-PC synchronization. That supports caution, not a universal statement about every future build or Steam backend state.

Use the in-game Save control after a boss, major purchase, boat upgrade or difficult catch. Leave through Main Menu or Quit when possible. Patch 1.0.6 identifies both actions as write points and says autosave continues every minute.

A one-minute autosave is a fallback, not proof that the most recent action is already durable. If the application crashes, the same patch says it does not create a new crash-state save. Recent progress since the last completed write may therefore be absent even when the prior save remains valid.

Avoid Task Manager or a forced window close as the normal exit path. A crash-prevention change protects against writing a new state during the crash; it does not transform force-closing into a recommended save method.

Dazed Games says up to 64 items dropped on the ground can persist between sessions. When more loose objects compete for that capacity, weapons, tools, quest items and creatures receive priority. The wording establishes a cap and priority order, not a guarantee that every loose object survives or that the ground is an unlimited locker.

Keep expensive and active equipment in supported inventory or equipment slots when possible. Reduce disposable clutter on the ground and boat. Before leaving, confirm whether the important item is equipped, held, stored or physically loose, then press Save.

When reporting a failure, distinguish ground items from inventory and equipped state. An object that fell through terrain after a lobby join is not automatically explained by the 64-item limit. A boat that does not appear is also a world-state problem, not merely another dropped object.

If the boat, weapon or inventory is already missing, stop creating new state. Do not immediately buy replacements, drop more items or start a fresh campaign over the same slot. Close normally if possible, copy the live folder and document where the object existed before the load.

For a missing boat, record the current island, last known boat position, whether you are host or joining player, and whether the issue began after an update or ordinary load. Patch 1.0.10 includes attempted fixes for item positions but does not announce a universal boat-respawn tool.

For missing equipment, record whether it was attached, skinned, cooked, equipped, in inventory, on the ground or on the boat. Those fields help separate an item-position issue from a persistence-cap or inventory issue. Do not state that Patch 1.0.10 recovers items already lost; the note adds persistence behavior and attempted fixes, not a public rollback command.

An endless boat loading screen does not by itself prove save corruption. Preserve the affected folder, restart Steam once and record whether the main menu and version text load normally. Run Steam’s installed-file integrity check once. That can restore program files, but it does not reconstruct campaign progress or missing inventory.

If a clean new-game test is necessary, keep it separate and stop if the game asks to overwrite the only slot. Compare whether both the affected save and a clean path stall. If only the existing save fails, keep the untouched backup and use the official support route referenced by the patch notes. If both paths fail, startup, installed files or session state may be a separate branch.

Repeating file integrity without a changed result is not a recovery plan. Preserve evidence and report the exact loading state, approximate wait, version and solo or co-op role.

The inspected Steam store surface does not list Steam Cloud, while current Steam discussions ask about cloud saves and Deck sync. This guide therefore treats automatic cross-device synchronization as not yet confirmed. Before changing devices, make dated local backups on both sides and do not assume the newest machine automatically contains the newest state.

Do not copy one folder over another until both originals are preserved. File timestamps can help compare recency, but they do not prove which save contains the desired world state. Keep each device copy intact and label it clearly.

Steam’s file integrity tool verifies installed application files. It is useful when the game executable or packaged assets are damaged, but it does not restore a player’s lost fish, upgrades, money, boat or campaign decisions. A successful integrity result also does not prove the save is healthy.

Official patch notes establish save behavior changes at a version boundary. Community reports establish that some symptoms still occur for some players. Neither source alone proves one universal cause. Keep language narrow and preserve the state before trying a fix.

Where is the How to Fish save file on Windows?

Current Windows-specific guides place the local folder under %USERPROFILE%\AppData\LocalLow\Dazed Games\How to Fish\. Back up the whole folder, not one guessed file.

How often does How to Fish autosave?

Patch 1.0.6 says autosave continues every minute. Manual Save, Main Menu and Quit are also named write points.

Do dropped items save?

Patch 1.0.10 says up to 64 ground items persist, with weapons, tools, quest items and creatures prioritized. This is capped persistence, not unlimited storage.

Does How to Fish support Steam Cloud?

Steam Cloud is not listed on the inspected store feature surface, and players report missing cross-device sync. Treat it as not yet confirmed and make local backups before switching devices.

Can Steam file integrity recover my lost inventory?

No. It checks installed program files; it does not reconstruct player state, money, upgrades or missing objects.

• How to Fish on Steam — platform and feature-list boundary; checked 2026-08-31.
• How to Fish official announcements — official save behavior changes through Patch 1.0.10; checked 2026-08-31.
• Patch 1.0.10 official announcement — 64 ground-item cap, priority order and attempted item-position fixes; checked 2026-08-31.
• Save location and missing boat guide — community-documented LocalLow path, symptom separation and current report links; checked 2026-08-31.
• Cloud saves Steam discussion — current community question about cloud behavior; checked 2026-08-31.