What Is an EDL (Edit Decision List)?
An EDL (Edit Decision List) is a short plain-text file that lists every cut in a sequence by source and record timecode, so any system can rebuild that edit from the original footage.
It is the oldest interchange format still in regular use, and the most stubbornly simple. Open one in a text editor and you can read it. That is the whole point.
Before EDLs, conforming an edit meant a person re-cutting tape by hand from notes. The EDL turned those notes into a machine-readable list a linear edit controller could execute. Decades later the format barely changed, which is exactly why it still works across gear that agrees on almost nothing else.
What an EDL actually contains
An EDL is an ordered list of events. Each event line names a source reel, the clip type (a cut, a dissolve), the source in and out timecodes, and the record in and out timecodes on the master timeline. Read top to bottom, it is a recipe: take this frame range from that reel, lay it here, then the next.
The dominant flavor is CMX3600, named after the CMX 600 editing system lineage. As Wikipedia's reference on the format puts it, an EDL contains an ordered list of reel and timecode data representing where each clip can be obtained in order to conform the final cut.
A worked example
A single CMX3600 event looks roughly like this:
001 TAPE01 V C 01:00:12:00 01:00:18:10 01:00:00:00 01:00:06:10
Read it left to right: event 001, source reel TAPE01, video track, a Cut, the source range 01:00:12:00 to 01:00:18:10, landing at 01:00:00:00 to 01:00:06:10 on the master. Six seconds and ten frames of footage, placed at the head of the timeline. Stack a few hundred of those lines and you have described an entire cut without moving a single frame of video.
What an EDL is good at
Universality. A CMX3600 EDL opens in DaVinci Resolve, Avid Media Composer, Premiere Pro, color grading suites, and tape-era hardware that predates all of them. When two systems share nothing else, they usually share EDL.
It is also tiny and human-readable. You can diff two EDLs, hand-edit a reel name, or scan an edit's structure in a text editor on a machine that has no NLE installed at all. For a color pipeline that just needs the cut points and source timecodes, that minimalism is a feature.
Where it falls short
The CMX3600 spec represents simple editing decisions only. That phrase is doing a lot of work. In practice an EDL carries cuts and basic transitions on one or two video tracks and little else. Effects, multiple layers, speed changes, titles, audio levels, and most modern timeline data do not survive the trip.
Reel names are capped at eight characters, and for a dissolve on the same reel you should keep names to seven, since the eighth character can get repurposed. That constraint feels absurd in 2026, and it is a real source of conform errors when a long camera-card name gets truncated.
The format is also dumb about media. An EDL points at timecode on a named reel; it does not embed the files. If your reel names and timecodes do not match the media in the destination system, the conform fails and you are matching frames by eye.
Common gotchas
- Drop-frame vs non-drop-frame. Mix them and your timecodes drift. Confirm the project frame rate and timecode standard before you export.
- One or two tracks only. A multi-layer timeline flattens. If your edit relies on stacked video, EDL is the wrong format.
- Reel-name truncation. Long source names get cut to eight characters and can collide. Rename or relink carefully on import.
- Audio is limited. Treat EDL as a picture-cut list. For audio round-trips, AAF is the right tool.
EDL vs XML vs AAF
Think of it as a ladder of richness. EDL carries cuts and timecode. FCPXML and other XML interchange formats carry far more of the timeline: multiple tracks, effects, metadata, and structure. AAF is common for Avid and audio round-trips into Pro Tools because it can reference and even embed media. As the EDL reference notes, modern systems often use more robust formats like AAF and XML, though EDLs remain commonly used.
So the choice is honest: reach for EDL when you need the widest compatibility and only the cuts matter. Reach for XML or AAF when the edit's detail has to come along.
Where an EDL fits in a transcript-first workflow
Most documentary and interview editors do their real thinking before the NLE, on the words. You read the transcript, mark the strongest lines, drop the dead weight, and arrange the story. That is the paper edit, and it is where the edit is actually won.
The handoff is where a format like EDL earns its keep. ScriptCut is built for that pre-edit: get footage transcribed, highlight the selects, remove fillers, arrange the order, get client sign-off, then export. Because each selected line carries word-level timecodes, the export comes out as an assembled sequence rather than a wall of raw clips. You can send XML, EDL, subtitles, or audio, and it opens in Resolve, Premiere, Final Cut, or Avid ready to refine.
For the deeper handoff mechanics, see exporting a paper edit to Final Cut and Avid and the broader transcript-to-timeline documentary workflow.
The takeaway
An EDL is a forty-year-old idea that refuses to die because it nails one job: describe the cuts in text that anything can read. Use it when compatibility beats detail, lean on XML or AAF when it does not, and do the storytelling on the transcript first so whatever you export is already a real sequence.
Sources
Frequently asked questions
Is an EDL still used in 2026?
Yes, mainly for color grading round-trips and any handoff where you need maximum compatibility and only the cuts matter. For richer timelines most editors now use XML or AAF.
What is the difference between an EDL and an XML?
An EDL carries cuts and timecode in plain text, usually on one or two tracks. XML formats like FCPXML carry multiple tracks, effects, and metadata, so far more of the timeline survives the export.
What does CMX3600 mean?
CMX3600 is the most common EDL format. It represents simple cuts and basic transitions and limits reel names to eight characters, which is why long source names sometimes get truncated on conform.
Can an EDL include audio and effects?
Only barely. Treat an EDL as a picture-cut list. Effects, multiple layers, and detailed audio do not travel well, so use AAF for audio round-trips and XML for effect-heavy timelines.