- Choose GitSync.md if you want the documented Obsidian vault workflow, the Connect credential handoff, and a paid iPhone/iPad app with manual Git and optional Background Sync included.
- Consider Working Copy if you need its documented signed commits, repository search, WebDAV access, or remote SSH commands, or already have a folder workflow that works for you.
Disclosure: this page is published by GitSync.md’s developer. It compares our documented capabilities with Working Copy’s official documentation and App Store listing, checked October 26, 2026. It is not a side by side performance test or an independent review. Prices and feature availability can change.
Both apps work with local Git repositories on iPhone and iPad. Either can suit an Obsidian workflow; the useful distinction is how you connect the vault, authenticate, automate, and pay for the capabilities you need.
Capabilities at a glance
| Workflow | GitSync.md | Working Copy |
|---|---|---|
| Local Git | Clone, edit, stage, commit, pull, and push. | Clone, edit, commit, and push; pushing requires Pro. |
| Obsidian files | Clone into Obsidian’s local folder or publish a local vault. | Link an external folder, including an Obsidian vault; requires an eligible Pro unlock. |
| Obsidian Git authentication | Connect configures supported GitHub HTTPS vaults from the existing GitSync.md sign-in. | Its documented external-folder route lets Working Copy perform Git operations. |
| SSH and other hosts | Manual remote URLs with HTTPS or SSH credentials. | SSH and multiple hosting providers are documented. |
| Conflicts and large files | Merge/rebase controls, three-way conflict editing, and Git LFS. | Merge/rebase conflict tools and Git LFS. |
| Automation | Apple Shortcuts, callbacks, and optional best-effort Background Sync. | Shortcuts, callbacks, and Auto-Sync for linked repositories. |
Sources: GitSync.md capabilities, Working Copy features, Working Copy manual, and its App Store listing. A shared feature name does not establish identical behavior or limits.
How the Obsidian workflows differ
GitSync.md: a shared local vault, with an optional credential companion
Clone a GitHub vault under On My iPhone → Obsidian, open it in Obsidian, and use GitSync.md to review and publish changes. You can also start with a local vault using Publish a Folder. Notes remain ordinary files with a local Git working copy.
If you want Git commands inside Obsidian, GitSync.md Connect can configure the Git plugin using your existing GitHub sign-in. This handoff requires a supported GitHub HTTPS repository, not SSH or a separate per-repository HTTPS token. Connect does not change the plugin’s mobile Git implementation or enable automatic sync. Native GitSync.md operations have their own capabilities.
Start with the full iPhone and iPad setup guide or the Windows and iPhone guide.
Working Copy: link the folder and use its Git workflow
Working Copy’s manual documents external repositories and an Obsidian workflow using a linked folder. It also documents Auto-Sync for that route. Read the external repositories section before choosing a folder layout or automation settings.
If your existing Working Copy setup already handles your vault reliably, changing tools may add little value. Check the specific setup step you want to improve before migrating.
Purchase terms
GitSync.md for iPhone and iPad: $19.99 once on the US App Store, with unlimited repositories, manual Git tools, the editor, and optional Background Sync included. There is no subscription. The separate Connect companion is free. Android uses a different free-download and one-time Full Access purchase model.
Working Copy: free to download, with Pro required for pushing and other features. Its App Store listing offers a 10-day Pro trial. An unlock keeps the features available at purchase plus those added during the next 12 months; later new Pro features can require another unlock. Existing unlocked features remain available. That is not a subscription requirement to retain those features. Check the current local in-app price and eligibility.
Compare the purchase needed for your actual workflow, including folder linking and pushing, rather than comparing download prices alone. View GitSync.md on the App Store →
When Working Copy deserves a closer look
Its published feature set includes commit signing, repository search, and HTML previews. Its manual also documents WebDAV and running commands over SSH. If one of these is central to your workflow, check that implementation directly instead of choosing only on Obsidian setup or price. [Features; manual]
GitSync.md’s focus here is its documented local-folder Git and Obsidian integration. This comparison does not establish feature parity for every development workflow.
Before switching Git clients
- Commit and push intended changes in the current client, and keep a separate copy of any unsynced notes.
- Try the new client with a disposable repository or a fresh clone. Verify an incoming note, an outgoing commit, and the remote branch.
- Choose which client performs Git operations. Pause overlapping automation before pointing multiple clients at the same working copy.
- Verify the local folder before removing the old repository from an app. Do not delete a vault as a migration step.
For GitSync.md failures, use the troubleshooting checklist. A successful import or clone does not by itself prove a daily sync workflow.
Common questions
Is GitSync.md a Working Copy alternative?
Yes, for workflows such as local Git repositories, editing Obsidian notes, reviewing diffs, and publishing commits from iPhone or iPad. Choose based on the operations and folder integration you need; the apps are not interchangeable in every detail.
Do I need Obsidian Git with either app?
Not when the native Git app performs all Git operations and Obsidian only edits the shared notes. GitSync.md Connect is relevant when you choose to run Git commands inside Obsidian’s Git plugin.
Does GitSync.md guarantee background sync?
See the detailed background-sync explanation for native attempts, plugin automation, and Shortcuts.
No. iOS controls when it grants background time. GitSync.md attempts permitted work and stops for unsafe Git states. Connect only configures credentials. Test manual transfers before enabling automation.
