Dropbox · Find duplicates
Updated August 12, 2026 · min read
Dropbox Conflicted Copies vs Exact Duplicates
Learn why a conflicted copy may preserve unique edits and how content_hash separates it from an exact duplicate.
Dropbox adds a username, the words conflicted copy, and a save date when it preserves competing edits. Common causes include two people editing at once, an offline editor reconnecting, or an application leaving a file open with auto-save. The suffix is a warning that two histories may exist, not a reliable cleanup label.
Start by opening or comparing both versions in the appropriate application, especially for documents, design sources, spreadsheets, and code. If the Dropbox size and `content_hash` match, the bytes are exact and the conflict may be redundant. If the fingerprints differ, keep both until someone merges or explicitly chooses the authoritative content.
A practical checklist
- 1Identify the original and every conflicted copy in the same work item.
- 2Compare content and history before considering any removal.
- 3Use equal size and Dropbox content_hash only for byte-identical proof.
- 4Merge or approve distinct edits when fingerprints differ.
- 5Correct the collaboration habit that produced the conflict.
Understand the situation
Dropbox adds a username, the words conflicted copy, and a save date when it preserves competing edits. Common causes include two people editing at once, an offline editor reconnecting, or an application leaving a file open with auto-save. The suffix is a warning that two histories may exist, not a reliable cleanup label.
Names and timestamps help a person understand context, but they are not exact-match evidence. For a metadata-only scan, matching byte size plus a provider-supported content fingerprint is the boundary between a candidate and a confirmed exact group.
Use a controlled workflow
Start by opening or comparing both versions in the appropriate application, especially for documents, design sources, spreadsheets, and code. If the Dropbox size and `content_hash` match, the bytes are exact and the conflict may be redundant. If the fingerprints differ, keep both until someone merges or explicitly chooses the authoritative content.
Review the groups in small batches. Favor obvious staging or import folders first, preserve shared or protected items for manual review, and require at least one retained copy in every group.
- Compare content and history before considering any removal.
- Use equal size and Dropbox content_hash only for byte-identical proof.
- Merge or approve distinct edits when fingerprints differ.
Make the final decision
Resolve the working practice after resolving the files. Coordinate edits, use real-time collaboration where supported, and avoid leaving auto-saving files open on unattended devices. For teams, identify an owner for conflict resolution. A duplicate cleanup can remove confirmed extra copies, but it cannot decide how to merge two genuinely different versions.
ClearCopies does not download file bodies during its initial scan and does not silently remove results. It produces exact groups from cloud metadata so the user can review and export a plan before any separate write step.
Limits and risks to check
- — The last saved conflicted copy can contain the newest unique edits.
- — Matching names and close timestamps do not establish equal content.
- — Removing one version before merging can discard a collaborator’s work.
- — Recurring conflicts indicate a workflow issue that cleanup alone cannot fix.
Official references
Frequently asked questions
Is every conflicted copy a duplicate?
No. Dropbox creates it precisely because edits competed. Treat it as a potentially unique version until content comparison or an exact provider hash match proves otherwise.
Can ClearCopies merge conflicted documents?
No. It can show whether bytes match, but document-aware merging requires the relevant editor and a person who understands the intended changes.
How can teams reduce future conflicts?
Coordinate editing, prefer real-time collaboration where available, avoid editing offline in parallel, and close auto-saving applications when work is handed to another person.
Scan first. Decide with evidence.
ClearCopies reads Dropbox metadata and groups exact copies by byte size plus content_hash. Original file bodies are not downloaded for the scan. You review the result and export a plan before any separate write step.