Exporting for Resolve: XML, AAF, FCPXML & EDL
The XML, AAF, or FCPXML export is the timeline data that Resolve will conform. This page covers best practices for generating a clean, conformable export from each major NLE.
Choosing the Right Format
The right export format depends on the NLE you’re exporting from:
| NLE | Preferred | Also Acceptable | Avoid |
|---|---|---|---|
| Avid Media Composer | AAF | — | XML (loses information) |
| Adobe Premiere Pro | XML (Final Cut Pro XML) | AAF | — |
| Final Cut Pro | FCPXML | — | Legacy XML |
| DaVinci Resolve | XML or FCPXML | — | — |
Rule of thumb: Use the format the NLE exports natively. Avid’s native format is AAF; Premiere and FCP use XML variants. Forcing a format the NLE doesn’t prefer often drops critical information.
General Export Principles
Regardless of format, follow these rules:
1. Export from a Flattened, Committed Sequence
Always export from the version of the sequence that has:
- Multicams committed
- Critical time-warps and complex effects flattened
- Unused media removed
- Tracks labeled
2. Include Handles
Handles are the extra frames of source media outside each clip’s cut points. The conformer needs handles to rebuild dissolves, adjust edits, and do fine timing.
| Scenario | Handle Length |
|---|---|
| Tight turnover, no changes expected | 24 frames minimum |
| Standard documentary | 24–48 frames |
| Expected transitions / dissolves | Length of transition + 24 frames |
| Color finishing with potential re-edits | 48+ frames |
| Media-managed / transcoded delivery | 48+ frames (can’t go back to source easily) |
3. Provide a Flattened Backup Sequence
Alongside the primary XML/AAF, also include a flattened version of the sequence — one where complex effects, speed changes, and time warps have been rendered into the clips. This is not what the conformer will use as the master, but it’s an invaluable troubleshooting reference.
4. Export Per-Track EDLs (Optional But Helpful)
An EDL (Edit Decision List) is a simple text file listing every edit point. While not used to build the conform, per-track EDLs are handy for quick cross-reference:
- One EDL per video track
- CMX 3600 format is standard
- Use the same reel IDs and source names as the main export
Avid Media Composer: Exporting AAF
Step 1: Prepare the Sequence
Load the locked, committed sequence into the Record monitor.
Step 2: File → Export
File → Export → select AAF as the format.
Step 3: Configure Export Settings
- Export As: AAF
- Include: Video tracks, audio tracks, markers
- Audio: Export as embedded or as linked sidecar WAVs (sidecar preferred for large projects)
- Video: Link to source media (AMA) — do not embed video
- Handle length: set to 24 frames minimum
Step 4: Save the AAF
Save to your delivery folder using the naming convention: SHOW_EP###_v##_YYYYMMDD.aaf
Step 5: Generate Reference EDLs (Optional)
File → Export → CMX 3600 EDL per track.
Adobe Premiere Pro: Exporting XML
Step 1: Open the Sequence
Make sure the locked, committed sequence is active.
Step 2: File → Export → Final Cut Pro XML
File → Export → Final Cut Pro XML.
Step 3: Save
Save to your delivery folder. Premiere will also write a .xml sidecar; keep it next to the video file references.
Step 4: Inspect the XML
- Open the XML in a text editor — look for error tags or missing references
- Verify effect tags are present for anything that needs to translate
Step 5: Export Flattened Reference (Recommended)
Export a self-contained ProRes 422 HQ of the sequence as a backup reference.
Final Cut Pro: Exporting FCPXML
Step 1: Prepare the Project
Make sure the project is consolidated and all media is online.
Step 2: File → Export XML
File → Export XML.
Step 3: Choose Version
Export as the latest FCPXML version compatible with Resolve. As of 2026, FCPXML 1.10 and later are well-supported.
Step 4: Save
Save to your delivery folder.
FCP note: Resolve does not natively read compound clips from FCP. Break apart compound clips before export, or the conform will treat each compound as a black box.
Common Export Issues
Issue: Effects Appear Missing in Resolve
- Some effects require Resolve to recognize them by name (e.g. standard dissolves are universal; custom plugin effects are not)
- Fix: flatten the section, re-export
Issue: Audio Tracks Merged Incorrectly
- Often caused by “Export as embedded audio” with complex track routing
- Fix: export audio as sidecar mono WAVs per track, reference them from the XML/AAF
Issue: Frame Rate Mismatch
- Sequence is 23.976 but clips are 24 — Resolve may interpret with a pulldown
- Fix: match sequence frame rate to delivery frame rate from the start
Issue: Offline Clips in Resolve
- The XML points to file paths Resolve can’t resolve
- Fix: ensure the media paths in the XML/AAF match what’s on the delivery drive. Most conformers relink anyway, but correct paths in the XML make the first import much smoother
Issue: Markers Missing
- Rare, but can happen on older XML export versions
- Fix: export markers separately as CSV (see Markers) and include them in the delivery package
The Export Package
A clean turnover export includes:
- Primary XML / AAF / FCPXML (locked, committed sequence)
- Flattened backup sequence (self-contained ProRes 422 HQ)
- Per-track EDLs (optional but helpful)
- Separate marker CSV (optional)
- Reference QuickTime with burn-ins
- All source media (OCM, archival, VFX, GFX, audio) on the delivery drive
- A manifest / read-me file listing every item in the package
See Delivery for how to structure and transfer the package.