Export a backup
Export a workspace archive you can retain for backup or transfer.
Last updated 16 September 2026
Export a workspace archive you can retain for backup or transfer.
Before you start
Open Settings → Data backups. A Choro workspace archive should be kept alongside your normal repository and file backups; do not assume it replaces them.
Demo screenshot: Settings → Data backups. Export creates an archive; Import restores one and replaces workspace data. Use Export for this guide.
Step by step
Finish or pause work that you want represented consistently in the backup, then open the export controls in Data backups.
Choose Export and wait for the operation to finish. Keep Choro open until it reports the result.
Read the success message for the exact exported path. The filename begins choro-workspace-export and includes a timestamp. Choro normally chooses Downloads, with other local fallback locations when a Downloads directory is unavailable.
Check the filename, timestamp, and that the file is present before relying on the export. Store a copy in a location appropriate for the workspace information it contains.
Keep older known-good archives until you have established that your new backup is usable. Back up the underlying project folders and Git repositories through your normal process too.
What to expect
You have a dated export file that can be selected in Choro’s import workflow. Exporting is separate from uploading or sharing that archive.
Troubleshooting and useful details
If no file appears, read the export result and check the destination’s available space and write access. Avoid repeatedly clicking Export while one operation is in progress. An archive can contain private workspace content, so review the destination before sharing it.
