# DaVinci Resolve Find Duplicate Clips in Media Pool: What Works > **Quick answer:** To find duplicate clips in the DaVinci Resolve Media Pool, compare their names, paths, durations, frame rates, and other metadata in List View; Resolve’s search and Smart Bins can narrow the list, but they are not proof that two entries point to the same file. Confirm the source path before removing anything. For repeated footage on a timeline, use View > Show Duplicate Frames instead. *Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.* *Updated 2026-10-30 · DaVinci Resolve 21.1 (October 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-find-duplicate-clips-in-media-pool* Two files with the same name can be different shots. Two different names can point to the same footage. And a clip that appears twice in a timeline may be exactly where you intended it to be. As of October 2026, the current release is DaVinci Resolve 21.1. The useful first step is to decide which kind of “duplicate” you mean, then compare evidence that identifies the source rather than trusting a thumbnail or filename. ## How do I find duplicate clips in the DaVinci Resolve Media Pool? To find likely duplicate clips in the DaVinci Resolve Media Pool, switch to List View, show useful metadata columns, and compare the entries’ names, paths, durations, and other media properties. Resolve’s search can narrow the candidates, but a matching filename alone does not prove the entries point to the same source. The distinction matters because people use “duplicate clip” to mean several different things. Resolve’s Media Pool holds entries in a project. Your storage drive holds files. A timeline holds edited instances. A duplicate in one of those places does not automatically mean there’s a duplicate in the others. | What looks duplicated? | Where to investigate | What counts as useful evidence? | What the check does not prove | | --- | --- | --- | --- | | Two entries in a bin | Media Pool List View and metadata | Matching source path and compatible media details | That either entry is unused | | Similar-looking files on disk | The full source path and file properties | Same path, or a verified byte-for-byte comparison outside Resolve | That the project has duplicate Media Pool entries | | A shot used twice in a timeline | Timeline and View > Show Duplicate Frames | Resolve’s duplicate-frame indicators | That the Media Pool contains duplicate entries | | Multiple timeline edits from one source | Timeline clips and their source relationships | Matching source and distinct edit ranges | That the edits are redundant | | A clip imported into multiple bins | Bin contents and the clip’s project identity | Whether the entries share a source and whether organization is intentional | That removing an entry will preserve every intended workflow | Blackmagic Design describes bins as folders for organizing Media Pool footage and Smart Bins as metadata-based collections that stay updated as new footage is added. That makes them useful for finding and grouping candidates, not a universal duplicate-file detector. [Blackmagic Design’s Media page](https://www.blackmagicdesign.com/products/davinciresolve/media) explains those organizational features. Here’s the safe rule: treat the first match as a lead, not a verdict. Confirm the file path, compare the media, and check how the project uses the entry before removing anything. **A matching filename is a clue, not proof that two Media Pool entries are the same media.** For a plain-language explanation of how the Media Pool’s search behaves, see [DaVinci Resolve Media Pool search not finding clips](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-media-pool-search-not-finding-clips). Search helps you locate candidates. It does not replace source verification. ## What does “duplicate clip” mean in DaVinci Resolve? A “duplicate clip” can mean a repeated Media Pool entry, a second copy of a file, or footage reused in a timeline. These are different situations, and Resolve’s tools reveal different parts of each one. Start by naming the problem precisely. If you are cleaning a bin, focus on Media Pool entries. If you want to check whether your edit repeats footage, inspect the timeline. If you are trying to reclaim disk space, compare files on storage. Mixing those questions can lead to deleting the wrong thing. # ## Is it a duplicate Media Pool entry? A Media Pool entry is a project item representing media Resolve can work with. Two entries may look alike because they have similar names, thumbnails, durations, or metadata. They might still point to separate copies of the footage, or they might be separate clip objects with different project-level details. The key comparison is source identity. Start with the location of the underlying file. If the entries point to different folders, the files could be independent copies even when the names match. If both entries point to the same location, that is stronger evidence of a repeated reference, but still check the project context before deleting one. Resolve’s own documentation has long distinguished a duplicated Media Pool clip from its original: the duplicated entry can behave as a separate source clip and retain distinct metadata and markers. The exact controls may differ by release, so use the current manual linked from [Blackmagic Design’s manual page](https://www.blackmagicdesign.com/welcome/en/W-DRE-03) for the interface in your installed version. The important practical point is that two similar entries should not be treated as interchangeable without checking their project relationships. [Blackmagic’s reference manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_12_Reference_Manual.pdf?_v=1488443189000) describes the separate-source behavior. # ## Is it a duplicate file on the drive? A duplicate file is a second stored file, not merely another visible item in a bin. Two files can have identical content but live in separate folders. Conversely, two files with identical names may contain different takes or revisions. The Media Pool can help you identify where a clip comes from, but a bin view is not a full disk audit. If reclaiming storage is the goal, verify the source files with a file-management tool or a trusted duplicate-file utility outside Resolve. Compare the full path and, when appropriate, a file checksum. Do not assume Resolve will identify or remove duplicate files merely because they appear together in a bin. A file comparison outside Resolve also needs care. A source file and a transcoded proxy may depict the same shot but differ in format, resolution, or compression. They are related media, not byte-for-byte duplicates. A camera original and a color-corrected render may look alike in a thumbnail but serve different purposes. # ## Is the footage repeated in a timeline? A timeline repeat means footage is used more than once in an edit. The timeline could contain the same source at different moments, or it could reuse the same range of source frames. Those are different kinds of repetition. For repeated frame ranges, Resolve includes Duplicate Frame Detection. The reference-manual description says it marks timeline clips with colored bars when a range of frames has been used more than once. That is a timeline check, not a Media Pool duplicate search. [Blackmagic’s reference manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_18_Reference_Manual.pdf) is often mirrored elsewhere, but prefer the current manual from Blackmagic’s [official manual page](https://www.blackmagicdesign.com/welcome/en/W-DRE-03) when confirming the exact current menu wording. The older official reference manual also describes flags as a way to identify timeline clips that share a Media Pool source. That can help when inspecting repeated uses of one source, but it still does not answer whether two entries in a bin are duplicate files. [Blackmagic’s Resolve 10 manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_10_Reference_Manual.pdf) discusses flags and shared Media Pool sources. **Timeline duplicate-frame detection answers “Have I reused these frames?” It does not answer “Are these two bin entries the same file?”** # ## Are they alternate edits from one source? A single source can appear in several timeline edits. One use might be a wide shot, another a close crop, and a third a shorter reaction. Their timeline instances can share source media while having different trims, effects, or timing. That is normally not a duplicate-cleanup problem. It may be a deliberate edit. If the source appears in the Media Pool more than once, compare the entries and inspect the timeline uses before drawing conclusions. Deleting a source entry to make the bin look tidy can create a missing-media problem or disrupt a relationship you still need. # ## Are they subclips, compound clips, or generated media? A subclip can represent a selected range from longer source media. A compound clip or another generated item can contain a different kind of project structure. Those items may look like ordinary footage in a bin, but their roles differ. When two entries look similar, check their type and inspect them in the viewer. Don’t make a deletion decision based on the thumbnail alone. A rendered copy, a proxy, a subclip, and an original camera clip might all show the same scene. They are not automatically redundant. ## How do I narrow down duplicate candidates in List View? List View helps you compare Media Pool entries by showing their metadata in rows. Use it to find clusters of similar names or properties, then inspect the full source path and preview any ambiguous matches. Start with the bin or group of bins you want to audit. If you search the wrong scope, a clip may appear to be missing simply because Resolve is looking somewhere else. The sibling guide on [Media Pool search](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-media-pool-search-not-finding-clips) covers the search controls and common scope mistakes. # ## Where should I start? 1. Open the project and select the bin that contains the footage you want to inspect. 2. Switch the Media Pool to List View. 3. Make the available metadata columns useful for comparison. Prioritize the clip name and source location, then add duration, frame rate, resolution, or other fields that help distinguish your media. 4. Sort by name to bring similar labels together. 5. Compare likely matches in pairs or small groups. 6. Check the source path and preview the clips before calling them duplicates. The exact set of visible columns can depend on the version and view configuration. The current DaVinci Resolve manual is available through [Blackmagic Design’s manual page](https://www.blackmagicdesign.com/welcome/en/W-DRE-03). Blackmagic says the Media page includes an inspector for viewing and editing more than 200 metadata parameters per clip, and that the software supports both file-level and frame-level metadata. Those details give you useful comparison fields, but you do not need to inspect every field for a simple bin cleanup. [Blackmagic Design’s Media page](https://www.blackmagicdesign.com/products/davinciresolve/media) describes the metadata tools. # ## Which fields are worth comparing? | Field or check | Why it can help | Limitation | | --- | --- | --- | | Clip name | Groups entries with identical or nearly identical labels | Cameras and delivery workflows can reuse names | | File path | Shows whether entries point to the same folder location | Similar paths can still contain different files | | Duration | Separates many takes and trims | Different file versions can have the same duration | | Frame rate | Helps identify media with different recording properties | Matching rates do not prove shared identity | | Frame dimensions | Distinguishes some originals, proxies, and exports | Different formats can share dimensions | | Audio or video properties | Can reveal an audio-only file, a transcode, or a different camera format | Matching broad properties do not establish exact identity | | Thumbnail and viewer preview | Helps identify visual content and obvious differences | Similar shots can be different takes; thumbnails may not show the whole clip | | Metadata such as reel, scene, or take | Helps distinguish production media where the fields are populated | Fields may be blank, copied, or inconsistent | No single row is a universal test. Combine the fields. If name, duration, and frame rate match but the paths differ, the files may still be separate. If the paths match but the Media Pool entries differ, inspect the project uses and metadata before removing either one. # ## How should I use search without mistaking a match for a duplicate? Use search to reduce the candidates, not to establish identity. Enter a filename fragment or another useful field, inspect the returned entries, then compare each candidate’s path and properties. Search behavior can feel inconsistent when the selected bin, search field, or filter scope is different from what you expect. Resolve’s official Media page describes search and metadata as part of the broader media-organizing workflow, while Smart Bins use metadata criteria to group clips. A result list can show you likely matches, but the criteria you searched on determine what the results mean. [Blackmagic Design’s Media page](https://www.blackmagicdesign.com/products/davinciresolve/media) outlines these features. If you are unsure why a clip is absent from a search, check the search scope and selected bin first. Don’t respond by importing the file again. That can add another candidate and make cleanup harder. # ## What is a good worked example? **Worked example, not an observed test:** imagine a bin contains `A001_C003_0101AB.mov` and another entry with that same displayed name. The first entry points to `Day-01/Camera-A`; the second points to `Day-02/Camera-A`. Their labels match, but the paths do not. They could be separate camera files or copies from different card dumps. You should not delete one until you preview both and confirm which, if either, the project no longer needs. Now imagine that both entries show the same source path and the same media properties. That makes a repeated reference more plausible. It still doesn’t tell you whether each Media Pool entry carries different markers or metadata, or whether a timeline relies on a particular entry. Check those details before cleanup. A third possibility: one entry is a camera original and the other is a proxy or transcode. The clips may represent the same photographed scene while the media files differ. Treat that as a media-management relationship, not as proof of an accidental duplicate. **The useful comparison is not “Do these thumbnails look alike?” but “What source does each entry represent, and how is the project using it?”** ## Why do two clips with the same name have different paths? Two clips with the same name but different paths may be separate copies, separate camera files, or different revisions. The filename alone cannot tell you which explanation is correct. Camera naming patterns can repeat across cards, days, cameras, or projects. A filename that looks unique inside one folder may not be globally unique across your storage. That’s why a name-based sort is a useful starting point, not a final decision. # ## What if the paths point to different folders? Treat the entries as separate until you establish otherwise. Open each one in the viewer and compare the footage, duration, and relevant metadata. If both show the same scene, look for signs that one is a copy, proxy, transcode, or alternate export. If you work from copied card structures, folder names can be useful evidence. A camera roll or day folder may indicate distinct capture sessions, even when a filename repeats. Don’t flatten or reorganize the footage just to make duplicate names disappear. First preserve enough folder context to tell the sources apart. For client or archive work, keep a record of which copy is authoritative. If the project references the copy on a shuttle drive but you later move the project to shared storage, the path relationship may matter more than whether two files look identical. Resolve’s [official media documentation](https://www.blackmagicdesign.com/products/davinciresolve/media) describes its media-organizing workflow, including bins and metadata. For broader project preservation, use a deliberate archive workflow rather than deleting source media based on a bin label; see [how to archive a DaVinci Resolve project without losing media](https://tryuncle.com/learn/davinci-resolve/how-to-archive-a-davinci-resolve-project-without-losing-media). # ## What if the paths are identical? A matching path is strong evidence that entries refer to the same location. Before removing an entry, check whether it is a separate Media Pool object with its own project details. Resolve documentation describes duplicated clip entries as capable of holding distinct metadata and markers. That distinction is one reason not to treat “same file location” and “interchangeable project entry” as identical concepts. [Blackmagic’s reference manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_12_Reference_Manual.pdf?_v=1488443189000) explains that duplicates can be separate source clips. If the entries also have separate markers, names, or metadata, decide whether those differences matter before cleanup. You might want to consolidate a bin, but the useful result is a tidy project that preserves meaningful organization, not merely fewer visible rows. # ## What if the viewer shows different footage? Stop treating the entries as duplicates. The filename may have been reused, the metadata may be incomplete, or one entry may have been relinked to another file. Check the file path and media properties. If one item is a proxy or alternate version, label or organize it so the distinction is visible to you and other editors. Do not delete an entry solely because the name matches another. A mismatch in the viewer is a clear warning that the name is insufficient evidence. # ## What if the viewer shows the same scene but a different duration? They might be different trims, different exports, or separate recordings of the same moment. Compare the actual content from beginning to end. A single thumbnail frame may not reveal a different edit point or take. A shorter item can also be a subclip or a pre-trimmed version of longer footage. It may be useful to the edit even when it depicts the same source event. Treat duration as one clue, not a verdict. ## How do I check whether the timeline repeats footage? To check whether the timeline repeats source frames, enable Duplicate Frame Detection from the View menu while examining the timeline. Resolve marks reused frame ranges with colored bars; this helps spot frame reuse in the edit, not duplicate Media Pool entries. The feature is sometimes called “dupe detection” by editors. The important limitation is its scope: the indicator relates to frames used in the timeline. It does not scan the bin and certify that two files are the same. # ## How do I turn on Duplicate Frame Detection? 1. Open the timeline you want to inspect. 2. Choose **View > Show Duplicate Frames**. 3. Look for the colored indicators along the top edge of timeline clips. 4. Scrub or play around each marked section to determine whether the repeated frames are intentional. 5. Turn the option off when you no longer need the indicators. Menu wording and placement can shift between releases. If the item is not where expected, check the current manual linked from [Blackmagic Design’s official Resolve manual page](https://www.blackmagicdesign.com/welcome/en/W-DRE-03). The manual is the right source for the installed release’s exact controls. # ## What does a colored duplicate-frame bar mean? It means Resolve has identified a range of frames that occurs elsewhere in the timeline under the feature’s duplicate-frame logic. It is a visual aid for finding reused material. It does not tell you whether the repetition is a mistake. A repeated establishing shot might be intentional. A reaction shot may return later for pacing. A looped background may be part of the design. The editor still decides whether each reuse belongs in the cut. If you need to understand which timeline clips share a source entry, flags can also help organize and identify related timeline clips. The official [DaVinci Resolve 10 reference manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_10_Reference_Manual.pdf) notes that flags can mark other timeline clips that share the same Media Pool source clip. That’s a related-source cue, not a Media Pool duplicate scan. # ## Why does Show Duplicate Frames not solve my Media Pool problem? Because the two tools answer different questions. Duplicate Frame Detection concerns frame reuse in a timeline. A Media Pool comparison concerns the entries and sources in a project bin. If your concern is “I may have imported the same file twice,” use List View and source-path comparison. If your concern is “I may have accidentally used the same portion of footage twice,” inspect the timeline with duplicate-frame indicators. If your concern is disk space, audit the files on storage and distinguish proxies, renders, and camera originals. **Resolve’s duplicate-frame indicators belong to the timeline; they are not a duplicate-file report for the Media Pool.** # ## What if there are no colored bars? No bars means the feature has not marked repeated ranges in the timeline under its detection behavior. It does not prove that the same source clip never appears more than once, and it says nothing about duplicate Media Pool entries. You could use the same source at different, non-overlapping frame ranges. You could also reuse a full clip in a way that does not produce the repeated-frame condition you are trying to detect. Review the edit based on the question you need answered. # ## What if bars appear on an intentional edit? That’s not a fault. The feature reports overlap or reuse, not editorial intent. If the repeated frames create a jump or an unintended repeated moment, adjust the edit. If the repetition is deliberate, leave it alone. If you are delivering a cut to a client or broadcaster, consider whether repeated visual material is a creative choice or an accidental echo. Scrub the marked range in context. A colored indicator is a prompt to inspect, not an instruction to remove. ## How do I check whether a Media Pool entry is used before removing it? Before removing a suspected duplicate, inspect the timeline uses and preserve a copy of the project. A Media Pool entry can look redundant while still carrying a relationship, metadata, or organization you need. There is no safe universal rule that says “keep the top entry” or “delete the newer one.” The correct choice depends on what each entry points to and how the project uses it. # ## What should I check before deletion? Use this checklist: - **Source path:** Does each entry point to the same file or to separate locations? - **Viewer content:** Do they show the same full shot, not just a similar thumbnail? - **Media properties:** Do duration, frame rate, frame dimensions, and audio/video properties agree? - **Clip type:** Is either item a proxy, subclip, still, compound clip, render, or other generated media? - **Metadata:** Does either entry have markers, keywords, notes, or other information you want to keep? - **Timeline use:** Does a timeline use one entry, both entries, or an alternate version? - **Bin organization:** Is the repeated appearance a deliberate way of organizing one asset? - **Project safety:** Have you saved a separate project copy before changing the Media Pool? If one entry has useful metadata and the other does not, consider preserving that information before cleanup. If the project depends on a particular entry, removing another entry may not have the effect you expect. The right procedure is to confirm and test, not assume. # ## Does deleting a Media Pool entry delete the file from disk? Do not infer disk behavior from a bin cleanup. Removing an entry from a project and deleting a stored source file are separate actions with different consequences. Resolve’s menus and prompts can depend on the operation and context. Read any confirmation dialog carefully and stop if you are unsure whether it affects only the project entry or the media on storage. For a duplicate audit, prefer a reversible project-level test. Save another project copy, remove only the verified redundant entry, then reopen the relevant timeline and check for offline media or missing references. Don’t use a cleanup pass as a reason to erase source files unless you have a separate, verified backup and know which file the project needs. # ## How can I make the cleanup reversible? 1. Save the current project. 2. Save a separate copy with a clear working name. 3. Record the candidate entries and their paths before changing anything. 4. Remove one confirmed redundant entry at a time. 5. Check the affected bins and timelines after each change. 6. If anything behaves unexpectedly, return to the saved copy rather than making more changes. This is a cautious workflow, not a guarantee that every project relationship will be obvious. In a collaborative library, a shared project can include other editors’ organization and assumptions. Ask the project owner before removing ambiguous sources. # ## What should I do if both entries are still needed? Keep both, then make their roles obvious. Rename a project-level clip label if that is appropriate for your workflow, organize the entries into clear bins, or add useful metadata. Avoid renaming source files on disk while the project depends on their current paths unless you understand how to relink them. Sometimes an apparent duplicate is a useful alternate. A camera original and an approved transcode may have different roles. A flattened render may be a review reference. A second copy may be the verified backup for a handoff. “Duplicate” is not the same as “unneeded.” # ## What if I want to remove the repeated bin entry but keep the source? Check the menu action and confirmation dialog before proceeding. The wording should make clear whether you are removing an item from the Media Pool or performing an operation on the underlying file. If it is unclear, cancel and consult the current manual. The point of a Media Pool cleanup is usually project organization. Deleting physical media is a storage-management decision, and it should be made only after checking backups, other projects, and the delivery or archive requirements. ## How do I handle common duplicate-looking cases? The safest response depends on what created the match. Camera imports, proxies, copied folders, relink operations, and alternate edits can all create entries that look similar for different reasons. # ## I imported the same folder twice. What now? First compare the source paths. If the entries point to the same media location, determine whether Resolve created another entry or whether you are seeing the same asset through bin organization. Check the bins and preview the candidates. Don’t immediately re-import or delete everything with the same name. If you imported a folder tree twice from two different storage locations, the path comparison will show the distinction. If you truly added the same location again, verify the project entry and timeline references before removing anything. When you find the right organizational fix, consider how the project will be handed off. If another editor expects a bin structure or specific clip labels, preserving that structure may be more valuable than removing every repeated-looking row. # ## I have duplicate camera card folders. Which copy should I keep? Keep the copy that the project uses and that your backup plan identifies as authoritative. Confirm the full path, verify the files, and make sure the other copy is not your only backup before removing or disconnecting it. Resolve’s Media Pool is not a substitute for a verified camera-card backup. Blackmagic describes media cloning and backup as part of the Media page’s workflow. That reinforces a practical distinction: a project bin helps organize references, while a proper backup process protects source files. See [Blackmagic Design’s Media page](https://www.blackmagicdesign.com/products/davinciresolve/media). # ## The duplicate has a different name. Can it still be the same file? Yes. A clip label can be changed independently of the filename shown in storage, and files can be renamed or copied through other tools. Compare the source path and inspect the footage. If you need stronger confirmation that two separate stored files are identical, use a trusted file comparison outside Resolve. Do not expect a name-based search to find every copy. A renamed duplicate will not match the original’s displayed name, even if the content is the same. Conversely, identical names can refer to different files. # ## One entry is offline and another is online. Are they duplicates? Not necessarily. The offline entry may point to a moved file, a disconnected drive, or a source path that no longer resolves. The online entry could be another copy, but it could also be a different take with the same name. Compare path and footage, then decide whether to relink, preserve both, or remove a project entry. If the project is being moved between machines, prefer a deliberate relinking or archive workflow to deleting entries to hide the offline state. The archive guide linked earlier covers preserving project media rather than treating missing links as duplicate cleanup. # ## I see the same shot in more than one bin. Is that a duplicate? Not automatically. A project may organize one source in a way that makes it accessible from more than one context, or there may be separate entries that happen to point at the same source. Check whether the items have the same underlying source path and whether the bin organization is intentional. Keep the distinction between “appears in multiple places” and “is a second copy” clear. A bin is an organizational view. Two rows in different bins do not prove there are two files on disk. # ## I have proxies and originals. Should I remove one? No, not just because they show the same scene. A proxy is intended to stand in for higher-quality source media during editing, while the original may be needed for final output or relinking. Compare their formats and role in the project. Keep the media relationships intact unless you have a specific, verified plan for changing them. A proxy and original can have different paths, dimensions, codecs, or names. Those differences are not evidence of an accidental duplicate. If you are unsure which version Resolve is using, check the project’s proxy and media settings before editing the bin. # ## Several clips have the same duration and thumbnail. Is that enough? No. A thumbnail shows only a small portion of the clip, and identical durations occur naturally. Open both in the viewer and compare their content. If the footage is visually similar, inspect more than one moment, then compare the source path and metadata. A thumbnail is useful for sorting, not for certifying source identity. Two takes of the same action can look nearly identical in one frame and differ elsewhere. ## Can Smart Bins find duplicate clips automatically? Smart Bins can collect clips based on metadata criteria, but that is different from proving that two entries contain identical media. Use a Smart Bin to build a review queue, then verify each candidate before removing it. Blackmagic describes Smart Bins as metadata-driven collections that stay up to date as new footage is added. That behavior makes Smart Bins useful for persistent categories, such as a particular camera, keyword, or metadata value. [Blackmagic Design’s Media page](https://www.blackmagicdesign.com/products/davinciresolve/media) describes Smart Bins and metadata. # ## What can a Smart Bin do well? A Smart Bin can collect entries that share a field or satisfy rules you choose. That helps when your project has reliable metadata, naming conventions, or tags. You can use those criteria to group candidates for human review. For example, **worked example, not an observed test:** suppose a project uses a camera-roll field consistently and you want to review items that share a roll label. A Smart Bin based on that metadata could bring the relevant entries together. You would still need to compare paths, preview the footage, and check timeline uses before deleting anything. If the project’s metadata is blank or inconsistent, the Smart Bin can only act on the information it has. A missing tag does not mean the footage is unique, and matching tags do not prove that two files are copies. # ## Why isn’t a Smart Bin a duplicate detector? Because matching metadata is not the same as matching file content. A Smart Bin can group items using defined criteria; the result depends on those criteria and the quality of the metadata. It cannot establish that two different paths contain byte-identical media merely because they share a label. Treat the Smart Bin as a sorter. It can reduce manual browsing and keep a review group current. The identity check still comes from source paths, media properties, and inspection. For more on the difference between a dynamic metadata collection and an ordinary bin, read [DaVinci Resolve Smart Bin not updating](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-smart-bin-not-updating). The goal in this article is narrower: identify likely duplicates, then verify them safely. # ## Could I tag checked clips as I work? Yes, if the project’s workflow supports it. A temporary keyword or color label can help you track which candidates you’ve inspected. Choose a label that does not conflict with the team’s existing conventions, and remove or repurpose it once the audit is done. Don’t mark an item “duplicate” before verifying it. Use a neutral temporary status such as “reviewed” or “check path,” then record your decision separately. That way, a partial audit does not leave misleading metadata behind. # ## What if metadata is wrong or missing? Fall back to direct checks. Compare the path, preview the footage, and inspect the available media properties. If the sources are on different drives or have been moved, resolve the path question before you try to tidy the bin. Missing metadata is normal in some projects. The answer is not to invent certainty from a thumbnail. It is to use the evidence that is available and preserve ambiguous entries until you can verify them. ## Does Resolve 21.1 change how I should look for duplicates? DaVinci Resolve 21.1 is the current release as of October 2026, but its new assistant integration should not be mistaken for an automatic guarantee that duplicate entries have been identified safely. The core manual workflow remains: narrow the candidates, verify the sources, and inspect project use. Blackmagic announced Resolve 21.1 on September 8, 2026. The announcement says assistant integrations can help users analyze projects, organize media, adjust settings, and batch render using conversational language. It does not say that an assistant automatically proves two Media Pool entries are identical or safe to remove. [Blackmagic Design’s 21.1 announcement](https://www.blackmagicdesign.com/media/partial/release/20260908-03) describes the new integration. For exact menu labels, check the manual for the version you have installed. Blackmagic lists the DaVinci Resolve 21.1 manual on its [official manual page](https://www.blackmagicdesign.com/welcome/en/W-DRE-03). If a control appears in a different location, use the manual and the application’s own menus rather than applying instructions for an older version blindly. The distinction between project entries, source files, and timeline repeats remains useful regardless of the release. If an assistant or a Smart Bin suggests candidates, treat those results as a starting point. Confirm the source and preserve a project copy before making changes. ## What does an experienced editor say about organizing footage? Editor Cesar Esparza described using Resolve to organize and tag footage while working on the documentary *Life on Waves*. In an article reporting on that project, Esparza said: “DaVinci Resolve Studio streamlined my workflow for ‘Life on Waves’ from start to finish by allowing me to efficiently organize and tag footage.” The quote is about media organization, not a claim that Resolve automatically detects duplicate files. [The published article](https://creativecow.net/life-on-waves-posted-with-davinci-resolve-studio/) attributes the statement to Esparza. That distinction fits this cleanup task. Tags and metadata make footage easier to organize and find. They do not replace a source-identity check. The editor still has to decide whether similar entries are redundant, useful alternates, proxies, separate takes, or intentional project organization. ## What is the safest duplicate-cleanup workflow? The safest workflow is a small, reversible audit: define the type of duplicate, compare likely candidates, inspect timeline use, save a separate project copy, and remove only entries you have verified as unnecessary. # ## Step 1: Define the cleanup goal Write down what you are trying to fix: - **Bin clutter:** find repeated-looking Media Pool entries. - **Timeline repetition:** find repeated frame ranges or repeated source use. - **Storage space:** locate redundant files on disk. - **Handoff confusion:** distinguish originals, proxies, renders, and alternates. - **Project recovery:** resolve offline or moved sources. One cleanup goal can expose another problem, but don’t treat them as the same task. For example, removing a repeated bin entry may not free any disk space if both entries pointed to the same file. Likewise, deleting a file from storage does not necessarily remove its project reference. # ## Step 2: Work in a specific scope Select the bin or group of bins that belong to your audit. Avoid searching the entire project until you understand how your current search is scoped. If results seem incomplete, verify which bins and fields are included before importing more footage or changing names. For large projects, break the review into sensible groups such as camera, shoot day, project section, or media type. This makes it easier to preserve context and to pause without losing track of what has been checked. # ## Step 3: Build a candidate list Use List View and sort by a field that brings possible matches together. Search by a filename fragment if names are meaningful. If you have consistent metadata, use it to narrow the group. Do not make a deletion list based only on matching names. Record the paths and any important differences you notice. If the candidate list contains an original, proxy, transcode, render, or subclip, mark that distinction before deciding what to keep. # ## Step 4: Confirm each candidate For each pair or group, compare the full source path, preview the footage, and check relevant media properties. Ask: - Does the entry refer to the same source location? - Does the footage match beyond a single thumbnail? - Do duration and media properties agree? - Is either clip a proxy, transcode, or derived item? - Are there separate markers or metadata worth preserving? - Does the timeline use one entry differently from the other? If you cannot answer these questions, keep both entries for now. A tidy bin is not worth losing a source relationship you need. # ## Step 5: Check timeline use Open the relevant timeline or timelines. If the issue is repeated source frames, use the duplicate-frame indicators. If the concern is that two entries are used independently, inspect the timeline clips and their source relationships. Do not assume that an entry is unused because it is not visible in the current timeline. Projects can have multiple timelines, alternate cuts, or other sequences. Check the scope of the work before removing a source. # ## Step 6: Save a separate project copy Save a distinct working copy before changing ambiguous project items. Give it a name that makes the purpose clear, such as a cleanup version, rather than overwriting the only copy you have. For team projects, coordinate before removing or renaming entries. A teammate may be using a bin, marker, or source relationship that is not obvious from your current view. # ## Step 7: Remove one confirmed entry at a time Use the appropriate Media Pool action only after reading the menu wording and confirmation dialog. If the dialog suggests a disk operation you did not intend, cancel. Remove one item, then recheck the relevant bin and timelines before continuing. This method is slower than selecting every similar-looking entry and deleting them all. It is also easier to reverse and less likely to create a confusing project state. # ## Step 8: Check the result After cleanup, verify that the intended timeline still plays and that the kept source behaves as expected. Check for offline media, missing references, or lost metadata. If something changes unexpectedly, return to the saved project copy and reassess the evidence. A good result is not simply a shorter list. It is a project where the remaining entries are understood and usable. If you’re stuck on a particular control while following this process, TryUncle is the on-screen assistant for DaVinci Resolve on Mac and Windows; ask in plain words and Uncle points at the exact control on your screen. [TryUncle](https://tryuncle.com/) offers that kind of guidance while you work, but you remain responsible for checking the source and deciding whether an entry is safe to remove. ## What should I do if Resolve keeps showing the same candidate? If the same candidate keeps reappearing in your search or Smart Bin, inspect the criteria and the bins included in the view before deleting it. A repeated result can be caused by how the project is organized, not by a second copy of the file. Check whether the item appears in different bins, whether the search scope includes several bins, and whether your Smart Bin rule matches a broad metadata value. If the same source is intentionally accessible from more than one organizational context, it may look repetitive without representing a duplicate file. Also check whether you are comparing a clip entry with a related timeline or generated item. A Media Pool can contain several kinds of project objects, and a common label does not make their roles identical. ## What should I do if I cannot confirm which entry is safe to remove? Keep both until you can confirm. Preserve the project copy, note the paths, and ask the project owner or editor who knows the media history if necessary. An unresolved candidate is not a failure. It is a signal that the evidence is incomplete. If one entry is offline or the files live on disconnected storage, reconnect the right media or consult the archive before making a permanent choice. For projects that need to move between drives or editors, prioritize relinking and archiving correctly. A duplicate cleanup should not become an improvised media migration. The [project archiving guide](https://tryuncle.com/learn/davinci-resolve/how-to-archive-a-davinci-resolve-project-without-losing-media) explains that separate handoff problem. ## Which result should I expect after cleanup? After a careful cleanup, the bin should be easier to read, the remaining entries should have clear roles, and the relevant timeline should still reference working media. You may not end with fewer entries if some apparent duplicates turn out to be useful alternates or separate files. That is a valid result. The goal is not to remove every repeated name. The goal is to remove only what you have verified as redundant and preserve the sources the project needs. When the candidates are ambiguous, keep them and improve the labels or organization instead. When the evidence is clear, make a reversible change and check the project afterward. That is the safer way to find duplicate clips in the DaVinci Resolve Media Pool. ## FAQ ### Does DaVinci Resolve have a button to find duplicate clips in the Media Pool? Resolve’s Media Pool search and metadata tools help you find and compare clips, but they do not establish that two entries are the same source file just because their names match. Compare the full source path and relevant media properties before removing an entry. ### How do I find duplicate frames in a DaVinci Resolve timeline? Open the timeline, then choose View > Show Duplicate Frames. Resolve marks ranges of frames that appear more than once in that timeline. This checks timeline frame reuse, not duplicate entries in the Media Pool. ### Can I delete one duplicate Media Pool clip without deleting the other? You can remove an entry from the Media Pool, but first check whether any timeline clips depend on that particular source entry. Duplicate source entries can be treated separately by Resolve, so matching filenames do not prove that deleting either entry is harmless. ### Why do two DaVinci Resolve clips have the same name but different paths? The files may be separate copies, camera files from different folders, or versions that share a filename. Compare their paths, duration, frame rate, and content before deciding whether they are redundant. ### Does DaVinci Resolve 21.1 automatically remove duplicate clips? DaVinci Resolve 21.1 adds AI assistant integration for tasks including media organization, but you should still verify any proposed change in your own project. Do not treat similar names or thumbnails as proof that two entries are safe to remove. ## Sources - [DaVinci Resolve 21.1 Manual and product support](https://www.blackmagicdesign.com/welcome/en/W-DRE-03) - [DaVinci Resolve 21.1 release announcement](https://www.blackmagicdesign.com/media/partial/release/20260908-03) - [DaVinci Resolve Media page: bins, Smart Bins, and metadata](https://www.blackmagicdesign.com/products/davinciresolve/media) - [DaVinci Resolve 12 Reference Manual](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_12_Reference_Manual.pdf?_v=1488443189000) - [DaVinci Resolve 10 Reference Manual: flags and shared Media Pool sources](https://documents.blackmagicdesign.com/UserManuals/DaVinci_Resolve_10_Reference_Manual.pdf) - [Life on Waves posted with DaVinci Resolve Studio](https://creativecow.net/life-on-waves-posted-with-davinci-resolve-studio/) - [Blackmagic Design Support Center](https://www.blackmagicdesign.com/support)