What Is FCPXML? (XML in Video Editing)
Definition
FCPXML is Final Cut Pro's structured interchange format
FCPXML is Apple's XML interchange format for Final Cut Pro: a text file, not a video file, that describes clips, timelines, effects, and metadata in a structure other applications can read and write. When a transcript-editing tool, a color app, or a graphics package needs to hand a project to Final Cut Pro, or take one from it, FCPXML is the document doing the handoff.
Not the old format
Modern FCPXML and legacy Final Cut Pro 7 XML are not interchangeable
Final Cut Pro 7's XML (often called xmeml) and modern FCPXML share a family resemblance and nothing else. They use different schemas, and a file built for one will not open correctly in the other. As of the current Final Cut Pro release cycle, Apple's release notes track FCPXML at version 1.13, and Apple's developer documentation is explicit that apps exchanging data with Final Cut Pro today should target the current FCPXML schema, not the retired Final Cut Pro 7 format some older tools still export.
What it actually stores
More than a cut list
An FCPXML file can carry multiple tracks and layers, applied effects and their parameters, keywords, markers, roles for audio and video, and the compound-clip and multicam structure of a project, not just a flat list of in and out points. That's the real difference from an EDL: an EDL is a cut list, and FCPXML is closer to a full project description.
Where it sits next to EDL and AAF
Three interchange formats, three different jobs
| Format | Native to | Carries effects/layers | Best for |
|---|---|---|---|
| EDL | Any NLE (legacy standard) | No | A simple, universal cut list |
| FCPXML | Final Cut Pro | Yes | A full project handoff into or out of Final Cut Pro |
| AAF | Avid Media Composer | Yes | A full project handoff into or out of Avid, with audio-heavy metadata |
None of the three is strictly "better." An EDL survives almost any system because it carries so little. FCPXML and AAF carry more but are tied more tightly to their native application's model of a project.
A worked example
Moving a paper edit into Final Cut Pro
A transcript-based paper edit, built by selecting and reordering lines from an interview's transcript, exports as an FCPXML that opens in Final Cut Pro as a sequence with each selected line already placed at its correct frame, sourced from the original camera media. The editor opens the project with the structure already built and the story order already approved, rather than re-cutting from scratch inside Final Cut Pro.
Common gotchas
Where FCPXML handoffs actually break
- Media relinking. FCPXML references original media by file path and metadata; if the media moved or was renamed, Final Cut Pro will prompt to relink before anything plays back correctly.
- Effects that don't exist on the receiving end. A custom effect built in a third-party plugin won't survive the round-trip unless both systems have the same plugin installed.
- Version mismatches. A newer FCPXML schema version opened in an older Final Cut Pro release can fail or silently drop newer fields.
Why this matters for a transcript-first edit
The format is the bridge between a paper edit and a real timeline
A transcript-first workflow is only useful if the selects it produces can leave the transcript tool and land in a real NLE at the right frame. FCPXML (alongside EDL and AAF, depending on the destination app) is what makes that handoff a file transfer instead of a manual re-cut. Without it, every selection made against a transcript would have to be re-found and re-cut by hand once the editor opened Final Cut Pro, which erases most of the time a transcript-first pass is meant to save.
ScriptCut exports a completed selection as a real FCPXML, EDL, or AAF, so a paper edit built by reading and marking a transcript arrives in Final Cut Pro, Premiere Pro, DaVinci Resolve, or Avid already placed on the timeline. For the underlying selection method, see what a paper edit is and how word-level timecode works.
Sources
frequently asked questions
No. Modern FCPXML and the legacy Final Cut Pro 7 XML (xmeml) use different schemas and are not interchangeable; a file built for one will not open correctly in the other.
Clips, timelines, multiple tracks and layers, applied effects and their parameters, keywords, markers, and project structure, not just a flat list of cut points.
An EDL is a simple, universal cut list with no effects or layer data; FCPXML carries a much fuller description of the project but is tied more closely to Final Cut Pro's own project model.
Only if the receiving application supports the same effect or plugin. A custom third-party effect generally won't carry over unless both systems have it installed.
Often yes, since FCPXML references original media by file path and metadata. If that media has moved or been renamed, Final Cut Pro will prompt to relink it before playback works.
You might also like...
