Syncthing syncs your files without routing them through California

When you drop a file into Dropbox on your desktop PC, it travels to an AWS data center in California before coming back down to your laptop sitting 30 centimeters away. That detour isn’t a bug — it’s the business model. Syncthing does the reverse: an open-source P2P protocol with no central server, where every device talks directly to its peers over TLS 1.3. The project crossed 87,000 GitHub stars in July 2026, v2.1.2 is the current stable release, and the Syncthing-Fork Android client (maintained by Catfriend1) fills the gap left by the official Android app’s discontinuation in December 2024. Here’s why your files no longer have an excuse to cross the Atlantic.

How Syncthing works without a central server

The model is fundamentally different from Dropbox, Google Drive, or even Nextcloud. All three depend on a server — cloud-hosted or self-hosted — that stores files and redistributes them to clients. Syncthing removes that link entirely: every device is an equal peer, and files travel directly from one node to another, encrypted end-to-end.

Identity is handled through Device IDs — a SHA-256 fingerprint of each device’s TLS certificate, displayed as a 56-character human-readable string. Two devices can only communicate after mutually exchanging their Device IDs. No password, no email, no user account. Authentication happens at the certificate level, not the login level.

Peer discovery works on two layers:

• Local discovery — IPv4 broadcast and IPv6 multicast every 30 seconds. Two machines on the same LAN find each other automatically with zero configuration.
• Global discovery — encrypted announcement sent to public discovery servers (discovery.syncthing.net) every 30 minutes. These servers never see your files; they only maintain a Device ID → IP address mapping.

When direct connections are impossible — double NAT, restrictive firewalls — Syncthing falls back to a public relay that encrypts the traffic but cannot decrypt it. You can also run your own relays and discovery servers if you want to exit the community infrastructure entirely.

What Syncthing 2.1 delivers

Released in May 2026, the 2.1 branch brings three concrete improvements for daily users:

• Folder and device grouping in the web UI. You can organize shares by project or context — a Work folder with its three machines, a Photos folder with your phone and NAS — and the interface displays them grouped rather than in a flat list.
• HTTP/HTTPS CONNECT proxy support alongside existing SOCKS proxies, making deployment easier in corporate environments where only an HTTP proxy is permitted.
• Block indexing toggle for folders where reducing local database size matters more than transfer optimization. Useful on resource-constrained hardware — Raspberry Pi, entry-level NAS boxes.

Version 2.1.2, released on July 15, 2026, fixes roughly twenty bugs with no regressions. 2.1.3-rc.2 is in pre-release as of July 28, 2026, signaling an active maintenance cycle.

Installation: one binary, one browser, done

Syncthing is written in Go and distributed as a single binary. No dependencies, no runtime, no external database. Deployment is three commands on any Linux box:

# Install via APT repository (Debian/Ubuntu)
curl -s https://syncthing.net/release-key.gpg | sudo apt-key add -
echo "deb https://apt.syncthing.net/ syncthing stable" | sudo tee /etc/apt/sources.list.d/syncthing.list
sudo apt update && sudo apt install syncthing

# Enable as a user service with auto-start
systemctl --user enable --now syncthing

The admin interface lives at http://localhost:8384. You add a folder, add the remote device via its Device ID, and sync begins. On Windows and macOS, the official site provides a graphical installer bundling the binary, the service, and a system tray icon.

Since the official Android client was discontinued in December 2024, the Syncthing-Fork project (available on Google Play and F-Droid) carries the torch, with active maintenance and extras like configurable sleep mode and per-folder notifications.

Versioning, folder types, and fine-grained control

Syncthing does more than copy files. Every shared folder supports several parameters independent of the remote peer:

• Folder types — send-receive (bidirectional, the default), send-only (one-way backup), receive-only (read-only). The receive-encrypted mode lets you sync encrypted files to an untrusted device — a friend’s NAS or a storage VPS — without that device being able to read the content.
• Versioning — three built-in strategies. Trash Can archives deleted files in .stversions with a configurable retention period. Simple keeps a defined number of timestamped versions. Staggered applies time-based retention tiers — ideal for working folders where a file edited 100 times in a day shouldn’t fill the disk.
• File ignore patterns — .stignore files with wildcard and regex support, equivalent to a .gitignore for sync.

These features make Syncthing feel closer to rsync than to Dropbox — with the decisive advantages of continuous, bidirectional sync and built-in encryption.

The showdown: Syncthing vs. Dropbox, Google Drive, and Nextcloud

The table below compares what fundamentally distinguishes each approach. The angle isn’t “which is best” — it’s “what do you actually need.”

Syncthing shines when you already have files across multiple machines and want them kept in sync with no intermediary. Nextcloud makes sense when you need a full collaborative platform. Dropbox still makes sense when you want to administer nothing — but you pay for that convenience in monthly fees and data residency.

Verdict: who should switch, who should wait

Switch to Syncthing if your files need to flow between your own machines — desktop, laptop, home server, NAS — and privacy matters more than collaboration. The absence of a central server means no VPS outage, no missed invoice, and no cloud provider can block access to your files: they live on your disks, period. The canonical use case remains syncing a Documents or Obsidian vault between a desktop and a laptop: transparent, instant, encrypted.

Pair Syncthing with Nextcloud if you need a web interface to access files from any browser, or want to share folders with people who won’t install Syncthing. The two tools aren’t competitors — they complement each other in a self-hosted stack.

Stay on Dropbox or Google Drive if you share files with clients who use those platforms, or have nobody to administer even a Go binary updated once a month. But for everything else, the California detour no longer has a reason to exist.

References

• Syncthing — Official website
• Syncthing GitHub — 87k stars, accessed July 2026
• Syncthing v2.1.2 — Release notes, July 15, 2026
• Syncthing v2.1.0 — Major changes, May 2026
• Syncthing-Fork — Android client, maintained by Catfriend1
• Syncthing Documentation — Security Principles
• Syncthing Documentation — File Versioning
• This Week in Self-Hosted — 10 July 2026, selfh.st
• XDA — I replaced Dropbox with Syncthing, and learned these 5 things