Direct device sync avoids a central file account
Syncthing watches selected folders and sends changes between approved devices. There is no provider account holding the master copy. Each machine has a cryptographic device ID, and two machines communicate only after both sides add each other. That arrangement is attractive for a laptop, desktop, home server, or family setup where the machines and disks are already yours. The web interface handles pairing, folder sharing, status, and conflicts without demanding that every user understand the wire protocol.
The absence of central storage changes availability. A new laptop can receive a folder only while another device containing it is online. With 2 frequently connected machines this is rarely a surprise; with several intermittently connected laptops it can be. An always-on home server makes the experience feel closer to hosted sync, but then you own its disk health, updates, remote reachability, and backups. Syncthing gives you control over storage rather than removing storage administration.
Synchronization will copy a mistaken deletion
The official FAQ is unusually direct: Syncthing is not an ideal backup application because changes and deletions propagate to other devices. File versioning can retain older copies, and receive-only folders can reduce certain accidental changes, but neither replaces a tested backup on separate media. If ransomware encrypts the files in a synchronized folder, those changed files are still changes for the system to distribute.
That distinction should decide where you deploy it. A 10.1 MB source checkout can become part of a good resilience plan, yet it cannot be the whole plan. Use Syncthing for current working data and a separate backup tool for history, retention, and recovery after operator mistakes. People replacing a cloud drive should also decide which machine stays online and where snapshots live before moving important folders.
What happened when we ran it
Our sandbox installed 169 Go packages in 65 seconds, and the build completed in 82 seconds. We used commit 38ac58c in an unprivileged Debian container with 3 CPUs and 8 GB of RAM. The checkout contained 900 files, about 128,502 lines of source, and occupied 10.1 MB before dependencies. Eight CI workflow files, a Dockerfile, and a tests directory were present.
The test command failed with exit code 1 after 428 seconds. Go reported 23 package results as passed and 2 as failed out of 25. The final lines identify github.com/syncthing/syncthing/lib/syncthing as a build failure, followed by successful results for packages including syncutil, tlsutil, upgrade, upnp, and versioner. The supplied tail does not include the compiler message, so it supports no claim about the cause.
That is a source-build finding, not evidence that the signed v2.1.3 binaries fail to run. It does mean the simple README instruction, go run build.go, does not tell a contributor everything about obtaining a clean full-suite result in this fresh container. Anyone modifying the Go code should capture the earlier failure lines and rerun the exact package before treating the checkout as ready.
Pairing is simple, while network policy needs thought
First launch creates configuration, encryption keys, a device ID, and a local admin interface on 127.0.0.1:8384. Two peers exchange IDs and accept the folder on both ends. Direct TCP and QUIC connections normally use port 22000. When direct paths fail, discovery and relay services help peers find and reach each other. File traffic remains encrypted, including when a public relay carries it.
The security documentation also states what those helpers can observe. Global discovery announces a device ID, external address, and listening ports every 30 minutes, while local discovery broadcasts every 30 seconds. A selected public relay learns the connecting device IDs. Administrators can disable these defaults or point the software at private infrastructure, but dynamic peers may then need explicit addresses or their own discovery service. The right setting depends on whether easy roaming or metadata minimization matters more.
The official client does not mimic every cloud-drive feature
Syncthing copies ordinary files into ordinary folders, which makes exit easy and lets existing applications work without a virtual filesystem layer. The tradeoff is disk use: every fully shared device holds its local copy. Open issue 10844 asks for Windows placeholder files and on-demand download through the operating system, behavior familiar from OneDrive and Dropbox. The request confirms that this is not an official-client feature readers should assume.
Ignore rules also deserve testing before a large rollout. Issue 8735 documents an incorrect local state involving negated ignore patterns under an ignored parent, while issue 7311 requests an easier way to share ignore rules across devices. These are specific edge cases, not proof that routine folders are unreliable. They matter to developers synchronizing source trees with changing build directories, because a small pattern mistake can create confusing local and remote views.
August 2026 activity is healthy, with a live scan regression
GitHub showed 88,027 stars and 377 combined issues and pull requests when fetched. The last push was August 25, 2026, and v2.1.3 was released on August 5. That release includes device and folder grouping, HTTP and HTTPS proxy support, configurable GUI session duration, and fixes spanning database connections, deadlock handling, UPnP, ignores, and the API. The combined open count should not be read as 377 confirmed bugs.
Current activity does not erase current defects. Issue 10869 reports very slow scanning with identical files since v2.1.0, specifically on v2.1.3, and issue 10868 reports frequent garbage collection with a very large number of small files. If either workload resembles yours, test a representative directory before committing. For ordinary personal sync, the mature release process, signed binaries, clear documentation, and direct ownership model outweigh the extra operational work, provided a real backup remains beside it.