The Truth About Syncthing on iOS: Sandboxing, Battery Drain, and Data Loss
Syncthing is unreliable on iOS because Apple's sandbox stops third-party apps from running continuous background sync. iOS suspends the app shortly after you leave it, so folders go stale, conflict files pile up, and forcing it to stay awake drains the battery. For dependable iPhone folder sync, you need a tool built to deliver files without keeping an app on-screen — which is how Relaaay works.
Syncthing is excellent software. On a Linux server or a desktop that stays awake, it is one of the most reliable ways to keep folders in sync. On an iPhone, that reputation quietly falls apart — and the reason has nothing to do with Syncthing's code quality.
Why is Syncthing so unreliable on iPhone?
The problem is Apple's sandbox. iOS is built to protect battery life and memory by suspending apps soon after you stop looking at them. It does not let an ordinary third-party app run an open-ended background process.
Syncthing depends on exactly that kind of process. It needs to continuously watch your folders and stay in contact with your other devices. When iOS suspends it, that continuous work stops.
The result is a phone that thinks it is in sync but is actually frozen at whatever state it held when you last opened the app. Hours or days later, you discover the folder never updated.
The chain reaction: stale folders, conflicts, and lost work
A suspended sync engine does not just pause. It sets off a chain of downstream failures.
First, the iPhone's copy of a folder goes stale while your laptop and desktop keep changing files. Then, when the app finally wakes, it finds the same files edited in two places. It cannot know which version you wanted, so it writes conflict files — duplicate copies with awkward suffixes.
In the worst cases documented across forums, people lose work entirely: an edit made on the phone is overwritten, or a conflict copy is mistaken for the real file and the original is deleted.
Doesn't a dedicated iOS client fix this?
Third-party iOS clients such as Möbius Sync and Sushitrain exist precisely to make Syncthing usable on iPhone. They help, but they operate inside the same sandbox, so the ceiling is the same.
Here is how the practical experience compares.
| Capability | Syncthing on iOS | Relaaay on iOS |
|---|---|---|
| Reliable background sync | No — suspended by iOS | Yes — built for iOS delivery |
| Battery impact when kept current | High if forced to stay open | Low |
| Conflict files from stale state | Common | Avoided by design |
| Setup complexity | Node IDs, folder paths, ports | Link a folder, join it |
| Works across Mac, Windows, Android | Yes | Yes |
The pattern is clear: clients can soften the symptoms, but they cannot escape the platform rule that an app may not run forever in the background.
What reliable iPhone sync actually requires
The lesson is not "Syncthing is bad." It is that continuous background processing is the wrong foundation on iOS. Any tool built on that assumption will inherit the same fragility.
Relaaay takes a different approach. Rather than keeping an app awake to push files, it is designed to deliver content to your iPhone in a way iOS supports, so your linked folder stays current without you babysitting a process.
The folder updates because the system is allowed to deliver to it — not because you left an app glowing on your screen.
That means no marathon foreground sessions, no battery sacrifice, and far less of the version drift that produces conflict files. For an iPhone that needs to stay in parity with a Mac, a Windows PC, or an Android device, that distinction is the difference between sync you can trust and sync you have to check.