Local First
Chordy stores data locally first. You can keep reading and editing available songs even when the device is offline.
Sync waits for connectivity and uploads pending changes when the device can reach the server again.
Synchronization
Sync and AI features are currently part of a closed alpha. An admin must approve your email address before you can sign in and use those features.
For sync to become active, you must be signed in and the device must be online. If those requirements are not met, Chordy collects changes locally and can synchronize them later.
In Settings, choose a sync interval or run Sync now manually. Available choices include Never, on start and changes, and fixed time intervals while the app is running. The sync panel shows:
- Connection status
- Account status
- Last successful sync
- Pending local changes
- Local folder, song, set, and file counts
- Storage persistence information
- Current diagnostic issues or hints
Recovery Actions
Use Recover from server to clear local sync metadata and pull a fresh copy from the server.
Use Replace server data only when this device is the version you want every other synced device to receive. Chordy creates a backup before replacement starts.
Backups
In Settings, create a backup before major imports or cleanup. You can also set an automatic backup interval, limit the number of stored backups, export a fresh backup, restore a saved backup, or import older Chordy archive files.
Backups are stored inside the app by default and can be downloaded, restored, or deleted. A backup is separate from sync. Keep exported backups somewhere you control if the library is important.
Restore From File
Chordy can restore current database backup files and import older archive files. Supported restore/import archive names include .chordydb, .chordydb.json, .chordybak, and .chordybak.json.
For .chordydb files, Chordy asks before import whether to overwrite the current local database or merge the backup data with existing songs, folders, sets, and files.
Repair Database
If songs, folders, or sets no longer appear under the expected project, you can run the database repair from Settings → Advanced. The repair scans the entire hierarchy and corrects incorrect project and folder assignments.
Unreachable items (e.g. when the target folder was deleted) are reported as orphans but not automatically fixed. The repair report shows which items are affected.
Before every repair, Chordy automatically creates a backup. On native devices, this backup is stored in the app data directory and is not shared via the system share sheet.