Find duplicates
Updated August 12, 2026 · 7 min read
OneDrive Sync Conflicts vs Duplicate Files: What’s the Difference?
Tell an unresolved edit conflict from a redundant exact copy before choosing a cleanup action.
Sync conflicts and duplicates can look alike in a folder view because both may produce two similarly named items. Their safe resolution is different: conflicts protect potentially unique work, while exact duplicate review focuses on redundant storage and item context.
Begin by asking whether the bytes differ. If size and fingerprint match, the content is exact. If they do not—or no trustworthy fingerprint is available—treat the pair as a version problem until someone reviews it.
A practical checklist
- 1Check for active sync errors, offline edits, or device-name suffixes.
- 2Preserve both items while diagnosing the conflict.
- 3Compare size and reliable content fingerprints.
- 4Merge divergent content in the native application when necessary.
- 5Only add confirmed exact, redundant items to a cleanup plan.
Recognize a conflict
Conflicts often follow concurrent edits, permissions changes, reconnects, or a client that worked offline. They may have similar names and nearby timestamps, but each item can contain valid changes.
The correct outcome may be a merged document rather than deletion. Spreadsheet formulas, comments, and presentation notes deserve application-level comparison when the files differ.
Recognize an exact duplicate
Exact copies share the same byte length and supported content fingerprint. Their names and folders may differ because copying or renaming changes item metadata without changing the file body.
Once confirmed, inspect which item owns the expected path, share links, permissions, and version history. Equality is the start of retention review, not the final instruction.
Apply the right resolution
For conflicts, stop the cause, compare versions, merge unique work, and confirm sync is stable. For exact duplicates, select at least one keeper, exclude protected or necessary copies, and export the proposed plan.
Never let a naming rule send both categories through the same bulk action. A transparent report should state whether each group is exact or merely needs review.
- Conflict: preserve and reconcile
- Exact copy: confirm and review context
- Uncertain: leave untouched
Limits and risks to check
- — Conflict copies can contain unique edits.
- — A matching name pattern cannot determine content equality.
- — Exact copies may still have different sharing or retention roles.
- — Sync must be stable before either resolution.
Official references
Frequently asked questions
Are all files with “copy” in the name sync conflicts?
No. The suffix may come from a browser download, manual copy, export, or sync process. Inspect the context and content.
Can metadata prove two conflict files are different?
Different size or fingerprint proves they are not exact copies, but understanding the edits requires opening or comparing content.
Which group does ClearCopies automate?
The MVP only groups exact candidates with matching size and quickXorHash. It leaves ambiguous relationships for review.
Scan first. Decide with evidence.
ClearCopies reads supported cloud-drive metadata and groups exact copies by byte size plus a provider-supplied content fingerprint. Original file bodies are not downloaded for the scan. You review the result and export a plan before any separate write step.