Expert Settings

FreeFileSync has a number of special purpose settings that can only be accessed directly via the global configuration file GlobalSettings.xml. Note that this file is read once when FreeFileSync starts and saved when it closes. Therefore do only apply changes while FreeFileSync is not running.

To locate this file on Windows enter %appdata%\FreeFileSync in the Windows Explorer address bar or go to the FreeFileSync installation folder if you are using the portable installation. On Linux you can find the file in ~/.FreeFileSync for the Launchpad release and in the installation folder for the portable version. On OS X go to ~/Library/Application Support/FreeFileSync.

<?xml version="1.0" encoding="UTF-8"?>
<FreeFileSync XmlType="GLOBAL">
        <FileTimeTolerance Seconds="2"/>
        <RunWithBackgroundPriority Enabled="false"/>
        <LockDirectoriesDuringSync Enabled="true"/>
        <VerifyCopiedFiles Enabled="false"/>
        <LastSyncsLogSizeMax Bytes="100000"/>

By default file modification times are allowed to have a 2 second difference while still being considered equal. This is required by FAT/FAT32 file systems which store file times with a 2 second precision only.
This setting can also be used to simulate a "compare by file size", ignoring last modification times: Set tolerance to -1 which will be considered as an unlimited file time tolerance. Changed files will then be detected as a conflict (same date, different file size) and the synchronization direction for conflicts can be used accordingly.

While synchronization is running, other applications which are accessing the same data locations may experience a noticeable slowdown. Enable this setting to lower FreeFileSync's resource consumption at the cost of a significantly slower synchronization speed.

In order to avoid race conditions of multiple FreeFileSync instances writing to the same folder at the same time, accesses are serialized by lock files (sync.ffs_lock). This allows to operate FreeFileSync with an arbitrary number of users in a network out of the box.

If active, FreeFileSync will binary-compare source and target files after copying and report verification errors. Note that this may double file copy times and is no guarantee that data has not already been corrupted prior to copying and corruption is not hidden by deceptively reading valid data from various buffers in the application and hardware stack.
Does the CopyFile function verify that the data reached its final destination successfully?

The progress logs of the most recent synchronizations (for both GUI and batch jobs) are collected automatically in the file LastSyncs.log. The maximum size of this log file can be set here.