DocsCopy & Move
Copy files to another location, or move them there and empty the source.
Copy and Move take files from one or more sources and put them in a destination.
Copy leaves the originals in place. Use Copy when both places should have the files: a backup of your photos on a remote, or a download from a remote to a local folder.
Move deletes each original once its copy has arrived, so the source ends up empty. Use Move when the files should end up in the destination only, for example when you archive a finished project to cloud storage and want the space back.
Setup
Choose the paths
Open the toolbar and type copy or move. Type the source, or tap the field and pick it; Copy and Move accept several sources for one destination. Copying a folder transfers its content, not the folder itself: to keep the folder name, make the destination end in it, Backups/Wedding rather than Backups.
Set the options
ignore_existing is worth knowing: it skips every file already in the destination, so a repeated copy only sends what is new. Without it, rclone compares by size and modification time and also updates changed files.
Filters choose which files take part, by name pattern, age or size. Config sets the pace: transfers (how many files at once), checkers, and bwlimit to cap the speed.
Hover any option to see its explanation. The complete list is on rclone copy and rclone move.
Start and watch
Press "START COPY" or "START MOVE", or run a dry run first with the eye icon: the job shows as "DRY RUN" in Transfers and changes nothing.
"VIEW TRANSFERS" opens the job: "Checking" first, then each file with its progress. After a copy the originals are untouched; after a move the source folder is empty. A file that failed to transfer is never deleted from the source.
Scheduling copy or move
A copy or move that you run regularly belongs in a schedule. Open the Cron section, type a cron expression or build it with the dropdowns, and the start button changes to "START AND SCHEDULE COPY": the operation runs once now and then on the schedule. The clock icon in the bottom bar schedules without running anything now.
A nightly copy with ignore_existing is the classic setup: each run only sends the files that appeared since the last one. The runs, their logs and their history live on the Schedules page.
How is this guide?