Convert PRPROJ to XML

No, and that is the point. The converter reads the .prproj file itself, so you can rescue a timeline from a project without a Premiere licence, an expired trial, or a version that will not open the file. It also sidesteps Premiere crashing on File > Export > Final Cut Pro XML, because Premiere is never opened.

Sequences, tracks, clip timing, source in and out points, names and media paths, bins, markers, track locks, clip gain and start timecode, along with cross dissolves and dips, constant speed changes, nested sequences, the selected multicam angle and basic titles. On 13 real Premiere projects, 97% of the 811 inspected elements match exactly. This is not a complete Premiere round-trip: check the report for what each file lost and compare effects, titles and audio after import.

FCP7 XML carries one sequence into an existing project in Resolve, Premiere or a conform tool, and is what most people mean by "the XML". A native Resolve project (.drp) carries every sequence and the media pool into Resolve in one import. FCPXML is for current Final Cut Pro. All three are written from the same reading of your .prproj, and a paid project converts to any of them for 24 hours.

In Resolve, choose File > Import > Timeline, select the converted .xml, and pick your import options. Resolve relinks the clips to your media files by path or by name; have the source media available for a full conform. The Premiere to Resolve page shows the exact results per test project.

Lumetri colour, Warp Stabilizer, blur and other effects, which FCP7 XML cannot describe and which Resolve rebuilds on its own pages. Speed ramps become constant-speed segments, eased keyframes become linear or held ones, and audio track routing is folded into clip gain. Each omission is listed in the conversion report so nothing disappears silently.

Projects saved by Premiere Pro CS6 through Premiere Pro 26 have been read and converted, including the 2026 multicam project structure. Earlier projects from CS3 to CS5 and Premiere 1.5 use a different internal layout that has not been tested. Use the preview and warnings to check your file rather than assuming.

Yes. Each source clip keeps its own frame rate and dimensions, nested sequences are written as nested sequences, and a multicam clip is written as the angle you selected. Processed or retimed nests are flattened to their visible edits, and the report says when that happened.

No. The .prproj is read and the XML is written in your browser tab. Media never leaves your disk, and the XML references it by the paths already in the project, so Resolve or Premiere relinks to the files you have.

A Premiere project up to 500 KB converts free, signed in or not. Above that, $5 converts this project to XML, .drp, FCPXML or AAF for 24 hours, or $15 for a project between 50 MB and 500 MB. Regular handoffs are covered by Pro at $9 a month for files up to 50 MB, or Studio at $19 a month up to 500 MB. See pricing.

Synthetic media (adjustment layers, Black Video, colour mattes) has no file on disk, so those clips are exported with their name and timing but no path, and you will see a note in the conversion warnings. Everything cut from real footage keeps its full path.

A project with no edited sequences has nothing to convert (the converter reads timelines, not bins). If your project does have sequences and still fails, the structure may be unusual. Get in touch via the About page and we will look at it.