Syncthing software icon

Syncthing 2.1.3

Syncthing is a free, open-source program that continuously synchronizes folders between your own devices over encrypted peer-to-peer connections, without storing data on a central server.

Updated August 5, 2026
11.45 MB
0.0

Use the arrow keys to choose a rating, then press Enter or Space to submit it.

Not rated yet 0 user ratings

App Specs

DeveloperSyncthing Foundation
LicenseFreeware
CategoryFile sharing
Available platformsWindows, macOS, Linux
Downloads203

Overview

Syncthing is a free, open-source program that keeps folders synchronized between two or more devices continuously. Files travel directly between your own machines, with no central server holding a copy. Syncthing runs on Windows, macOS, Linux, FreeBSD, OpenBSD and other systems. You control it through a web interface that opens in a browser. The code is released under the Mozilla Public License 2.0.

Pairing devices by ID

On first start, Syncthing generates encryption keys and a unique device ID derived from the device’s certificate. The ID works like a public key, so it does not need to be kept secret. Two devices connect only when each has the other’s ID.

The web interface lists folders on the left and remote devices on the right. Adding a device means pasting its ID and choosing which folders to share with it. No IP addresses are needed. Devices find each other on the local network or through global discovery servers. UPnP can open the port on a router. A device marked as an introducer passes along the other devices that share folders with you. A larger group therefore does not require entering every ID by hand.

How changes move between devices

Syncthing watches shared folders for changes and also rescans them roughly every hour, because a filesystem watcher can miss events. The watcher collects changes for a few seconds before acting, so a short delay is normal.

Syncthing splits each file into blocks with a SHA-256 hash for every block. It transfers only changed blocks. A needed block can come from any connected device that has it, or from a local file that already holds the same data. Syncthing checks received blocks against their hashes and writes them to a temporary file before replacing the original. This means an interrupted transfer never leaves a half-written file.

When the same file is edited on two devices before they sync, Syncthing keeps the newer version. It renames the older one to a .sync-conflict copy marked with the date, time and originating device. That copy then syncs like any other file.

Folder roles

  • Send & Receive, the default, passes changes both ways.
  • Send Only ignores changes from other devices. An “Override Changes” button pushes this device’s state to the group, overwriting edited files and deleting files missing here.
  • Receive Only accepts changes but never sends local edits. “Revert Local Changes” removes local additions and restores modified files, which suits mirrors and backup targets.
  • Receive Encrypted is used on untrusted devices.

Storing data on an untrusted server

You can share a folder with a password so that a rented server or cloud machine stores only encrypted data. File contents, names, timestamps and folder structure are hidden from it; the folder ID, label and approximate file sizes remain visible. Any trusted device that knows the password can still sync the data through it. This feature carries a beta label. Renaming a file means transferring its data to the untrusted device again. Losing the password makes the encrypted copy unreadable.

Keeping old versions

Syncthing’s versioning applies when a change from another device replaces or deletes files. It does not archive local edits. Old copies go to a .stversions folder or another chosen path, using one of four methods:

  • Trash can keeps the latest replaced copy of each file, optionally for a set number of days.
  • Simple keeps a fixed number of time-stamped versions per file.
  • Staggered thins versions by age, from one per 30 seconds in the first hour down to one per week, up to a maximum age.
  • External hands each file to your own script, for example to move it to the Recycle Bin.

Excluding files with .stignore

A .stignore file in a folder’s root lists what Syncthing should skip, such as build output or system clutter. Patterns support wildcards, case-insensitive matching and negation with !, and the first matching rule wins. Syncthing does not sync the ignore file itself. That file can include another file that does sync, so several devices can share one rule list.

Connections, relays and limits

All connections use TLS with perfect forward secrecy, and each device authenticates with its own certificate. If two devices cannot reach each other directly, Syncthing uses a relay. The relay forwards the encrypted stream without reading it, though it sees device IDs, IP addresses and traffic volume. Syncthing keeps retrying a direct link and drops the relay once one works. Organizations can run their own discovery and relay servers.

Speeds can be capped globally or per device. You can pause folders and set them to stop automatically when disk space runs low. You can also set them to pull files in random, alphabetical, size or age order. The web interface can require a password and HTTPS.

Desktop wrappers and packages

The core Syncthing program has no windowed interface of its own. Community projects add one around the same engine: a macOS application bundle, a Windows installer, and SyncTrayzor, a Windows tray utility. Many Linux distributions package Syncthing, and the project maintains its own Debian and Ubuntu repository.

Key Features

  • Explicit device-ID trust
  • Continuous peer-to-peer folder synchronization
  • Send-only and receive-only modes
  • Ignore patterns and file versioning
  • Discovery and relay support without cloud file storage

Similar Apps