Answer: Preserve the required project, sources and approved deliverables with a manifest that explains dependencies and recovery status. A folder full of exports is not a complete editable archive.
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
An archive should answer what was approved, what can be regenerated and what is needed to reopen the edit. Distinguish original media from proxies and rebuildable cache. Include application version and important fonts or plugins according to their licenses. Keep private client data out of a public manifest; the archive can remain local or in an authorized storage service.
A practical sequence
- Identify the approved deliverable by exact filename, duration and version.
- List project data, originals and unique linked assets required for reopening.
- Mark proxies and cache as generated artifacts with their recreation method.
- Test a separate restored copy and record any missing dependencies before releasing working space.
Decision record
| Check | What it means | What to verify |
|---|---|---|
| Approved output | Exact file and status | Delivery reference |
| Editable archive | Project and dependencies | Reopening goal |
| Generated artifacts | Proxy/cache scope | Rebuild decision |
Worked example
A hypothetical archive contains final.mp4 and proxy clips but omits the camera originals and project database export. It preserves a viewing copy but not the promised editable project. The manifest should describe that actual scope rather than call it a complete archive.
Verify the result
Keep at least one verified recovery route before planned cleanup. Check stored artifacts after transfer using an appropriate local integrity workflow. A matching file count alone does not establish matching content or a working project.
Download the editable CSV worksheet · Delivery workbook
Question and answer
Should cache always be archived? Decide from the recovery goal and regeneration cost. Keep the source dependencies and document whether cache is included or intentionally rebuildable.
Sources and scope
- Blackmagic Design: support and manuals — Locate the manual matching your Resolve release and edition.
- Adobe Premiere: export proxies — Export source selection in Premiere; our checklists are proposed verification procedures.
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
- DaVinci Resolve proxy media vs optimized media vs render cache
- Inspect an exported video before sending it
- 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 →
