DaVinci Resolve Media Management: Consolidate, Trim and Archive

Quick answer: use File → Media Management when you need a portable copy of the media behind a project, selected timelines or selected clips. Pick Copy when you want to keep the source files as they are, and Transcode only when the handoff or archive actually calls for a new codec. If storage is tight, collect used media or trim it with handles, but keep the original drives until a second project opens and plays correctly from the managed folder alone.

That last step is what makes the package trustworthy. A finished copy job proves Resolve wrote files to a destination, and not much more. Blackmagic's manual even notes that Resolve now skips files that throw errors and carries on with the rest of the job, so "done" can still hide gaps. It doesn't prove that every still, audio recording, nested timeline, title, LUT or odd source clip can be restored from that folder.

What Media Management Does

Resolve uses the phrase media management in two related ways. The Media page is the workspace for importing, organizing, syncing and inspecting footage, and Blackmagic's Media page overview also covers metadata, camera-media cloning and backup tools there.

The Media Management window under the File menu does a narrower job: it builds a new media set for the whole project, one or more timelines, or selected clips. Depending on the source and your settings, it copies full files, collects only used media, trims clips down to handles, or transcodes the lot. This walkthrough of the Media Management window shows those scope and operation choices in context.

It isn't a project backup. A DRP or Project Library backup protects edit decisions, grades, timelines and project metadata; the managed folder protects the files those decisions point to. If project recovery is what you're really after, start with the DaVinci Resolve project backup guide and treat Media Management as the media half of the package.

Decide What the Package Is For

Don't open the Media Management window until you can finish this sentence:

This package must let someone complete a defined task without access to my source drive.

Your answer changes which settings are safe.

• A color or sound handoff usually needs the locked timelines, the media they use, enough handles for transitions and small revisions, and a written list of external dependencies.
• An active project transfer needs more room for editorial changes. Full source clips or generous handles are usually safer than a tightly trimmed set.
• A long-term archive needs a restorable project, durable media, documentation and a second physical copy. The smallest possible folder isn't the only goal.
• A temporary space-saving copy can be narrower, but it should never become the only surviving media set until it passes the same restore test.

Defining the job up front heads off a classic mismatch: building a tiny finishing package and then expecting it to carry a future re-edit.

Choose the Scope: Project, Timelines or Clips

Media Management works at three levels, picked at the top of the window. Use the narrowest scope that still owns the work you have to preserve. Whatever you had selected before opening the window decides which scope is highlighted, so glance at it before you change anything else.

Project

Choose Entire Project when several timelines, shared source clips or alternate versions belong together. It's the safer call when you're not sure which timeline is the final one, or when a clip used in one sequence may be needed in another. A project-level job also writes a .drp file next to the managed media, already linked to it, which you can import as a new project.

The cost is volume. A project-level collection can drag in media that a single delivery timeline never touches, especially when bins hold selects, alternate edits or abandoned versions.

Timelines

Choose selected timelines for a locked cut, a color handoff or a delivery-specific archive. It keeps the collection focused without making you pick hundreds of clips by hand, and Resolve writes a matching .drt timeline file alongside the media.

Before you run it, make sure the timelines you ticked are the versions you actually mean to keep. Duplicates named Final, Final 2 and Final Approved are an archive problem, not a Media Management setting.

Clips

Choose selected clips when the job really is clip-specific: moving a small group of shots, collecting VFX pulls or isolating media for another project. It's precise, but it puts the burden on you to prove nothing else is needed.

If the package has to reproduce a timeline, timeline scope is usually easier to audit than a hand-picked clip list.

Choose Copy or Transcode

This choice decides whether the managed set keeps the original media essence or creates new files.

Use Copy When Source Fidelity Matters

Copy is my default for an archive or a transfer whenever the destination can use the original formats. It doesn't add a new generation, and it keeps the source files' native codec and container where the requested operation is supported.

Copy is also easier to explain later: the managed folder holds copied source media, not a new mezzanine interpretation someone picked during cleanup.

That doesn't mean every format trims exactly as requested. The manual says trimming now works with temporally compressed camera codecs such as XAVC and AVC-Intra without recompressing, but behavior still depends on the format and clip type, so check what Resolve actually writes before you assume every copied file got cut down to the used range.

Use Transcode for a Defined Delivery Requirement

Transcode creates new media. Use it when the receiving system needs a common finishing codec, when the original format doesn't suit the workflow, or when a controlled mezzanine set is part of the handoff spec.

Before you commit, pin these down in writing:

• codec and container;
• resolution and frame rate;
• bit depth and chroma sampling;
• how source timecode is handled;
• audio channel layout;
• alpha-channel requirements;
• whether camera RAW controls have to stay available.

A transcode can play perfectly and still be wrong for finishing. Reduced bit depth, a missing alpha, collapsed audio channels or lost RAW flexibility will sail through a casual playback check and then fail the real handoff.

Choose Full Files, Used Media or Trimmed Media

The next decision controls how much source range survives.

Full Source Files

Full files are the least compact option and the easiest to reason about, because every frame of each collected clip stays. Pick them when editors may change the cut substantially, when a source format doesn't trim reliably, or when nobody knows yet what the project will be used for.

Used Media Without Aggressive Trimming

A used-media collection leaves behind clips that aren't part of the selected scope and copies the clips that are in their entirety. That often saves a useful amount of space without shortening a single file.

It's a good middle ground for active transfers: unrelated footage stays home, and the collected clips keep their complete source range.

Trimmed Media With Handles

Trimmed media keeps the portions the edit uses plus extra frames before and after each use. This finishing workflow example shows why editors reach for it on compact handoffs, but its handle count and storage numbers belong to that one project. They aren't universal settings. If several timeline clips come from the same source file, the Consolidate multiple edit segments into one media file option writes one file per source, frames in between included, which costs space but keeps each clip's relationship to its original file.

Pick handles from the edit, not from habit. Ask what might need frames outside the visible cut:

• dissolves and other transitions;
• speed changes and reverse playback;
• stabilization or reframing that can expose other parts of the source;
• optical-flow work;
• VFX pulls and replacement shots;
• likely editorial revisions;
• source clips reused inside nested, compound or multicam structures.

If you can't explain why a handle length is safe, make it longer or keep full clips. Storage is cheaper than rebuilding an archive around missing frames.

Keep the Destination Readable

Make a new, empty destination folder for every managed package. Don't mix it with camera originals, proxies, cache files or an older collection. A clean root might hold:

• the managed media folder;
• the matching DRP or timeline export (Resolve writes a .drp or .drt next to the media for you);
• a plain-text manifest;
• LUTs, DCTLs, fonts and other dependencies you packaged on purpose;
• a small verification render, if one helps with comparison.

Tie the package name to the project and the date. Write down the Resolve version, the selected timelines, Copy or Transcode, the handle policy and any exceptions.

Watch duplicate file names closely. Two camera cards can both contain C0001, and separate audio recorders repeat names across shoot days. Resolve's Preserve folder hierarchy option can keep part of the original folder structure, and the manual explains that trimmed segments from one source get extra characters added to their names so they don't overwrite each other. An official Blackmagic forum discussion about Media Management still includes reports of duplicate-name, timecode and folder-structure surprises. They don't prove every project will fail, but they hand you exact conditions to test before you trust a flattened or reorganized folder.

Audit Dependencies That Are Easy to Miss

Media Management mainly collects media, and a portable project can depend on a lot more than ordinary camera files.

Go through this list before the copy:

• separately recorded audio and manually synced clips;
• still images and image sequences;
• nested, compound and multicam timelines;
• retimes, freeze frames and reverse clips;
• Fusion compositions, generated elements and rendered VFX;
• titles, subtitle files and caption data;
• installed fonts and third-party effects;
• LUTs and DCTLs stored outside the project;
• graphics that need an alpha channel;
• multichannel or polyphonic audio;
• proxies, render cache and gallery stills if the next workstation is expected to use them, and optimized media, which the manual says Media Management doesn't include at all.

Some of these are project data, some are external files, and some need to be rendered because the receiving workstation lacks the same plugin or font. Don't assume Media Management packages all of them. List them, decide who owns each dependency, and check the result on the receiving side.

For collaboration built around Blackmagic Cloud and proxies, follow the separate Cloud collaboration media handoff workflow. Media Management works best as a deliberate collection and archive tool, not as a stand-in for every shared-media strategy.

Run Media Management

Once the scope and package rules are settled:

1. Save the project and make a restorable project or timeline backup.
2. Open File → Media Management.
3. Select the scope you intend: Project, Timelines or Clips.
4. Choose Copy or Transcode.
5. Choose full, used or trimmed media and set handles where they apply.
6. Select the new, empty destination folder, and decide on Relink to new files: with Copy it relinks the selected clips or timelines in the current project to the new media, which is handy but means the project you're in stops pointing at the originals.
7. Look at the estimated size, but treat it as planning information, not proof.
8. Click Start and keep the originals once the job completes.

This Media Management overview from DVResolve sums up the durable idea well: collect a lean media set for the work you need to keep. Its comments also include a report of trimmed RED media reopening with sync and handle problems. One report can't define current behavior for every R3D project, but it's a good reminder to test the exact source mix you have.

Prove the Managed Package Can Restore

This is the acceptance test.

1. Duplicate the project, or import the backup meant for the managed package.
2. Point that copy at the managed media root and nothing else.
3. Temporarily unmount the original source drive, or rename its root folder, so Resolve can't fall back to it.
4. Reopen the project.
5. Confirm the expected clips are online.
6. Check the difficult sections, not just the opening shot.
7. Render representative stretches with proxies and render cache turned off when the managed source files are what you're verifying.

Check the first and last frames around cuts, transitions and speed effects. Open the multicam, compound and nested timelines. Listen to clips with separate or multichannel audio. Look at stills, image sequences, graphics with alpha and any shot that depends on RAW controls.

Compare the properties the next stage cares about: resolution, frame rate, timecode, audio channels and codec. If you transcoded, confirm the new files meet the written handoff spec.

Only after this test does the package earn the word portable. Leave the source drive alone until the archive exists in at least two places.

Troubleshooting by Symptom

The Managed Folder Is Much Larger Than Expected

Some source files may have been copied in full because the requested trim wasn't available for that format or clip type, and the Consolidate multiple edit segments option deliberately keeps the frames between uses. Find out which files dominate the folder before you rerun the job. If a compact size really matters, weigh a controlled transcode against the finishing requirements; don't switch codecs blindly.

Clips Are Offline When the Original Drive Is Disconnected

First confirm the managed files exist and the duplicate project is linked to the new root. Then use the Media Offline troubleshooting guide to tell a path problem apart from a codec, permission, mount or metadata problem.

Don't reconnect the source drive until you understand the failure. Plugging it back in can make the project look healthy by quietly restoring the old paths.

The Wrong Clip Relinks

Look for duplicate base names, overlapping timecode and media copied from several cards into a flattened folder structure. Compare reel names, source paths and clip metadata. A wrong relink that succeeds is more dangerous than an obvious offline clip, because it can slip through to export.

Audio Is Missing or Out of Sync

Check whether separately recorded audio came along, whether synced or multicam structures still point to the intended files, and whether a transcode kept the channel layout and timecode. Look at several points in long clips; checking only the first frame can miss drift or problems at a trimmed boundary.

Titles, Fusion Work or Effects Look Different

Confirm fonts, plugins, LUTs, DCTLs and external assets on the destination system. If the setup can't be reproduced there, render the element or supply an agreed interchange version, and keep the editable original in the archive even when a flattened render goes out with the handoff.

The Copy Finished, but Some Clip Attributes Changed

Compare a representative original clip with its managed counterpart. Check framing, transform-sensitive metadata, clip speed, audio interpretation and source properties. Community reports show that unusual formats and clip attributes deserve a direct look; they don't support a blanket rule that one codec or workflow always fails.

Archive and Handoff Checklist

Before you delete, return or shelve any source drive, confirm:

• the package has a clear purpose: handoff, transfer or archive;
• the right project, timelines or clips were selected;
• Copy or Transcode matches what happens downstream;
• handle length covers transitions, retimes and expected revisions;
• stills, image sequences and external audio are all there;
• nested, compound and multicam timelines were checked;
• fonts, plugins, LUTs, DCTLs and other external dependencies are documented;
• the duplicate project opens with the original source drive unavailable;
• representative difficult sections render from the managed media;
• the package includes a project backup and a short manifest;
• at least two copies exist before any original is removed.

Media Management earns its keep when it shrinks a project down to the media that matters without hiding what got left behind. Build the smallest package that still does its declared job, then try to break it while the originals are safe. That restore test is what turns a copied folder into an archive you can trust.

Jason Miller I run DaVinci Resolve Club as an independent publication: hands-on edits, color grading breakdowns, Fairlight sessions, Fusion tests, and honest notes on where Resolve gets in the way.