Obsidian offline sync: keep your vault local and in sync

Overview

Obsidian stores notes as plain Markdown files in a vault folder. “Offline sync” means keeping that folder consistent across your phone, laptop, and desktop—while still being able to read and edit without an always-on connection.

There is no single official Obsidian sync requirement. You choose a sync strategy that matches privacy, cost, and how much automation you want downstream (for example, feeding audio into a local transcription pipeline).

Why file-based sync matters

Obsidian’s strength is local files you can back up, grep, and version-control. Sync methods that treat the vault as a normal folder preserve that:

• Notes remain readable outside Obsidian
• Automation tools can watch folders for new audio or Markdown
• You are not locked into one vendor’s note format

If you use Nucleate, the vault folder can double as incoming audio and summary output paths. See Cloud & mobile workflow for a Box + Obsidian example inside Nucleate docs.

Option 1: Obsidian Sync (official)

Obsidian Sync is Obsidian’s paid end-to-end encrypted sync service.

Good for: minimal setup, encryption handled by Obsidian, conflict resolution built in
Tradeoffs: subscription cost; sync is tied to Obsidian’s service, not arbitrary folder watchers on all platforms

Works fully offline on each device once files are synced; sync runs when connectivity returns.

Option 2: Cloud storage folder (Dropbox, OneDrive, Box, iCloud)

Point your vault at a folder inside a cloud provider’s synced directory. The desktop sync client mirrors files locally; mobile apps read the same tree.

Good for: simple mental model, mobile access, pairing with phone recorders
Tradeoffs: files pass through vendor cloud; conflict handling can be messy if two devices edit the same note offline simultaneously

Tips:

• Use one primary editing device when possible to reduce sync conflicts
• Avoid editing the same note on two offline devices before sync completes
• Keep the vault small and text-heavy—large binary assets slow sync
• On Windows/macOS, confirm the cloud client uses placeholder/sync, not “online only”

Nucleate’s recommended mobile workflow uses a synced folder for incoming audio and Markdown outputs. Details: Cloud & mobile.

Option 3: Syncthing (peer-to-peer)

Syncthing syncs folders directly between your devices without a central cloud account.

Good for: privacy, no monthly sync fee, full control of where data lives
Tradeoffs: you operate the mesh; mobile setup is more involved than Dropbox-style apps

Typical pattern: vault lives on a desktop; phone and laptop pair as Syncthing devices; all copies update when online on the same network or over the internet.

Option 4: Git (version control)

Store the vault in a private git repository and push/pull from each machine.

Good for: developers who already use git, explicit history, backup on GitHub/GitLab
Tradeoffs: not real-time; merge conflicts in Markdown require manual resolution; poor fit for non-technical mobile editing

Best combined with another sync method for mobile, or for vaults edited mainly on one or two computers.

Choosing a pattern

Vault layout for audio workflows

If transcription tools write into your vault, separate concerns with subfolders:

vault/
├── inbox/audio/          # incoming recordings (optional)
├── notes/daily/          # daily summaries
├── notes/weekly/         # rollups
└── templates/

Use paths Nucleate or your recorder can target consistently. After processing, archive or delete raw audio to keep sync lean—Nucleate can move processed files to a local archive folder.

Troubleshooting

Duplicate or conflicted copies (Note (1).md)
Two devices edited offline before sync. Pick one version, merge manually, and establish a single “primary” device for hot files.

Vault empty on mobile
Cloud app may not have finished initial sync, or the vault path on mobile points at the wrong folder. Open the cloud app and wait for “synced” status.

Sync loops / high CPU
Exclude .obsidian/workspace.json and plugin caches from sync if your tool allows ignore rules—or accept that Obsidian workspace state syncs frequently.

iOS limitations
iOS sandboxes apps; direct folder sync is harder than on Android. Obsidian Sync or a provider with a solid iOS app is often the practical path. Nucleate’s iOS mobile workflow notes are on the cloud workflow page.

Using this with Nucleate

Nucleate reads and writes Markdown on disk. Point incoming audio and summary output folders at vault subfolders (local or cloud-synced). Processing stays on the machine where Nucleate runs; only files you choose sync outward.

Example desktop flow (Box + Obsidian) is documented in Cloud & mobile.

For the full audio → notes loop, continue to Voice memos to Markdown.

Related guides

• Voice memos to Markdown
• Local vs cloud transcription
• Ollama on Windows