# ManYue manual backup and restore: keep app data and comic originals separately Language: en Canonical: [ManYue manual backup and restore: keep app data and comic originals separately]() 中文：[中文 HTML]() English: [English HTML]() Published: 2026-10-22T00:00:00+08:00 Modified: 2026-10-23T10:34:07+08:00 Author: Bison Follow app-data export through post-restore checks, identifying the saved state, potentially sensitive information and comic files that need their own backup. English translation of the [Chinese original](), translated on 2026-10-23. The article body uses automated translation; app descriptions, historical reading notes and video subtitles receive separate editorial checks. Original publication dates, attribution, code and version notes are retained. Before large shelf changes, sync setup or device migration, save a dated app-data backup as a recovery point. ManYue provides import and export controls for app state. Comic originals need separate retention; list both together so restoring does not recover only titles. ## Decide what this backup must preserve List important shelf groups, recent positions, key bookmarks and server types. Choose two or three sample books with sources and chapters for restore checks. For sync conflicts, save every device’s current data under distinct names instead of indistinguishable backups. Also locate original comics. Local imports need an independent saved copy; server comics depend on server originals and backups. App-data backups do not contain every page, download record or NAS index. Reimport files or reconnect folders after restoring shelf state, so preparation requires more than one backup file. ## Export App Data and save somewhere you can locate In settings’ app-data area, choose Export App Data, or use Export Local Backup in Sync Centre. Wait for completion and select your own folder in the system save interface. Label the folder or external record with date and device, such as “Tablet reading data—before reorganisation”. After saving, confirm in Files that the backup exists and is not zero bytes, and record its location. Wait for any cloud upload to finish before using it on another device. Clicking Export and securely saving the file are separate stages; only the latter gives you recovery material. ## Treat backups as private data Manual backups may include cookies, WebDAV settings and source information. Treat them as personal account data, not public tutorial attachments. Keep them under your control and share only necessary error descriptions rather than uploading entire backups in public comments. Keep clearly labelled versions from different times, not immediately overwriting the only old backup. Record export date, app version, source device and approximate shelf count privately. These notes help choose a restore point; there is no need to open or modify the backup package, which could damage restoration. ## Back up the current device before importing Restoring changes current app data. Export its current state first, then confirm the chosen backup’s device and date. Use Import App Data or the Sync Centre’s local-backup import, select the file and wait. If it fails, retain the message and check file integrity and origin instead of trying multiple files without recording outcomes. During recovery, temporarily stop other devices syncing changes to the same data. Inspect the result before choosing the next upload or download direction. Restored old groups may differ from current cloud state; choose which to retain before restarting automatic sync. ## Open and check each item after restore Check important groups and sample books, recent positions and key bookmarks. Restore local comic files and recheck remote credentials and folders. Rescan NAS indexes against actual directories; unmatched records require file-location checks, not an assumption that all older entries are corrupt. Finally, open beginning, middle and end pages, then reopen to verify resume. A restore-success message confirms the process, not every expected item. Classify missing checklist items as state, file or connection issues rather than repeatedly restoring all app data to recover one file. ## Example: a recovery point before major shelf changes Suppose twenty old groups will become five. Export app data, record three sample books’ original groups and confirm separate comic originals. Fix isolated mistakes directly afterwards; if many group relationships are wrong, the earlier backup provides a clear recovery option. Even if restoring, first back up the current reorganised state to retain newly added information. Recheck three sample books after recovering old groups, then handle additions. Two retained time points are safer than reconstructing a complex shelf from memory. ### Does a small backup mean export is incomplete? Size alone cannot tell. App state is usually far smaller than comic images because automatic and manual app-data packages do not carry every comic file. Verify the backup and restore results, and keep comic originals separately. ### Can sync snapshots replace my own long-term backup? Existing sync-restore snapshots can support partial recovery according to their timestamps and descriptions, but remain app-managed. Before migration or major reorganisation, also export a separate backup you can locate and retain originals to control retention and recovery sources. ## What to read next - [Restore files and connections when changing devices](). - [Decide upload and download direction before syncing](). - [What to keep before clearing storage](). ## Sources and version Checked on October 22, 2026: ManYue 2.0.2 for iPhone / iPad. Based on [the public description on the China App Store](), [Apple release lookup]() and the corresponding feature entry points. Interface labels may change with the version. Feature access is determined by the app’s current purchase screen.