Cloud Backup and Automatic Sync

Back up shared data such as accounts and bookmarks to WebDAV or GitHub Secret Gist, synchronize it across devices, and restore it when needed. Upload or download backups manually, or enable automatic sync for your chosen data scope and strategy.

Cloud sync shares data rather than making a complete device backup. Before migrating devices, export a separate local JSON backup to retain device-specific settings.

Highlights

Backup and restore: Choose a provider on the Import/Export page, then upload or download a JSON backup.
Automatic sync: Run background sync on a schedule (every hour by default), merging or replacing data according to your strategy.
Three strategies: Merge, upload only, or download only, depending on each device's role.
Conflict merging: Keep newer accounts, bookmarks, and preferences by update time. Account and bookmark deletions carry deletion markers so older backups do not restore them during the next merge.
Upload verification: Read back and compare the cloud backup after upload, reporting success only after confirming that it was saved.
GitHub Secret Gist: Connect an existing Secret Gist with a GitHub token, or create a new unlisted Gist. Gist uploads always use encrypted backups.

Prerequisites

Choose WebDAV (such as Nextcloud, Nutstore, Alist WebDAV, or a NAS) or GitHub Secret Gist.
For WebDAV, obtain a URL, username, and password with read/write access. For Gist, prepare a GitHub token and a backup encryption password.
Allow the browser to run in the background for automatic sync. Scheduled tasks cannot run normally while the browser is closed or the device is asleep.

Setup

Open the extension → Import/Export → Cloud Sync settings.
Choose WebDAV or GitHub Secret Gist as the sync provider.
For WebDAV, enter:
- Server URL: A directory or a specific JSON file. A directory URL uses all-api-hub-backup/all-api-hub-1-0.json beneath it.
- Username/password: Credentials for Basic Auth.
Click Test Connection, then use Upload Backup or Download Backup as needed.

The service, sync data scope, strategy, and automatic sync switch save automatically. The interval saves when you leave its field. Connection details and encryption passwords save when you leave the field, including empty values. Configuration completeness is checked when syncing.

WebDAV uploads update the backup file at the configured location. The extension selects a write method supported by the service and verifies the result, usually without additional settings.

GitHub Secret Gist

Create a GitHub personal access token. Prefer a fine-grained token with Gists: Read and write; a classic token needs the gist scope. See the GitHub Gist API permissions. The token stays in the current browser and is excluded from backups.
Select GitHub Secret Gist and enter the token. For an existing Gist, enter its ID or https://gist.github.com/... link; leave this blank when creating one.
Set an encryption password and click Upload to Secret Gist. If the ID is empty, the extension automatically creates an unlisted Gist with public: false, stores encrypted content in all-api-hub-backup.json, and fills in the ID. Later uploads update the same Gist.
For an existing Gist, click Test Connection to check that it is a readable Secret Gist with a nonempty backup file. Import and sync also decrypt and validate the backup; a successful connection test alone does not guarantee that its content can be imported.

A Secret Gist is unlisted, not access-controlled. Protect the token, encryption password, and Gist link, and keep tokens out of screenshots or backup files. Manual JSON exports exclude the Gist token, ID/link, and encryption password. Configure Gist again on a new device. Existing WebDAV manual export behavior is unchanged.

Automatic Sync

Enable Automatic Sync on the same page to schedule the selected provider:

Option	Description
Enable automatic sync	WebDAV and Gist share these settings; only the selected provider runs. Manual backups and Sync Now remain available when scheduling is disabled.
Sync interval	In seconds; defaults to 3600 (one hour). Minimum: 60 seconds for WebDAV, 300 seconds (five minutes) for Gist.
Sync strategy	Merge, upload only (replace remote data with local data), or download only (replace local data with remote data). Sync Now also uses the saved strategy.
Sync Now	Run one sync immediately. If another sync is running, wait and retry. Pending setting changes finish saving before the sync starts.

How Sync Runs

Saving settings updates the background schedule for the selected provider.
During a sync:
- Test the provider connection and credentials.
- Download the remote backup. A missing WebDAV backup can be initialized according to the strategy. Automatic Gist sync stops if its backup file is missing or empty; initialize it with a manual upload first.
- Export local accounts and preferences, then apply the strategy:
  - Merge: Keep the latest entries by updated_at / lastUpdated. Merge account and bookmark deletion markers to prevent older copies from restoring deleted items. Account conflicts use whole-account last-write-wins (LWW), not field-by-field merging: a newer account replaces the older account together with its check-in configuration.
  - Upload/download only: Use the local or remote data, respectively.
- Merge and download-only strategies write their results locally; merge and upload-only strategies upload the backup.
- Check the cloud file's content after upload. If saving cannot be confirmed, report a failure.
Check the settings page for success/failure status and the last execution time.

Version Compatibility and Multi-device Upgrades

The current backup format is V4, and older V6 accounts have their check-in configuration upgraded to V7. V1–V3 backups remain importable. The previous V3 reader attempts to reject V4 backups to avoid overwriting data with an older structure; earlier clients that permissively parse unknown versions are not guaranteed safe.

Pause automatic sync, upgrade every device sharing the backup to a version supporting V7 accounts, then re-enable sync. V6 and V7 clients must not write to the same backup concurrently: whole-account LWW can let an older client replace V7 check-in configuration with a V6 account. Before downgrading, stop sync on other devices and keep a separate backup.

If the Gist revision changes before the write check, the extension reports a conflict and stops that upload; retry sync later. This is a best-effort check, not an atomic conditional write. Another device can still write after the check, so stagger sync times where possible.

Automatic Check-in Across Devices

Accounts and preferences can sync through WebDAV or Gist, but today's execution state, recent results, and browser alarms do not sync across devices. Multiple devices with daily schedules can still check in twice. Enable scheduled check-in on only one device if you want to avoid this.

Security Tips

Use a dedicated WebDAV account or access token for the backup directory. Grant GitHub tokens only the required Gists permissions.
Avoid saving WebDAV passwords on public devices; rotate them when necessary.
Keep a separate local backup of important data. The extension does not maintain cloud version history, and some services may leave an incomplete file after an interrupted upload. Do not rely solely on the latest cloud backup.

FAQ

Problem	What to do
WebDAV connection test fails	Check that the URL includes a protocol (`https://`) and that remote writes are allowed.
WebDAV returns 401/403	Check the username, password, and read/write permissions on the backup directory and file. If the directory cannot be created automatically, create it manually on the cloud service first.
Automatic sync does not run	Check that automatic sync is enabled, the service configuration is complete, and the browser is not suspended. Review errors in the sync status.
Duplicate accounts or bookmarks after merging	Delete duplicates and upload again; use upload-only mode if you need strict control. Deletion markers normally prevent older backups from restoring deleted accounts or bookmarks.
Remote backup reported corrupt before upload	The existing WebDAV backup is not valid JSON. If this device has complete data, follow the prompt to rebuild it from all shared data on this device. Otherwise, upload from a complete device or import a complete backup first.
Gist backup file missing or empty	Automatic sync and import stop; missing content is not treated as an empty backup that clears local data. If this device has complete data, manually upload and confirm replacement to initialize the existing Secret Gist.
Gist content corrupt or incompatible	Import or sync stops. Check `all-api-hub-backup.json` and the encryption password, repair the backup, and retry. Do not replace the remote backup with incomplete local data.
Gist returns 401/403/404 or a rate limit	For 401, check token expiry; for 403, check Gists permissions; for 404, check the Gist ID or whether it was deleted. For rate limits, wait until the indicated retry time.
Verification fails after upload	Check the network and cloud read/write permissions, then retry. If the cloud backup is damaged, upload again from a device with complete data or restore from a separate backup.
The backup directory contains `.tmp.` files	These temporary upload files are normally cleaned up automatically and do not affect successful syncs. To attempt recovery from a retained file, pause sync and download it for inspection first. Later uploads may remove temporary files older than 24 hours. Encrypted files still require the original encryption password.
JSON file too large	Remove obsolete accounts to stay within the provider's limits. Separate manual exports can be used for archiving, but automatic sync still uploads a complete backup of the selected data.