EDL vs XML vs AAF: which file carries what.
An EDL carries one track of cuts, an XML carries the sequence with its names and markers, an AAF carries the tracks and audio for a mix. Which to send when.
EDL, XML and AAF describe the same edited sequence in three amounts of detail. An EDL is a plain-text list of cuts on one video track. An XML is the whole sequence: every track, clip name, marker and note. An AAF adds the audio, levels and fades a sound mix is built from. Send the smallest one that carries what the next person needs.
What are these files for?
None of them contains footage. Each is a set of instructions that says which part of which source file sits where on a timeline, so another program can rebuild the cut from media it already has. The receiving editor still needs the camera files, at a path it can find, and the frame rate the cut was made at. The three differ in how much of the timeline they describe, and that is the whole question when someone asks which to send.
What does each file carry?
| What travels | EDL | XML | AAF |
|---|---|---|---|
| Video tracks | One per file | All of them | All of them |
| Audio tracks | A few channels, cuts only | All, with levels | All, with levels, pans and fades |
| Clip names | As comment lines | Yes | Yes |
| Markers and notes | As comment lines, if the reader keeps them | Markers with names and notes | Markers, usually with notes |
| Transitions | Cuts, dissolves, some wipes | Cuts, dissolves, basic effects | Cuts, dissolves, audio fades |
| Multicam | No, one source per event | Depends on the dialect and the pair of editors | No, flatten first |
| Media | Linked by reel name and timecode | Linked by file path | Linked by path, or embedded |
| Who reads it | DaVinci Resolve, Premiere Pro, most other tools | Depends on the dialect, see below | DaVinci Resolve, Premiere Pro, audio post tools |
EDL is the oldest and the smallest. A CMX 3600 EDL has one event per cut: a reel name, a source in and out, a record in and out. Comment lines under an event can carry the clip's file name and a note, which the reader may or may not use. It has one video track, so a second track means a second file, and it has no frame rate, only whether the timecode is drop frame. Everything it lacks is also why it works: nearly every editor and conform tool reads one. The reel-name field and what it does to relinking are in how to import an EDL from a transcript into DaVinci Resolve.
XML is the sequence as the editor sees it: every track, every clip with its name, markers with names and notes, audio levels, speed changes, dissolves and whatever effects the receiving editor happens to understand. Two unrelated files share the name. Final Cut Pro 7 XML is the older dialect, a .xml file that Premiere Pro and DaVinci Resolve read and write. FCPXML is the format current Final Cut Pro exports, as .fcpxml or an .fcpxmld package, and Resolve reads it while Premiere Pro does not. An FCPXML can carry a multicam clip from Final Cut Pro into Resolve. Which dialect your tool wrote matters more than anything else about it.
AAF carries the most and travels the least. It was built around a broadcast editing system rather than any of the three editors here, and it is the file audio post asks for: every audio track with its levels, pans and fades, clip names, markers and, if you choose, the audio media embedded inside the file so the mixer gets nothing offline. Between picture editors it does less. Premiere Pro and DaVinci Resolve read and write it, Final Cut Pro does not without a converter utility, and a multicam clip has to be flattened before it goes in. Picture effects rarely cross; the cut, the track layout and the audio do.
Which should you send?
Send an EDL when the next person needs the cut and nothing else: a colorist conforming from camera originals, an online suite, a second editor who wants the order of the selects and will do the rest themselves. It is also the right file when you do not know what the other end runs, because it will open.
Send an XML when the next person needs to keep editing. A stringout with clip names and notes, a rough cut going to a second editor, a sequence coming back from a transcript tool: all of these are worth more with their tracks and markers intact. Pick the dialect by the receiving editor. For Premiere Pro, Final Cut Pro 7 XML, imported as in how to import XML into Premiere Pro. For Final Cut Pro, FCPXML only. For Resolve, either.
Send an AAF when the next stop is sound. The mixer wants every track, level and fade you set, with handles, and an AAF with embedded audio carries all of it without a relink. Between two picture editors an XML is usually enough and smaller.
When the destination is Final Cut Pro, only FCPXML opens directly. The usual route for an EDL or an AAF is through DaVinci Resolve, which imports it, free edition included, and exports FCPXML; the route and what breaks on the way are in how to export XML from Final Cut Pro.
What breaks in all three
Media paths, first. Every one of these files points at footage it does not contain, and the pointer is only as good as the path or reel name it was written with, so moved drives and renamed folders send clips offline on import. Frame rate, next: an EDL does not state one, and the XML and AAF do not stop a project set to a different rate from reading the file wrong, so set the receiving project to the camera rate before you import. Effects, last. A dissolve crosses in all three; a grade, a title, a plug-in and most speed ramps do not. Treat an interchange file as the cut, and plan to rebuild the finish.
Doza Assist is a local-first AI editing assistant for interviews and dialogue that writes the right file for the editor you name, so the choice above is made once. The "Edit in" selector in the project header picks Final Cut Pro, Premiere Pro or DaVinci Resolve, and every export button then uses that format: a timeline sent straight to Final Cut Pro as FCPXML, with keyword ranges and chapter markers and the original multicam container kept; a Final Cut Pro 7 XML for Premiere Pro, with the cuts on V1 and A1/A2, the clip names, markers and your notes; a CMX 3600 EDL for Resolve, with clip names and notes as comments, or FCPXML when the interview is multicam. The transcript, the selects and the camera files stay on your Mac. The post-production facilities page shows where it fits inside a suite.
Common questions
What is the difference between an EDL and an XML?
An EDL is a plain-text list of cuts on one video track, with reel names and timecodes and little else. An XML describes the whole sequence: every track, clip name, marker, note and audio level, plus the transitions and effects the receiving editor understands. Send an EDL for a conform, an XML to keep editing.
What is an AAF file used for?
Mostly for sending a cut to audio post. An AAF carries every audio track with its levels, pans and fades, and can embed the audio media so nothing is offline at the mix. Premiere Pro and DaVinci Resolve read and write it; Final Cut Pro needs a converter utility or a pass through Resolve.
Does an EDL carry audio?
Only cuts. A CMX 3600 EDL can mark that an event carries audio channels, but it has no levels, pans or fades, and no more than a few channels per file. For anything a mixer will use, send an AAF; for a picture edit with its audio tracks laid out, an XML.
Can an XML carry a multicam clip?
Sometimes. An FCPXML carries a multicam clip from Final Cut Pro into DaVinci Resolve. Whether a multicam survives any other pair of editors depends on the dialect and the versions, so test one clip before you send a project. An EDL never carries one, and an AAF needs the multicam flattened first.
Which file does Final Cut Pro import?
FCPXML, with File > Import > XML. Final Cut Pro does not import an EDL, an AAF or a Final Cut Pro 7 XML on its own. Import the file into DaVinci Resolve, free edition included, export the timeline as FCPXML, and import that.
Doza Assist transcribes every interview locally, finds the strongest moments across all of them, then sends your chosen ranges to Final Cut, Premiere, or Resolve. Your video never leaves your Mac.
Free trial: every feature on your first 2 minutes — no account, no card · 30-day money-back guarantee · Requires a Mac with Apple Silicon (M1 or later)