Obsidian Git backup and sync on iPhone with LocalGit
Write in Obsidian; keep versioned notes on GitHub with LocalGit. Link a local vault that both apps can access under On My iPhone, review its changed files, and tap Synchronize. LocalGit handles the Git steps and provides per-file history without requiring a Git plugin inside Obsidian.
How to use it
Confirm the vault location
Use a local Obsidian vault with Store in iCloud turned off. In Files, confirm its folder is under On My iPhone and that Obsidian can still open and edit it. Select the vault root, not just a notes subfolder.
Prepare a GitHub repository
Create a separate copy of your vault before setup and test with disposable notes first. Choose a writable GitHub repository; use a private repository for personal notes. Review the keep-local or replacement choice carefully when either side already has content.
Link and synchronize
Link the vault in LocalGit, make a test edit in Obsidian, and let the editor finish writing. Review changes, synchronize, then confirm the note appears on GitHub. Notes and attachments are included unless your Git ignore rules exclude them.
Browse history and automate the routine
Use Free file history to browse changes to a committed note. Apple Shortcuts can trigger Synchronize when Obsidian opens or closes. The Pro preview adds deleted-note search and Restore as copy; purchases are not enabled in the current build.
Check the fit
Synchronize can bring GitHub changes into your vault as well as upload local edits. It is two-way Git sync, not a one-way backup or continuous background protection. Keep a separate backup and avoid combining sync services on the same vault. iCloud Drive vaults are unsupported. Only files captured in Git can be recovered from Git history.
In short
Choose LocalGit for Obsidian when you want a guided GitHub workflow for a compatible local vault: edit notes, review changes, Synchronize, and inspect file history. Working Copy can also link Obsidian folders and automate sync; LocalGit emphasizes stable capture and explicit recovery in a focused interface.
