Sync Mode
Sync Mode
The Desktop App's Sync Mode runs a one-time sync between a local folder and a folder on Files.com. It is well suited for major one-time transfers where you need to move a large volume of files quickly in a single operation. Common uses include migrating a media library to Files.com, moving a completed project archive into long-term storage, or consolidating files from a local drive when onboarding to Files.com.
The Desktop App's parallel transfer engine delivers high-speed throughput for these bulk operations, transferring files two to five times faster than conventional FTP or SFTP tools. If you need recurring, automated transfers between any two locations without running the Desktop App, see Desktop App Sync Mode vs. Files.com Sync below.
How Sync Mode Works
Each sync run compares the source and destination and transfers only the files that differ. A Push run sends files from a local folder to Files.com. A Pull run brings files from Files.com down to a local folder.
Multiple sync runs can be active at the same time. Each run progresses independently.
Sync Mode is available from File > New Sync… in the Desktop App. Each run shows one of four statuses: Running, Completed, Failed, or Cancelled.
Progress can be viewed in the Syncs tab in the transfers pane. Sync history is session-only. Completed and failed runs remain visible until the Desktop App is closed, and the list clears on the next launch. Logs appear under File Actions when filtering the Interface field by Desktop.
Sync Options
| Option | Description |
|---|---|
| Direction | Push (Local to Remote) sends files from a local folder to Files.com. Pull (Remote to Local) brings files from Files.com down to a local folder. |
| Local path | The folder on your local system. |
| Remote path | The folder on Files.com. |
| Profile | The Files.com connection to use for this sync. |
| Delete source files | Remove files from the source after they are successfully transferred to the destination. |
| Delete source empty folders | Remove empty folders from the source after the transfer completes. |
| Move source | Specify an archive path on the source. Successfully transferred files are moved there rather than deleted. |
| Include patterns | Limit the sync to files matching these patterns. Specify one pattern per line. For example, *.pdf includes only PDF files, and reports/** includes everything inside a reports folder. |
| Ignore patterns | Exclude files matching these patterns from the sync. Specify one pattern per line. For example, *.tmp skips temporary files, *.log skips log files, and archive/** skips everything inside an archive folder. |
| Dry run | Compare source and destination and report what would transfer, without making any changes to the destination. |
Stop and Resume
A running sync can be stopped at any time. Stopping cancels the active transfer and preserves the sync configuration. Resuming starts a fresh sync run with the same settings. The sync engine re-scans source and destination and skips files already transferred in the previous run.
Closing the Desktop App discards in-progress and stopped sync state. Stopped syncs that have not been resumed are lost when the app exits.
Desktop App Sync Mode vs. Files.com Sync
Desktop App Sync Mode and the Files.com Sync feature are built for different workflows. They are not two ways to do the same thing.
Desktop App Sync Mode is for moving files between your local computer and Files.com on demand, in either direction. A Push run sends files from your local machine to Files.com. A Pull run brings files from Files.com down to your local machine. You start each run manually. It runs on your machine and stops when the transfer is done. It fits workflows where a person is driving the process, for example delivering a batch of files to a project folder or pulling down a set of files to work on locally.
The Files.com Sync feature transfers files between any two locations configured in Files.com: folders within your site, remote servers (including Amazon S3, Azure, Google Cloud Storage, Box, Dropbox, OneDrive, SharePoint, and FTP/SFTP systems), and child sites. It runs on a recurring schedule or when triggered by an Automation. Each run compares the source and destination and transfers files that are missing or have a different size. It requires no local machine and runs entirely within Files.com's infrastructure.