What Is FCPXML? (XML in Video Editing)
FCPXML is Apple's XML interchange format for Final Cut Pro: a structured text file (extension .fcpxml) that describes clips, projects, timelines, and metadata so apps can exchange edits with Final Cut Pro.
Where an EDL is a flat list of cuts, FCPXML is a full description of an edit. It can carry multiple tracks, effects, keywords, markers, ratings, and the relationships between clips. That richness is the reason a whole ecosystem of tools generate and read it.
Apple describes the format plainly in its FCPXML Reference: it is used to describe clips, projects, and other items so you can exchange data with Final Cut Pro. In other words, it is the official doorway in and out of Final Cut for anything that is not Final Cut.
FCPXML vs the old Final Cut Pro 7 XML
This is where people trip. There are two different Apple XML formats and they are not the same thing.
- FCPXML (.fcpxml) is the modern format used by Final Cut Pro (the version formerly branded Final Cut Pro X). It has gone through many versioned revisions as the app gained features.
- Final Cut Pro 7 XML (xmeml) is the legacy interchange format from the old Final Cut Pro 7 era. Premiere Pro and DaVinci Resolve have long read and written this older XML, which is why people loosely say they import Final Cut Pro XML.
If a tool says it exports Final Cut Pro XML, check which one. Sending modern .fcpxml to an app that only speaks the legacy xmeml will fail, and vice versa.
What FCPXML stores
A lot. The format represents the structure of a project: the clips and their source media, the order and timing on the timeline, multiple video and audio lanes, transitions and effects, markers, keywords, ratings, and metadata. Newer revisions even introduced a bundle package (the .fcpxmld bundle) that keeps the core XML readable while carrying extra data like color and stabilization alongside it.
That makes it genuinely useful for round-trips. A logging tool can hand Final Cut a stack of keyworded clips. A grading or finishing app can pull a timeline out, work on it, and send structure back. An assistant can build a rough cut elsewhere and deliver it as .fcpxml that opens as a real sequence.
A worked example
Say you logged interview selects in a separate app and want them in Final Cut. You export .fcpxml. In Final Cut Pro you choose File > Import > XML, point at the file, and the app rebuilds your clips, ranges, and keywords in a new event or project. The footage does not move; the XML tells Final Cut which frames to reference and how to lay them out.
Where it fits next to EDL and AAF
Picture a richness scale. EDL carries the cuts and timecode and almost nothing else. FCPXML carries the structured timeline with tracks, effects, and metadata. AAF sits in the Avid and audio world and can reference or embed media for Pro Tools round-trips.
None of them is best at everything. EDL wins on universality. AAF wins for audio and Avid. FCPXML wins when you are moving a detailed edit in or out of Final Cut Pro, and the broader Final Cut Pro XML family is the common tongue between Final Cut, Premiere, and Resolve.
Common gotchas
- Version mismatches. FCPXML is versioned. An older app may reject XML written by a newer Final Cut. Keep both ends current or export to a version the destination supports.
- Modern vs legacy XML. .fcpxml is not xmeml. Confirm which format your target NLE actually imports.
- Effects do not always survive. A custom Final Cut effect has no equivalent in Premiere or Resolve, so it can drop on import. Cuts, structure, and timing travel; bespoke looks may not.
- Media relinking. The XML references media by location and identifiers. If the files are not where the destination expects, you will relink before you can edit.
Why this matters for a transcript-first edit
For interviews, podcasts, and documentary work, the smart move is to make your selection and story decisions on the words before you touch the NLE. You read the transcript, keep the strongest lines, cut fillers, and arrange the order. That is a paper edit, and a good one means the timeline is half finished before you open it.
ScriptCut handles that pre-edit and then exports the result so it opens as an assembled sequence in your NLE. Because each selected line carries word-level timecodes, the handoff is a real cut, not a bin of raw clips. Send XML or EDL into Final Cut Pro, Premiere, Resolve, or Avid and start refining instead of assembling. For the round-trip details, see exporting a paper edit to Final Cut and Avid and the Premiere Pro transcript workflow.
The takeaway
FCPXML is the structured, modern way to move an edit in and out of Final Cut Pro: richer than an EDL, scoped to the Apple ecosystem, and versioned. Know whether you need modern .fcpxml or legacy xmeml, expect to relink media, and do the storytelling on the transcript first so whatever XML you export is already an edit worth refining.
Sources
Frequently asked questions
What is the file extension for FCPXML?
It is .fcpxml. Recent Final Cut Pro versions also use a .fcpxmld bundle that wraps the XML with extra data while keeping the core file readable.
Is FCPXML the same as Final Cut Pro 7 XML?
No. FCPXML (.fcpxml) is the modern Final Cut Pro format. Final Cut Pro 7 XML (xmeml) is the older legacy format. Many apps read the legacy one, so always confirm which your target supports.
Can Premiere Pro and DaVinci Resolve open FCPXML?
They work with the Final Cut Pro XML family, primarily the legacy xmeml interchange. Support for the newest .fcpxml revisions varies, so check the version before relying on a clean round-trip.
FCPXML or EDL, which should I use?
Use FCPXML when you are moving a detailed timeline in or out of Final Cut Pro and want tracks, effects, and metadata to travel. Use an EDL when you only need the cuts and the widest possible compatibility.