Nextcloud vs Syncthing

Nextcloud is a client-server application. One machine runs the server (Apache or nginx, PHP 8.3 or newer, MariaDB or PostgreSQL), it holds the canonical copy of every file, and clients sync against it. On top of that sits everything else: calendar and contacts via CalDAV and CardDAV, Nextcloud Talk for chat and calls, Photos, and as of Hub 26 Spring (server 34, released June 2026) two office suites, Collabora Online and Euro-Office, running side by side. There are hundreds of apps in the app store. It is a platform, and the file sync client is just one door into it.

Syncthing has no server at all. Every device runs the same small MPL-2.0 licensed Go binary, devices are paired by exchanging device IDs, and folders sync directly between them over TLS. Community-run discovery and relay servers help devices find each other across the internet (you can self-host both), but your data never touches anything you do not own. Version 2.0 in August 2025 swapped the internal index database from LevelDB to SQLite and made multiple connections between v2 devices the default, and the current 2.1.1 release added folder grouping in the GUI and HTTP proxy support.

The practical consequence: Nextcloud gives you one authoritative copy with user accounts, permissions, and quotas. Syncthing gives you N equal copies as plain files on N disks, which doubles as a crude backup and means no database ever sits between you and your data. Neither model is wrong. They are answers to different questions.

Be honest with yourself about the Nextcloud maintenance load. A proper install wants PHP-FPM tuning, Redis for file locking, a cron job, a reverse proxy with TLS, and a database you back up separately from the files. The AIO (All-in-One) Docker image bundles most of that and is the sane path for a homelab, but you are still running a five-container application. Major versions land every four months and each is supported for one year, so upgrades are a recurring chore you cannot skip for long. Budget 2GB of RAM or more for a comfortable instance once preview generation and office documents enter the picture.

Syncthing is one binary and a web GUI on port 8384. Install it from your distro repos, a Docker image, or the NAS package center, add device IDs, pick folders, done. There is no database to back up (the SQLite index rebuilds itself from disk if lost), no PHP to patch, and upgrades are automatic by default. It runs happily on a Raspberry Pi, an old laptop, or the router-adjacent mini PC you forgot about. The one real resource consideration is that RAM and initial scan time grow with the number of files, so a folder with a million tiny files deserves a machine with some headroom.

If you measure tools by how often they page you, Syncthing is about as quiet as self-hosted software gets. Nextcloud is not painful, but it is a real application server with a real upgrade treadmill, and you should only sign up for that if you will use more than the sync.

This is the messiest part of the Syncthing story, so here is the current state. The official Syncthing Android app was discontinued with its final release in December 2024. Maintainer Simon Frei was direct about the reasons: Google kept making Play Store publishing harder while nobody had time to maintain the app. That headline scared a lot of people into thinking Syncthing on Android was dead. It is not.

The long-running community fork, Syncthing-Fork, was already more capable than the official app (per-folder sync conditions, better battery controls) and became the recommended client. Its original maintainer Catfriend1 stepped away in late 2025 and the repo briefly vanished, which caused another round of panic, but the project was handed to a new maintainer and now lives at github.com/researchxxl/syncthing-android. It tracks upstream closely (version 2.1.1.0 shipped June 2, 2026, matching Syncthing 2.1.1) and F-Droid or GitHub releases via Obtainium are the dependable install paths. Treat the Play Store as a bonus, not the channel you rely on.

On iOS there is no official client and never has been. Möbius Sync, a third-party commercial app built on the real Syncthing engine, is the workable option, with the usual iOS caveat that background sync only runs in short bursts. Nextcloud, by contrast, ships first-party apps on both stores with automatic photo upload, and they just work. If phone support with zero drama is a hard requirement, that is a genuine point for Nextcloud.

Syncthing has no sharing links, full stop. You cannot send your mother-in-law a URL to download a folder or let a client upload files to you. Every participant needs Syncthing installed and paired. Nextcloud does all of this well: password-protected links, expiring links, upload-only file drops, and a browser UI that works from any machine. If files need to leave your circle of trusted devices, Nextcloud is the tool, and that is not going to change.

What Syncthing does have is a killer off-site trick: receive-encrypted folders (still officially flagged beta, widely used anyway) let a box at a friend's house or a cheap VPS hold your data without being able to read it. Combined with no exposed web login and no PHP attack surface, Syncthing is much easier to reason about from a security standpoint. Nextcloud is a large internet-facing web app, and if you publish it you own the patching cadence that comes with that.

The pattern that actually wins in a lot of homelabs is both: Syncthing shuttles working files between laptop, desktop, phone, and NAS, and Nextcloud runs alongside for calendars, contacts, and the occasional share link. You can even point a Nextcloud external storage mount at a Syncthing folder on the same box (run occ files:scan or enable the scanner cron so Nextcloud notices outside changes). We already covered the server-suite-vs-server-suite fight in our Nextcloud vs Seafile piece; this matchup is a different question entirely.