The 'conflicted copy' problem: sync that silently duplicates your files
2013–2026
When Dropbox cannot reconcile two versions of a file, it preserves both — saving the loser as a duplicate stamped 'conflicted copy' — a data-safety mechanism that in practice creates lasting duplication and version confusion that users cannot turn off.
What happened
When Dropbox detects that a file has been edited in two places at once, or that two diverged versions exist, it does not overwrite either one. Instead it keeps the 'winning' version under the original name and saves the other as a duplicate decorated with the editor's username, the literal phrase 'conflicted copy,' and a date — for example, 'report (Jane's conflicted copy 2023-01-15).docx'. By design this guarantees no edit is ever lost.
In practice the behavior is a chronic source of clutter and confusion. Dropbox's own help center lists three triggers: two users editing the same file simultaneously; someone editing offline while another edits the same file; and a file left open in an application on another computer, which Dropbox notes is 'especially common with auto-save applications.' Because the mechanism is last-writer-preservation rather than true file locking or content merging, conflicted copies routinely appear even for a single user working across multiple devices. Community threads complaining about the behavior — including cases where users insist they were the only person editing — span well over a decade and continue to the present.
Crucially, there is no setting to disable it; Dropbox's guidance is to merge the copies manually and to 'take turns editing.'
Impact
For individual users, conflicted copies mean duplicated, fragmented files and the real risk of editing the wrong version or losing recent changes buried in a copy they never noticed. For teams, they undermine Dropbox's core promise of a single shared source of truth, since a document can quietly fork into multiple parallel versions. The absence of any opt-out, and the fact that the behavior can fire even with one editor, have made it one of the longest-running and most consistently voiced reliability gripes about Dropbox sync.