Last updated: October 20, 2026
First decide what you need to recover from
Most comparisons start with a price table. That misses the failure you actually fear.
Imagine a vault containing five years of research. You edit one note on your laptop while your phone has an old copy. You accidentally delete a folder. Later you lose the laptop. These events need different solutions:
- Cross-device access: get the same current files onto the phone and computer.
- Conflict handling: resolve edits made before all devices agree.
- Version history: retrieve an older version of a specific note.
- Independent backup: restore the whole vault even if its synchronized copies disappear or become corrupted.
- Privacy and portability: know where the files are, which operator could access them, and how you could leave.
Our recommendation across four options: choose Obsidian Sync for mixed devices and integrated sync with version history; consider iCloud Drive if you use Apple devices only; choose Syncthing when free peer-to-peer synchronization is worth managing device availability, conflicts, versioning and a separate backup (with substantial iOS caveats); choose Git if you want explicit versioned commits and can resolve merges. None substitutes for an independent backup.
Official Obsidian backup guidance makes that distinction explicit. The strongest rule in this article is not “buy Sync”; it is do not put a single working vault in two competing sync systems, and do not mistake identical files on several devices for a restorable backup.
The decision matrix that matters
| Choose | What you gain; what you must manage |
|---|---|
| Obsidian Sync | Cross-platform synchronization inside Obsidian, end-to-end encryption and plan-dependent history. Manage the encryption password, storage limits and any concurrent edits. |
| iCloud Drive | An Apple file workflow you may already use. Keep files downloaded for offline access; iCloud is not an integrated Obsidian note-history interface. Not recommended here for Windows vaults. |
| Syncthing | Free, peer-to-peer folder synchronization without a paid cloud account. You must configure device availability, conflict handling, file versioning (off by default) and an independent backup. No official Syncthing iOS client; check iPhone/iPad limitations before choosing it. |
| Git | Explicit checkpoints and readable diffs. Pull before editing, commit and push afterwards; resolve conflicts. A private repository is not automatically end-to-end encrypted. |
Do not interpret the table as a laboratory finding that one engine has fewer bugs. It describes officially documented workflows and the risks inherent in their architectures.
Option 1: Obsidian Sync — pay for fewer workflow decisions
Obsidian Sync’s appeal is integration. There is a remote vault, your local vaults connect to it, and the client exposes synchronization history and older versions. You do not have to build a Git repository or manually shuttle folders between devices.
The official Sync page, checked October 19, 2026, lists Standard at $4/month billed annually ($48/year) or $5 billed monthly, and Plus at $8/month billed annually ($96/year) or $10 billed monthly, before any applicable tax. These are fees for the add-on service, not for using Obsidian itself, which is free.
| Plan | Limits that affect the choice |
|---|---|
| Standard | 1 vault; 1 GB total; 5 MB maximum per file; 1 month of note history. |
| Plus | 10 vaults; 10 GB total, expandable to 100 GB; 200 MB maximum per file; 12 months of note history. |
The limits come from the official plan documentation. Attachment retention differs from note history: Obsidian’s history guide says older attachment versions are held for two weeks. Plus is therefore not a 12-month revision archive of every PDF.
A case where Standard may be enough: one research vault of 350 MB with every synced file within the 5 MB limit, several devices and no need for a year of note revisions. Attachments and version history also count toward storage, so 350 MB of current files is not the whole quota calculation. Leave room for revisions. This is an illustrative workload, not a benchmark.
A case where Plus becomes relevant: multiple separate projects, large attachments, or a genuine need to recover a note version months later. But if your biggest concern is catastrophic loss of the entire library, buy or arrange backup first; extending sync history is not the same protection.
One non-negotiable setup practice: when switching from iCloud or another cloud service, Obsidian says to move the vault out of the old syncing location before enabling Sync. Running the two engines against the same files may produce conflicts. A second copy created manually is different from two active live sync services.
Option 2: iCloud — the practical Apple route, with awkward failure modes
If your life is Mac plus iPhone or iPad, Obsidian’s official multi-device documentation lists iCloud among the recommended options for iOS. The familiar advantage is that the files live in Apple’s file-provider ecosystem and you may already pay for iCloud storage.
But iCloud gives you file synchronization, not an Obsidian-aware collaboration log. An important risk is file availability: a document visible in a cloud folder may need downloading to the device before an offline session. You should test a travel-day offline workflow rather than assuming every attachment is already local. This is an operational precaution, not a claim that iCloud always drops files.
A safe Apple-only trial
- Create a small throwaway vault in the supported iCloud/Obsidian location, not with your only irreplaceable research.
- Add three notes and a small attachment on the Mac.
- Wait for iCloud to finish processing, then open them on the phone.
- Put the phone in airplane mode; edit a test note. Do something different on the Mac while the phone is disconnected.
- Reconnect and inspect what the files look like. Did a duplicate appear? Did a local file need re-downloading? If so, understand your recovery route before migrating the production vault.
- Confirm you still have a separate restorable copy of the whole original vault.
Choose iCloud if: you have an Apple-only workflow, your vault is modest and your existing plan has adequate storage. Obsidian explicitly warns that iCloud Drive on Windows can cause duplication or corruption. For a vault that must work on Windows as well as an iPhone, choose another transport; this is not just a question of convenience.
Apple’s storage pricing varies by country, so this guide does not invent a global iCloud+ monthly cost or suggest that all readers have the same free quota after other backups and photos.
The important fourth option: Syncthing — free device-to-device synchronization
Not every Obsidian user needs a paid remote vault or Git commits. Obsidian’s official cross-device guide also documents Syncthing: a free, open-source way to keep a folder aligned between devices. It is especially relevant to someone moving Markdown notes among a Windows computer, a Mac, a Linux machine or Android, without paying for an Obsidian-specific cloud service. Unlike Git, its purpose is to synchronize files rather than ask you to commit every change. It does not make a separate recoverable backup unnecessary.
The trade-off is operational responsibility. Syncthing’s official conflict documentation describes how incompatible edits can create a `sync-conflict` file. Its versioning documentation states that retaining old received versions is disabled by default and, when enabled, applies to changes received from other devices, not necessarily to a file you just changed locally. Do not treat this as an automatic 30-day backup.
iPhone/iPad warning: the Obsidian guide does not officially support Syncthing on iOS, where third-party workaround apps are needed, while Syncthing itself says it has no official iOS client. Choose Syncthing when you are comfortable configuring peers, versioning and recovery, and when your devices support the workflow. For simple iPhone + Mac use, iCloud or Obsidian Sync may be easier; for explicit source history, Git has a different role.
Our evidence boundary: this is a comparison of vendor-documented features, not a claimed firsthand Syncthing speed, reliability or iOS test.
Option 3: Git — a record of changes, not magic real-time sync
Git is valuable when you want to see what changed and keep meaningful checkpoints. Imagine each week’s research as a series of edits. A commit can capture a deliberate state, and a remote repository can hold copies of those commits outside your laptop. For developers or technical researchers this workflow may feel natural. For someone who just wants notes on a phone in seconds, it can become a source of chores.
Obsidian’s own Git guidance describes the steps: configure a remote repository, commit locally and push, then pull on other machines. The maintainer’s Obsidian Git documentation stresses that Git/GitHub is not a live syncing service. Changes will not appear instantaneously between two open editors.
A safe workflow in plain language
- Place the vault in a Git repository and create a private remote if its contents are not public. Private visibility is access control, not end-to-end encryption; do not push secrets or sensitive material on the assumption that a remote is unreadable to its operator.
- Make your first commit and push from the main computer.
- On a second device, clone the repository and verify the same tracked Markdown files arrived.
- Before editing on a different device, pull and resolve any conflicts; after editing, commit and push again.
- Practise a deliberate conflict in two throwaway notes. If you cannot understand or restore the result, Git is not yet the safest primary transport for your real vault.
- For iOS, consider the officially discussed third-party Working Copy path; verify its current paid features and required file access rather than calling it a free turnkey solution.
Choose Git when readable version diffs and repository processes matter more than simplicity. Avoid it when you need nontechnical family members to edit the same research simultaneously or you cannot invest time in merging.
Is Git better backup?
It may form part of a backup strategy, but only if the remote is configured and you actually push. Repository history can be deleted, credentials lost, remote accounts closed, or an accidental force-push performed. Keep a separate, independent exported copy, ideally with offsite or offline retention. Obsidian explicitly calls out Git as one possible backup method but warns that synchronization and recovery are different disciplines.
What we actually tested: a Git conflict and exact restoration
To move beyond generic vendor descriptions, we ran a reproducible, disposable Git experiment with an ordinary Markdown note and a synthetic binary attachment, using Git 2.47.3. This was not a test of the Obsidian application or of Obsidian Sync, iCloud or Syncthing.
Two copies of the same vault-like folder were edited independently. Git rejected the push from the stale copy. When we deliberately changed the same line in both copies, it flagged a conflict that required a human resolution. We then deleted and committed the removal of the note and binary attachment, restored them from the previous commit, and verified that a fresh third clone received the recovered files. The binary attachment’s SHA-256 matched its original: 4fbfd5178f6c262593c170c46d0385ae912669c3b739e00283be30e89e10653d.
Result: 10/10 scripted checks passed under those controlled conditions. The critical limitation: Git could recover the files only because their earlier contents had actually been committed and still existed in reachable history. That is useful evidence for recoverability of committed content, not proof of automatic sync, good mobile usability, or the reliability of another product. Read the full reproducible protocol and results before drawing a broader conclusion.
The case study: one vault, three devices, one accidental deletion
Imagine a 700 MB Markdown vault used on a Mac, an iPhone and a Windows laptop. On Friday, 30 notes are edited; one important research folder is accidentally deleted on Saturday.
With Obsidian Sync: the deletion may sync. For deleted files, use Settings → Sync → Deleted files → View, select the files and restore them within the retention period. The Sync sidebar does not list deleted items. For a note that still exists but was changed, inspect its version history. Neither route is a full-backup guarantee.
With iCloud: this mixed Windows/Apple setup is one we advise against, following Obsidian’s warning. If you are already in it, preserve local snapshots before migrating. On a supported Apple-only setup, deletions can still propagate; check iCloud/Files recovery and your independent backup instead of assuming the phone retains yesterday’s copy.
With Git: if the lost folder was tracked in commits, you may be able to recover it from repository history, provided those commits still exist locally or remotely. If your work was never committed, Git cannot recreate it. If access to the remote and every local copy is lost, history there may be unreachable.
A fourth protection layer works regardless of sync tool: have a scheduled, independent, tested copy of the vault. Pick a file from last month, restore it to a different folder and open it. Then verify that restoring did not overwrite newer changes.
How to switch without creating duplicates or losing attachments
When you migrate, think of the change as a short project, not a toggle. Make a complete local snapshot first. Identify exactly one active sync system for the working vault. Let the old system finish, stop it for that vault, and move the working copy to a safe non-synced location before configuring the new one. Follow Obsidian’s migration instructions rather than improvising with folders that are still updating.
Start from the main device, verify counts and a few random attachments, then connect the next device one at a time. Leave all other devices offline during the initial sync if you are uncertain about their last state. The correct success test is not a green indicator alone; it is being able to open the same notes and attachments, then restore a deliberately changed test note from the documented history.
Do not assume deleting a “duplicate” vault is safe until you can identify which copy contains the latest version of every irreplaceable note. When unsure, preserve both snapshots and sort the difference on a disposable copy.
Four decisions that choose the right method for you
Do I have Apple-only devices, a modest vault, and a reliable separate backup? Consider iCloud first; an already-familiar file workflow may be enough.
Do I have mixed devices or want an integrated encrypted sync history without Git maintenance? Obsidian Sync is the better natural fit if the price and plan limits work for your files.
Do I want free automatic synchronization between compatible computers or Android devices, and can I manage peers and conflicts? Syncthing deserves a serious look, with version history enabled deliberately and a separate backup. Its unsupported official iOS route may be decisive.
Do I need explicit revision commits and am I comfortable resolving merges? Git offers a different kind of control. It is not the sensible default for everyone who owns a laptop.
Final recommendation: choose one synchronization method based on your devices and tolerance for maintenance, then choose a separate backup based on how much of your work you cannot replace. A paid sync service and a free Git repository can both be good choices — for different people and different failure modes.
If you are choosing a knowledge-management app rather than sync transport, see our Notion vs Obsidian vs Anytype and Anytype vs Obsidian guides.
Sources and limitations, October 2026
Obsidian pricing · Sync limits · Version history · Official backups vs syncing · Migration without mixing systems · Git/iOS device guidance · Obsidian Git maintainer docs. Price quotes are US-dollar examples shown on the vendor site; no original performance, conflict-rate, restore-speed or security penetration testing is claimed.