Obsidian Sync - Sync notes between PC and Mobile

Obsidian Sync is a paid, end-to-end encrypted way to keep an Obsidian vault consistent across a PC and a mobile device—without relying on cloud storage that treats notes like generic files. The practical payoff is straightforward: ideas captured on a phone (on the bus, at work, or while camping) can land on the desktop ready for deeper drafting, while the desktop remains the main workspace.

The setup starts with Obsidian’s “local-first” model: notes live as folders and files on each device. That design differs from tools like OneNote, where notes are stored on a remote server and pulled down from the cloud. Obsidian Sync bridges that gap by syncing vault contents to a remote “sync vault,” then downloading updates to other devices. The service is not free—plans begin at $4 per month (the transcript notes a recent price drop from $8). The $4 tier includes one synced vault, 1 GB storage, a 5 MB maximum file size, and one month of version history; higher tiers raise storage and file-size limits and extend version history.

Security is a major selling point. Sync uses AES-256 and offers end-to-end encryption options, including either automatic key generation or user-managed keys. The walkthrough also emphasizes operational controls that matter in real life: syncing can be paused (useful when traveling without reliable internet), deleted files can be reviewed and restored based on the plan’s version history window, and an activity log provides visibility into what’s uploading and when errors occur.

A key feature for managing mobile constraints is selective sync. Instead of syncing an entire vault, users can include or exclude specific file types (images, audio, video, PDFs, and more) and exclude folders entirely. This is positioned as a way to keep mobile storage under control—e.g., syncing only the folders needed for quick idea capture while leaving heavy assets or campaign prep materials on the PC.

The transcript then drills into a real-world complication: some community plugins store critical state outside the note text, which can break when synced. The clearest example is Obsidian Leaflet. Leaflet pins and map data are stored in a data.json file, and the walkthrough shows that edits made on one device may not reliably appear on the other when the note is open—leading to “fighting” between devices and missing pins. The workaround recommended is to right-click pins and convert them to code blocks, so the map markers are saved into the note content itself rather than only into external plugin state.

After addressing that plugin edge case (and noting the image converter plugin can also cause issues by renaming/converting assets during sync), the walkthrough demonstrates the core workflow: create or edit a note on PC, see it appear on mobile, then type on mobile and watch changes propagate back to the desktop with a small delay. The overall message is that Sync works well for typical note-taking and offline-then-sync patterns, but plugin-heavy vaults may require careful configuration or workarounds to ensure data survives round-trips between devices.