A home network links computers, cloud storage, a NAS, and an off-site drive for secure file syncing and backup.
Syncthing is a free, open-source way to keep folders in sync across Windows, macOS and Linux machines without a Dropbox subscription. XDA Developers writer Ayush Pande says he has swapped Dropbox for it. He keeps coding projects, home-lab documentation and academic notes in sync across a MacBook, a mini-PC and a full-size desktop. The story is worth a look for anyone weighing a self-hosted setup against a subscription. The fine print matters, though, and "free" and "no internet needed" are doing some heavy lifting in the headline.

A home network links computers, cloud storage, a NAS, and an off-site drive for secure file syncing and backup. The author's case against Dropbox​

Pande's complaint is partly cost and partly architecture. He says he has a few hundred gigabytes of files he considers essential. Dropbox's Plus plan lists at $9.99 a month. Dropbox's plan page shows that tier as 2 TB of storage with 30 days to restore deleted files. He finds the 30-day window short for some files. He also objects to paying over a hundred dollars a year to sync files between three devices that sit on the same network.

He raises two further objections:

  • Connectivity. Even with LAN sync enabled, he says Dropbox still wants constant internet access to coordinate his devices.
  • Privacy. He is wary of keeping sensitive project data and embargoed-hardware benchmarks on a third-party cloud.

These are one user's priorities, not a universal verdict. The "over a hundred bucks a year" figure is his own arithmetic. It compares a subscription against hardware he already owned. It does not account for the cost of buying and running that hardware.

What Syncthing is and how it differs​

Syncthing's own site describes it as continuous file synchronization between two or more computers. It runs on Windows, Unix-like systems including Linux and macOS, Android and other platforms. Your data lives on your devices, not on a central server. Communication is encrypted with TLS, and only devices you explicitly authorize can connect.

That architecture is the real difference from Dropbox. There is no hosted account and no storage quota. You also get no web interface, no managed off-site copy and no vendor-run recovery. The devices you own are the service.

On Windows specifically, the project itself does not ship an installer. One self-hosting write-up notes this and uses a community package, Syncthing Windows Setup. Wikipedia also lists SyncTrayzor, a community-built taskbar tray wrapper for Windows. The same walkthrough notes the service account needs change permissions on any folder you want to sync.

The setup Pande describes​

  • Three Send & Receive nodes. The MacBook, mini-PC and gaming PC all both send and receive changes.
  • A fourth, receive-only node. A Proxmox LXC container runs Syncthing in Receive-only mode. Per Pande, it accepts changes from the other three but never pushes its own back. It works as a makeshift storage server.
  • Staggered versioning with a 90-day maxAge. This is meant to balance edit history against disk space.
  • Tailscale. This gives the laptop access to the other devices when he is away from home.
  • Proxmox Backup Server. The Syncthing LXC is snapshotted to a local PBS instance. That instance is linked to a second PBS machine at a relative's house, built from an old N100 NAS and spare hard drives. He calls this his 3-2-1 backup pipeline.

Fine print: what the documentation says​

Several of the claims in the story need scoping against Syncthing's official documentation.

Versioning only covers remote changes. Staggered versioning moves files to the .stversions folder when they are replaced or deleted on a remote device. Syncthing's docs add that if you change a file locally, it cannot archive the old version. Community forum answers say the same. In one thread on a Windows-to-Ubuntu setup, a user was told to check the versioning folder on the server side, not on Windows. In practice, turn versioning on for the devices that receive changes, such as Pande's receive-only LXC. Then test a restore before you rely on it.

The 90-day setting is not a 90-day snapshot. Staggered versioning keeps one version per 30-second interval in the first hour, one per hour in the first day, one per day in the first 30 days, and one per week until the maximum age. That is a thinning schedule, not a full point-in-time backup of every file. Setting the maximum age to 0 keeps versions forever.

Receive-only is not a backup. Syncthing's folder-type docs say receive-only mode is useful for replication mirrors and backup destinations. Local changes made on that node are not sent out. The docs also say a locally modified node will look out of sync to the other devices. Syncthing then offers a "Revert Local Changes" button to undo the divergence. The mode keeps a mirror tidy. It does not stop a bad edit or deletion on the other nodes from propagating to it.

"No internet required" has caveats. Local devices can sync over the LAN without a cloud repository. But Syncthing's docs say relaying is enabled by default. It is used only when two devices cannot connect directly. The relay still sees device IDs and traffic volume, though not the content. Relayed connections are also much slower than direct ones. So Syncthing avoids a central data store. It does not remove every piece of shared network infrastructure unless you configure it that way.

Tailscale is a separate layer. Syncthing does not include remote access. Tailscale's documentation says devices must be added to your tailnet. If an admin has turned on device approval, new devices show a "Needs approval" status until someone with the right role approves them. That is two services to install, authenticate and maintain.

The backup chain is Proxmox's job. Proxmox's documentation describes remotes and sync jobs for copying datastores between PBS servers. Backups are sent incrementally and deduplicated on the server. Transfers use TLS, and client-side encryption is available but off by default. Pande's off-site copy therefore depends on his own PBS arrangement. A plain Syncthing install does not provide it.

Dropbox vs. Syncthing at a glance​

ConsiderationDropbox Plus (per its plan page)Syncthing (per its docs and the author's setup)
Cost$9.99/monthNo license fee; you supply devices and storage
Storage2 TBLimited by your own disks
Deleted-file recovery30 daysPer-folder versioning you configure, only for remote changes
Off-site copyIncluded in the serviceYour responsibility (here, PBS to a relative's home)
Remote accessBuilt into the serviceDirect, relayed, or via something like Tailscale
MaintenanceVendorYou

Who should consider this​

A self-hosted setup suits people who already run a home lab, are comfortable with Proxmox or a NAS, and want direct control of their data. Pande clearly fits that profile. His storage was already sitting in a drawer, so the real cost of his approach is time and attention.

If you want a web interface, shareable links, managed off-site storage or someone else on the hook when a drive dies, Dropbox's price buys that. Pande's own admission that Syncthing "can't provide" cloud backup is the key caveat in his article.

Practical takeaways before you switch​

  1. Decide which devices need versioning, and enable it where they receive changes.
  2. Treat any receive-only node as a mirror, not a backup.
  3. Keep a separate off-site copy, and consider encrypting it. PBS client-side encryption is off by default.
  4. Test a restore of a deleted and an overwritten file before trusting the setup.
  5. If you roam, plan the remote-access layer, whether Tailscale, direct connections or relays.

Bottom line: Pande's story is an enthusiastic single-user account, not a benchmark or a controlled comparison. His results rest on his own hardware and skills. The documentation backs up the core idea, which is a subscription-free, device-to-device sync that fits a home lab well. The responsibility for backups, recovery and remote access moves to you.

 

References

  1. I ditched Dropbox after finding this free self-hosted file-sharing app, and I'm not going back XDA 2026-11-18T11:00:21+00:00
  2. Struggling with staggered file versioning - #5 by tomasz86 - Support - Syncthing Community Forum forum.syncthing.net
  3. Folder Types — Syncthing documentation docs.syncthing.net