{"id":"data-transfers.bidirectional-sync-conflicts","url":"/faq/data-transfers/bidirectional-sync-conflicts","category":{"id":"data-transfers","title":"Data Transfers"},"subcategory":{"id":"operations","title":"Copy, Move and Sync"},"question":"What happens if the same file changes on both sides of a two-way sync?","alt_questions":["two-way sync conflict mac","file edited in both places sync","how are sync conflicts handled","bidirectional sync conflict resolution","where do I see sync conflicts"],"short_answer":"When a file changed on both sides, Bidirectional sync records the conflict in the transfer's log instead of silently choosing. Check the Log card, keep the version you want, and the next run carries it across.","answer_markdown":"That's a conflict, and Bidirectional sync records it in the transfer's log rather than silently picking a winner. Select the transfer in Data Transfers and read the **Log** card to see which files were affected.\n\nTo keep conflicts rare:\n\n- Run the sync often (a schedule helps), so each side has fewer changes waiting.\n- Avoid editing the same file in both places between runs.\n- Close a file before a run if you're editing it.\n\nIf you find a conflict, open both versions, keep the one you want, and let the next run carry it across.\n\nRelated: [What is Bidirectional sync?](/faq/data-transfers/what-is-bidirectional-sync) · [Where is the transfer log?](/faq/data-transfers/where-is-the-transfer-log)","answer_html":"

That's a conflict, and Bidirectional sync records it in the transfer's log rather than silently picking a winner. Select the transfer in Data Transfers and read the Log card to see which files were affected.

\n

To keep conflicts rare:

\n\n

If you find a conflict, open both versions, keep the one you want, and let the next run carry it across.

\n

Related: What is Bidirectional sync? · Where is the transfer log?

","answer_text":"That's a conflict, and Bidirectional sync records it in the transfer's log rather than silently picking a winner. Select the transfer in Data Transfers and read the Log card to see which files were affected.\n\nTo keep conflicts rare:\n\n- Run the sync often (a schedule helps), so each side has fewer changes waiting.\n- Avoid editing the same file in both places between runs.\n- Close a file before a run if you're editing it.\n\nIf you find a conflict, open both versions, keep the one you want, and let the next run carry it across.\n\nRelated: What is Bidirectional sync? · Where is the transfer log?","tags":["conflicts","two-way sync","log"],"related":[{"id":"data-transfers.what-is-bidirectional-sync","question":"What is Bidirectional sync and when should I use it?","url":"/faq/data-transfers/what-is-bidirectional-sync"},{"id":"data-transfers.where-is-the-transfer-log","question":"Where can I see the details or log of a transfer?","url":"/faq/data-transfers/where-is-the-transfer-log"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"What happens if the same file changes on both sides of a two-way sync? — Storage Studio FAQ","description":"When a file changed on both sides, Bidirectional sync records the conflict in the transfer's log instead of silently choosing. Check the Log card, keep the version you want, and the next run carries it across.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Data Transfers","path":"/faq/data-transfers/"},{"name":"What happens if the same file changes on both sides of a two-way sync?","path":"/faq/data-transfers/bidirectional-sync-conflicts"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/data-transfers/bidirectional-sync-conflicts","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"What happens if the same file changes on both sides of a two-way sync?","alternateName":["two-way sync conflict mac","file edited in both places sync","how are sync conflicts handled","bidirectional sync conflict resolution","where do I see sync conflicts"],"acceptedAnswer":{"@type":"Answer","text":"That's a conflict, and Bidirectional sync records it in the transfer's log rather than silently picking a winner. Select the transfer in Data Transfers and read the Log card to see which files were affected.\n\nTo keep conflicts rare:\n\n- Run the sync often (a schedule helps), so each side has fewer changes waiting.\n- Avoid editing the same file in both places between runs.\n- Close a file before a run if you're editing it.\n\nIf you find a conflict, open both versions, keep the one you want, and let the next run carry it across.\n\nRelated: What is Bidirectional sync? · Where is the transfer log?","url":"https://storagestudio.us/faq/data-transfers/bidirectional-sync-conflicts"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Data Transfers · Copy, Move and Sync

\n

What happens if the same file changes on both sides of a two-way sync?

\n

Short answer: When a file changed on both sides, Bidirectional sync records the conflict in the transfer's log instead of silently choosing. Check the Log card, keep the version you want, and the next run carries it across.

\n

That's a conflict, and Bidirectional sync records it in the transfer's log rather than silently picking a winner. Select the transfer in Data Transfers and read the Log card to see which files were affected.

\n

To keep conflicts rare:

\n
  • Run the sync often (a schedule helps), so each side has fewer changes waiting.
  • Avoid editing the same file in both places between runs.
  • Close a file before a run if you're editing it.
\n

If you find a conflict, open both versions, keep the one you want, and let the next run carry it across.

\n

Related: What is Bidirectional sync? · Where is the transfer log?

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}