---
title: "Backup"
description: "Backup root selection, export/import workflow, backup lifecycle, and database cleanup helper."
url: "https://docs.closex.org/launchnext/settings/backup.html"
markdown_url: "https://docs.closex.org/launchnext/settings/backup.md"
site: "CloseX Docs"
product: "LaunchNext"
language: "en"
last_updated: "2026-05-01T05:09:25.000Z"
alternates:
  en: "https://docs.closex.org/launchnext/settings/backup.md"
  zh-Hans: "https://docs.closex.org/zh/launchnext/settings/backup.md"
  ja: "https://docs.closex.org/ja/launchnext/settings/backup.md"
---

# Backup

`Backup` is your safety net before major layout or settings changes.

![Backup](https://ucarecdn.com/2534f5ff-e82d-444d-ac5d-9a1c07df075a/Archive.webp)

## What you can do here

- choose a backup root folder
- create timestamped snapshots
- restore from any snapshot
- delete one or multiple old snapshots
- copy an advanced database cleanup command

## Safe workflow before big changes

1. Open `Backup`
2. Click `Choose Backup Folder` (first time only)
3. Click `Create Backup`
4. Verify the new snapshot appears
5. Proceed with risky edits

## Snapshot format

Backup folders use this pattern:

`LaunchNext_YYYY-MM-DD_HH.mm.ss.launchnext`

Each valid snapshot includes `Data.store` plus exported preferences.

## Restore options

- Click `Import` on a snapshot row
- Or use `General > Import Data` and choose specific categories to restore

## Advanced cleanup block

You can reveal and copy a SQL cleanup command that:

- checkpoints WAL
- removes unused history rows (`ACHANGE`)
- vacuums database size

Only run this manually in Terminal after quitting LaunchNext.

## Troubleshooting

## No backups shown

- confirm a backup folder is selected
- verify file permissions
- create a new backup to test write access

## Restore result is partial

Use full import scope instead of selective checkboxes.