Export a Paper Edit to Final Cut Pro and Avid
A paper edit only becomes useful once it lands in a real timeline. Final Cut Pro and Avid Media Composer each expect a specific file, built a specific way, or your selects show up as black gaps, wrong speed, or the wrong reel entirely. Here is what actually works for both, and why the two systems don't behave the same.
What Travels
What a selection needs to carry before it can export
A paper edit is just a list: in point, out point, source file, and order. For that list to become a real timeline, every selection needs three things attached to it: a frame-accurate timecode pulled from the source media, a stable reference to which file it came from, and the order the editor arranged it in. Miss any one of those and the import either fails outright or silently offsets by a frame or two, which is worse, because it looks right until someone checks it against the audio.
Final Cut Pro
Getting a paper edit into Final Cut Pro
Final Cut Pro imports timelines through FCPXML, Apple's XML-based interchange format, via File > Import > XML. FCPXML carries clip references, in/out points, and basic timeline structure, but it does not carry embedded media, so Final Cut needs to locate the original camera or audio files at the same relative paths, or you'll be relinking manually. The practical workflow: export the paper edit as FCPXML from the pre-edit tool, keep the source media in the same folder structure it was in when you transcribed it, then import and let Final Cut auto-relink.
Avid Media Composer
Getting a paper edit into Avid Media Composer
Avid takes AAF, EDL, or ALE, and each does a different job. AAF is the richest option: it carries the actual sequence structure, including multiple tracks and basic transitions, and imports as a real sequence in a bin via File > Import. EDL is older and flatter, effectively a shot list with timecodes and no track complexity, useful for simple assemble cuts. ALE carries metadata only, no timeline at all, so it's for syncing logging notes to existing bins, not for building a cut. For a documentary pre-edit with layered selects, AAF is almost always the right call.
AAF Vs EDL
Why AAF beats EDL for anything beyond a straight cut
The Advanced Authoring Format was published in 1998 by a consortium that included Microsoft, Avid, Digidesign, Pinnacle Systems, and Adobe, specifically to solve the interchange problem between production tools. That history matters here: AAF was built to carry structure, not just a list of timecodes, which is why it survives round-tripping between a transcript tool and Avid without losing track layout. An EDL, by contrast, was designed for the single-track tape-to-tape era and starts breaking down the moment a sequence has more than one video track or an overlapping audio selection.
Format Choice
Picking the right export for the job
Use AAF for Avid whenever the selects have any layering, b-roll cutaways over interview audio, or multiple speaker tracks. Use EDL only for a flat, single-track assembly where simplicity matters more than fidelity. For Final Cut Pro, FCPXML is close to the only real option since Final Cut doesn't read AAF natively without a third-party translator. XML works for both Premiere Pro and Final Cut and is the safest default when you're not sure which NLE the footage will land in.
Common Failures
Where these imports actually break
Frame rate mismatches are the top cause of an import that looks fine until the audio drifts, this happens when the source was logged at 29.97 but the timeline was built at 30. Relative file paths are the second: if the pre-edit tool references media at a path that no longer exists once files move to a new drive, both FCPXML and AAF imports will show offline media instead of failing loudly. The third is exporting before picture lock and re-exporting on top of manual trims the editor already made in the NLE, which silently discards that work.
Worked Example
A 12-person panel discussion cut two ways
A production company transcribes a 90-minute panel with five speakers, marks 22 minutes of usable selects across the transcript, and needs two versions: one cut in Avid for the broadcast client, one in Final Cut for the digital team. From the same set of selections, the AAF export goes to Avid and imports as a sequence with each speaker's selects already ordered on the timeline. The FCPXML export goes to Final Cut on the digital editor's machine, referencing the identical source files, and imports with the same structure. Neither editor re-builds the selection by hand.
The Takeaway
Match the format to the system, not the other way around
AAF for Avid, FCPXML for Final Cut Pro, and generic XML when you need one export that lands in either. The format choice isn't a formality, it decides whether the receiving editor gets a real sequence to refine or a pile of offline clips to relink by hand.
Related reading: What Is an AAF File?, What Is a Paper Edit?, Premiere Pro Transcript Workflow, and What Is Offline Editing?
Sources
frequently asked questions
Export the paper edit as FCPXML, keep the source media in the same folder structure it was in during transcription, then import via File > Import > XML and let Final Cut auto-relink the clips.
Export as AAF for a full sequence with tracks and structure, then import it into a bin via File > Import. EDL works for a flat single-track assembly, and ALE carries metadata only, no timeline.
Use AAF whenever the selects have any layering, b-roll cutaways, or multiple speaker tracks. EDL only holds up for a simple, single-track assembly.
Not natively. Final Cut Pro reads FCPXML for timeline interchange; AAF requires a third-party translator to bring it in.
The two most common causes are a frame rate mismatch between the source and the timeline, and relative file paths that break when media moves to a new drive, both of which show up as offline clips or drifting audio.
A frame-accurate timecode from the source media, a stable reference to which file it came from, and the order the editor arranged it in. Missing any of the three causes a failed or misaligned import.
Generic XML is the closest to a universal option and works reasonably well in both, but for full track fidelity you're better off exporting FCPXML for Final Cut and AAF for Avid separately.
You might also like...
