Answer: Preserve the project, locate the intended originals and verify more than the filename. Duration, recording identity, timecode and a visible content check help avoid relinking a similarly named file.
On this page
Creator Edit Lab editorial project · Updated October 21, 2026 · Original decision framework and illustrative example. No physical product measurement or hands-on benchmark is claimed.
Why the distinction matters
Cameras can reuse short filenames across cards. Flattening folders or renaming originals can therefore create plausible-looking collisions. Work from a preserved card or acquisition structure where possible. Keep originals, proxies and exports in identifiable locations. Do not rename or move the only copy as an experiment to make the application’s relink dialog accept it.
A practical sequence
- Save a separate project version and record the missing file references.
- Locate the original card or acquisition folder and compare identity fields.
- Use the editor’s supported relink route with a small group first.
- Inspect the relinked image and audio at known edit points before applying broad matches.
Decision record
| Check | What it means | What to verify |
|---|---|---|
| Filename | Potentially repeated across cards | Insufficient alone |
| Identity | Card, duration, timecode or metadata | Cross-check the source |
| Content | Expected shot and audio | Verify the actual edit |
Worked example
Two hypothetical cards both contain C0001.mp4. A filename-only match can attach an interview to a landscape shot with the same name. Keeping card IDs in separate folders and checking known content exposes the wrong match before the final export.
Verify the result
Keep the prior project and relink notes until the reopened project and delivery are checked. If an original remains missing, label the limitation rather than silently substituting a proxy or another take.
Download the editable CSV worksheet · Delivery workbook
Question and answer
Should I rename every camera clip before relinking? Preserve the source structure and use a planned ingest convention. Renaming the only originals during recovery can create more unresolved references.
Sources and scope
- Adobe Premiere: export proxies — Export source selection in Premiere; our checklists are proposed verification procedures.
- Blackmagic Design: support and manuals — Locate the manual matching your Resolve release and edition.
The decision sequence, diagrams, worksheet and worked case are our editorial work. AI assisted research, drafting and implementation. Official references support the named technical distinctions; examples do not establish real product performance.
Continue the task
- A project folder structure that survives handoff
- Check that a proxy matches its original before editing
- Browse the complete resource library
Build on what you just learned
Your next useful step.
Organize, relink and restore with confidence.
Upgrade to Resolve 21 with a project-copy acceptance test
I would upgrade a working editing system only after preserving a recoverable project library and testing a representative project copy.
Read the guide →
Resolve 21 IntelliSearch: budget the analysis before relying on search
I would test IntelliSearch on a representative media subset and keep a conventional folder and logging system alongside it.
Read the guide →
