How it works
Updated August 12, 2026 · 7 min read
What Is an Exact Duplicate File?
Understand byte-identical copies, why names are not enough, and what an exact match can—and cannot—prove.
“Duplicate” is often used for several different relationships: the same bytes, the same photo at another resolution, two revisions of a document, or simply two items with the same name. Cleanup is safer when those meanings are kept separate.
ClearCopies uses the narrowest meaning for its exact groups. It compares byte count and OneDrive’s quickXorHash when available. That evidence supports a content claim, not a business claim about which folder or copy is dispensable.
A practical checklist
- 1Confirm that both items are files, not folders or shortcuts.
- 2Compare byte size as a first-pass filter.
- 3Require the same supported content-fingerprint algorithm and value.
- 4Inspect paths and sharing before deciding whether a redundant copy exists.
- 5Keep uncertain or fingerprint-free items outside automatic recommendations.
Exact, near, and functional duplicates
Exact duplicates are byte-for-byte equal. Near-duplicates differ at the binary level but may look alike, such as a resized photo or recompressed video. Functional duplicates may communicate the same information while containing revisions, formatting changes, or different embedded metadata.
Each category needs different evidence. Exact matching can be deterministic. Visual and semantic similarity need thresholds and human judgment, making them unsuitable for the same safety label.
What a fingerprint contributes
A content fingerprint is derived from file bytes and provides a compact comparison value. Combined with byte size and the same algorithm, it lets a scanner group exact candidates without comparing filenames or downloading the body itself when OneDrive supplies the value.
A fingerprint match does not merge identities. The copies still have distinct item IDs, paths, permissions, timestamps, and histories. Those attributes determine whether removing one would disrupt a workflow.
Use precise labels in a cleanup plan
Call size-only or name-only matches “possible” rather than exact. Reserve “exact” for groups meeting the defined evidence rule and document that rule in the export. This helps reviewers understand why each item appeared.
ClearCopies’ current exact rule is intentionally simple: same byte size and quickXorHash. It does not claim that visually similar files or equivalent document revisions are duplicates.
Limits and risks to check
- — Identical content does not mean identical permissions or link behavior.
- — Different files can legitimately share a common filename and size.
- — Near-duplicates require content processing and subjective thresholds.
- — Hash availability differs by account, file state, and provider.
Official references
Frequently asked questions
Are two files with the same name exact duplicates?
No. Names can repeat in different folders and often describe unrelated content.
Are resized photos exact duplicates?
No. Resizing changes the bytes, even when the images look nearly identical.
Does an exact match make one copy safe to delete?
It proves content equality, not dispensability. Check sharing, path dependencies, ownership, and history first.
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.