Sync conflicts

When two devices edit the same file

A conflict happens when two of your devices change the same file before either one gets a chance to sync with the other. Foldpair never guesses which version is “right” — it keeps both and lets you decide.

What causes it

You or another folder member edited the same file on two devices before those changes synced. The version that reached the relay first keeps the original name. On the device with the later conflicting edit, Foldpair preserves that local edit beside it as <name>.conflict-<stamp><ext>, then applies the published version. Compare both copies before deciding what to keep.

Find the preserved copies

Open Review sync conflicts. This is a read-only list of copies found on this device. Select Reveal saved copy to locate a file in your file manager, then open the versions you want to compare.

The window does not replace, rename, or delete files for you. An empty list does not prove that every conflict is resolved, and the list is not a complete version history.

Compare before changing a file

A preserved copy may have a name such as <name>.conflict-<stamp><ext>. The timestamp in that name does not verify which device or source version it came from. Check the contents before deciding what to keep.

If you manage the versions manually, first copy any version you may need to a separate safe location. You can then keep both files under distinct names, or replace the working file with the version you choose. Changes in a synced folder can propagate to other devices.

Recovery has limits

Files that Foldpair removes or replaces during sync can be kept in the folder’s local recovery bin. These protected copies are not removed by automatic cleanup, but they can be deleted manually. Recovery requires the local copy to remain available. Do not assume a file you delete manually will be kept there. See Recover a deleted file for recovery instructions.