Where Does Syncthing Put Conflict Files?
Syncthing conflict copies appear inside the synced folder with .sync-conflict names. Pattern, limits and config paths.
Last updated
Syncthing never hides a conflict in a system folder. When two devices change the same file, the loser gets renamed with a .sync-conflict stamp and stays right next to the winner inside the same synced folder. The copies then sync around like ordinary files.
The name carries the story: original name, conflict tag, date, time and the device that lost. The older timestamp loses by default. Cap the pile with maxConflicts in config.xml, which defaults to keeping ten per file. This is easier through the GUI than by editing XML.
Where Syncthing stores this, by platform
<synced-folder>\<filename>.sync-conflict-<date>-<time>-<device>.<ext>
Example report.sync-conflict-20260115-093000-ABCDEF7.docx beside report.docx. Config lives at %LOCALAPPDATA%\Syncthing\config.xml with maxConflicts defaulting to 10. Stop Syncthing before copying config by hand.
<synced-folder>/<filename>.sync-conflict-<date>-<time>-<device>.<ext>
Same naming on Mac. Config lives at ~/Library/Application Support/Syncthing/config.xml. Homebrew services use the same path, so CLI and app installs converge.
<synced-folder>/<filename>.sync-conflict-<date>-<time>-<device>.<ext>
Same naming on Linux. Config lives at ~/.local/state/syncthing/config.xml on current builds, ~/.config/syncthing on installs from before 1.27. Overrides exist via --config and STHOMEDIR.
Frequently asked questions
How do I resolve a Syncthing conflict file?
Open both copies and merge by hand, then delete the .sync-conflict version. Deleting it on one device deletes it everywhere, which is what you want once the winner holds the merged content. Back up both first when the file matters.
Can I turn off conflict copies?
Yes by setting maxConflicts to 0 in config.xml, though keeping the default of 10 is safer. Unlimited retention uses -1. The GUI exposes the same setting per folder, which beats editing XML across several nodes.
Why did a conflict appear when I only deleted a file?
Another device edited the file while yours deleted it, and the delete won. Syncthing still keeps the edited copy as a conflict file so no content vanishes silently. Check the device tag in the name to see which side edited it.
Notice an outdated path? Let us know.