*You can enjoy 1-way sync if your setup meets the following preconditions:
Insync version must be 3.4.0 and higher
License must be within our current pricing plans
1-way sync involves two main parts: the source (where the file originated) and the target (where you want it synced to). Here’s your guide on getting started:
Sync Cloud to Local: Top-Level folders
You can 1-way sync top-level folders from the cloud to your Base Folder (sync location on your computer).
Hover over the top-level folder
1-way syncbutton. It will ask you where you'd like to sync it: base folder, merge with a folder/drive, or inside folder/drive. This guide explains what each option means.
Sync Cloud to Local: Select multiple folders
You can also 1-way sync multiple top-level folders via the Cloud Selective Sync dropdown.
Click on the
Cloud Selective Sync (CSS)button
Check the folders you want to sync
Folders that are cloud-to-local 1-way synced will show a gray folder with a down arrow like below:
Sync Local to Cloud
Folders on your machine can also be 1-way synced to the cloud via Local Selective Sync.
Click on the
Local Selective Sync (LSS)button
Select the folder you want to sync and where you want to sync it to
Folders that are 1-way synced local-to-cloud will show a blue folder with an upward arrow like below:
1-way sync limitations
Only top-level folders can be 1-way synced. This does not include top-level files.
If a top-level folder has been 1-way synced, it cannot be changed to a 2-way sync directly. Users will need to unsync it first, then re-sync as 2-way. This also applies to the opposite case (2-way to 1-way).
A top-level folder synced 1-way cannot have subfolders synced as 2-way (and vice versa).
1-way sync behavior
Let's recall that:
target folder = where files get 1-way synced to (i.e., the destination)
source folder = where files come from or originate
Your target folder will always mimic the source folder, but not the other way around. Whatever you do in the source will be reflected in the target. Whatever you do in the target will be ignored by the source.
Edit. Editing a file/folder in the source will be synced to the target. If you change a file in the target folder, it won't change anything on the source.
Move. Moving a file from a source folder to another source folder will be synced accordingly. Moving a file from target A to target B will not be synced on the source.
Delete. Deleting a file from the source deletes it in the target. Deleting any file in your target will be ignored and redownloaded from source to target immediately.
Let's say that the cloud is your source and the local computer is your target. In this case, you only want the cloud to sync the changes down to your computer but not the other way around.
If you edit a file in the cloud, it gets synced to your local folder. But if you edit a file in your local folders, it doesn't sync up to the cloud.
If you move a file in the cloud, it is also moved locally. But not the other way around.
If you delete a file in the cloud, it is also deleted locally. But not the other way around. If you delete a file locally, it gets ignored, and the file is redownloaded immediately.
Unsyncing your 1-way synced folders
This action follows the behavior of 2-way sync.
1-way CSS (gray folders): Your files will be deleted locally but kept in the cloud
1-way LSS (blue folders): Your files will stay both locally and in the cloud.
You want to sync 2-way instead? Check out this guide to get started.
If you have any other questions or use cases we missed, send us an email at firstname.lastname@example.org :)