What is Rclone
Rclone is a CLI tool that copies and synchronizes files between local disks, servers, and cloud providers through a consistent command interface.
Learning Focus
Use this lesson to understand rclone's mental model (remotes, paths, and safety) so you can run production sync jobs without surprises.
Core Idea
You define a provider once as a remote, then reuse the same command shape for every provider.
Concept Overview
Rclone is not "one cloud" tooling. It is an abstraction layer:
- A backend implements a storage system (S3, B2, R2, Drive, OneDrive, local).
- A remote is your configured instance of a backend (credentials + endpoint + defaults).
- A remote path uses
remote:prefix/pathaddressing.
Rclone Is Great For
| Scenario | Why rclone works |
|---|---|
| Offsite backups | Works with object storage APIs |
| Multi-provider portability | Same command shape across providers |
| Integrity checks | rclone check, size audits, hash listings |
| Scheduled jobs | Good logging, retry behavior, non-interactive operation |
Rclone Is Not The Best For
| Scenario | Better tool |
|---|---|
| Server-to-server delta copies over SSH | rsync |
| Long-term snapshot history + dedup | restic |
| Git-tracked code deployments | git + CI |
Why Teams Use Rclone
| Need | Rclone capability | Practical effect |
|---|---|---|
| Multi-cloud backup | 70+ supported backends | One command model across S3, B2, R2, Drive, and more |
| Hybrid architecture | Local + remote copy/sync | Keep fast local restore and durable offsite copy |
| Data integrity checks | rclone check, hashes, size checks | Detect drift and corruption early |
| Safer operations | --dry-run, logs, retries | Lower risk in production automation |
Architecture at a Glance
Terminology You Must Know
| Term | Meaning | Example |
|---|---|---|
| Remote | Named configuration for a backend | remote-prod |
| Backend | Storage driver type | s3, b2, drive |
| Bucket/container | Top-level storage | my-bucket |
| Prefix | Folder-like path inside a bucket | backups/app/ |
| Object | A file stored in object storage | backups/app/db.sql.gz |
| Mirror sync | Destination becomes the source | rclone sync SRC DST |
Command Shape
rclone-command-shape.sh
rclone <command> <source> <destination> [flags]
# example
rclone sync /srv/uploads remote-prod:site/uploads --dry-run
warning
Most incidents come from mistargeted sync. Build the habit: preflight path checks + --dry-run + logs.
Command Families
| Family | Examples | Use when |
|---|---|---|
| Transfer | copy, sync, move | Sending/changing data |
| Listing | ls, lsl, lsd, tree | Auditing structure |
| Validation | check, md5sum, sha1sum | Verifying consistency |
| Maintenance | delete, purge, mkdir, rmdir | Lifecycle and cleanup |
warning
sync can remove files at destination that do not exist at source. Always test with --dry-run first.
How Rclone Compares to Rsync (Mental Model)
- Rsync usually targets filesystems.
- Rclone often targets object storage where "folders" are prefixes.
Practical Use Cases
Backup a Dataset to Cloud
rclone sync /backup/app/current remote-prod:backups/app/current --progress
rclone check /backup/app/current remote-prod:backups/app/current --one-way
Publish Build Artifacts
rclone copy ./dist remote-prod:releases/my-app/2026-02-11 --checksum
Common Mistakes
| Mistake | What happens | Safer habit |
|---|---|---|
Running sync without dry-run | Unexpected deletes | Always preview with --dry-run |
| Using remote root as destination | Data lands in wrong prefix | Always use explicit remote:prefix/path |
| No post-transfer verification | Drift stays hidden | Add rclone check for critical data |
Hands-On Practice
Try these on a non-production remote path:
rclone listremotes
rclone lsd remote-prod:
rclone mkdir remote-prod:labs/rclone
rclone rmdir remote-prod:labs/rclone
Quick Reference
Quick Reference
# list remotes
rclone listremotes
# list top-level directories in a remote
rclone lsd remote-prod:
# safe preview sync
rclone sync /srv/data remote-prod:data --dry-run