Desktop App Sync Mode runs a one-time comparison and transfer between a local folder and a folder on Files.com. It transfers files missing from the destination or whose sizes differ, skipping the transfer for files with the same path and size. Each sync run is a one-time operation you start manually.

Desktop App Sync Mode 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 uses parallel transfers for these bulk operations. Throughput depends on your network, storage, and file sizes. 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 file paths and sizes, so it can identify transfers without reading every byte of both copies. It does not compare file contents or use content hashes to establish equality.

A file changed without changing its size is not transferred when a file of the same size already exists at the destination path. Use Turbo Transfer Mode with the appropriate overwrite option to transfer a known revised file that this comparison would skip.

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 source files after a successful transfer or when the destination already has a file with the same path and size.
Delete source empty folders	Remove empty folders from the source after the transfer completes.
Move source	Specify an archive path on the source. Move files there after a successful transfer or when the destination already has a file with the same path and size.
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.

Source File Cleanup

Delete source files and Move source let you clear a working folder once its files are present at the destination. Both options apply to files that transfer successfully and files already present at the destination with the same path and size.

An existing match needs no transfer before the source is deleted or archived, regardless of which user, application, or earlier run placed the file there. Because the comparison does not check contents, cleanup can occur even if the destination file's contents differ while its size matches.

Choose Move source to retain an archive at the source instead of deleting the files. For a Push, the source and archive are on your local computer; for a Pull, they are on Files.com. With either cleanup option, a file stays at its original source path if its transfer fails or the Include or Ignore patterns exclude it.

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 transferring files already present with the same path and size. Source cleanup still applies if enabled.

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 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. Files.com runs the Sync without the Desktop App. A Sync that uses an On-Premise Agent still requires the Agent and its local storage to be available.