Syncthing Problems & Issues
Real user-reported problems, complaints, and limitations for Syncthing. Based on analysis of 14 signals.
Overall score: 70/100
Issues by Category
Deletions sync everywhere and versioning is off by default
Syncthing is sync, not backup: a deletion or mass wipe on one device propagates to all of them. File versioning is disabled by default and only keeps copies of changes received from other devices, so users who never enabled it can lose data.
Syncthing not syncing or stuck on 'Out of Sync Items'
The most common forum thread type: devices show as connected but a folder sits at a partial percentage or lists out-of-sync items that never clear. Causes range from ignore patterns and permissions to case-mismatched paths and stale index data; fixes often end in restarting, rescanning or removing and re-adding the folder.
Syncthing sync-conflict files keep appearing
When a file changes on two devices before they sync, Syncthing keeps both and writes a .sync-conflict copy. Obsidian vaults and other apps that constantly rewrite config files (workspace.json) generate a steady stream of these, and some users report conflicts even when editing on one device only.
Official Syncthing Android app discontinued
The official Android app was retired with its last release in December 2024, citing Google Play publishing hurdles and lack of maintainers. Users now rely on the community Syncthing-Fork, whose maintainership and Play Store ownership have changed hands, which worries some users.
No official Syncthing iOS app
There is no official iPhone or iPad app because iOS background limits make continuous sync impossible. Third-party clients like Möbius Sync (paid beyond 20 MB) and SyncTrain only sync while open or when iOS grants background time, so it is not set-and-forget on iPhone.
Syncthing-Fork drains battery or stops syncing in the background on Android
Android battery optimisation kills the sync service after the screen locks unless the app is exempted, so phones only sync when opened. After the fork moved to Syncthing v2, many users reported 20%+ battery drain and rolled back versions.
Syncthing 2.0 database migration takes hours or days
Version 2.0 (2025) moved the index database from LevelDB to SQLite. On large setups the first start migrated for 27 hours, 40 hours or even more than a week according to forum reports, and a few upgrades failed with 'database disk image is malformed', requiring a database rebuild.
Why is Syncthing so slow? Relay connections
When devices cannot connect directly (NAT, firewall, Windows 'Public' network profile), Syncthing falls back to relay servers, and speeds drop to kilobytes per second. The official FAQ tells users to check that the connection type does not start with 'Relay' and fix direct connectivity.
Syncthing high CPU usage while scanning
Hashing new files and periodic rescans of large folders can pin CPU on NAS boxes, Raspberry Pis and laptops. CPU should drop once in sync, but folders with constantly changing files keep it busy; the FAQ suggests GOMAXPROCS to cap cores.
Cryptic 'folder marker missing' and 'folder path missing' errors
If the hidden .stfolder marker disappears (unmounted drive, cleaner apps on Android, moved folder) Syncthing pauses the folder with an error many users don't understand. In Docker or NAS installs the container path versus host path confusion causes the same message.
No selective sync, sharing links or web file access
Unlike Dropbox or Resilio, Syncthing syncs whole folders (only ignore patterns exclude files), has no share links for outsiders, no web file browser and no online copy. Both devices must be online at the same time for anything to move.
Windows tray app SyncTrayzor stalled
Many Windows users relied on SyncTrayzor for an installer, tray icon and autostart; it stalled and the community had to revive it, while the alternative Syncthing Tray needs more technical setup. Plain Syncthing on Windows starts as a console window unless you configure Task Scheduler.
Why is Syncthing so hard to set up?
Reviewers on Capterra and elsewhere repeatedly call first-time setup confusing: you exchange device IDs, accept folders on each device, choose folder types and work in a browser-based admin GUI. The official FAQ frames this as security over convenience; non-technical users often give up.
No official support, only a community forum
Syncthing has no helpdesk; help comes from the volunteer forum and docs. Maintainers answer quickly but usually ask for logs and versions, and a review notes the docs can lag behind releases. Businesses must buy third-party support.
Regret Patterns
Common reasons users regret choosing Syncthing.
Lost files because deletions synced everywhere
A folder was wiped or a drive unmounted on one device and the deletion propagated; versioning was never enabled, so there was nothing to restore.
Bought into it, then the Android app was retired
Users built phone photo and notes sync around the official Android app and had to migrate to Syncthing-Fork after December 2024, worrying about its maintainership.
Switched to an iPhone and sync stopped being automatic
Moving from Android to iOS means relying on Möbius Sync or SyncTrain, which only sync when iOS lets them run.
Weekend lost to an 'Out of Sync' folder
A folder stuck at 99% or with phantom out-of-sync items led to hours of log reading, rescans and finally removing and re-adding the folder.
Upgrade to 2.0 locked the NAS for days
On large libraries the SQLite migration ran for many hours or days with no sync in the meantime, and a few databases had to be rebuilt.
Gave up on getting family members set up
Device IDs, accepting folders and the browser GUI were too much for non-technical relatives, who went back to Google Drive or iCloud.
When Syncthing Breaks Down
Specific scenarios where Syncthing fails or underperforms.
iPhone in the mix
No official app; third-party clients sync only when opened or briefly in the background, so iPhone copies lag behind.
Hundreds of thousands of files on a NAS
Initial hashing and rescans pin CPU, and the 2.0 database migration took hours to days on large datasets.
Devices behind strict NAT or corporate firewalls
Direct connections fail and traffic falls back to relays, cutting speed to a crawl.
Apps that constantly rewrite their files
Obsidian workspace files, databases and open documents edited on two devices produce repeated .sync-conflict copies.
External or removable drives
If the drive is unmounted Syncthing reports 'folder marker missing'; misconfigured markers can even let deletions spread.
Using sync as your only backup
Ransomware, accidental deletes or corruption replicate to every device unless versioning and separate backups exist.
Android phone with aggressive battery saving
The OS kills the sync service when the screen locks, so the phone only syncs when the app is opened.