Runs rclone for cloud file ops across 70+ remotes: copy/sync/move, mount, bisync, encrypted backups, server-side copy, and S3-compatible config. Use when the user mentions rclone or terminal cloud transfer, mount, or remote management. Not for vendor web consoles or treating rclone.conf as shareable; never log rclone config show with redaction disabled.
Runs rclone for cloud file ops across 70+ remotes: copy/sync/move, mount, bisync, encrypted backups, server-side copy, and S3-compatible config. Use when the user mentions rclone or terminal cloud transfer, mount, or remote management. Not for vendor web consoles or treating rclone.conf as shareable; never log rclone config show with redaction disabled.
Rclone is a command-line program to manage files on cloud storage. It is a feature-rich alternative to cloud vendors' web storage interfaces. Over 70 cloud storage products support rclone including S3 object stores, business & consumer file storage services, and standard transfer protocols.
Rclone has powerful cloud equivalents to the unix commands rsync, cp, mv, mount, ls, ncdu, tree, rm, and cat. It preserves timestamps and verifies checksums at all times. Transfers can be restarted from the last good file.
On Windows (PowerShell), download the zip from rclone.org/install/ or use winget install Rclone.Rclone / . Ensure is on your .
scoop install rclone
rclone.exe
PATH
For detailed installation troubleshooting, read references/install.md.
Procedure
Step 1: Configure a Remote
# Interactive configuration (recommended)
rclone config
# Show current config (redacts secrets by default)
rclone config show
# List configured remotes
rclone listremotes
# Create a remote non-interactively
rclone config create myremote s3 provider=AWS env_auth=true region=us-east-1
# Update existing remote
rclone config update myremote region=us-west-2
HARD RULE: Never expose credentials in plain text on the command line. Use rclone config to store credentials securely, or use environment variables. The config file ~/.config/rclone/rclone.conf contains sensitive data — protect it with chmod 600.
HARD RULE:rclone config show --redacted=false outputs full secrets. NEVER share, log, or commit this output.
Step 2: Understand Basic Syntax
rclone subcommand [options] source:path dest:path
Source and destination paths use remote:path syntax. For local paths, just use /path/to/dir.
Step 3: List and Inspect
rclone ls remote:path # list all objects with size
rclone lsd remote:path # list directories
rclone lsl remote:path # list with size, modtime, path
rclone lsf remote:path # list in flexible format
rclone size remote:path # total size and object count
rclone tree remote:path # tree view
rclone about remote: # get quota information
Step 4: Copy Files
# Local to remote
rclone copy /local/path remote:path
# Remote to local
rclone copy remote:path /local/path
# Remote to remote (server-side if possible)
rclone copy remote1:path remote2:path
copy does NOT delete files at destination — it is safe for additive transfers.
HARD RULE: Do NOT mix --include, --exclude, and --filter flags. Use --filter exclusively when combining rules.
Filter pattern syntax:
* matches any sequence of non-separator characters
** matches any sequence including separators
? matches any single non-separator character
{a,b} matches pattern alternatives
{{regexp}} matches using Go regexp
For complex filter rules, read references/filtering.md.
Step 11: Mount as Local Filesystem
# Basic mount
rclone mount remote:path /mnt/remote
# Recommended mount with caching (safer writes)
rclone mount remote:path /mnt/remote \
--vfs-cache-mode full \
--vfs-cache-max-size 10G \
--vfs-read-chunk-size 128M
# Unmount
fusermount -u /mnt/remote # Linux
umount /mnt/remote # macOS
HARD RULE: Mount operations can cause data loss if the mount is interrupted during writes. Use --vfs-cache-mode full for safer writes.
For detailed mount documentation, read references/commands/rclone_mount.md.
Step 12: Serve Protocols
rclone serve http remote:path # HTTP file server
rclone serve webdav remote:path # WebDAV server
rclone serve sftp remote:path # SFTP server
rclone serve ftp remote:path # FTP server
rclone serve s3 remote:path # S3-compatible server
rclone serve dlna remote:path # DLNA media server
rclone serve restic remote:path # Restic backup backend
rclone serve docker remote:path # Docker registry
HARD RULE: Remote control API (--rc) should bind to localhost only by default. Exposing it without authentication (--rc-htpasswd) allows anyone to control your rclone instance.
For API details, read references/rc.md.
Step 13: Encrypted Backup (Crypt Remote)
# Configure encrypted remote wrapping another remote
rclone config
# Choose "crypt" type, point to an existing remote (e.g., "drive:private")# Use crypt remote — files are encrypted/decrypted transparently
rclone copy /local/files crypt:path
rclone ls crypt:path
# Check integrity of encrypted files
rclone cryptcheck crypt:path
For crypt configuration details, read references/crypt.md.
Step 14: Global Flags (Most Common)
# Verbosity
-v # info level
-vv # debug level (shows filter matches)
--log-level LEVEL # DEBUG|INFO|NOTICE|ERROR# Safety
--dry-run # preview without doing anything
-i, --interactive # ask before each operation
--ignore-existing # skip files that exist at dest
-I, --ignore-times # transfer all, ignore modtime/size# Transfer control
--transfers N # parallel transfers (default 4)
--checkers N # parallel checks (default 8)
--bwlimit RATE # bandwidth limit (e.g. 10M)
--max-transfer SIZE # stop after transferring this much
-c, --checksum # use checksum instead of modtime
--size-only # compare by size only# Performance
--multi-thread-streams N # multi-thread downloads (default 4)
-P, --progress # show real-time progress# Config
--config STRING # config file path
-C, --no-check-dest # skip dest check on copy
For the complete flags reference, read references/flags.md.
# First configure a crypt remote wrapping your storage remote
rclone config
# Then use the crypt remote for all operations
rclone sync -P /sensitive-data crypt:backup
Scheduled Backup (cron)
# Add to crontab (daily at 2am):
0 2 * * * rclone sync -P /data remote:backup >> /var/log/rclone.log 2>&1
Detailed Reference Files
For in-depth information, consult these reference files in this skill's directory. These files are converted from the official Hugo-based rclone documentation under testdata/rclone/docs/. Treat any remaining Hugo shortcode or template syntax as a conversion bug: replace it with normal Markdown, a static table, or an official URL before relying on it in an answer.
File
Content
When to read
Official link
references/usage.md
Full usage guide: syntax, config, remote paths, options
For configuring specific cloud storage providers, read the corresponding file in references/providers/ when present. Some virtual/backing providers, such as crypt, cache, chunker, union, combine, and hasher, live as top-level files in references/ because they are cross-provider backends rather than single cloud services.
And 60+ more providers — each has a page at https://rclone.org/<name>/
Command References
For detailed command documentation, read the corresponding file in references/commands/:
rclone_copy.md, rclone_sync.md, rclone_move.md — transfer commands
rclone_mount.md — FUSE mount
rclone_serve_*.md — various serve modes
rclone_config*.md — configuration management
rclone_bisync.md — bidirectional sync
And 80+ more commands — each has a page at https://rclone.org/commands/<command>/
Pitfalls
rclone sync deletes files at destination that don't exist at source. Always run with --dry-run first and review the output carefully before committing.
rclone purge ignores all filters. It deletes everything under the specified path regardless of any --include, --exclude, or --filter rules. Use rclone delete instead if you need filter support.
Mixing --include, --exclude, and --filter flags produces unexpected results. Use --filter exclusively when combining include and exclude rules.
Mount interrupted during writes causes data loss. Always use --vfs-cache-mode full for safer write operations.
rclone config show --redacted=false outputs full secrets. Never share, log, or commit this output. It exposes S3 secret keys, OAuth tokens, and service account JSON.
Remote control API exposed without authentication. Binding --rc to anything other than localhost without --rc-htpasswd allows anyone to control your rclone instance.
Private keys and tokens committed to version control. The config file ~/.config/rclone/rclone.conf contains sensitive data — protect it with chmod 600 and never commit it.
Assuming examples work without environment-specific testing. Verify commands, dependencies, credentials, and external service behavior before applying changes. Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
Hugo shortcode/template syntax in reference files. These are conversion bugs from the original documentation. Replace with normal Markdown, a static table, or an official URL before relying on the content.
Verification
Verify rclone is installed and working:
rclone version
# Expected: rclone v1.xx.x with build date and OS/arch info
Verify a remote is configured and accessible:
rclone listremotes
# Expected: lists all configured remote names, one per line
rclone lsd remote:
# Expected: lists top-level directories on the remote
Verify a sync operation before running it:
rclone sync --dry-run -v /local/path remote:path
# Expected: lists files that would be transferred and deleted# Review carefully — especially any "Deleted" entries
Verify integrity after transfer:
rclone check /local/path remote:path
# Expected: "0 differences found" or lists of differing files
Verify config file permissions:
ls -la ~/.config/rclone/rclone.conf
# Expected: -rw------- (600) — only owner can read/write
Related skills
s3-cli — Direct AWS CLI S3 operations when rclone is not available
restic — Encrypted, deduplicated backups (can use rclone as a backend via rclone serve restic)
