I am new to FFS and have a question that I can't find an answer I fully understand in the forums.
My issue is how I may set up FFS to automatically handle scenarios where a file has changed in both locations.
By default, FFS notifies me when a file in both locations has changed and does not copy these files.
Instead, I'd like to configure FFS to perform one of these two options.
A: If a file changes in both sync folders, sync the newer file and remove the old one.
B: If a file changes in both sync folders, transfer the new file to both folders and rename the old one as a conflict file.
Here is an example of the FFS batch file I'm using. Any help would be appreciated.
<?xml version="1.0" encoding="utf-8"?>
<FreeFileSync XmlType="BATCH" XmlFormat="23">
<Notes/>
<Compare>
<Variant>TimeAndSize</Variant>
<Symlinks>Exclude</Symlinks>
<IgnoreTimeShift/>
</Compare>
<Synchronize>
<Changes>
<Left Create="right" Update="right" Delete="right"/>
<Right Create="left" Update="left" Delete="left"/>
</Changes>
<DeletionPolicy>Permanent</DeletionPolicy>
<VersioningFolder Style="TimeStamp-File">C:\FFS\Versioning</VersioningFolder>
</Synchronize>
<Filter>
<Include>
<Item>*</Item>
</Include>
<Exclude>
<Item>\System Volume Information\</Item>
<Item>\$Recycle.Bin\</Item>
<Item>\RECYCLE?\</Item>
<Item>\Recovery\</Item>
<Item>*\thumbs.db</Item>
</Exclude>
<SizeMin Unit="None">0</SizeMin>
<SizeMax Unit="None">0</SizeMax>
<TimeSpan Type="None">0</TimeSpan>
</Filter>
<FolderPairs>
<Pair>
<Left>C:\Local Folder 1</Left>
<Right>C:\Local Folder 2</Right>
</Pair>
</FolderPairs>
<Errors Ignore="true" Retry="0" Delay="5"/>
<PostSyncCommand Condition="Completion"/>
<LogFolder/>
<EmailNotification Condition="Always"/>
<GridViewType>Action</GridViewType>
<Batch>
<ProgressDialog Minimized="false" AutoClose="false"/>
<ErrorDialog>Show</ErrorDialog>
<PostSyncAction>None</PostSyncAction>
</Batch>
</FreeFileSync>
How I may set up FFS, to automatically handle scenarios where a file has changed in both locations
- Posts: 1
- Joined: 29 Oct 2025
-
- Posts: 2978
- Joined: 22 Aug 2012
> By default, FFS notifies me when a file in both locations has changed and does not copy these files.
This suggests you have checkmarked "Use database file to detect changes" in your Synchronization Settings (F8). (Which is a must when using the Two Way sync variant).
If both sides have changed since the last sync, FreeFileSync (FFS) then (correctly) reports such cases as unresolved conflicts.
Your option A):
By removing the "Use database file to detect changes" checkmark in the Two Way sync variant, that variant changes into a Custom sync variant with settings as you describe for option A), and should simply copy the most recent recently changed side to the other side.
Your option B):
FFS can not do exactly what you describe.
However, in addition to what I describe for option A), you can use Versioning. Of all files that get deleted or overwritten by your FFS sync, Versioning allows you to retain as many versions as you select for as long as you select, in a self-selected location.
Note that by removing the checkmark for "Use database file to detect changes" you loose the benefit of automatically detecting moved or renamed files.
This suggests you have checkmarked "Use database file to detect changes" in your Synchronization Settings (F8). (Which is a must when using the Two Way sync variant).
If both sides have changed since the last sync, FreeFileSync (FFS) then (correctly) reports such cases as unresolved conflicts.
Your option A):
By removing the "Use database file to detect changes" checkmark in the Two Way sync variant, that variant changes into a Custom sync variant with settings as you describe for option A), and should simply copy the most recent recently changed side to the other side.
Your option B):
FFS can not do exactly what you describe.
However, in addition to what I describe for option A), you can use Versioning. Of all files that get deleted or overwritten by your FFS sync, Versioning allows you to retain as many versions as you select for as long as you select, in a self-selected location.
Note that by removing the checkmark for "Use database file to detect changes" you loose the benefit of automatically detecting moved or renamed files.
