Exports the current timeline as an EDL (Edit Decision List) file.
An EDL is a text-based interchange format that describes editing decisions, not media content.
What an EDL is
An EDL records how a timeline is edited, including:
- Clip order
- Source in/out points
- Timeline in/out points
- Basic transitions (usually cuts only)
- Track assignments (limited)
It does not contain video, audio, effects, or rendered output.
An EDL answers the question:
“How the edit is put together?”
not
“What does the final video look or sound like?”
Purpose of exporting an EDL
EDL export is primarily intended for interoperability and offline workflows, such as:
- Moving an edit from Shotcut to another NLE
- Conforming an offline edit to higher-quality media
- Archiving edit decisions separately from media
- Educational or documentary workflows
It is not meant for final delivery.
What is included in Shotcut’s EDL export
Typically included:
- Clip references
- Source timecodes (in/out)
- Timeline placement
- Simple cuts
Typically not included:
- Filters or effects
- Transitions beyond simple cuts
- Speed changes
- Keyframes
- Color correction
- Audio filters
- Generators
- Titles
- Compositing or track blending
- Most multi-track relationships
EDL support is intentionally minimal.
Format characteristics and limitations
- Plain text format
- Line-based, rigid structure
- Originally designed for linear tape editing
- Limited metadata capacity
- No extensibility for modern effects
Note:
The EDL format is limited to a single video track and a small number of audio tracks (commonly up to four).
Because of this, EDLs are lossy representations of modern timelines.
Compatibility with other software
EDL is an old but widely recognized format.
Commonly supported (non-exhaustive list):
- Natron
- Blender (VSE)
- Pitivi
- KDEnlive
- DaVinci Resolve
- Avid Media Composer
- Adobe Premiere Pro (import with constraints)
- Final Cut Pro (via conversion tools)
- Various conforming and finishing systems
Important:
Each application interprets EDLs slightly differently. Results may vary.
Requirements and expectations
To successfully use an exported EDL:
- Source media must be available to the target application
- File names and timecodes must match
- Reel names (if used) must be compatible
- Expect manual cleanup after import
EDL workflows assume editor intervention, not one-click transfer.
What this export is not
- Not a project backup
- Not a render
- Not a universal interchange format
- Not suitable for complex timelines
Recommended use cases
- Rough cut transfer
- Offline-to-online conform workflows
- Archival documentation of edit decisions
- Educational demonstrations of editing structure
- Legacy broadcast workflows
Practical usage note
If your timeline relies heavily on filters, effects, compositing, or generators, exporting to EDL will produce a simplified and incomplete representation of the edit.
This is expected behavior, not a bug.