Syncthing — My Simple Local-First File Sync Setup
I needed my notes accessible from both my Mac (main workstation) and a Windows desktop in another room. Cloud sync works but feels wrong for hundreds of MB of personal markdown — I don't want my notes on a third-party server, I don't want to pay for storage I don't need, and I don't want to wait for uploads when I'm just editing plain text.
Enter Syncthing. Open-source, peer-to-peer, encrypted, no cloud dependency.
How It Works
Syncthing keeps a directory in sync between two machines over LAN. Edit a file on one machine, it appears on the other within seconds. No manual sync, no "which version is this" confusion, no cloud round-trip.
This setup covers two devices on the same local network. Scaling to more is straightforward — add the new device, share the folder.
Setup
Install
Mac (Homebrew):
brew install syncthing
brew services start syncthing
Windows:
Download the installer from syncthing.net or use winget:
winget install syncthing
The web UI runs at http://127.0.0.1:8384 on both machines.
Pair Devices
- Open the web UI on both machines
- On one machine, click "Add Remote Device" and enter the other device's ID (found under "Actions > Show ID")
- Accept the pairing request on the other machine
- Both devices should now appear as connected
Share a Folder
- Click "Add Folder" on one machine
- Give it a label (e.g.,
Notes) - Set the folder path to your document directory
- Under "Sharing", check the other device
- On the other device, accept the folder share and set the local path
Syncthing will scan and sync the directory.
Key Settings
Ignore Patterns (.stignore)
You can exclude files you don't want synced. Create a .stignore file in the folder root:
workspace.json
cache/
tmp/
*.log
This prevents Syncthing from syncing machine-specific state files and temporary data.
Folder Type Options
- Send & Receive (default) — bidirectional sync. Changes on either machine are propagated.
- Send Only — changes from this machine go out, but incoming changes are ignored. Useful for a primary workstation where the other machine is for reading.
- Receive Only — this machine receives changes but doesn't send its own. Useful for a backup or reference machine.
Scan Interval
Default (60 seconds) works well for most use. For faster sync, reduce to 10 seconds. Filesystem watchers on most modern OSes trigger faster than the scan interval anyway.
Why Syncthing
| Tool | Why Not |
|---|---|
| Dropbox / Google Drive / OneDrive | Cloud dependency, subscription cost, privacy concerns |
| Git | Great for code, poor for real-time note sync (conflicts, manual pushes) |
| Resilio Sync | Proprietary, free tier limited |
| iCloud Drive | Mac-only, unreliable with SMB mounts |
| rsync / cron | Manual, one-directional, no conflict detection |
| Nextcloud | Overkill for two machines, requires a server |
| SMB-only (no sync) | Works but no conflict resolution, manual version tracking |
Syncthing hits the sweet spot: peer-to-peer, encrypted, no server, no subscription, cross-platform, and handles conflicts gracefully (keeps both versions with a .sync-conflict- suffix).
Considerations
- No built-in version history. If a file is deleted on one device, it's deleted everywhere. Enable "File Versioning" in the folder settings for a recycle bin.
- LAN is fast. Syncthing can run over the internet, but for two machines in the same building, LAN is faster and more private.
- Large binary files. Syncthing handles them, but syncing a 500 MB file every time it changes is wasteful. Exclude large build artifacts and model files from sync.