Haniewicz440 downloadsTwo-way auto/manual sync for an Obsidian vault using Google Drive.
Google Drive Vault Sync is a community plugin that syncs an Obsidian vault two-way with Google Drive using the Google OAuth 2.0 Device Authorization Flow.
This plugin is not affiliated with, endorsed by, or sponsored by Obsidian. Obsidian is a trademark of its respective owner.
Always make a full backup of your vault before using this plugin, especially before enabling automatic sync or using reset actions. Sync software can overwrite, move, or delete files when misconfigured, interrupted, or used with conflicting changes.
The author is not responsible for any data loss, file corruption, missed synchronization, account issues, Google Drive quota usage, or any other damage caused directly or indirectly by using this plugin.
Sync now command.main.jsmanifest.jsonstyles.css.obsidian/plugins/google-drive-vault-sync/
Settings > Community plugins.BRAT can give you access to the newest plugin features before they are included in a stable release. These builds may be buggy, not fully tested, and potentially unsafe for your vault. They can overwrite, move, delete, or corrupt data if a sync bug slips through. Make an independent backup of your vault before using BRAT builds, and avoid testing them on your only copy of important notes.
If you accept that risk:
Settings > BRAT.Add Beta plugin.https://github.com/Haniewicz/ObsidianGoogleDriveSync
Google Drive Vault Sync in Settings > Community plugins.npm install
npm run dev
The plugin avoids Node-only runtime APIs where possible. Local vault access uses the Obsidian Vault API, HTTP uses requestUrl, and hashing uses Web Crypto.
Create a Google OAuth client suitable for TVs and limited-input devices in Google Cloud Console when available, enable the Drive API, and use the https://www.googleapis.com/auth/drive.file scope. Paste the OAuth client ID and client secret into the plugin settings.
Do not commit your OAuth client secret or plugin data.json to any repository.
The settings tab includes reset actions for replacing Google Drive data from the local vault or replacing the local vault from Google Drive. These actions ask for confirmation and use trash where possible, but they can still overwrite files. Review the prompts carefully before running them.
Automatic backups can run in safety-only, timed, or every-sync mode. Safety backups are created before risky sync actions that can overwrite or remove files. Timed backups also capture routine local changes at a controlled interval. Manual full backups can be named and are stored separately from automatic backups, so they are not removed by the automatic backup retention limit.
Backup preview supports text diffs where possible. You can restore all files stored in a backup or restore a single file from that backup.
Cloud watch checks the remote manifest frequently and starts a full sync only when Google Drive changes are detected. The full sync interval is kept as a slower fallback safety net. The plugin also registers a mobile Sync now command with an icon so it can be added to Obsidian mobile command surfaces where available.