What is FCPXML?

The text file that lets other software talk to Final Cut Pro — an entire edit described in XML, without a single frame of media inside.

What does an FCPXML file actually contain?

Two things: a resources section and a structure that uses those resources. The resources section declares formats (frame size, frame rate) and assets — references to media files by location, along with their properties. The structure then describes what Final Cut should do with them: events, projects, and inside each project a spine, the primary storyline holding clips in order. Clips come in several element types — plain asset clips, multicam and sync clips, gaps, compound clips — each carrying its in and out points, connected clips, markers, keywords, ratings, roles, and notes.

One detail that surprises newcomers: FCPXML expresses time as rational fractions of a second, such as 1001/30000s, rather than decimal timecode. That's deliberate — fractions represent frame durations at rates like 29.97 fps exactly, with no rounding drift over a long timeline.

What it never contains is the media itself. An FCPXML describing an 80GB library can be a few kilobytes, because it holds only pointers and decisions. Whoever receives the file also needs access to the media — or, in the timeline-import case, Final Cut relinks to media already on disk.

How do versions and the .fcpxmld bundle work?

The format carries a version number that has stepped upward with Final Cut releases — 1.9, 1.10, 1.11, and onward — as Apple adds elements for new features. Final Cut validates imports against a DTD (a formal schema bundled inside the application), so a file that puts elements in the wrong order or targets a mismatched version can be rejected at import with a validation error. Tools that write FCPXML have to track this schema carefully; "it looks right in a text editor" is not the same as DTD-valid.

Newer versions of Final Cut also introduced .fcpxmld, a bundle variant: a macOS package — a folder the Finder presents as a single file — containing the XML document (Info.fcpxml) alongside any supporting resources the exchange needs. Functionally it plays the same role as a bare .fcpxml file; Final Cut exports and imports both.

How do third-party tools use FCPXML?

It's the doorway in and out of Final Cut for an entire ecosystem: transcription and logging tools, subtitling apps, color and audio round-trips, and AI assistants. The pattern is usually a round-trip — export FCPXML from Final Cut so an outside tool can see the project's structure, do work against it (transcribe the clips, build a selects sequence, add markers), then write a new FCPXML that Final Cut imports as a fresh timeline with everything landing in place. Because the file is small and textual, this beats re-rendering or re-transcoding media just to move an edit between applications.

Do Premiere Pro and DaVinci Resolve read FCPXML?

Only partly, and the naming trips people up. Adobe Premiere Pro does not import FCPXML; the "Final Cut Pro XML" it exchanges is the older format from the Final Cut Pro 7 era, a different XML dialect entirely. DaVinci Resolve, by contrast, imports and exports FCPXML timelines directly, alongside its own project format, AAF, and EDL. So a tool that supports "XML export" may mean either dialect — worth checking which one before assuming a file will open in your NLE.

How do you convert FCPXML to XML for Premiere Pro or Resolve?

There is no rename trick — .fcpxml and Premiere's .xml are different dialects, and changing the extension just produces an import error. The practical routes, as of August 2026:

1. Go through DaVinci Resolve — free. Resolve imports FCPXML timelines directly (File → Import → Timeline). Once the timeline is in, you can keep working in Resolve, or export it again as FCP7-style XML, AAF, or EDL — which makes the free version of Resolve a perfectly good FCPXML converter for getting a cut into Premiere.
2. Use a dedicated translator. Utilities exist whose whole job is dialect translation — Intelligent Assistance's XtoCC, for example, converts FCPXML into the Final Cut Pro 7-style XML that Premiere imports. Worth it if round-trips are a regular part of your workflow; verify current format support before buying.
3. Skip the conversion at the source. If the timeline is coming out of a tool rather than out of Final Cut itself, the cleanest fix is to have that tool speak each NLE's native dialect directly instead of exporting FCPXML and converting after.

Going the other direction — Premiere XML into Final Cut — is the same problem mirrored, and the same Resolve or translator routes apply.

Common questions