DaVinci Resolve DRP versus a media archive

Distinguish a project file from the recordings it references

Blackmagic’s Resolve 20 beginner and editor training identifies DRP as a project-information file without the audio and video media. The sender’s project can open and show organization while still relying on source recordings stored elsewhere.

Clarify whether the recipient needs an editable project, a playable finished movie or both. A rendered export can serve viewing while omitting clip choices, source references and other editable decisions. Conversely, a small project file cannot substitute for the actual movie when the recipient only needs playback.

Identify the media scope before delivery. A selected cut, unused interview material and production sources are different handoff requirements. Keep authorized source context and useful version notes so a recipient can distinguish the intended footage from another clip with the same name.

Use the documented archive workflow where it fits

Blackmagic’s Resolve 20 colorist guide describes Project Manager → the project thumbnail’s contextual menu → Export Project Archive. Its training explains consolidation of the project, timelines and media into one folder for sharing or retrieval.

Follow the installed version’s current archive dialog and read what media is selected. Do not infer that every cache, proxy, unused recording or external resource is included solely from the archive command’s name. Compare the requested handoff scope with what the operation actually collects.

Choose a destination that preserves the working project and source files. Complete the operation and review any errors before reporting success. A progress bar reaching its end is useful process evidence, but the receiving edit still requires verification.

Keep the DRA directory intact at its intended location

Treat a DRA archive as a directory with contained resources, not a single rendered movie to play or a suffix to append to a DRP. Copy the intact directory through an appropriate storage handoff and preserve its structure while verifying delivery.

Place it at the intended receiving storage location before the recipient checks the edit. A project opened while the sender’s original source drive remains available can conceal missing transferred media. Use a controlled verification that preserves originals rather than deleting sources to prove independence.

Inspect capacity and actual transfer completion. If the archive arrives inside a ZIP or other transport package, extract it to the intended location before the native restore workflow. A transport archive and Resolve’s project archive have different roles.

Restore the archive through Project Manager

The Resolve 20 colorist training describes Restore Project Archive in Project Manager, selecting the DRA resource, then opening the restored project. Use the supported receiving procedure instead of importing a finished movie and calling that an editable-project restore.

Check that the expected project and timelines appear. Confirm their media references identify the supplied recordings and usable representations. A low-demand proxy can make review smooth while leaving a required full-resolution source absent; keep that role explicit.

If media is offline or the wrong clip appears, identify the particular source and version before substituting another file. Preserve the archive while resolving that issue through the editor’s maintained guidance. A matching basename alone is insufficient identity evidence.

Check external dependencies and the recipient’s edit

Review resources the project needs beyond ordinary video bytes, such as captions, graphics, plug-ins or relevant color interpretation information. Do not promise the archive automatically supplies or licenses every dependency. Check what the recipient actually needs to render the agreed result.

Play distinctive moments in the required timelines and review meaningful transitions, sound and titles. Test a representative output when delivery rendering matters. A project opening without an immediate warning is weaker evidence than the recipient successfully using the intended media and edit.

Record included, separately supplied and unresolved resources in a concise handoff note. Keep account credentials and private provider tokens out of it. The recipient needs retained assets and authorized access, not an expiring source address described as permanent media.

Keep a checked handoff separate from the broader archive

A verified project package serves its agreed editing scope. It can still differ from the complete production archive, earlier versions or an independent disaster-recovery backup. Preserve those separately when needed and use the existing restore-test guide for recovery evidence.

Keep the source until the recipient confirms the actual task. Label the project package and finished viewing export separately. If a dependency remains unresolved, state it rather than presenting the archive as universally self-contained.

SocialVidDownloader can supply supported authorized media as an editing input. It does not export Resolve projects, create DRA directories or reconstruct editable state from a movie. This guide uses versioned Resolve 20 documentation and does not claim a native editor account or project transfer was manually tested here.

Worked example

Illustrative handoff: a sender supplies a DRP, but the recipient sees offline clips because the original recordings are on the sender’s drive. They agree on the required media scope, prepare and transfer an intact supported archive, then restore and test the selected timelines at the receiving location. A finished review movie remains a separate artifact.

Related guidance

• Collect Premiere project media for an authorized handoff
• Copy a Final Cut library with the media the recipient needs
• Clipchamp project saving versus retaining its media and export

Sources and verification

• Blackmagic: Resolve 20 beginner guide and DRP media boundary
• Blackmagic: Resolve 20 colorist guide and DRA restore workflow

Reviewed 2026-10-08. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.