← Part of: the AAF Everything guide
Final Cut ⇄ DaVinci Resolve

Final Cut Pro to DaVinci Resolve — and back.

Resolve reads and writes AAF on both its edit and Fairlight side. Final Cut writes FCPXML. The conversion goes both ways.

Short answer: In Final Cut Pro, open Window ▸ Extensions ▸ AAF Everything and send the timeline straight to AAF. Or export File → Export XML from Final Cut Pro and convert it to .aaf for Resolve. In the other direction a Resolve AAF converts to .fcpxml or the .fcpxmld bundle — and Resolve’s MXF-wrapped audio becomes WAV automatically, because Final Cut does not read MXF from an XML reliably.

Two applications, no shared format

Resolve imports AAF into the edit page and into Fairlight, and exports one from the Deliver page. It does not read FCPXML from Final Cut Pro, and Final Cut has no AAF import of its own. The AAF carries the timeline between them.

Resolve is also the source of most AAFs that turn up in a Final Cut suite — a locked cut coming from the online, or a Fairlight session coming back from the mix. That leg is AAF back into Final Cut.

Final Cut to Resolve, step by step

The direct way: in Final Cut Pro open Window ▸ Extensions ▸ AAF Everything, choose AAF and export. The workflow extension writes the AAF from the current timeline. It is the same conversion as the app, without exporting XML by hand. The steps below take the route through the app.
  1. Export the XML from Final Cut Pro

    File → Export XML. A single .fcpxml or the .fcpxmld bundle — drop either one in.

  2. Convert to .aaf

    Drop the file in and pick .aaf. Resolve reads interleaved stereo, so the Channels options can stay off unless you specifically want per-channel files.

  3. Decide about the media

    Link to original media is fine when both machines see the same storage; Collect next to output gives you a movable package. MXF-wrapped audio can stay untouched here — switch the transcode off and Resolve reads the originals natively.

  4. Import in Resolve

    File → Import → Timeline and pick the AAF — on the edit page or on the Fairlight side. The report next to the output names what could not travel.

  5. Coming back: a Resolve AAF into Final Cut

    Export from Resolve — Deliver page with the Pro Tools preset, or File → Export → AAF — and convert to .fcpxml or the .fcpxmld bundle. Leave the MXF transcode on for this leg: Final Cut does not read MXF audio from an XML reliably.

Resolve’s split stereo: Resolve often delivers a stereo pair as two mono tracks (_A01 / _A02). Switch on Combine split stereo tracks and the converter proposes the pairs it recognises, with a review window before anything is written — see split-stereo & channels.
Speed changes and video dissolves: audio speed changes are rendered only when Separate combined channels is on. Without it, the AAF points to your original recordings and the report lists every retimed clip with its position, so you can rebuild the speed in Resolve. With it on, the audio of constant speed changes is rendered at the speed Final Cut plays it; speed ramps never are. A video cross dissolve is not carried, and picture after it can slip by the length of the dissolve: render or consolidate it in Final Cut before you export.

What travels — and what does not

Pan is written into the AAF as track pan when every clip on a track has the same value in Final Cut, but Resolve ignores pan on AAF import. Where the values differ, nothing is averaged and the report names the track. On the way back into Final Cut, no pan is written. Markers are written into the AAF, but Resolve ignores AAF markers, so do not count on seeing them there. Track and clip colours ride in a private AAF comment that only this converter reads back.

We open the AAFs we write in Resolve ourselves. AAF dialects differ, so convert one reel with the demo and open it on your own system before a delivery depends on it.

FAQ

Should I let MXF audio transcode?

Going to Resolve, no — it reads MXF natively, so reference as-is keeps your originals untouched. Coming from Resolve into Final Cut, yes: Final Cut does not read MXF audio from an XML reliably.

Resolve gave me _A01 and _A02 tracks.

That is how Resolve writes a split stereo pair. Switch on Combine split stereo tracks and confirm the pairing in the review window before converting.

Do my markers show up in Resolve?

They are written into the AAF, but Resolve ignores AAF markers. Do not plan a workflow around them on this route.

Can I go Resolve to Premiere instead?

Yes — an AAF from Resolve converts to Premiere XML the same way. Note that Premiere XML is a delivery format, not a source: coming from Premiere, use Premiere’s own AAF export.

Try it on your own timeline first.

The demo is the complete app with unlimited conversions — each output covers the first 120 seconds with the full track layout. If your file converts the way you need, buy a license.

Download the free demo Buy — $79