How to Fix EDL Import Issues in DaVinci Resolve: Complete Troubleshooting Guide
Fix EDL import issues in DaVinci Resolve: misaligned cuts from frame rate mismatch, missing media from reel name errors, and total import failures from corrupted EDL text. Here is the troubleshooting guide for each problem.
Why does an EDL import fail in DaVinci Resolve?
An EDL import fails in DaVinci Resolve for one of four reasons: frame rate mismatch between the EDL and the Resolve project, incorrect timecode on the source media, missing or mismatched reel names, or corrupted text in the EDL file itself.
EDLs are plain-text files, which makes them both robust and fragile. They are robust because any text editor can open and repair them. They are fragile because a single incorrect character — a wrong frame rate value, a misaligned timecode column, or a garbled reel name — causes Resolve to misread the entire file. Understanding which of the four failure modes you are facing is the first step to fixing it.
Issue 1: The Pre-Conformed EDL Does Not Slice Correctly
The most common use of an EDL today is slicing a single, flattened master video file into individual clips for color grading. If the cuts are landing in the wrong spots, the culprit is almost always a frame rate or timecode mismatch.
The Fix (Frame Rate Mismatch): Ensure that the project settings in Resolve — specifically the timeline frame rate — exactly match the frame rate of the original timeline from which the EDL was exported. If the original edit was 23.976 fps, your Resolve timeline must be 23.976 fps before you import the EDL. Even a 0.1% difference causes cumulative drift. A 23.976 EDL imported into a 24.00 project will be off by roughly 1 frame every 42 seconds.
The Fix (Timecode Start): Check the starting timecode of your flattened video file. If the EDL expects the video to start at 01:00:00:00 but the video file starts at 00:00:00:00, all the cuts will be offset by exactly one hour. Right-click the video file in the Media Pool, choose Clip Attributes > Timecode, and manually offset the start timecode to match what the EDL expects. You can verify the expected start timecode by opening the EDL in a text editor — the first line usually shows the source reel name and starting timecode.
Issue 2: Resolve Cannot Find the Media for EDL Clips
If you are using an EDL to link to individual camera files rather than a flattened master, you might encounter offline clips. Resolve cannot find the media because the EDL's media references do not match the actual files on your system.
The Fix (Reel Names): EDLs rely heavily on Tape or Reel names to identify source files. If your source NLE did not export reel names properly, or Resolve is not reading them correctly, the link will fail. Go to Project Settings > General Options in Resolve. Under Conform Options, check "Assist using reel names from the" and choose either "Source clip file pathname" or "Embedded in source clip file" depending on your camera media.
For ARRI, RED, and Sony camera files, the reel name is usually embedded in the clip metadata. Choose "Embedded in source clip file." For transcoded proxies or screen recordings that lack embedded metadata, choose "Source clip file pathname" — this tells Resolve to match clips by file name instead of reel name.
If neither setting works, you can manually edit the EDL in a text editor to replace reel names with actual file names. Find the asterisk lines in the EDL that begin with the reel name and change them to match the file names on your system. This is tedious for timelines with many clips but is guaranteed to resolve reel-name mismatches.
Issue 3: Missing Tracks or Effects in the Imported EDL Timeline
If the EDL imports successfully but your timeline is missing video tracks, audio channels, or effects, the issue is not a bug — it is a limitation of the EDL format itself.
The Fix (Manage Expectations): A standard CMX 3600 EDL only supports a single video track (V1) and up to four audio channels. If your original timeline had titles on V2, B-roll on V3, compound clips, or speed ramps, the EDL simply ignored them during export. You cannot fix this in Resolve; you must go back to your editing software, flatten the timeline to a single video track, bake in any speed effects, and export a clean EDL.
For audio, the four-channel limit means any tracks beyond A4 are dropped entirely. If your project needs more than four audio channels to survive the transfer, switch to XML or AAF. EDL is the wrong format for complex multi-track projects.
Issue 4: The EDL Fails to Import Entirely
If Resolve rejects the EDL file outright — showing an "Invalid EDL" error or simply refusing to open it — the file is likely corrupted or contains unexpected characters.
The Fix (Clean the Text): EDLs are text files. Open the .edl file in a basic text editor like Notepad or TextEdit. Look for strange, non-alphanumeric characters, incredibly long file paths, or corrupted lines of text. Sometimes a single garbled line representing a problematic clip causes the entire import to fail. Delete that line, save the file, and try importing again.
Also check the file format and encoding. EDLs should be saved as plain ASCII text with .edl extension. If the file contains Unicode characters, smart quotes, or line breaks from a Mac versus Windows system, Resolve may reject it. Re-saving the file with plain text encoding often fixes this.
How do you prevent EDL import issues before they happen?
Preventing EDL import issues is more efficient than troubleshooting them. Follow these preparation steps before exporting from your NLE.
First, verify your project frame rate and match it to the destination Resolve project. Second, confirm that all source media has consistent timecode by checking Clip Attributes in your NLE. Third, flatten your timeline to a single video track and verify that no effects, transitions, or titles are present. Fourth, export a test EDL with a short three-clip sequence and import it into Resolve before committing to the full export. If the test works, the full export will work.
Using Cutsio as a pre-editing layer also prevents EDL import issues before they start. Because Cutsio generates clean XML and EDL exports from AI-processed rough cuts, the exported files contain only simple cuts with consistent media references. There are no nested compound clips, no unsupported effects, and no complex audio routing to confuse the EDL format. The result is that Cutsio exports import into DaVinci Resolve without errors on the first attempt, saving editors hours of troubleshooting time on every project.
FAQ
Why do my EDL cuts keep landing a few frames off?
EDL cuts landing a few frames off is almost always caused by a frame rate mismatch between the source project and the Resolve project. Verify that both projects use the exact same frame rate. Even a 0.1% difference — such as 23.976 fps versus 24.00 fps — causes cumulative drift that becomes visible within a minute of timeline playback.
Can I convert an existing XML to an EDL in Resolve?
Yes, DaVinci Resolve can import an XML and then re-export it as an EDL. This is a common troubleshooting step when an XML import fails but the EDL format works correctly. Import the XML first, then export the resulting timeline as an EDL.
What is the best EDL format to use for maximum compatibility?
CMX 3600 is the most widely supported EDL format. It works with every modern NLE, color grading system, and conform tool. Choose CMX 3600 in DaVinci Resolve's EDL export dialog for the broadest compatibility.
How do I check which frame rate my EDL was exported at?
Open the EDL file in a text editor. The second line usually contains the frame rate specification. Look for "FCM: NON-DROP FRAME" for 23.976 or 29.97 non-drop, or "DROP FRAME" for 29.97 drop-frame. The edit lines themselves also use timecode formatting that reveals the frame rate.
What is the difference between drop frame and non-drop frame timecode?
Drop frame timecode skips certain frame numbers to keep the timecode duration aligned with real clock time at 29.97 fps. Non-drop frame timecode counts every frame sequentially and drifts away from real time by approximately 3.6 seconds per hour. Most broadcast and television workflows use drop frame timecode, while film and web projects typically use non-drop frame. Using the wrong timecode type is a common source of EDL import errors that manifests as progressively worsening offset as the timeline plays forward.
For more EDL and XML guides, see the EDL vs XML comparison, the FCP to Resolve XML workflow, and the XML import fix guide.