A production local workspace needs a backup of its whole folder. Automatic desktop snapshots of .tano/ protect only some workspace metadata; they do not replace backups of Markdown and attachments.
What to preserve
| Data | Location | Backup method |
|---|---|---|
| Markdown, attachments, and other user files | Workspace folder | Full export or your own file backup |
| Workspace identity, file IDs, objects, and relations | .tano/ |
Full export; automatic local snapshots also exist |
| Unsaved drafts, sync queue, and device settings | Application data | Device backup; not included in a full workspace export |
.tano/ is portable source data, not a disposable cache. Copying only .md files may lose identity, objects, and relations.
Export a full workspace
Choose Export entire workspace in desktop workspace settings, then select a destination outside the workspace. The export includes ordinary files, attachments, the complete .tano/ directory, and other workspace files, plus a verification manifest. To import, choose the archive from the welcome screen or workspace settings and select a new destination. Existing workspaces are not overwritten.
The archive does not include unsaved drafts, login tokens, sync queues, or server history. Keep it on another drive or versioned storage, and periodically check that it can be read and verified.
Missing or damaged .tano/
The desktop app keeps recent valid snapshots of .tano/ in application data. When identity files for a known workspace disappear or change, normal writes stop and a recovery entry is offered. Preview snapshot time, file count, and differences before confirming recovery. Recovery does not rewrite current Markdown or attachment bytes.
Without a valid snapshot or full archive, old file IDs, objects, and relations cannot be reconstructed from Markdown alone. You can copy surviving user files into a new folder, but that creates a new workspace identity.
File sync's Workspace history covers only synchronized revisions and complements a local full backup. See File sync.