rclone is a free, open-source command-line tool for moving and syncing files across cloud storage. Think of it as rsync for the cloud: one command vocabulary — copy, move, sync, list, delete — that works the same way against more than seventy storage providers. You point it at a "remote" (rclone's word for a configured storage location), type a command, and rclone handles the transfer. Engineers reach for it inside scripts, cron jobs, and CI pipelines because it turns "move these files from here to there" into a single, repeatable line.

Files.com is one of the providers rclone supports natively. That makes the two a common pairing whenever a team needs to move files between Files.com and the rest of their cloud landscape from the command line.

The pairing is friendly by design. rclone is a sponsored partner of Files.com, and the support is first-class: the Files.com remote in rclone exposes the full API, respects your Files.com permissions, and produces the same audit log entries every other transfer method does. The rest of this post explains what rclone is, how to connect it to Files.com, and the workflows it fits best.

What Is rclone?

rclone is a command-line program that manages files on cloud storage. The easiest way to picture it is as a cloud-native version of the Unix commands you already know — rsync for syncing, cp for copying, mv for moving, ls for listing, and rm for deleting. The syntax feels familiar, and because rclone reads and writes from standard shell pipelines, it slots into scripts and automation the same way any other command-line tool does.

A few things make rclone the tool engineers keep reaching for:

• rsync for the cloud. It syncs files between two locations and only transfers what changed, the way rsync does on a local disk.
• Built for scripts. It runs cleanly inside shell scripts, cron jobs, and pipelines, so recurring transfers happen on their own.
• A dry-run safety net. The --dry-run flag shows you exactly what a command would do before it touches a single file, so you can check a destructive sync before running it for real.
• Wide reach. It speaks to more than seventy cloud storage providers through one consistent interface.

That combination — familiar syntax, scriptability, and a long list of supported providers — is why rclone is a staple in IT and systems-administration toolkits for file syncing, transfers, and backups.

What You Can Do with rclone and Files.com

Once Files.com is configured as an rclone remote, you can run the full set of rclone operations against it: list directories, upload new files, download files to a local or cloud destination, keep folders in sync, copy or move files, generate secure share links, and delete files to clean up storage.

Because rclone treats every provider the same way, those operations work in any direction you need:

• On-premises to the cloud. Push files from a local server up to Files.com or another cloud platform.
• Cloud to cloud. Sync or transfer files between Files.com and another cloud provider.
• Cloud to on-premises. Pull files down from Files.com to a local system.
• On-premises to on-premises. Move files between two local systems.

How Files.com Handles the Transfer in the Cloud

Here is the part that matters most for large jobs. When you copy or sync between Files.com and another cloud provider, rclone doesn't have to download every file to your machine and then upload it again. It can hand the work to Files.com, which moves the data directly between the two clouds on the server side.

In practice that means the bytes never round-trip through your laptop or your build server. For a one-time move of a few files it makes little difference. For syncing large datasets, archiving, or a cloud migration, it is the difference between saturating your own bandwidth for hours and letting Files.com do the heavy lifting in the background. The job finishes faster and your local machine stays free.

How to Get Started

The Files.com support in rclone is available in rclone version 1.68.0 and higher. Connecting the two takes three steps:

1. Install the latest version of rclone.
2. Configure your Files.com account as an rclone remote using rclone's interactive rclone config setup.
3. Start running rclone commands against it, like rclone sync and rclone copy.

From there you can drop those commands into scripts or cron jobs to automate the transfers you run on a schedule. The Files.com rclone documentation walks through the configuration in detail.

Running rclone on a Modern File Platform

rclone is the right tool for command-line file movement, and the native Files.com support means it stays first-class no matter how your storage grows. What rclone doesn't try to be is the platform underneath it — the place your files live, your partners connect, and your transfers get governed. That's where Files.com fits.

Files.com is the cloud-native File Orchestration Platform: one platform that replaces the stack of legacy tools IT teams run to move files — SFTP and FTP servers, MFT suites, file-sharing apps, and the custom scripts holding them together. It speaks every protocol, connects to more than fifty cloud and on-prem systems, automates transfers, and keeps a complete audit trail across eight global data-residency zones. rclone becomes one of the many ways you reach that platform: when an engineer wants the command line, rclone is right there; when a partner wants SFTP or a teammate wants a web folder to sync, the same files and the same permissions are waiting for them. Every action, whoever takes it and however they connect, lands in the same audit log.

That's the value of the pairing: rclone gives your scripts a clean, consistent way to move files, and Files.com gives those files a governed home that the rest of your organization can reach over every protocol they already use.

To wire up rclone, follow the Files.com rclone setup guide. To see the platform it connects to, explore Files.com's protocol support or start a free trial — no credit card, live in minutes.