Using Cuecraft with Premiere Pro
Last updated 3 September 2026
Cuecraft hands you a DaVinci Resolve timeline. That is a deliberate choice: the whole product ends in one file, so it aims at one application and gets that file right rather than half-right in four.
If you cut in Premiere Pro, you can still use it. There is a free three-step route that takes a couple of minutes. Here it is, with the straight explanation of why it is three steps and not one, and where the reasoning behind each cut ends up.
The short version
- 1. Export from Cuecraft as normal. You get an FCPXML file.
- 2. Open it in DaVinci Resolve, then export the timeline again as Final Cut Pro 7 XML. Resolve does the conversion.
- 3. Import that file into Premiere. File > Import, pick the XML, open it.
The free version of DaVinci Resolve is enough. It is a full download from Blackmagic Design and there is no licence to buy for this. You are using it as a converter and then closing it.
Why it takes three steps
Premiere Pro cannot import FCPXML. Not in any version. Adobe say so on their own help page for moving a Final Cut Pro project into Premiere: it is "a .fcpxml file format that Premiere cannot directly import", and the answer Adobe give there is a paid third-party converter called XtoCC. (Read 3 September 2026.)
What Premiere does read is FCP7 XML, sometimes called xmeml. That is an older and completely different format. The two share the word XML and very little else. Resolve reads the first and writes the second, which is the only reason it can sit in the middle, and it is why the free download replaces the paid converter here.
Where the reasoning lives
Every cut Cuecraft makes is explained: the camera it chose, what beat what, and how confident it was. You read those in Cuecraft itself, next to the cut they belong to, before you export anything.
They stay in Cuecraft. They do not travel into Premiere, and they do not travel into Resolve either. DaVinci Resolve does not import markers from FCPXML at all, so there is nothing for the conversion to carry forward. What reaches your editor is the cut itself: the right camera at the right moment. The reasoning is something you read in Cuecraft when you want to know why, not something you carry around in your timeline.
What actually lands in Premiere
A single video track, one clip per shot, each one pointing at your original camera file, with the master audio on its own track. No multicam clip, no nesting, nothing clever. It is the shape an assistant editor would hand you, and that plainness is exactly why it survives being passed between three applications instead of breaking somewhere in the middle. Relink the media if Premiere asks, and cut from there.
If you would pay for this without the middle step
We would rather tell you the limitation plainly than let you find it after you have paid. So: Cuecraft targets Resolve, and Premiere editors go through Resolve to get to Premiere.
If native Premiere support is something you would actually pay for, tell us. Email support@cuecraft.net with one line saying what you cut on and what it would be worth to you. We read every one, and it is the only honest way to find out whether there is real demand behind the question.