How to move a Final Cut Pro project to Premiere Pro

To move a project from Final Cut Pro to Premiere Pro, export the project as FCPXML from Final Cut, convert that FCPXML into a Premiere-readable XML (the older FCP7 XML format), then import the XML into Premiere and conform it against a reference render. Premiere cannot open a Final Cut library, and it does not read FCPXML directly, so the conversion step is the part people miss. What travels is the edit itself: clips, in and out points, track order and simple transitions. Effects, grades, styled titles and some audio work need to be rebuilt on the Premiere side.

The steps below cover the two common conversion routes, how to prepare the Final Cut timeline so less breaks, and how to check the result before anyone starts working on it.

Why there is no direct route

Final Cut Pro and Premiere Pro describe a timeline in different ways. Final Cut uses a magnetic primary storyline with connected clips, secondary storylines and roles. Premiere uses numbered video and audio tracks. A converter has to turn connected clips into tracks and roles into track assignments, and it has to make choices along the way.

Each app also has its own exchange format. Final Cut writes FCPXML. Premiere reads and writes the older FCP7 style XML, plus EDL and AAF. Neither app speaks the other's native format, so something in the middle has to translate. If you want the broader background on these formats, our guide to moving a cut between Premiere, Resolve and Final Cut explains what each one carries.

Step 1: prepare the Final Cut project

A cleaner timeline converts more predictably. Do this on a duplicate of the project, named for the handoff, so your working version stays untouched.

1. Get the media out of the library. If your media is managed inside the Final Cut library, Premiere will struggle to find it. Use Final Cut's consolidate option to copy the media to a normal folder outside the library, then make sure the receiving editor can reach that folder.
2. Break apart what you do not need live. Compound clips and multicam clips can arrive flattened, nested or partly missing. If the Premiere editor does not need to change angles, break them apart or render them first.
3. Render speed ramps and complex effects. Retiming curves and third-party effects rarely survive. A rendered clip is just a clip, and it will come across cleanly.
4. Put titles and graphics on their own lane. They usually arrive as placeholders or disappear. Keeping them separate makes them easy to find and rebuild.
5. Assign roles to all audio. Many converters use roles to decide which audio track a clip lands on. Dialogue, music and effects roles give you a sensible track layout in Premiere.
6. Export a reference render. Share a master of the whole timeline with burnt-in timecode if you can. This is the file you will compare against later.

Step 2: export FCPXML from Final Cut Pro

Select the project in the browser, then use File, Export XML. Final Cut writes an .fcpxml file (or an .fcpxmld bundle in recent versions). If you are offered a choice of FCPXML version, pick the one your converter documents as supported. Converters lag behind Final Cut releases, so an older FCPXML version is sometimes the safer pick. Check the converter's release notes.

Step 3: convert to a Premiere-readable XML

There are two routes most editors use.

Route A: a dedicated converter

Third-party tools exist that read FCPXML and write the FCP7 style XML Premiere imports. Intelligent Assistance publishes one of the better known options for this job. These tools are built for this exact conversion, they usually handle roles and connected clips with more care, and they often write a log of what they changed. They are typically paid apps, so check the vendor's current pricing and make sure the tool supports your Final Cut version.

Route B: through DaVinci Resolve

If you already have DaVinci Resolve, you can use it as a translator. Import the FCPXML into Resolve as a timeline, check that the media links, then export the timeline as an FCP7 XML for Premiere. This costs nothing extra if you have Resolve installed, but it is a double translation: Final Cut to Resolve, then Resolve to Premiere. Each hop can drop or reinterpret something, so the reference render matters even more on this route.

What about EDL and AAF?

An EDL is a useful safety net for a colourist or online editor, but it carries one video track per list and almost no audio detail, so it is not a good way to move a whole project. AAF matters for sound turnovers to Pro Tools rather than for a picture handoff to Premiere. Final Cut does not write either format on its own, so you need a third-party tool or an intermediate app such as Resolve if a recipient asks for one.

Step 4: import into Premiere and conform

In Premiere, use File, Import and select the converted XML. Premiere creates a bin with the sequence and its clips. If clips come in offline, relink them to the consolidated media folder from Step 1.

Then verify the cut instead of trusting it:

1. Check that the sequence frame rate, resolution and start timecode match the original project.
2. Put the reference render on the top video track and toggle it or use a difference blend. Any frame that is not black has drifted.
3. Walk every speed change, freeze frame and transition.
4. Check scale and position on any clip whose source resolution differs from the timeline. Final Cut's spatial conform settings do not always map one to one.
5. Listen through the audio, especially long takes and anything that was retimed. Check that clips landed on the tracks you expect.
6. Save a version of the Premiere project before creative work starts on the new side.

What you will rebuild

Plan for these, whichever route you used:

• Colour. Grades from Final Cut do not translate. Regrade in Premiere, and if the look was built on a LUT file, send that LUT so it can be reapplied in Lumetri.
• Titles and generators. Final Cut titles and Motion templates are specific to Apple's apps. Rebuild them with Premiere's tools.
• Effects and plug-ins. Built-in effects map poorly between the two. Third-party plug-ins need to be installed on the Premiere side and reapplied.
• Audio effects and levels. Basic clip levels often survive. Audio effects, keyframed mixes and role-based routing usually need another pass.
• Multicam. If you did not break multicam apart, expect to check every angle cut by eye.

Writing these down in a short handoff note, next to the XML and the reference render, saves the receiving editor from discovering them one by one. If you are still weighing which app the project should end up in, our Final Cut Pro vs Premiere Pro comparison covers the day-to-day differences.

Where cinemaOS fits

cinemaOS is a Mac-native editor for Apple silicon, and it can act as a checkpoint in the middle of a handoff. It imports an XML or EDL cut, conforms it against your media and gives you a conform report that shows whether the media is online and the edits are preserved, with any warnings. You see problems in writing before anyone starts working on the timeline.

From there it can export the cut as FCPXML or EDL, with a saved report that flags things like audio roles, timecode and track layout. Premiere does not import FCPXML, so for a Premiere recipient the converter routes above remain the direct path. Whatever you send, check the result in the receiving application: a clean export report proves the file was written, not that Premiere will read it identically. cinemaOS also does not open .prproj files directly, so when a Premiere editor sends work back, ask for an XML export.

The import a cut tutorial shows the import, conform report and export in about a minute. If you also need to look inside a Premiere project you received without owning Premiere, see how to open a Premiere project without Premiere.

FAQ

Can Premiere Pro open a Final Cut Pro library directly?

No. Premiere cannot open a .fcpbundle library and does not import FCPXML directly. Export FCPXML from Final Cut, convert it to an FCP7 style XML with a dedicated converter or through DaVinci Resolve, then import that XML into Premiere.

Why are my clips offline after importing the XML into Premiere?

Usually because the media was managed inside the Final Cut library, or the media paths on the receiving machine differ from the original. Consolidate the media to a normal folder before exporting, then relink in Premiere to that folder.

Will my Final Cut titles and colour grade come across?

Generally not. Titles, Motion templates, grades and most effects are stored differently in each app and arrive as placeholders or not at all. Move the edit first, then rebuild titles and regrade in Premiere, using the reference render as your guide.