# Step 1 – preview rclone sync /source remote:dest --dry-run --verbose
If you are unsure, use rclone copy . You can always manually delete files from the destination later, but you cannot easily recover files deleted automatically by sync . This is especially true when scripting backups to run automatically (e.g., via cron). rclone sync vs copy
| | | rclone sync | |---|---|---| | Deletes destination files | Never | Yes (if missing from source) | | Safe for one‑way replication | ✅ Yes (append‑only) | ✅ Yes (exact mirror) | | Risk of data loss | Very low | Low to moderate (depending on usage) | | Typical use case | Backup, archive, migration | Mirroring, deployments, cleanup | | Dry‑run recommended? | Optional | Strongly recommended | # Step 1 – preview rclone sync /source
Rclone is a powerful command-line tool for managing files on cloud storage (S3, Google Drive, Backblaze B2, SFTP, etc.). Two of its most frequently used commands are copy and sync . While they seem similar, their behavior around and destination management differs fundamentally. | | | rclone sync | |---|---|---| |
| Feature | rclone copy | rclone sync | | :--- | :--- | :--- | | | Copied to destination. | Copied to destination. | | Changed Files | Overwritten on destination. | Overwritten on destination. | | Deleted Files (Source) | Ignored. File remains on destination. | Deleted. File removed from destination. | | Storage Space | Grows over time (accumulates). | Stays proportional to source. | | Data Safety | High. Cannot delete data. | Lower. Can delete data if misconfigured. | | Speed | Slower over time (must scan more files). | Faster scanning (prunes deleted files). |
Because copy never deletes files, the destination can become a "junk drawer" over time.