Sync
Sync your files between any two storages
See how RcloneView keeps any two locations in step — cloud-to-cloud, local-to-cloud or local-to-local. Set up a sync job, preview the changes, and run it.
- Create sync jobs between any two remotes, cloud or local
- Sync one source to multiple destinations (1:N)
- Schedule recurring syncs with RcloneView Plus
The demo player couldn’t load. Use “Open in new tab” instead.
Watch next
See all demos →Step-by-step guide
How to sync files between two storages
The same 30 steps as the interactive demo, with screenshots — skim it, or jump into the demo at any step.
-
1Try this step ↗
Open the Wizard for a guided setup.
We begin on the RcloneView home screen. Click Wizard to open the guided setup.
-
2Try this step ↗
Sync mirrors a folder: the destination ends up identical to the source.
The wizard handles several kinds of steps. Choose Sync, mirror directories. Mirroring means the destination is made identical to the source, so anything that exists only at the destination is removed. Keep that in mind, because we will see it happen.
-
3Try this step ↗
Pick the cloud that will hold the mirror. More than eighty providers are supported.
First we add a remote to sync with. RcloneView supports more than eighty storage backends, and any of them can be a source or a destination. For this demo we will use Google Drive.
-
4Try this step ↗
Provider chosen. Next you name the connection and authorize it.
With the provider selected, click Next.
-
5Try this step ↗
Give this connection a short name you will recognize later.
Give the new remote a short name you will recognize later. It is only a label for the connection, and you will see it everywhere in RcloneView.
-
6Try this step ↗
The name you type here is how this cloud appears everywhere in RcloneView.
We will call ours my google drive. Click Next to save it and start the connection test.
-
7Try this step ↗
Continue, and RcloneView hands you to the provider's own sign in page.
Click Next. RcloneView now opens the sign in page hosted by the provider, right in your browser.
-
8Try this step ↗
Sign in at Google. Your password goes to Google, never to RcloneView.
Sign in with the account that owns the storage. This page belongs to Google, so your password is never seen by RcloneView. The app receives only an access token, and that token is stored on this computer.
-
9Try this step ↗
The remote works. Click "Next"
RcloneView tests the new remote straight away. Connect, authenticate, and list root all pass, so the connection is ready to use.
-
10Try this step ↗
Choose the side to mirror from. Sync never modifies the source.
Now we choose the source, the side that will be read from. Sync only ever modifies the destination, so the source is never changed. Here we pick Local Disk C.
-
11Try this step ↗
Pick the exact folder to mirror. Everything under it travels with it.
Browse to the folder you want mirrored. We will use the My Pictures folder, and everything inside it, including the Adtech subfolder, is part of the job.
-
12Try this step ↗
Source set. Next you choose where the mirror will live.
With the source folder set, click Next.
-
13Try this step ↗
The destination is the only side sync will modify.
Now the destination. This is the only side that sync will change, so choose it carefully. We will use the Google Drive remote we created a moment ago.
-
14Try this step ↗
Use a folder made just for this job. Sync only touches what is inside it.
We choose a folder called My Pictures Sync. Sync only changes what is inside that folder. Everything else in your Drive stays safe.
-
-
16Try this step ↗
The default options are fine and Click "Next"
Filters are optional. You can skip files over a certain size, files older than a certain age, or folders deeper than a set level. The recommended defaults are fine here, so click Next.
-
17Try this step ↗
A dry run. This is what would happen, nothing has been written yet.
Before anything moves, RcloneView shows a dry run. Every line here is a simulation. The files from the Adtech folder are listed to copy, and so far nothing at all has been written to Google Drive.
-
18Try this step ↗
One delete: sync removes whatever the source does not have. Click "Execute"
Scroll to the bottom and the difference between sync and backup is right there. Thirty three files to copy, zero to skip, and one to delete. That file exists only in the cloud folder, so mirroring takes it away. If you would rather keep what is already at the destination, use Backup instead, which is a one way copy and never deletes. This preview is your chance to check that before anything happens. Click Execute to run it for real.
-
19Try this step ↗
The sync has started, and the whole setup was saved as a job. Click "Open Job Manager"
The sync is running, and the setup you just walked through was saved automatically as a job. You never have to repeat these steps. Open Job Manager to see it.
-
20Try this step ↗
Your new sync job, ready to run again whenever you need it.
Here it is in the job list, recorded as a sync from the My Pictures folder to My Pictures Sync.
-
21Try this step ↗
The Transfer panel follows the job file by file.
The Transfer panel tracks the job as it runs, with progress, speed and time remaining. Each file is marked success the moment it lands.
-
22Try this step ↗
Open the destination remote and check the result yourself.
Once the job finishes, open the Google Drive remote and look at the result yourself rather than trusting the progress bar alone.
-
23Try this step ↗
My Pictures Sync now exists in the cloud, created by the job.
The My Pictures Sync folder is now in Drive, created by the sync itself. Open it to see what arrived.
-
24Try this step ↗
Same thirty three files, same total size, on both sides.
Source on the left, destination on the right. Thirty three files and forty point four megabytes on each side, and the file that lived only in the cloud is gone. That is what mirroring means.
-
25Try this step ↗
Reopen Job Manager to reuse the job instead of rebuilding it.
Now for the part that saves time later. Open Job Manager again.
-
26Try this step ↗
The same job, now with a last execution time recorded.
The sync job is still here, and it now shows when it last ran. Select it to work with it.
-
27Try this step ↗
Run repeats the whole mirror in one click. Dry run previews it first.
This is the payoff. One click on Run repeats the entire mirror. Only new and changed files move, and anything you removed from the source is removed from the cloud as well. Dry run shows you that in advance, and Edit Job lets you change the paths.
-
28Try this step ↗
Compare checks any two folders against each other, file by file.
Finally, let us prove the mirror is exact. Compare checks any two folders against each other, file by file, whichever remotes they sit on. Click Compare.
-
29Try this step ↗
Zero left only, zero right only, zero different, thirty three identical.
Here is the proof. The two folders match exactly, which is precisely what sync set out to do.
-
30Try this step ↗
Every row lines up, same size and same timestamp on both sides.
The detailed view shows the same thing row by row. Every file appears on both sides with the same size and the same modification time, and the totals agree. Zero folders, thirty three files, forty point four megabytes on each side.
-
Ready to try it yourself?Free for Windows, macOS and Linux.Get RcloneView Free