GuideSync & data
Offline and sync
How local-first sync works, offline editing, merging concurrent edits and history.
Local first
Every change is written to your device first (IndexedDB in the browser, a local database on desktop) and pushed to the server in the background. So:
- Offline, you can create, edit and organize as usual; the status reads "Offline · N changes will sync when you are back online".
- When the connection returns, pending changes are pushed automatically.
- The app never waits for the server to open your notes.
Live sync
While online, the server tells your other devices about new changes and they pull them, usually within a second or two.
Editing on two devices at once
- Title, notebook, tags, pinned and other properties merge per field; the latest change of each field wins.
- Body text is merged three-way against the version you started from. Edits to different paragraphs combine into one note.
- When both sides changed the same lines and cannot be merged, your version is saved as a conflict copy and the original stays as it was. No words are lost; compare the two and merge by hand.
History
Synced libraries keep history automatically. Open History from the note menu to view and restore an older version.
Retention: everything from the last hour; one version per 10 minutes for a week; then one per day until the server's retention period.
Trash
Deleted notes go to the trash first and can be restored.
Sync status
| Status | Meaning |
|---|---|
| Synced | This device and the server agree |
| Syncing… | Pushing or pulling |
| Offline | No connection; changes are kept on this device |
| N changes refused by the server | E.g. an attachment over the size limit; see the message |
Signing out with unsynced changes asks you to confirm, because those changes would be lost.
Still stuck? Send feedback Feedback