Saves folder. Akron stores them in Saves/AkronBackups, then excludes that folder from later snapshots so each archive contains save data rather than older backup ZIPs.
Use it before risky mod changes, save-file edits, testing sessions, or any run where losing the current profile would be expensive. Backups can be created manually or triggered on launch, close, save/settings writes, chapter entry, and timed intervals.
Restore is intentionally conservative. Akron verifies the selected ZIP, creates a pre-restore backup of the current save files, extracts the selected backup to disk, reloads the restored save slot, and returns to the main menu so Celeste does not keep using stale in-level save data. That safety backup stays in the browser like any other backup, so you can recover the state you had immediately before the restore.
Backup metadata
Every ZIP includes_akron-backup.json. This file records why the backup was created, when it was created, the Celeste and Akron versions, the active save slot and profile name, the current area and room when available, and the enabled Everest module list. Metadata makes the restore browser easier to inspect and helps diagnose backups made around mod changes.
Retention
Retention runs only after a successful backup. A failed new ZIP is deleted and does not cause older archives to be cleaned up. Akron can clean up by backup count, age, and total backup folder size. The newest protected backups are kept even when they exceed those limits, and pinned backups are never deleted by automatic retention.
Pin important backups from the restore browser when you want to keep them outside the normal cleanup rules.