How to Import FCPXML into Premiere Pro

You exported an edit as .fcpxml, dropped it on Premiere Pro, and got "file format not supported." Nothing is broken. Premiere has simply never supported the modern Final Cut Pro exchange format — and the fix takes about two minutes once you know which route you are on.

What an FCPXML file actually is

An .fcpxml file is a text file describing a timeline: which clips are used, their in and out points, their order, and basic effects. It contains no media — just instructions that point at media files. It is the interchange format Final Cut Pro uses today, and tools across post-production (including FrameQuery's NLE export) write it because Final Cut reads it natively.

The confusion comes from its older sibling. Before .fcpxml existed, Final Cut Pro 7 used a different XML schema with a plain .xml extension. That legacy format outlived FCP7 itself: Premiere Pro, DaVinci Resolve, and most post tools still read FCP7 XML as a de facto interchange standard. Premiere imports .xml. Premiere does not import .fcpxml. Every method below is just a way of crossing that gap.

Route 1: Convert with DaVinci Resolve (free)

The free version of Resolve is a fully capable FCPXML converter:

1. Open any project in Resolve, then use File → Import → Timeline and select your .fcpxml. Resolve builds the timeline, relinking to the referenced media (point it at your media folder if it asks).
2. Check the timeline plays and the cuts look right.
3. Export it in the legacy format: File → Export → Timeline, and choose Final Cut Pro 7 XML (.xml) as the type.
4. In Premiere Pro: File → Import, select the exported .xml. Premiere rebuilds the sequence; relink media if prompted (right-click the offline clips → Link Media).

Expect timeline structure — clips, order, in/out points, basic transitions — to survive. Effects, color, retimes, and titles generally do not translate between NLEs in any XML workflow; plan to rebuild those.

Bonus: if your actual destination is Resolve rather than Premiere, you are already done at step 1 — Resolve consumes .fcpxml directly, no conversion needed.

Route 2: Convert with XtoCC (paid, more faithful)

XtoCC (Intelligent Assistance) is a purpose-built converter that translates FCPXML into Premiere-compatible XML. It preserves more edit metadata than a Resolve round-trip and is the tool professional facilities reach for when FCPXML-to-Premiere handoffs happen regularly. If this is a one-off, use the free Resolve route; if it is weekly, XtoCC pays for itself in relink time.

Route 3: Export Premiere-native XML at the source

The cleanest fix is not converting at all. If the .fcpxml came from a tool that offers multiple export formats, re-export in Premiere's own format. FrameQuery, for example, exports search results and selects as FCPXML for Final Cut, Premiere XML for Premiere Pro, and EDL for DaVinci Resolve — so a selects reel headed for Premiere never touches the conversion problem, and dialogue selects built from a transcript search drop straight into a Premiere bin.

Which route to take

| Your situation | Route | | --- | --- | | One-off .fcpxml from a collaborator | Resolve round-trip (free) | | Regular FCP → Premiere handoffs | XtoCC | | Destination is Resolve, not Premiere | Import the .fcpxml directly | | The .fcpxml came from FrameQuery | Re-export as Premiere XML instead |

One habit that prevents the whole problem: when a collaborator asks for "an XML," ask which NLE they are cutting in before exporting. "XML" means .fcpxml to a Final Cut editor and FCP7 .xml to a Premiere editor, and the two are not interchangeable — as you now know firsthand.