Home » Syncthing vs rclone: continuous peer sync or controlled cloud transfers?

Syncthing vs rclone: continuous peer sync or controlled cloud transfers?

CLOUD BACKUP & PHOTO LIBRARIES

Syncthing and rclone often appear in the same storage discussions, but their default jobs differ. One keeps folders aligned between peers; the other gives you explicit transfer operations across supported storage services.

Editorial review: 15 November 2026 · United States

Quick answer

Use Syncthing for ongoing folder synchronisation between participating devices. Use rclone for scripted copies or syncs involving its supported local and cloud backends. Decide where deletions should go before selecting a command or folder type.

Steps to follow

  1. Before you start

    Draw the participating devices and cloud destinations, then mark where edits are allowed. Make independent copies of the sample data and include a destination-only test file. Decide whether the goal is an additive copy, a one-way mirror or continuing changes between peers before selecting a command or folder type.

  2. Set up the right scope

    Draw the source and destination, including whether both devices are normally online. Check rclone’s backend support and Syncthing’s client availability. Specify whether you want an additive copy, a destination mirror or edits travelling both ways.

  3. Apply the relevant settings

    For Syncthing, pair device IDs and share a test folder with the intended folder type. For rclone, configure a restricted remote and start with a dry-run of a small copy operation before any sync that can delete destination-only files.

  4. Complete the first run

    Test updates, renamed files and one disposable deletion. Record scheduling, authentication, transfer logs and how the workflow resumes after a connection interruption.

Decisions and checks

The limitation that matters

rclone sync makes the destination match the source and can delete files there. Syncthing can propagate deletions between peers. Neither becomes a historical backup merely because the destination is elsewhere; add independent retention and test it.

How to verify the result

Compare actual recovery of an earlier sample, not only throughput. Check the result when one peer is offline and when a remote credential expires, then choose the tool whose operational requirements you can maintain.

Keep the result reliable

Inspect the service or scheduled job after credential changes, software updates and storage moves. Keep logs that identify the affected operation without exposing secrets. Periodically restore an older sample from your independent retention system so the workflow proves recovery as well as successful transfer. Before an unattended mirror, verify that the expected source storage is mounted and populated; an unexpectedly empty source needs investigation rather than an automatic attempt to empty the destination.

Choose the transfer model before choosing the tool

Continuous peers and explicit remote operations solve different jobs

Syncthing exchanges folder changes among paired devices when they can communicate. It is useful when the working folder should remain aligned across computers without running a separate transfer command each time. Plan when the peers will be available, including any additional device that keeps a current copy for laptops that are rarely online together.

rclone provides operations against supported local and remote storage backends. A scheduled cloud copy, a controlled migration or a repository-maintenance task can fit that model. Verify the actual backend’s capabilities and authentication, because a generic cloud-service name does not guarantee identical metadata, checksum or sharing behaviour. Choose from the specific operation and destination you need to maintain.

Copy, sync and two-way changes are different instructions

rclone copy transfers source content without deleting destination-only files, although changed files at matching paths can still be replaced. rclone sync makes the destination match the source and can delete extra destination content. Start with the least destructive operation that meets the task, and inspect a dry-run with the exact source and destination before running a mirror.

Do not treat two independent one-way sync commands as a simple substitute for a designed two-way workflow. Syncthing folder types and rclone’s separate bidirectional tooling have their own rules and recovery considerations. If both sides may edit, choose and test an explicitly supported arrangement. Keep the authoritative source clear for a one-way job so a reversed path does not overwrite the version you intended to preserve.

A destination-only file makes the deletion test informative

Create harmless source and destination folders containing an overlapping file, a source-only file and a destination-only file. Preview the intended operation and write down which items should remain. Then run the trial and inspect the actual contents. This shows whether the chosen copy or mirror semantics match your expectation before any real archive is exposed.

For Syncthing, test an edit and a disposable deletion across the selected folder types, with versioning configured where required. Its versioning applies to received remote changes on the device where it is enabled, not every local edit everywhere. For rclone, test the separate retention or backup destination you have designed. A second location that immediately mirrors a mistake is not a complete history strategy.

Availability, credentials and supervision determine reliability

A continuously running peer service and a scheduled command fail in different ways. Syncthing may wait for another device to become reachable; an rclone job may fail because a credential expires, a backend rejects a request or its scheduled environment lacks a path. Test the actual unattended arrangement instead of assuming a successful interactive run proves the schedule.

Keep the required configuration and encryption material recoverable independently of the source system. Check the logs after a controlled interruption, resume through the documented process and verify the resulting files. Choose the approach whose ongoing responsibilities you can manage. Combining the tools can be reasonable for distinct stages, such as peer working copies and a separate cloud archive, but those stages need clear ownership and independent retention.

Compare the transfer requirements

Task or symptom Action Important boundary
Working folders on several trusted devices Syncthing peer availability and folder types Test edits and a disposable deletion between peers
Controlled copy to supported cloud storage rclone backend and copy operation Inspect a dry-run with a destination-only sample
One-way destination mirror rclone sync direction and deletion behaviour Verify the exact paths and independent recovery history

Frequently asked questions

Does rclone copy preserve every earlier destination version?

No. It avoids deleting destination-only files, but matching paths can be updated. Use a separate supported versioning or backup arrangement when older content must remain recoverable, and test an earlier-version restore.

Can Syncthing replace a hosted cloud destination automatically?

It synchronises among participating devices rather than automatically creating a general cloud-storage account. Plan which peers hold the data and when they are reachable. If you need a particular cloud backend, evaluate the supported tool and operation for that destination.

Can I combine them safely?

Give each tool a distinct role and prevent competing writers over the same live data. For example, peer synchronisation and an independently versioned archive are different jobs. Document the direction, schedule and recovery method for each, then test the complete arrangement.

Official documentation

This guide combines current official documentation with practical recovery checks. It does not claim hands-on testing of your installation. Menu labels and supported procedures can vary by release; follow the documentation for your installed version.

Scroll to Top