ReelWorkshop's duplicate detection works by fingerprinting each imported file and comparing it to others already in your project. It's built to catch exact-duplicate files — the same file imported twice, or copies saved without any changes — not to judge whether two clips look similar to a human eye.
Likely cause: two copies of the same original file
The most common false-positive scenario isn't actually false at all: it's two identical copies of the same file that got named differently, perhaps one from your phone and one from a cloud backup. The content is genuinely identical even though you think of them as different sources.
Less common cause: an unedited export re-save
If you exported a clip from an editing app without changing anything and re-saved it, some apps re-encode to an identical or near-identical file, which can register as a match even though you consider it a distinct step in your workflow.
What the flag does and doesn't do
The duplicate flag is advisory only — it tells you two files match, it doesn't block the import or delete anything automatically. You decide what to do with the flagged clip.
- Check the flagged pair
Open both clips in the inspector and compare them directly rather than assuming the flag is wrong.
- Keep both if they're genuinely different
If they're actually different takes or moments that happen to fingerprint the same way, keep both in your project — the flag doesn't force removal.
- Remove one if they really are identical
If they are the same file, removing the redundant copy keeps your project cleaner and avoids repeating the same footage in your compilation.
Fingerprinting flags identical files. It does not catch two different takes of the same shot, even if they look nearly identical to you — that's a separate limitation, covered on the near-duplicate page.
When to trust the flag versus your own eyes
Trust the flag as a starting point, not a final answer. It's telling you the file data matches, which is a useful signal, but the decision of whether that matters for your compilation is still yours.
Can I turn off duplicate detection?
The check runs automatically on import as a helpful signal, but it never removes anything for you, so there's nothing to disable — just ignore the flag if it doesn't apply to your situation.
Why would two different-looking clips fingerprint the same?
If the underlying file data is identical, for example an unedited copy saved under a new name, the fingerprint will match even though you think of them as separate clips.