Moonlight Peaks Save Backup & Recovery Guide (PC, Mac & Steam Cloud)

Save recovery is one of the few topics where a calm, small precaution is more valuable than a clever workaround. For the Steam desktop build, SteamDB publishes the game’s Steam Cloud configuration and the local folder paths it derives from that configuration. A dated copy of that folder gives you a restore point that Steam Cloud alone does not necessarily provide.

This guide covers backups and evidence collection, not save editing. It is deliberately conservative: do not overwrite files while the game is open, do not assume another platform uses the same path, and do not treat a random download or forum post as an official recovery tool.

Confirmed Steam save locations

SteamDB lists the following paths for Moonlight Peaks’ Steam Cloud files:

Platform	Listed local save location
Windows	%USERPROFILE%/AppData/LocalLow/Little Chicken Game Company/Moonlight Peaks/
macOS	~/Library/Application Support/Little Chicken Game Company/Moonlight Peaks/
Linux / SteamOS override	$XDG_DATA_HOME/Little Chicken Game Company/Moonlight Peaks/

These are paths for the Steam desktop configuration, not a promise that every storefront, console, or mobile version exposes files in the same way. SteamDB is a third-party reference built from Steam configuration data; use it to locate a folder, then treat the files in it carefully.

Make a safe manual backup

The safest routine is simple: back up after a normal session when you can confirm your latest progress is present.

1. Exit Moonlight Peaks normally. Do not copy a live save while the game is actively writing it.
2. Wait for Steam to finish any visible sync activity. The goal is to back up a settled local state rather than racing the client.
3. Open the relevant folder above and copy the entire Moonlight Peaks folder to a separate, dated location you control—such as a folder named Moonlight-Peaks-backup-2026-08-03.
4. Do not rename files inside the live folder. The copy is your insurance; leave the active save structure alone.
5. Keep more than one dated copy if you are experimenting with mods or about to make a major in-game decision.

Steam’s own Backup Feature is designed for game files. It is useful to understand as a separate tool, but it should not be confused with a tested, game-specific rollback system for a save. A plain dated copy of the known local save folder is easier to inspect and less likely to create false confidence.

If progress appears missing

First, stop. Reopening the game and immediately playing to a new save point can make it harder to understand which state changed. Record the platform, storefront, installed game version, approximate time of the last good save, and what happened just before the problem appeared. If you are on Steam desktop, make a copy of the current local folder before attempting any change.

Then install the current update. Marvelous’ July 31 notes list a Google Play Games fix for a cloud-save failure that could lead to lost progress, alongside an infinite loading-screen fix. That is a platform-specific patch—not evidence that a Windows, Mac, console, or Steam Cloud issue has the same cause—but it is a good reminder to compare the affected platform and version to the official notes.

Avoid force-closing the game while it is saving. If the save is still present but a quest or achievement is stuck, check the relevant official patch condition first: for example, the July 21 notes state that some progression fixes apply after an in-game day passes. Our July patch round-up collects those cases by platform.

Modded saves need an extra layer of caution

The Official Moonlight Peaks Wiki’s modding documentation includes a persistence guide that recommends a sidecar file for custom-object state instead of editing the game’s save data. That is a strong principle even if you are only installing, not creating, a mod: preserve an untouched backup before changing the setup, and do not use a tool that asks you to overwrite unknown save files without explaining what it does.

Keep a short note beside each backup: game version, whether mods were enabled, and what you were doing at the time. If a problem only appears after a mod is added, you now have a clean point of comparison. See the safe modding guide for the same cautious workflow from the mod side.

When to contact support

A support report is most useful when it is reproducible. Include the platform, storefront, game version, save/back-up timing, last action before the issue, and whether a mod was installed. Attach screenshots or requested log files only through the publisher’s official support channel. Do not publish a save that contains personal account information in a public thread.

The goal is not to turn every frustrating moment into a manual rollback. It is to keep one clean copy, avoid overwriting evidence, and use platform-specific patch notes rather than a one-size-fits-all fix.