TIME WAIT BLOG.
#Productivity Tools August 20, 2026 12 MIN READ

Free Obsidian Multi-Device Sync for Windows, Mac, and Android

Mac at home, Windows at work, and Android in your pocket can share one Obsidian vault with Syncthing. This guide covers backups, device pairing, folder sharing, conflicts, offline edits, and version protection.

Free Obsidian Multi-Device Sync for Windows, Mac, and Android

Mac at home, Windows at work, and an Android phone in your pocket. The three devices do not need to be on the same Wi-Fi to keep one Obsidian vault in sync.

An Obsidian vault is a normal local folder. Syncthing keeps a selected folder consistent across devices. Each device trusts the others through a Device ID, and the same Folder ID is shared with the devices that should receive the files.

This setup does not require Obsidian Sync, GitHub, or a regular cloud-drive folder. You still own a few responsibilities. At least two participating devices must be online for a while, conflicts need human review, and independent backups are still necessary.

You can connect only a Mac and Android, or add Windows and build a fully connected three-device group. A device that is not added will not receive the vault.

This guide covers Android. iPhone requires a separate setup.

Syncthing connects Windows, Mac, and Android through Device IDs and one Folder ID

Back up before the first sync

Choose the device that has the most complete copy of your notes. This is the source device.

The other devices will receive the vault.

For the first sync, the destination folder on every receiving device should be empty. Do not let several devices start with different copies of the same notes.

Close Obsidian on every related device. Compress the source vault into a ZIP file and copy that ZIP somewhere outside the folder you are about to sync.

If the vault currently lives inside OneDrive, Dropbox, iCloud, or Google Drive, copy it to an ordinary local folder first. Two sync services writing to the same vault make conflicts much harder to understand.

Recommended paths:

Windows

C:\Users\your-name\ObsidianVaults\MainVault

Mac

/Users/your-name/ObsidianVaults/MainVault

Android

/storage/emulated/0/Documents/Obsidian/MainVault

Start with one complete source, empty receiving folders, and a separate ZIP backup

Install Syncthing

Install it only on the devices you plan to use.

The six-step path from installing Syncthing to opening the Obsidian vault

Windows

Open Syncthing Windows Setup and download the latest .exe installer.

Use these choices during setup.

  1. Install for the current user.
  2. Keep launch at user logon enabled.
  3. Allow the Windows Firewall rule.
  4. Leave the other options at their defaults.

The browser will usually open:

http://127.0.0.1:8384

The Syncthing page confirms that it is running.

Open Actions, then Settings, and name the device:

Windows-PC

Mac

Open Syncthing for macOS and download the latest version.

  1. Drag the app into Applications.
  2. Launch Syncthing.
  3. Allow network access when macOS asks.
  4. Find the Syncthing icon in the menu bar.
  5. Open Preferences.
  6. Enable launch at login.

Open the Syncthing page from the menu bar and name the device:

Mac

If macOS blocks the first launch, open System Settings, go to Privacy & Security, and choose Open Anyway near the bottom.

Android

Install the community-maintained Syncthing-Fork. The F-Droid build is the recommended option.

You can also use the GitHub releases. Confirm that the package name is:

com.github.catfriend1.syncthingfork

Allow these permissions on the first launch:

In Android system settings, find Syncthing-Fork and set its battery mode to Unrestricted. Depending on the phone manufacturer, this may be called Allow background activity or Don’t optimize.

Name the device:

Android

Pair the devices

Each device has a long Device ID. It is the device identity used for trust. Syncthing does not use one shared login account.

On the first device, open Syncthing, choose Actions, then Show ID. On Android, open the Device ID page in Syncthing-Fork.

Copy the ID.

On the other device, choose Add Remote Device, paste the ID, and enter the device name.

Save it, return to the first device, and accept the new-device request.

When both devices show Connected, this pair is ready.

With Windows, Mac, and Android, create all three connections if you want any two devices to sync directly:

Windows ↔ Mac
Windows ↔ Android
Mac ↔ Android

If Mac and Android only know Windows, Windows becomes the only path between them. When Windows is offline, that pair cannot pass changes through it. Add Mac and Android to each other if you want them to sync while Windows is off.

At this point the devices know one another, but the vault has not been shared yet. The next section starts the actual file sync.

Share the Obsidian folder from the source device

Do this on the device that contains the complete vault.

Open Syncthing and choose Add Folder.

Set Folder Label to:

Obsidian Main

Set Folder ID to:

obsidian-main

Choose the real vault path.

Windows example:

C:\Users\your-name\ObsidianVaults\MainVault

Mac example:

/Users/your-name/ObsidianVaults/MainVault

Android example:

/storage/emulated/0/Documents/Obsidian/MainVault

Set Folder Type to:

Send & Receive

Under Sharing, select every device that should receive this vault.

Under Ignore Patterns, add:

.git
.obsidian/workspace.json
.obsidian/workspace-mobile.json
.trash
.DS_Store
Thumbs.db

Save the folder.

Accept the folder on every receiving device

Each receiving device will show a shared-folder request. Choose Add or Accept on each one.

Choose a local destination.

Windows

C:\Users\your-name\ObsidianVaults\MainVault

Mac

/Users/your-name/ObsidianVaults/MainVault

Android

/storage/emulated/0/Documents/Obsidian/MainVault

The folder should be empty on the first receive. Keep Folder Type set to Send & Receive and use the same ignore patterns.

.git
.obsidian/workspace.json
.obsidian/workspace-mobile.json
.trash
.DS_Store
Thumbs.db

Wait until every participating device shows Up to Date. Do not close Syncthing during the first transfer, and keep Android awake until it finishes.

Open the vault in Obsidian

Wait for Up to Date before opening the received folder in Obsidian.

On Windows or Mac, choose Open folder as vault and select MainVault.

On Android, open the vault manager, choose Open local folder, select:

Documents/Obsidian/MainVault

Allow Obsidian to read and write that folder.

A complete Mac and Android example

For a Mac and Android-only setup, the final relationship is:

Mac
/Users/your-name/ObsidianVaults/MainVault

             Syncthing

Android
/storage/emulated/0/Documents/Obsidian/MainVault

If the Mac already has the complete vault:

  1. Install Syncthing on Mac and Android.
  2. Copy Android’s Device ID and add it on the Mac.
  3. Accept the Mac on Android.
  4. Add MainVault on the Mac.
  5. Share it with Android.
  6. Accept the folder request on Android.
  7. Choose Documents/Obsidian/MainVault as the Android destination.
  8. Wait for both devices to show Up to Date.
  9. Open the folder in Android Obsidian.

Windows and GitHub are not involved in this two-device setup.

Run a two-way test

Create a note on the source device:

sync-test.md

Write:

This is the first line from the source device.

Wait for both devices to show Up to Date.

Open the same note on the receiving device and add:

This is the second line from the receiving device.

Wait for Up to Date again, then return to the source device.

Both lines should be present. That confirms two-way sync.

Daily use

Before switching devices, wait for the current device to show Up to Date. On the next device, wait for Up to Date before editing.

If multiple devices edit the same note at the same time, Syncthing may create a file containing sync-conflict. Do not delete it immediately. Open the versions, merge the content you need, and then remove the extra copy.

Keep the conflict copy, compare the content, and merge it manually

Syncthing does not keep an always-available cloud copy for you. At least two participating devices must be online for a while before a change can move between them. If the Mac at home is off, edits made on the phone stay on the phone. When the Mac comes online, the devices continue syncing.

Phone edits wait locally while the Mac is offline, then sync after the Mac returns

The devices can be in different locations. Syncthing tries a direct connection and may use a relay when a direct path is unavailable. A company network may restrict these connections. Follow your company’s data and network rules if a work PC is involved, and confirm that Syncthing shows Connected.

Enable old-version protection

On a computer, open Edit for Obsidian Main.

  1. Open File Versioning.
  2. Choose Staggered File Versioning.
  3. Set Maximum Age to 30.
  4. Save.

When the computer receives a replacement or deletion from another device, Syncthing puts the old file into .stversions. This can help recover an accidental deletion, but it is not a complete backup. Keep the independent ZIP archive.

Remote changes send old files to .stversions, while an independent ZIP backup remains necessary

Common problems

Android stays offline

Check Wi-Fi, background permissions, and battery restrictions. Open Syncthing-Fork and wait a minute.

Sync stops after closing the Mac window

Syncthing must remain running in the menu bar. Do not choose Quit, and confirm that launch at login is enabled.

Windows does not sync after a restart

Open Syncthing from the Start menu. If you reinstall it, keep launch at user logon enabled.

Obsidian cannot see the Android folder

Confirm that the folder is in ordinary shared storage:

Documents/Obsidian/MainVault

Do not put the vault inside Syncthing-Fork’s private application directory.

A folder shows Out of Sync

Close Obsidian on every related device and inspect the failed files in Syncthing. Keep the ZIP backup. Do not choose Override Changes, and do not delete the whole vault.

Start with a TestVault

For the first attempt, create a TestVault with only one note called sync-test.md. Wait for every participating device to show Up to Date, then edit the note from another device.

Once both directions work, back up and migrate the real vault. A small test keeps a first-time configuration mistake away from your actual notes.

/related_artifacts

rsync Two Large Directories: Resume Interrupted Copies and Verify Them
#Software Engineering Aug 14, 2026

rsync Two Large Directories: Resume Interrupted Copies and Verify Them

Don’t stuff two trees into one rsync. Dry-run first, copy serially with partial files and logs, then verify. A 100% progress bar is not permission to wipe the source disk.

read full log arrow_right_alt
Building Agent Memory That Survives the Next Session
#AI Agents Jul 16, 2026

Building Agent Memory That Survives the Next Session

A context window isn’t memory. I use a three-layer Markdown setup, write-time checks, and regular archival so agents can pick up where yesterday left off.

read full log arrow_right_alt