Short answer

Sync copies your current files between devices, including mistakes and deletions. A backup keeps older states you can go back to. Git with a private remote gives you a history and an off-device copy, as long as every device commits and pushes. Keep one non-Git copy as well, such as Time Machine or a zip, because that is what Obsidian’s own backup guidance recommends.

Sync, backup and version history: which one you have now

Obsidian’s help page “Back up your Obsidian files” says syncing is not a backup. Sync makes the files match on every device. A backup is a copy kept somewhere else so you can recover after loss or corruption. Version history sits between the two: it lets you open an earlier state of one note. The table shows what each common option gives you, as checked on November 20, 2026.

What each layer protects, checked November 20, 2026
OptionOff-device copy?Protects against accidental delete?How far back?Works on iPhone?
File recovery core pluginNo. Snapshots are device-specific and stay local.Yes, on the device where the edit was made.7 days by default. You can change it in settings.Not stated on the help page.
Obsidian Sync version historyYes, on Obsidian’s servers.Yes. Obsidian documents restoring a deleted file.1 month on Standard, 12 months on Plus.Yes.
iCloud DriveYes, in iCloud.Not as a backup. Obsidian lists iCloud among the services that sync notes between devices, and says syncing is not a backup.Not documented by Obsidian as a history source.Yes.
Git with a remoteYes, once you push.Yes, for anything that was committed.Every pushed commit, until you delete the history.Yes, with a Git client such as GitSync.md.

Two limits apply to Git. It records only what you commit, so an edit you never committed is not in history. And it protects only what reached the remote. For the full comparison of sync methods, see Obsidian Sync alternatives by device and iCloud vs Git for Obsidian. If you are weighing a subscription, the Obsidian Sync cost calculator compares the cost with Git.

Set up Git as the backup layer

This is the short version. Sync Obsidian with GitHub on every device has the full setup, and Obsidian Git on iPhone and iPad covers the phone side.

  1. Use a private repository. Create it on GitHub or your own Git server and push the vault to it. A private repository is only accessible to you and people you share it with, but your notes still live on the host’s servers. Keep secrets out of the vault.
  2. Add a .gitignore. Window layouts change on every device and create noise in history. Choose what your .gitignore shares shows a starter file. Ignored files are never backed up, so do not ignore notes or attachments.
  3. Commit on a schedule on the desktop. In the Obsidian Git plugin, turn on its automatic commit-and-sync (commit, pull and push on a schedule) and set the interval in its settings. Without it, nothing is backed up until you run a command.

Back up notes written on your phone

A note you write on iPhone or iPad is backed up only once it is committed and pushed. Saving it in Obsidian is not enough, and neither is a local commit. Phone-only edits are the ones most often missed.

  1. Open the vault’s repository in GitSync.md.
  2. Review the changed files and the diff.
  3. Commit and push from your iPhone with GitSync.md, or get it on Google Play if you use Android.
  4. Check the remote. Open the repository on GitHub and confirm the latest commit contains the phone edit.

You can reduce the manual steps. A Shortcuts sync action can pull, commit and push in one go; see Shortcuts automation for Git on iOS. GitSync.md also offers optional Background Sync, but iOS decides when background work runs, so it is not continuous and not guaranteed. What works for Obsidian Git background sync on iPhone explains the limits. Treat the remote check above as the proof.

Restore a note, a deleted note or a folder

The examples use a synthetic vault with Projects/Plan.md. Run the commands in a terminal inside the vault folder. They were tested on a throwaway repository. Quote paths that contain spaces.

Get an earlier version of a note

  1. Find the commit. List the commits that changed the file. See git log.
    git log --oneline -- "Projects/Plan.md"
  2. Check it. Compare the old version with the current one: git diff <commit> -- "Projects/Plan.md".
  3. Restore it. This overwrites the file in your working folder with the old version, so make sure the current content is committed or copied first. See git restore.
    git restore --source=<commit> -- "Projects/Plan.md"
    git add "Projects/Plan.md"
    git commit -m "Restore Projects/Plan.md"

Get back a deleted note

  1. Find the deleting commit.
    git log --diff-filter=D --oneline -- "Projects/Idea.md"
  2. Restore it from that commit’s parent, which still had the file (^ means the parent).
    git restore --source=<commit>^ -- "Projects/Idea.md"
    git add "Projects/Idea.md"
    git commit -m "Restore Projects/Idea.md"

Roll back a folder

Pick the commit that had the folder as you want it, then restore the folder path from it:

git restore --source=<commit> --staged --worktree -- Projects/
git status
git commit -m "Roll back Projects to <commit>"

The folder then matches that commit exactly. Notes you added to it after that commit are removed from the working folder and staged as deletions, so read git status before you commit. They stay in history and can be restored with the steps above.

Avoid git reset --hard on a vault with unsaved work

git reset --hard discards uncommitted edits with no undo. If you need to roll back the whole vault, copy the vault folder somewhere safe first, or commit your current state, then restore paths as above.

Without a desktop

  • GitHub in a browser. Open the file in your repository and choose History (the commit list for that file). Open the commit you want, view the file at that commit, and copy its text back into the note. For a deleted file, open the commit that removed it: its diff shows the old text in full, which you can copy. GitHub documents viewing a file.
  • GitSync.md. Use its commit history, with the files changed in each commit and their diffs, to find the commit and the old text. Copy the old content back into the note in Obsidian. This guide does not rely on an in-app restore button; confirm the result by reviewing the diff before you commit.

Finish: commit, push, pull

After restoring, commit and push so your other devices get the restored note, then pull on them. If a pull stops because the same note changed on two devices, follow the merge conflict guide.

When Git cannot help

Git cannot return an edit that was never committed. For that, open Obsidian on the device where you made the edit and use the File recovery core plugin: Settings → Core plugins → File recovery → Snapshots → View. Snapshots are kept per device, for 7 days by default, so act before they expire. If the note is missing on another device rather than lost, see the missing-note checklist.

Keep a second copy outside Git

Obsidian’s backup help recommends a one-way backup to a separate location, such as a computer backup like Time Machine or a periodic copy of the vault folder to a drive. It also lists Obsidian Git among popular backup plugins. A second copy protects you if you lose access to the Git host or push something wrong. GitSync.md does not make this copy for you.

Backup checklist

  • ☐ The vault is pushed to a private remote, and secrets are kept out of the vault.
  • ☐ A .gitignore excludes workspace files but not your notes.
  • ☐ Desktop auto commit-and-sync is on.
  • ☐ Your phone commits and pushes, and the latest commit on the remote shows a phone edit.
  • ☐ You restored a test note once, so the steps are not new to you in a panic.
  • ☐ A second copy exists outside Git.

FAQ

Is Obsidian Sync a backup?

Not by Obsidian’s own definition. Its backup page says sync services such as Obsidian Sync are “not designed for backups.” Sync does keep version history, for 1 month on Standard and 12 months on Plus, which helps you restore a note, but it is not a separate copy.

Does iCloud keep old versions of my notes?

Obsidian’s backup page lists iCloud among the services that sync notes across devices, which is not the same as a backup, and this guide does not rely on iCloud for old versions. Use Git history, File recovery or a separate backup for old versions.

Can I back up Obsidian from my iPhone?

Yes, if the phone commits and pushes. In GitSync.md, review the changes, commit and push, then check the commit on the remote. See the iPhone and iPad setup.

How do I recover a note I deleted?

If it was committed, find the deleting commit with git log --diff-filter=D -- <path> and restore from its parent with git restore --source=<commit>^ -- <path>. If it was never committed, try the File recovery plugin on that device.

Is a GitHub backup private?

GitHub says private repositories are only accessible to you and people you explicitly share access with, but the files are still hosted on GitHub’s servers. Do not store secrets in the vault.

Related guides