Obsidian - Sync Vaults Between PCs with Github

Keeping an Obsidian vault in sync across multiple PCs doesn’t require an always-on cloud service. Because Obsidian stores everything as a plain folder of files (including a hidden .obsidian settings folder), the vault can be backed up and synchronized using standard file-sync tools—most notably GitHub—so changes made on one machine can be pulled onto another.

The core tradeoff is straightforward: Obsidian Sync is the official, paid, subscription-based option (listed as $10/month or $96/year) and is positioned as the recommended path, especially for Apple users. But the practical appeal of Obsidian is that its local, file-based design lets users choose their own sync method. The transcript walks through several alternatives—USB drives, Google Drive, OneDrive, and SyncThing—then focuses on GitHub as a preferred approach for “live” syncing and version history.

GitHub works here because it functions as a code repository: it tracks changes, supports collaborative editing, and maintains a commit history. In practice, the vault folder is turned into a GitHub repository using GitHub Desktop. Once the repository is published, changes can be pushed from one PC to GitHub and then fetched/cloned onto another PC. The result is a near-real-time workflow where notes, folders, and content appear on the second machine as GitHub updates are pulled down.

A major advantage highlighted is auditability. GitHub’s commit history lets users inspect what changed in a specific note, including line-level differences (with removed content shown in red and additions in green). If something breaks—like a custom CSS tweak—users can browse prior commits and roll back to earlier versions.

The transcript also emphasizes the operational rule that prevents headaches: avoid opening the same vault on two computers at the same time. GitHub can handle merges, but Obsidian’s constantly changing state (such as active tabs and other session-like settings stored in the .obsidian folder) makes conflicts more likely. The recommended routine is to work on one PC, push changes to GitHub, close Obsidian, then switch to the other PC, fetch updates, open Obsidian, work, push again, and close.

Setup is presented step-by-step: install GitHub Desktop (or use git as an alternative), create or select an Obsidian vault folder, initialize it as a Git repository (adding a .git and .git attributes plus a README if desired), publish the repository (public or private), then use GitHub Desktop’s commit/push and fetch/clone features on the second PC. The workflow is framed as free for public repositories (with a stated storage allowance) and paid for private repositories, with the transcript noting private vaults may matter for copyrighted material.

Overall, GitHub-based syncing is positioned as a flexible, version-controlled alternative to Obsidian Sync—one that leverages Obsidian’s file-based vault structure while trading away the “set-and-forget” simplicity of an official sync service.