The starting point

An error while loading does not by itself prove the save is destroyed. Patch 1.0.3 fixed heavily cleaned worlds that appeared corrupted even though their files were intact. Patch 1.0.5 fixed a repeatable freeze about half a minute after loading some worlds. Identify which symptom you have before deleting or replacing data. S02S04

Official Windows folder · S03C:\Users\[user-name]\AppData\LocalLow\DragDropGames\MoonSweepers\Backups

Replace [user-name] with your Windows username. Copying this path does not restore a save.

Official Windows backup location

The developer gives this folder:

C:\Users\[user-name]\AppData\LocalLow\DragDropGames\MoonSweepers\Backups

In Windows File Explorer, the equivalent shortcut is:

%USERPROFILE%\AppData\LocalLow\DragDropGames\MoonSweepers\Backups

The shortcut substitutes your Windows user profile for the user-name segment. This page locates backups; it does not automatically download or restore your files.

What the game keeps

Starting with 1.0.4, each save slot keeps up to five full world backups. The developer says backups are taken a minute into each session and then every 30 minutes. They are stored outside Steam Cloud. S03

The game can automatically repair a damaged save from backups during loading and notify you. It also checks save files after a crash on the next start. These are developer-described recovery features, not a guarantee that every lost world can be recovered.

Preserve a separate copy

  1. Close Moon Sweepers before copying its files.
  2. Open the MoonSweepers folder containing Backups.
  3. Copy the whole MoonSweepers folder to another location, giving the copy a date and clear name.
  4. Inspect the copied folder to confirm files are present. Leave the originals and existing backups in place.
  5. Record the version, affected slot, last successful session and exact error before trying recovery.

This is a preservation procedure. Do not rename a random backup, replace a slot, or edit world data based on a guess. This guide does not validate manual restoration, account transfer or Steam Cloud conflict resolution.

Check the symptom and patch

Symptom Relevant documented change
A heavily cleaned base will not load 1.0.3 fixed large worlds that appeared corrupted
It loads, then repeatedly freezes after about 30 seconds 1.0.5 reports a fix on both DirectX 11 and 12
A save or part of it is damaged 1.0.4 describes automatic restoration from backups
A new save cannot open on an old version The developer says 1.0.4 saves cannot open in older versions

Preserve the copy, then check for current game updates and retry the affected slot. If the problem remains, send the developer the build, exact behavior and requested diagnostic material through the official bug-report route. Do not assume verifying installation files repairs a damaged world save.

Source references

Checked 5 November 2026. Source types describe the evidence; they do not imply gameplay testing by this site.

  1. S02 · OfficialPatch 1.0.3 — 24 October 2026 ↗
  2. S03 · OfficialPatch 1.0.4 — 25 October 2026 ↗
  3. S04 · OfficialPatch 1.0.5 — 28 October 2026 ↗