Nextcloud vs Syncthing (2026): Full Comparison for Self-Hosting

Quick Verdict

Nextcloud and Syncthing solve different problems. Nextcloud is a full cloud platform — file sync, sharing, calendars, contacts, office suite, and 400+ apps. It replaces Google Drive/Workspace. Syncthing is a pure file sync tool — no server, no web UI for browsing, no sharing links. It replaces Dropbox’s sync engine. Choose Nextcloud if you want a cloud platform. Choose Syncthing if you just want files in sync across devices.

Updated March 2026: Docker images, version numbers, and feature comparisons verified current.

Overview

Nextcloud is a self-hosted productivity platform with file sync at its core. It runs as a PHP web application backed by a database (PostgreSQL or MariaDB) and serves files through a web browser, desktop sync clients, and mobile apps. It supports link sharing, collaborative editing, video calls, and hundreds of third-party apps. Think of it as Google Workspace that you run yourself.

Syncthing is a decentralized, peer-to-peer file synchronization tool. There is no central server — devices sync directly with each other using a custom protocol (BEP) over TLS. It runs as a lightweight daemon with a local web UI for configuration. It does one thing — keep folders in sync across devices — and does it exceptionally well.

Feature Comparison

Feature	Nextcloud	Syncthing
Architecture	Client-server (central hub)	Peer-to-peer (decentralized)
Web file browser	Yes (full web UI)	No (config-only web UI)
File sharing links	Yes (password-protected, expiring)	No
Desktop sync client	Yes (Windows, macOS, Linux)	Yes (Windows, macOS, Linux)
Mobile app	Yes (iOS, Android)	Yes (Android; no official iOS)
Office suite	Yes (Nextcloud Office / Collabora)	No
Calendar & contacts	Yes (CalDAV/CardDAV)	No
Email integration	Yes (via Mail app)	No
Video calls	Yes (Nextcloud Talk)	No
Third-party apps	400+ apps in app store	No (sync only)
File versioning	Yes	Yes
Conflict resolution	Server wins (renames conflicts)	Renames conflicts (both kept)
End-to-end encryption	Yes (per-folder, client-side)	Yes (TLS in transit, untrusted relays)
Selective sync	Yes	Yes (per-folder)
Sync protocol	WebDAV + proprietary chunking	BEP (Block Exchange Protocol)
Sync speed	Moderate (HTTP overhead)	Fast (direct P2P, block-level)
Server required	Yes (PHP + database + web server)	No (P2P, no central server)
RAM usage (server)	512 MB - 2 GB+	50-100 MB
CPU usage	Moderate to high	Low
Docker setup complexity	Complex (app + db + cron + Redis)	Simple (single container)
User management	Yes (multi-user, LDAP, SSO)	No (device-level only)
External storage	Yes (S3, SMB, FTP, WebDAV, SFTP)	No
License	AGPL-3.0	MPL-2.0

Installation Complexity

Nextcloud requires a PHP runtime, a database (PostgreSQL recommended), a web server or Apache, Redis for caching, and a cron container for background tasks. A typical Docker Compose setup has 3-4 services and 10+ environment variables. Initial setup includes configuring trusted domains, setting up SSL, and tuning PHP memory limits. See our Nextcloud Docker guide.

Syncthing is a single binary (or single Docker container). Start it, open the web UI on port 8384, add a device ID from another Syncthing instance, choose folders to share, and sync begins. No database, no web server, no cron. See our Syncthing Docker guide.

Winner: Syncthing, dramatically. But this comparison isn’t entirely fair — Syncthing does far less than Nextcloud.

Performance and Resource Usage

Resource	Nextcloud	Syncthing
RAM (idle)	256-512 MB	30-50 MB
RAM (active)	512 MB - 2 GB+	50-100 MB
CPU (sync)	Moderate (PHP processing)	Low (Go binary, efficient)
Sync speed (LAN)	~50-100 MB/s	~100-200+ MB/s
Sync speed (WAN)	Depends on server bandwidth	P2P (direct, often faster)
Disk overhead	Database + cache + app data	Minimal (~1% for index)

Syncthing is significantly faster for raw file sync, especially on a LAN. Its block-level sync means only changed portions of files are transferred. Nextcloud syncs whole files through an HTTP stack with PHP processing overhead.

Community and Support

Metric	Nextcloud	Syncthing
GitHub stars	29,000+	68,000+
License	AGPL-3.0	MPL-2.0
Commercial support	Nextcloud GmbH (enterprise plans)	None (community only)
Documentation	Extensive (official docs)	Good (official docs + community)
Active development	Very active (enterprise-driven)	Active (community-driven)
Community size	Large (forums, Reddit)	Large (forums, Reddit)

Security and Privacy

Both tools keep your data under your control, but they approach security differently.

Security Feature	Nextcloud	Syncthing
Encryption in transit	TLS 1.3 (HTTPS)	TLS 1.3 (BEP protocol)
Encryption at rest	Server-side encryption (optional)	Untrusted device encryption (per-device)
End-to-end encryption	Per-folder client-side E2EE	No E2EE (encrypted transit + untrusted mode)
Authentication	Username/password, TOTP 2FA, FIDO2/WebAuthn, LDAP, SAML/SSO	Device certificate (Ed25519 key pair)
Multi-user access control	Yes (groups, shares, quotas, ACLs)	No (device-level trust only)
Audit logging	Yes (admin audit log app)	No
Brute-force protection	Yes (built-in rate limiting)	N/A (no login)
Attack surface	Large (PHP, web server, database, API endpoints, app ecosystem)	Small (single Go binary, local web UI only)
Security audits	Regular third-party audits (published)	Community audits, well-documented protocol
CVE history	Regular patches (large codebase = more surface area)	Very few CVEs (minimal codebase)

Nextcloud’s security model is enterprise-grade but comes with complexity. You’re running a PHP web application behind a web server with a database — a stack with a large attack surface. Keeping it secure means staying on top of updates, configuring fail2ban, using a reverse proxy with rate limiting, and managing SSL certificates. The upside is comprehensive access control, audit logging, and integration with enterprise identity systems.

Syncthing’s security model is minimalist. There’s no web-facing service to attack (the web UI listens on localhost by default). Devices authenticate using Ed25519 key pairs — no passwords to brute-force. The attack surface is a single Go binary. The trade-off: no centralized access control, no audit logging, and no multi-user permissions. Syncthing trusts devices, not users.

For privacy-focused users: Syncthing is architecturally superior because no data ever resides on a server unless you choose to use an “untrusted” relay — and even then, the relay only sees encrypted data. Nextcloud stores everything on your server, which is still under your control but represents a single point to secure and a potential target.

Mobile Experience

Mobile support is a key difference between these tools, especially after Syncthing’s Android app discontinuation in late 2024.

Mobile Feature	Nextcloud	Syncthing
iOS app	Yes (official, full-featured)	No official app (Möbius Sync, paid third-party)
Android app	Yes (official)	Syncthing-Fork (community-maintained)
Auto photo upload	Yes (background upload, Wi-Fi only option)	Yes (camera folder sync via Syncthing-Fork)
Offline file access	Yes (mark files for offline use)	Yes (all synced files are local)
Selective sync on mobile	Yes (browse and download on demand)	No (entire folder syncs or nothing)
File browsing on phone	Yes (in-app file browser with preview)	No (use device file manager)
Background sync	Yes (limited by iOS/Android restrictions)	Yes (with battery optimization caveats)
Data usage control	Yes (Wi-Fi only upload/download options)	Yes (bandwidth limits, Wi-Fi only option)

Nextcloud’s mobile apps are full-featured clients with file browsing, preview, sharing, and auto-upload. The iOS app is polished and actively maintained. The Android app handles auto-upload well but is more of a browse-and-download client than a true real-time sync client — you can’t work on files locally and expect them to sync back automatically the way a desktop client does.

Syncthing on mobile requires Syncthing-Fork on Android (the original Syncthing Android app was discontinued in December 2024). Syncthing-Fork is actively maintained and available on F-Droid and GitHub. It does true two-way sync, but it’s all-or-nothing per folder — you can’t browse and download individual files. On iOS, there’s no official app. Möbius Sync is a paid third-party client ($4.99) with limited features.

If mobile access is a deciding factor, Nextcloud wins, especially for iOS users. Syncthing’s Android support is solid through the Fork, but the iOS gap is significant.

Network Setup and Firewall Requirements

How each tool handles network connectivity is a practical decision factor, especially for users behind restrictive firewalls or double NAT.

Network Aspect	Nextcloud	Syncthing
Requires exposed ports	Yes (443/HTTPS for remote access)	Optional (port 22000, but works through relays)
Works behind double NAT	Only with VPN/tunnel	Yes (via relay servers)
Reverse proxy needed	Yes (recommended for HTTPS)	No
SSL certificate needed	Yes (Let’s Encrypt or similar)	No (TLS built into protocol)
Discovery mechanism	DNS (your domain name)	Global discovery servers + local broadcast
NAT traversal	Manual (port forward or Cloudflare Tunnel)	Automatic (UPnP, relays, STUN-like)
Corporate firewall compatible	Needs port 443 open outbound	Yes (relays use port 443)
Works without internet	Yes (if server is on LAN)	Yes (local discovery, LAN sync)

Nextcloud requires you to expose a web service to the internet for remote access. This means a domain name, SSL certificates, a reverse proxy (Nginx Proxy Manager, Caddy, or Traefik), and either port forwarding or a tunnel like Cloudflare Tunnel. For LAN-only use, none of this is needed — but that defeats much of Nextcloud’s purpose.

Syncthing handles connectivity automatically. It uses global discovery servers to find your devices, attempts direct connections via UPnP, and falls back to relay servers when direct connections fail. You never need to open firewall ports, configure a reverse proxy, or manage SSL certificates. Syncthing even works behind double NAT and corporate firewalls. The trade-off: relay-based sync is slower than direct connections, and you’re trusting Syncthing’s public relay infrastructure (though all data is encrypted in transit).

For users who don’t want to deal with DNS, SSL, and reverse proxies, Syncthing is dramatically simpler.

Cost Comparison

Both tools are free and open source. The real cost difference is infrastructure.

Cost Factor	Nextcloud	Syncthing
Software license	Free (AGPL-3.0)	Free (MPL-2.0)
Minimum server	1-2 GB RAM VPS ($5-10/month) or home server	No server needed (runs on existing devices)
VPS hosting (if used)	$5-12/month (1-2 GB RAM minimum)	$3-5/month (512 MB RAM sufficient for always-on peer)
Domain name	~$10-15/year (recommended)	Not needed
SSL certificate	Free (Let’s Encrypt)	Not needed
Home server electricity	$3-8/month (depending on hardware)	Same, if running 24/7 peer
Cloud alternative replaced	Google Workspace ($7/month), Dropbox ($12/month)	Dropbox sync ($12/month), Resilio Sync ($60/year)
3-year self-hosted cost	$180-430 (VPS) or $100-290 (home server + electricity)	$0-180 (no server vs always-on VPS peer)
3-year cloud cost	$250-430	$430-720

Syncthing can run at zero ongoing cost if you only sync between devices that are online simultaneously (laptop + desktop during work hours). An always-on peer (home server or cheap VPS) adds $3-8/month but gives Dropbox-like availability.

Nextcloud’s total cost is higher because it needs a more capable server (PHP, database, Redis), but it replaces more cloud services — not just file sync but also calendar ($0-3/month), contacts, document editing ($7-20/month for Google Workspace/Office 365), and more. The per-service value is strong.

What’s New in 2026

Nextcloud 30 (Hub 9)

Nextcloud 30 (released late 2025) brought significant improvements:

Nextcloud Assistant — AI-powered features including text generation, image generation, and smart search across files. Runs locally with models like Whisper and LLaMA via the Local AI app, keeping data private.
Federated file sharing improvements — Better interoperability between Nextcloud instances, making it easier to share across organizations.
Performance improvements — PHP 8.3 support with measurable speed gains. The desktop client sync engine was overhauled for faster initial sync of large libraries.
Nextcloud Office — Deeper Collabora integration with improved mobile editing and real-time collaboration stability.

Syncthing 2.0

Syncthing 2.0 (released 2025) was a major milestone:

Database migration from LevelDB to SQLite — Improved reliability, crash recovery, and reduced corruption risk. The database is now queryable and easier to debug.
Untrusted (encrypted) devices — Sync to an “untrusted” device where files are stored encrypted. The untrusted device never sees plaintext data. This enables using cheap VPS storage as a sync relay without trusting the server.
Connection prioritization — Better handling of multiple connection types (LAN vs relay vs WAN), preferring direct connections when available.
Android app discontinued — The original Syncthing Android app was discontinued in December 2024. Syncthing-Fork (community-maintained, available on F-Droid) is the recommended replacement with battery optimization improvements and Android 14+ compatibility.
No architectural changes — Syncthing’s core strength remains: it does one thing and does it reliably. No feature bloat.

Use Cases

Choose Nextcloud If…

You want a complete cloud platform, not just file sync
You need file sharing via links (with passwords, expiry)
You need a web-based file browser accessible from any device
You want collaborative document editing (Nextcloud Office)
You need calendar and contact sync (CalDAV/CardDAV)
You need multi-user support with permissions and quotas
You want to replace Google Workspace or Microsoft 365
You want a single platform for multiple productivity tools

Choose Syncthing If…

You only need to keep folders in sync between your own devices
You don’t want to run or maintain a central server
You need fast, efficient sync (especially large files or many changes)
Privacy is paramount — no data touches any server you don’t control
You want something lightweight that runs on everything, including Raspberry Pi
You don’t need file sharing links or a web file browser
You want it to “just work” with minimal maintenance

Use Both Together

Many self-hosters run both tools simultaneously for different purposes. This is a legitimate and common setup:

Nextcloud handles shared family files, external link sharing, calendar/contact sync, and web-accessible storage. Anything you need to share with others or access from a browser goes through Nextcloud.
Syncthing handles fast device-to-device sync of working files — code projects, Obsidian vaults, KeePass databases, video editing files. Anything where speed and reliability matter more than sharing features goes through Syncthing.

Critical rule: Never point both tools at the same directory. Nextcloud tracks files in its database. If Syncthing modifies files outside Nextcloud’s API, the database goes out of sync and you’ll get conflicts, missing files, or corruption. Keep them on separate directories.

A typical setup:

~/Nextcloud/ — synced by Nextcloud client (shared photos, documents, family files)
~/Sync/ — synced by Syncthing (working files, code, personal databases)

Scalability

Scalability Factor	Nextcloud	Syncthing
Maximum users	Thousands (enterprise deployments)	N/A (device-level, no user accounts)
Maximum devices	Unlimited (per user)	Practical limit ~20-50 devices
Storage backends	Local, S3, SMB, FTP, WebDAV, SFTP	Local filesystem only
Clustering	Yes (load balancer + multiple app servers)	No (mesh topology)
Multi-tenancy	Yes (separate user accounts, quotas)	No
Federation	Yes (share between Nextcloud instances)	Yes (any device can join the mesh)

Nextcloud scales to enterprise deployments with load balancing, external storage backends (S3, SMB), and database clustering. It’s used by the German federal government and organizations with thousands of users.

Syncthing scales comfortably to dozens of devices. Beyond 20-50 devices, the mesh topology means each new device adds connections to every other device in a shared folder, which increases bandwidth and CPU usage. For personal use or small teams, this isn’t a concern. For large organizations, Nextcloud is the appropriate tool.

Ongoing Maintenance

Maintenance Task	Nextcloud	Syncthing
Software updates	Manual (major upgrades can break things)	Automatic (built-in auto-update)
Database maintenance	Yes (PostgreSQL/MariaDB backups, vacuuming)	No external database
PHP updates	Yes (version compatibility matters)	N/A
SSL certificate renewal	Yes (Let’s Encrypt auto-renewal)	N/A
Backup complexity	Database + files + config (3 components)	Config folder only (files are on all devices)
Cron jobs	Yes (background tasks must run)	No
Typical monthly effort	1-2 hours (updates, monitoring, occasional troubleshooting)	~0 hours (set and forget)

Nextcloud requires ongoing attention. Major version upgrades (e.g., 32→33) sometimes break apps or require PHP version changes. You need to back up both the database and the data directory. Cron jobs must run reliably for background tasks. If you enjoy tinkering with your server, Nextcloud provides plenty of opportunities. If you don’t, budget for occasional troubleshooting.

Syncthing is effectively maintenance-free after initial setup. It auto-updates by default, has no external database to manage, and its config is a few XML files. Backups are almost unnecessary — your files exist on multiple devices by design. The most common maintenance task is removing old conflict files.

Docker Compose Setup Comparison

Here’s the difference in deployment complexity at a glance.

Syncthing — one service, no dependencies:

services:
  syncthing:
    image: syncthing/syncthing:2.0.15
    container_name: syncthing
    restart: unless-stopped
    ports:
      - "8384:8384"   # Web UI
      - "22000:22000" # Sync protocol
    volumes:
      - ./syncthing-config:/var/syncthing/config
      - /path/to/data:/var/syncthing/data
    environment:
      - PUID=1000
      - PGID=1000

Nextcloud — app + database + Redis + cron (4 services):

services:
  nextcloud:
    image: nextcloud:33.0.0
    container_name: nextcloud
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - nextcloud-data:/var/www/html
    environment:
      - POSTGRES_HOST=nextcloud-db
      - POSTGRES_DB=nextcloud
      - POSTGRES_USER=nextcloud
      - POSTGRES_PASSWORD=changeme
      - REDIS_HOST=nextcloud-redis
    depends_on:
      - nextcloud-db
      - nextcloud-redis

  nextcloud-db:
    image: postgres:16-alpine
    restart: unless-stopped
    volumes:
      - nextcloud-pgdata:/var/lib/postgresql/data
    environment:
      - POSTGRES_DB=nextcloud
      - POSTGRES_USER=nextcloud
      - POSTGRES_PASSWORD=changeme

  nextcloud-redis:
    image: redis:7-alpine
    restart: unless-stopped

  nextcloud-cron:
    image: nextcloud:33.0.0
    restart: unless-stopped
    volumes:
      - nextcloud-data:/var/www/html
    entrypoint: /cron.sh
    depends_on:
      - nextcloud

volumes:
  nextcloud-data:
  nextcloud-pgdata:

The complexity gap is significant. Syncthing is up in 30 seconds with zero configuration. Nextcloud requires database setup, trusted domain configuration, SSL, and ongoing PHP tuning. Both are well worth running — they just serve different needs.

Migration Between Nextcloud and Syncthing

Moving from Dropbox/Google Drive to Nextcloud

Install the Nextcloud desktop client on each device
Export your files from Dropbox/Google Drive (Settings → Download all files)
Place files in the Nextcloud sync folder
Desktop client syncs everything to the server
Set up CalDAV/CardDAV if you also want calendar/contact sync

Moving from Dropbox/Google Drive to Syncthing

Install Syncthing on each device
Share device IDs between your machines (displayed in Syncthing’s web UI)
Export files from the cloud service
Place them in a Syncthing-shared folder on any device
Syncthing propagates the files to all connected devices within minutes

Switching from Nextcloud to Syncthing (or vice versa)

Stop the sync client you’re leaving before starting the new one. Both can point to the same folder, but running them simultaneously on the same data causes conflicts. Syncthing doesn’t require migrating a database — just point it at your files. Moving TO Nextcloud requires an initial full upload to the server.

Final Verdict

These are complementary tools, not competitors. Nextcloud is a cloud platform that happens to sync files. Syncthing is a file sync tool that does nothing else.

If you’re choosing one: Nextcloud if you need a cloud platform with sharing, collaboration, and multi-user support. Syncthing if you just want your files on all your devices, fast and privately.

Many self-hosters run both — Nextcloud for shared family files and external sharing, Syncthing for fast device-to-device sync of working files. In 2026, both are mature and actively maintained. The question isn’t which is “better” — it’s whether you need a cloud platform (Nextcloud) or a sync tool (Syncthing). Answer that, and the choice makes itself.

FAQ

Can Syncthing replace Nextcloud?

Only if you don’t need web-based file access, sharing links, calendars, contacts, or any of Nextcloud’s platform features. Syncthing replaces the sync engine only.

Can I sync Nextcloud’s data folder with Syncthing?

Don’t. Nextcloud tracks files in its database. If Syncthing modifies files outside Nextcloud’s API, the database goes out of sync and you’ll get conflicts, missing files, or corruption. Use Nextcloud’s sync client for Nextcloud data.

Which is better for large files?

Syncthing. Its block-level delta sync transfers only changed blocks, making it much faster for large files that change incrementally (databases, disk images, video projects).

Does Syncthing work without internet?

Yes. On a LAN, Syncthing discovers peers via local broadcast and syncs directly without any internet connection. Nextcloud also works on a LAN if the server is locally accessible.

Is Syncthing more private than Nextcloud?

Both are private in the sense that you control the data. Syncthing is architecturally more private because it has no central server — files go directly between your devices. Nextcloud stores files on your server, which is still under your control but represents a single point to secure. Syncthing’s untrusted device feature adds another layer — you can sync through an encrypted relay without the relay ever seeing your files.

Can I access Syncthing files from a phone?

On Android, yes — Syncthing-Fork syncs folders to your phone’s storage, accessible through any file manager. On iOS, there’s no official or maintained Syncthing app. Nextcloud has polished apps on both iOS and Android with photo auto-upload, offline files, and in-app document preview. If mobile access matters, Nextcloud is the stronger choice.

Which handles sync conflicts better?

Syncthing keeps both versions when a conflict occurs, appending .sync-conflict-[date] to the older version. You manually resolve by keeping the version you want. Nextcloud uses a server-wins approach — the last upload wins, and conflicting files are renamed. Neither approach is perfect, but Syncthing’s method ensures you never lose data silently.

Can I use Nextcloud with Syncthing for backup?

Not for syncing the same data, but they pair well for different purposes. Use Nextcloud as your web-accessible cloud with sharing links. Use Syncthing to keep a fast local copy of working files between your laptop and desktop. Keep Nextcloud and Syncthing pointed at different directories to avoid conflicts.

Is Syncthing safe and secure?

Yes. Syncthing encrypts all traffic with TLS 1.3 and authenticates peers using device certificates. No data passes through any third-party server — relay servers (used for NAT traversal) only see encrypted traffic. The “untrusted device” feature lets you sync to a VPS where files are stored encrypted at rest, meaning even the relay never sees plaintext. Syncthing has been audited by security researchers and its protocol is well-documented.

Can Nextcloud auto-upload photos like Google Photos?

Yes. The Nextcloud mobile app (iOS and Android) supports automatic photo and video upload in the background. You can configure it to upload over Wi-Fi only, choose the destination folder, and exclude certain file types. Combined with the Memories app (a Google Photos-like gallery for Nextcloud), it’s a functional Google Photos replacement for sync and browsing — though it lacks Google’s AI-powered search and editing features.

Which is faster for syncing large files?

Syncthing is significantly faster. Its Block Exchange Protocol (BEP) transfers only changed blocks within files, making it 2-4x faster than Nextcloud for large files that change incrementally (video projects, databases, disk images). On a gigabit LAN, Syncthing can sustain 100-200+ MB/s, while Nextcloud’s WebDAV-based sync typically maxes out at 50-100 MB/s due to HTTP overhead and PHP processing.

Do I need a server for Syncthing?

No. Syncthing is peer-to-peer — devices sync directly with each other. However, at least two devices must be online simultaneously for sync to happen. If you want always-available sync (like Dropbox), you can run Syncthing on a VPS or home server that’s always on. This “always-on peer” approach gives you the availability of a server without the complexity of Nextcloud.

Should I use Nextcloud or Syncthing?

It depends on what you need. Use Nextcloud if you want a full cloud platform — web file browser, link sharing, calendars, contacts, office suite, and multi-user support. Use Syncthing if you only need to keep folders synced between your own devices without running a server. Many self-hosters run both: Nextcloud for shared/external access and Syncthing for fast device-to-device sync of working files.

Can Syncthing replace Nextcloud completely?

Only if you don’t need a web file browser, link sharing, calendar/contact sync, collaborative document editing, or multi-user access. Syncthing replaces the file sync engine — not the cloud platform. If you just sync files between your laptop, desktop, and phone, Syncthing handles that better and faster than Nextcloud. But if you need to share a file with someone via a link, access files from a web browser, or sync calendars, you still need Nextcloud (or a similar platform).

Which uses less resources: Nextcloud or Syncthing?

Syncthing uses significantly fewer resources. It idles at 30-50 MB RAM as a single Go binary with no external dependencies. Nextcloud requires PHP, a PostgreSQL or MariaDB database, Redis for caching, and a cron worker — totaling 256 MB-2 GB+ RAM depending on usage. For file sync on a Raspberry Pi or low-resource VPS, Syncthing is the clear choice. Nextcloud needs at least 1-2 GB of RAM to run comfortably.

Is Syncthing or Nextcloud faster for file sync?

Syncthing is 2-4x faster. Its Block Exchange Protocol (BEP) transfers only changed blocks within files and uses direct peer-to-peer connections, sustaining 100-200+ MB/s on a gigabit LAN. Nextcloud syncs through an HTTP/WebDAV stack with PHP processing overhead, typically maxing out at 50-100 MB/s. For large files that change incrementally (video projects, databases, disk images), the difference is substantial.

Does Syncthing still have an Android app?

The original Syncthing Android app was discontinued in December 2024 by its maintainer. The recommended replacement is Syncthing-Fork, a community-maintained fork available on F-Droid and GitHub. Syncthing-Fork is actively developed and includes battery optimization improvements, Android 14+ support, and the same core sync functionality. It’s a drop-in replacement — install it, import your device ID, and continue syncing.

Can I use Syncthing to sync Obsidian vaults?

Yes, and it’s one of Syncthing’s most popular use cases. Many users sync Obsidian vaults between desktop and Android using Syncthing-Fork. Since Obsidian stores notes as plain Markdown files, Syncthing’s file-level sync handles it well. The block-level delta sync is efficient for note files that change frequently. The main limitation is iOS — without a maintained Syncthing iOS app, you’d need Nextcloud or iCloud for iOS Obsidian sync.

Which is better for a Raspberry Pi?

Syncthing. It runs comfortably on a Raspberry Pi 3 or 4 with 30-50 MB RAM and minimal CPU usage. Nextcloud can run on a Pi 4 (4 GB model) but will feel sluggish — PHP processing is slow on ARM, and the database adds overhead. If you’re running a Pi as an always-on sync server, Syncthing is the better fit. If you insist on Nextcloud on a Pi, expect to spend time optimizing PHP and database performance.

How does file versioning work in Syncthing vs Nextcloud?

Syncthing offers four versioning modes: Simple (keeps the last N versions), Staggered (keeps versions at increasing intervals — hourly for 24h, daily for 30d, weekly for a year), Trash Can (moves deleted files to a .stversions folder), and External (runs a custom script on version events). You choose per folder.

Nextcloud handles versioning automatically on the server — every file change creates a version that’s retained based on a time-based policy (frequent versions for recent changes, fewer for older ones). Versions are accessible through the web UI under “Version history” for each file. The trade-off: Nextcloud’s versioning consumes server storage, while Syncthing’s versioning consumes local storage on each device.

Can Nextcloud and Syncthing work with Tailscale?

Yes. Both work well with Tailscale or other VPN solutions, but they benefit differently. Nextcloud behind Tailscale eliminates the need for a reverse proxy, SSL certificates, and exposed ports — you access it via a Tailscale IP or MagicDNS hostname over an encrypted tunnel. Syncthing with Tailscale gets direct device-to-device connections without relying on public relay servers, improving sync speed for remote devices. Tailscale is a natural complement to both tools.

Is Nextcloud overkill if I just want file sync?

Yes. If all you need is files synced between your devices, Nextcloud’s PHP web application, database, Redis cache, and cron container are unnecessary overhead. Syncthing gives you faster, more reliable file sync with a fraction of the resource usage and zero maintenance. Nextcloud is worth the complexity only if you’ll use its platform features — sharing links, calendar, contacts, collaborative editing, or the app ecosystem.

Which is better for syncing KeePass databases?

Syncthing. KeePass databases (.kdbx files) are small, change frequently, and are used across multiple devices — exactly what Syncthing excels at. Its block-level sync is fast, its conflict handling preserves both versions (so you never lose passwords), and it works peer-to-peer without exposing a server to the internet. Nextcloud works too, but its WebDAV-based sync adds latency and the server-wins conflict resolution could theoretically overwrite recent password entries if two devices edit simultaneously.