- Mac, iPhone, and iPad: iCloud is an option when you want file syncing without a Git workflow.
- Windows and iPhone: consider Git if you want commits and can manage pulls, pushes, and conflicts. For integrated syncing, compare Obsidian Sync with Git.
- Already using iCloud successfully? Adding GitSync.md is not required to keep using that setup.
Disclosure: this comparison is published by GitSync.md’s developer. It compares documented workflows, not measured sync speed or reliability. Sources were checked October 26, 2026. GitSync.md is independent of Obsidian and Apple.
Start with the devices you actually use
Obsidian lists macOS, iOS, and iPadOS as the recommended systems for its iCloud method. It warns that iCloud Drive on Windows may cause duplicated or corrupted files. That is a vault-specific caveat, not a claim that Apple offers no Windows software. Read Obsidian’s current iCloud guidance before choosing it for a Windows vault.
GitSync.md’s documented iPhone route uses a local Obsidian vault and a Git remote. On Windows, a desktop Git client manages another local working copy. The Windows and iPhone walkthrough explains the setup and verifies edits in both directions. This requires more deliberate handoffs than opening a cloud-synced folder.
What changes when you choose Git?
On a narrow screen, scroll the table sideways to compare both methods.
| Decision | iCloud | Git workflow |
|---|---|---|
| Apple devices | Obsidian documents an iCloud vault setup for Mac, iPhone, and iPad. | Each device needs a local working copy and a compatible Git client. |
| Windows + iPhone | Obsidian warns about iCloud Drive on Windows. | Use desktop Git on Windows and GitSync.md on iPhone, with the same remote and branch. |
| Publication | File changes are handled by the cloud sync service. | Review changes, commit a snapshot, then push it to the remote. |
| History | Do not treat file synchronization as a substitute for a separate backup. | Review committed versions and diffs. Uncommitted edits are outside commit history. |
| Storage location | iCloud Drive’s Obsidian folder. | A local vault outside folders managed by another sync service. |
| Troubleshooting | Check the vault location and downloaded files. | Check the working copy, credentials, branch, and pending changes. |
The folder you open determines the workflow
For iCloud, Obsidian’s mobile instructions place vaults in iCloud Drive → Obsidian → Your Vault. Its documentation also explains keeping files downloaded so they remain available locally. Follow that setup rather than creating an unrelated folder with a similar name.
For our Git route, clone into On My iPhone → Obsidian, or the equivalent local iPad folder, with Store in iCloud off. Open the exact cloned folder in Obsidian. GitSync.md and Obsidian then use the same local files. Follow the full iPhone and iPad Git setup for prerequisites and authentication.
Our recommendation is to give one sync method responsibility for each active working copy. A second service moving files underneath a Git operation adds another source of changes to diagnose.
Git history records what you commit
Git records selected versions of files so you can inspect earlier states. It does not save every keystroke. If you write a note but never commit it, that edit is not in commit history. A commit saved only on the phone also has not reached your remote until you push. See Git’s explanation of version control.
When devices make different changes, Git may need a merge. It does not guarantee conflict-free notes. The conflict recovery guide covers preserving edits and reviewing the result. Pull before starting on a second device, and push before leaving the first.
Keep a separate recoverable copy with either method. A sync system can propagate an unwanted change; a Git remote contains only the history and files you actually sent. Obsidian’s backup guide explains choosing a separate backup location and checking that your vault can be recovered.
Compare privacy settings and the whole cost
Apple distinguishes standard iCloud protection from optional Advanced Data Protection. Its security table lists iCloud Drive as encrypted in transit and on the server under standard protection, and end-to-end encrypted with Advanced Data Protection. Review Apple’s security overview, including recovery requirements and applicable limitations, for your account.
An ordinary private GitHub repository restricts access, but that does not make the notes end-to-end encrypted. Choosing HTTPS or SSH protects the connection; it does not by itself encrypt the Markdown for only your devices. Consider what you store and who can access your remote.
For cost, check whether your vault fits your available iCloud storage and whether you would need a storage plan. For the documented Git route, GitSync.md costs $19.99 once on the US App Store; local prices differ. Git hosting and any backup service have their own terms. A one-time app purchase does not include unlimited storage from a Git host.
Move to a new method in a separate copy
- Finish editing, allow the current sync method to catch up, and preserve any device-only notes.
- Make a separate backup and open several notes and attachments from it to check the copy.
- Create a new local destination for the method you chose. Keep the original until the new workflow is verified.
- For Git, follow the local-folder publication guide or the Windows setup. Review which files will be published before the first push.
- Use a disposable note to verify an edit reaches the other device, then verify an edit travels back. Check an attachment too.
- Open the new vault on each device and retire the old sync route for that active copy. Keep the backup.
These steps describe a migration approach, not a tested one-click import from iCloud. Avoid deleting the old vault to troubleshoot an incomplete transfer.
Common questions
Do I need the Obsidian Git plugin?
Not for the manual workflow described here. GitSync.md can run Git operations while Obsidian edits the local vault. The plugin is a separate option if you want Git operations inside Obsidian; Connect configures supported GitHub authentication, rather than changing the vault’s sync service.
Will Git sync while my iPhone app is closed?
Do not choose it on the assumption of a fixed background schedule. Read the background-sync limits and test manual pull and push first.
Can I keep iCloud and Git on the same active vault?
This guide uses separate local Git working copies. Keep a backup separately and choose one active sync route per copy. If your goal is automated syncing without managing commits, evaluate Obsidian Sync as well.
