SyncFolder — Desktop User Guide

General Settings

The General section of the Advanced Task Settings dialog contains foundational options that control how SyncFolder scans the destination, handles empty folders, and treats Windows reparse points such as symbolic links and junctions. These settings apply to the task as a whole and affect every run of that task.

Settings Overview

SettingTypeDefault
Scan destination on every sync Toggle Off
Don't copy empty folders Toggle Off
Handling of system shortcuts and junctions Select Ignore only inaccessible links

Scan Destination on Every Sync

Scan destination on every sync Toggle Default: Off

When this setting is off (the default), SyncFolder maintains an internal cache database for the destination location. After the first run — or after a task reset — the cache records which folders and files exist at the destination. Subsequent runs use this cache instead of scanning the destination again, which makes those runs significantly faster.

When this setting is on, SyncFolder performs a full scan of the destination at the start of every run. The cache is not used.

When to use the cache (default — off)

The cache is the right choice when the destination is only ever modified by SyncFolder itself. In that situation the cache is always accurate, and using it avoids the overhead of a full destination scan on every run. This is the most common scenario for both one-way and backup tasks where the destination is a dedicated sync or backup folder.

When to enable scanning on every sync

Enable this setting when the destination may be modified outside of SyncFolder between runs — for example, when files are manually added, deleted, or changed directly on the destination, or when another application also writes to the same location. In these cases the cache would be out of date and SyncFolder might make incorrect decisions about which files need to be copied or deleted. Scanning on every run eliminates this risk at the cost of a longer startup phase.

If the destination is modified outside of SyncFolder while the cache is active, the cache becomes stale. A stale cache can cause SyncFolder to miss changes or take incorrect actions. Either enable this setting, or reset the task after any external modification to force a fresh scan on the next run.
Resetting the cache. The cache is cleared when you reset a task. You can do this from the task action button on the Tasks Page or on the Task Status Page. After a reset, the next run always performs a full destination scan to rebuild the cache.
2-way sync tasks. This setting is not available for 2-way sync tasks. Because 2-way sync must always reconcile changes from both locations, a full scan of both sides is performed on every run.

Don't Copy Empty Folders

Don't copy empty folders Toggle Default: Off

When this setting is off (the default), SyncFolder replicates the complete folder structure of the source to the destination, including folders that contain no files.

When this setting is on, folders that are empty — or that contain only excluded files — are not created at the destination. Only folders that contain at least one file that will be copied are created.

This setting is useful when a source tree contains many scaffolded or placeholder folders that have no content yet, or when file exclusion filters strip all files from certain folders, leaving them empty at the destination. Enabling this option keeps the destination clean and avoids creating a folder hierarchy with no meaningful content.

A folder is considered empty if it contains no files that pass the active file filters. A folder that contains only subfolders — but no files at any level below it — is also treated as empty when this setting is on.

Handling of System Shortcuts and Junctions

Handling of system shortcuts and junctions Select Default: Ignore only inaccessible links

This setting controls how SyncFolder treats Windows reparse points — a category that includes symbolic links, junction points, and volume mount points. These are file system objects that point to another location rather than containing data directly.

Three options are available:

OptionBehaviour
Ignore only inaccessible links Default. Links that cannot be followed (broken links, links to offline or restricted locations) are silently skipped. Links that are accessible are treated as ordinary folders: SyncFolder follows the link and copies all files and subfolders found at the linked location as if they were part of the source folder tree. No link is created at the destination — the copied content appears as a regular folder.
Include all linked content All reparse points, whether accessible or not, are followed and their content is copied. Inaccessible links are not skipped; SyncFolder will attempt to follow them and report an error if they cannot be resolved. The content is copied as regular folders and files at the destination.
Ignore all links All reparse points are skipped entirely, regardless of whether they are accessible. Only real folders and files are processed. This is the safest option when the source tree contains links that should not be followed.

What is a reparse point?

Windows uses reparse points to implement several features. The most common types you may encounter in a source folder tree are:

  • Symbolic links — a pointer to another file or folder, anywhere on the system.
  • Junction points — similar to symbolic links but limited to folders on local volumes. Widely used by Windows itself (e.g. C:\Users\Default, C:\ProgramData).
  • Volume mount points — a volume mounted inside a folder rather than at a drive letter.
Risk of duplicate copies. When links are followed (the default or "Include all" option), the content at the linked location is copied to the destination as a regular folder. If the same linked location is also the source or destination of another SyncFolder task, or is reachable through multiple links in the same tree, its content may be copied more than once. If this is a concern, use Ignore all links or restructure your tasks to avoid overlapping coverage.
Tip for development trees. Source trees for .NET and Node.js projects sometimes contain junction points created by package managers or build tools. If you do not need to sync the linked content, selecting Ignore all links avoids unexpectedly copying large dependency trees that are already excluded elsewhere.

Related topics: Advanced Task Settings Overview · Performance Settings · Using Filter Patterns

Last updated: 1 May 2026