---
title: "How to Export an EDL from DaVinci Resolve (Step-by-Step)"
author: "Cutsio Team"
date: "2026-04-17"
lastmod: "2026-04-17"
category: Tutorials
excerpt: "A practical guide to exporting an Edit Decision List (EDL) from DaVinci Resolve for conform, handoff, or archiving—plus the common mistakes that break relinking."
tags:
  - "davinci resolve"
  - "edl"
  - "xml"
  - "post-production"
  - "workflow"
---

# How to Export an EDL from DaVinci Resolve (Step-by-Step)

To export an EDL from DaVinci Resolve, you’re usually preparing a timeline handoff for conform, finishing, or archival workflows. EDL is a simple interchange format, so the most important part is not the button click—it’s keeping frame rate, reel names, and timecode consistent so the EDL can relink correctly. If you want to avoid EDL headaches entirely, **Cutsio can be your pre-edit layer**: assemble a rough cut using transcripts, [Semantic Search](https://cutsio.com/#semantic-search), and [Silent Slicer](https://cutsio.com/#silent-slicer), then export a clean timeline (XML/EDL) into Resolve for finishing.

## What is an EDL (and when should you use it)?

An EDL (Edit Decision List) is a plain-text file that describes a sequence:

- which clips are used
- in what order
- with what timecode in/out points

EDL is best for:

- simple conform workflows
- legacy pipelines
- basic timeline handoff

EDL is not great for:

- complex edits with many layers
- heavy effects and transitions
- rich metadata workflows

For modern interchange, XML is often more reliable.

If you want a Mac-focused overview, see: [How to Open EDL Files on Mac](https://cutsio.com/blog/how-to-open-edl-files-mac).

## Why Resolve exports EDLs that sometimes “don’t work”

Most EDL failures come from:

- frame rate mismatch (23.976 vs 24, 29.97 DF vs NDF)
- reel name mismatch (EDL references reels, not filenames)
- media timecode mismatch (files have different or missing timecode)
- EDL flavor differences (some systems expect different formatting)

So the correct workflow is:

1. confirm project/timeline settings
2. export EDL
3. validate the EDL and relinking assumptions

## Step-by-step: export an EDL from DaVinci Resolve

The exact menus can vary by Resolve version, but the workflow is consistent:

1. Open the project and go to the **Edit** page.
2. Select the timeline you want to export.
3. Use the timeline export options to export an **EDL**.
4. Choose:
   - the correct timeline
   - the correct track selection (usually the main video track)
   - the correct reel naming behavior (depends on media)
5. Save the EDL and keep it with a copy of the media reference info.

The most important thing is to export from the timeline that matches your final structure. If you export from an early cut, your conform will drift.

## What settings matter most when exporting EDL

### Frame rate and timecode format

Before exporting, confirm:

- project frame rate
- timeline frame rate
- drop-frame vs non-drop-frame (if relevant)

If frame rate is wrong, conform will drift. Don’t “fix it later.” Fix it before export.

### Reel name strategy

EDLs often identify clips by reel name rather than file path.

If your reel names are inconsistent, relinking becomes painful.

Practical rule:

- keep media naming consistent
- avoid random reel naming across folders

If reel names don’t match, consider exporting XML instead.

## How to validate an EDL quickly (before handing it off)

EDLs are plain text. You can open them in any text editor.

Check:

- does the EDL show expected reel names?
- do timecodes look plausible?
- do clip counts roughly match your timeline?

If the EDL references reels you don’t recognize, relinking will fail downstream.

## Common EDL export mistakes (and fixes)

### Exporting the wrong timeline

Fix: rename timelines clearly and export from the locked cut.

### Exporting after major pacing changes without updating

If you removed dead air late, or tightened a cut, export again from the final timeline.

If you want to tighten pacing upstream (before finishing), see: [How to Remove Dead Air From Lecture Videos](https://cutsio.com/blog/how-to-remove-dead-air-from-lecture-videos).

### Relying on EDL for complex timelines

EDL is limited. For complex work, XML is usually the safer interchange.

## EDL vs XML: which should you export?

Use this decision rule:

| If you need… | Prefer |
|---|---|
| simple conform | EDL |
| richer metadata | XML |
| complex multilayer edits | XML |
| maximum compatibility with legacy systems | EDL |

Many modern workflows use both: EDL for basic conform and XML for richer structure.

## A practical “EDL export checklist” (so your handoff actually works)

Before you export:

- confirm project frame rate and timeline frame rate
- confirm media timecode is consistent
- confirm reel naming behavior is predictable
- simplify the timeline if needed (EDL dislikes complexity)

After you export:

- open the EDL in a text editor and verify reel names look correct
- spot-check clip count and timecode ranges
- do a small test import in the destination project if possible

If you can’t validate quickly, you can’t trust the conform.

## How Cutsio reduces the need for complex EDL handoffs

Many EDL handoffs exist because someone needs a rough cut, fast.

Cutsio can produce that rough cut faster upstream:

- transcripts make content scannable
- semantic search finds moments by meaning
- silent slicer tightens pacing automatically

Then you export a clean timeline into Resolve for finishing. This often results in a simpler final timeline—and simpler timelines produce more reliable EDLs.

## When you should export EDL vs XML from Resolve (practical)

If you’re unsure which to export, use this:

- Export **EDL** when the destination system expects it or the timeline is simple.
- Export **XML** when you need a richer handoff (more structure, better relinking signals).

In many modern workflows, editors will export XML for the main handoff and EDL for a simplified conform reference.

## How to avoid broken relinks in the receiving project

If your EDL is going to another system (or another editor), the receiving project must be set up correctly.

Practical handoff tips:

- provide the media folder structure (or at least a consistent path)
- include a short note about frame rate and timecode format
- keep reel naming consistent between export and import
- avoid renaming media after exporting the EDL

If you’re handing off to a Mac-based finishing workflow, see: [How to Open EDL Files on Mac](https://cutsio.com/blog/how-to-open-edl-files-mac).

## Common reasons you export an EDL from Resolve (real workflows)

Most people export an EDL for one of these reasons:

- **Conform**: rebuilding the cut in another project/system for finishing.
- **Color workflow**: handing off a simplified edit list so another project can relink and grade.
- **Archival**: storing a lightweight representation of edit decisions alongside the media.
- **Interchange**: moving between tools when XML isn’t available or isn’t accepted.

If your goal is simply “share the cut with another editor,” XML is often the safer option. But if the receiving workflow expects EDL, a clean export can work well.

## How to make your EDL “conform-friendly” (so it imports cleanly)

If you want your EDL to import cleanly in the receiving workflow, simplify the timeline before export:

- keep the main edit on a single primary video track (V1)
- avoid complex transitions and layered graphics (EDL won’t represent them well)
- flatten nested timelines if possible
- keep clip names and reel metadata consistent

Think of EDL as an edit *skeleton*. The more complex the timeline, the less reliable EDL becomes. If the project is complex, export XML alongside the EDL so the receiver has a richer option.

That one choice prevents most downstream surprises.

## How Cutsio fits into Resolve workflows

Resolve is powerful for finishing:

- color
- audio mixing
- mastering

Cutsio is powerful for pre-editing:

- transcripts and semantic search for selection
- silent slicer for pacing cleanup
- quick assembly into sequences

So a practical workflow is:

1. ingest and assemble in Cutsio
2. export a clean timeline into Resolve
3. do finishing polish
4. export final deliverables

This reduces the time you spend scrubbing through raw footage inside Resolve.

## FAQ

### Why would I export an EDL from Resolve?

To hand off a simple timeline for conform, finishing, or archival workflows—especially in pipelines that expect EDL.

### Why does my EDL import show offline clips?

Usually because reel names or timecodes don’t match your media. EDL relies on correct relinking metadata.

### Should I export EDL or XML from Resolve?

If the timeline is complex, export XML. If the pipeline is legacy or simple conform, EDL can work well.

### Where does Cutsio fit if I use Resolve?

Cutsio speeds up pre-editing: transcripts, semantic search, dead-air removal, and fast assembly—then you export to Resolve for finishing.

### What’s the biggest EDL export mistake?

Frame rate/timecode mismatch. If project settings don’t match the source and the intended conform format, the entire EDL becomes unreliable.

### What’s the simplest EDL workflow if I just want to archive an edit?

Exporting an EDL can be a good “lightweight archive” of your cut because it preserves edit decisions even if you later move projects.

To make the archive usable:

- keep a copy of the media (or at least the file list and naming)
- store a note with frame rate, timecode format, and reel naming rules
- store an XML as well if the project is complex

EDL alone is often not enough for complex edits, but it can be a useful safety net alongside your project file.