FCP XML vs. AAF vs. EDL.

A locked cut isn't ready to leave editorial. It is bound to the Premiere Pro project that produced it, its sequences, its effects, its render cache. To carry that work cleanly into a colorist's DaVinci Resolve, a mixer's Pro Tools or an online editor's Avid Media Composer, you need a translation layer. That layer is an interchange file.

FCP XML, AAF and EDL are the three interchange formats in common use for handoff. They are not interchangeable. Each one preserves a different slice of the timeline, and each is the right format for a different downstream tool. Picking the wrong one is a common way a handoff arrives incomplete.

What each format carries

At a high level, an interchange file is a text description of your timeline. It does not contain the footage. Instead, it points at the media on your storage and tells the receiving application: place this clip here, with this in-point and this out-point, on this track. The differences between formats are about what gets preserved beyond that basic structure.

FCP XML is a plain-text XML file. It supports multiple video and audio tracks, transitions, motion (position, scale, rotation), time remapping and clip metadata, the richest of the three in terms of editorial structure. AAF is a binary multimedia container that, unlike FCP XML, can embed the audio media inside the file itself. EDL is the oldest and simplest: one event per line, a single video track, no effects.

FCP XML, strengths and limits

Reach for FCP XML when video is the priority and you are sending the cut to a tool that speaks it, most importantly DaVinci Resolve. Resolve's XML importer is reliable and preserves the editorial structure faithfully enough that a colorist can grade your cut and trust it lines up.

What FCP XML does not handle well is Premiere-specific effects. Plugin transitions, Premiere's own Lumetri grades and many warp/stabilization effects will not translate. The accepted practice is to flatten the timeline first, bake in only what needs to survive, strip out what doesn't, before exporting the XML.

AAF, when audio is the priority

AAF is the format audio post expects. A Pro Tools mixer importing your project wants AAF, not XML, because AAF carries audio cleanly and can embed the audio media inside the file. It is also the format of choice if any part of your pipeline involves Avid Media Composer.

Premiere's AAF export gives you two important choices. The first is embedded versus linked media: embedded is safer for handoff because nothing can go missing on the way to the mix stage. The second is frame handles, extra frames before and after each clip. More handles means more flexibility for the mixer to slide edits and crossfade audio without coming back to you.

EDL, the simplest of the three

An EDL is plain text, one cut per line, a single video track. It strips out almost everything: transitions, effects, multi-track structure, audio sync. It survives because some legacy systems read only EDL, and because when everything else fails you can open one in a text editor and see exactly what is there.

Reach for EDL when your destination explicitly asks for one, or as a fallback reference when an XML or AAF refuses to import cleanly somewhere downstream.

Which format for which destination

As a working rule:

• DaVinci Resolve for color: FCP XML.
• Pro Tools for sound mix: AAF.
• Avid Media Composer for online or conform: AAF.
• A finishing system that asks for cuts only: EDL.

When in doubt, send the format the receiving department asks for. Mixing engineers and colorists have strong preferences for a reason, those are the formats their tools handle most cleanly.

Common breakages, and how to avoid them

Three failures recur.

Media reconnection

The interchange file points at your media on your storage. If the receiving editor or colorist does not have access to the same paths, every clip arrives offline. The fix: send the interchange file alongside the media, or relink in a location both parties can see.

Frame handles

A colorist or mixer needs extra frames before and after each cut so they can extend transitions or slide edits. A common minimum is twenty-four frames at the head and tail of every clip. Without handles, every refinement downstream becomes a phone call back to editorial.

Unsupported effects

Premiere-specific transitions or plugin effects often do not translate at all. The reliable fix is to flatten and bake any effect that needs to survive into the source media before exporting the interchange file.

Picking the format is only the start. For the audio side, see exporting an AAF for Pro Tools; for the full delivery, the Premiere Pro handoff checklist; and for color, the step-by-step on preparing a timeline for color grading and the Premiere to DaVinci Resolve roundtrip.