How to convert a Premiere Pro project to DaVinci Resolve
By Greg Thompson, Founder, CutConvertPublished Updated
There are two working routes from a Premiere Pro project to DaVinci Resolve, and neither requires opening Premiere. The direct route: convert the .prproj straight to a native Resolve .drp project and import it with File → Import Project. The classic route: convert the .prproj to FCP7 XML and import one timeline at a time. Both read the .prproj file itself, so they work when Premiere isn't installed, the license lapsed, or the project predates the version you have. This guide covers both, and when to pick which.
Why there's no built-in path
Premiere has no "export for Resolve" and Resolve can't read a .prproj. Adobe's project format is undocumented and version-locked. The traditional escape hatch is opening the project in Premiere and exporting Final Cut Pro XML, which assumes a working Premiere. If that's exactly what you don't have (the freelancer's classic: a client hands over a .prproj and the media, and you cut in Resolve), a converter that reads the .prproj directly is the way through.
Route 1: .prproj → .drp (native Resolve project)
The prproj to DRP converter rebuilds your Premiere sequences as a DaVinci Resolve project file:
- Drop the .prproj on the converter. Use the project file itself, no export needed. The converter decompresses and parses it, and you'll see each sequence with its tracks and clips before converting.
- Convert. Sequences become Resolve timelines inside a .drp project archive, with tracks, cuts, clip names, media paths, and frame rate carried over. Multiple sequences arrive as multiple timelines in one project.
- Import in Resolve. In the Project Manager, right-click → Import Project (or File → Import Project), pick the .drp, and open it. Works in free Resolve and Studio alike.
- Relink media. The timeline references your files by their original paths. Point Resolve at the original media, then compare cuts, picture and sound before relying on the handoff.
Timelines with different frame rates or dimensions are written into separate DRP projects. Open each corresponding output and inspect its report; differently rated timelines are not silently omitted.
Route 2: .prproj → FCP7 XML
The prproj to XML converter writes the veteran interchange format instead. In Resolve: File → Import → Timeline → select the .xml. You get one sequence per import into the currently open project, rather than a whole project arriving at once. Pick this route when you want the timeline added to an existing Resolve project, or when you also want a file that Premiere itself can re-import.
What carries over, and how to check it
The route and the source edit determine what survives. Supported tracks, cuts, media references, markers, transitions, motion, audio controls and nested edits can transfer, but unsupported effects, speed maps, title styling and channel routing can require recreation. Read the warnings for your file rather than assuming the two routes produce identical results.
The handoff evidence table separates converter read-back from native Resolve acceptance. It includes related course-project saves and editor samples. Source clip and transition counts describe the inputs; they are not proof of visual or audio fidelity. One six-clip example has a scoped render comparison using recovered Adobe exercise media. Other corpus files remain unverified for playback even where native import, save and reopen succeed.
For a concrete six-clip example and the complete import, relink and playback checklist, follow the checked Premiere-to-Resolve walkthrough.
FAQ
How do I convert a Premiere project to DaVinci Resolve? Convert the .prproj file directly: to a native .drp project (import via File → Import Project in Resolve) or to FCP7 XML (import via File → Import → Timeline). Neither route needs Premiere installed.
Which should I choose, .drp or XML? .drp when you want the whole project to arrive at once, all sequences as timelines, media pool populated. XML when you want to add one timeline to an existing Resolve project, or keep a file Premiere can also re-import. When in doubt, .drp into a fresh project is the cleaner start.
Do I need Premiere Pro installed? No. The converters read the .prproj file itself. That's the main reason to use them: rescuing a timeline from a project you can't open is exactly the situation where "export XML from Premiere" fails.
Will my effects and transitions come across? Support depends on the route and the individual edit. Supported dissolves, fades, motion and audio controls can transfer; some transitions are approximated and unsupported effects need recreation. Read the per-file warnings and verify playback in Resolve. A successful import does not establish identical rendering.
Does this work with the free version of DaVinci Resolve? Yes. Free Resolve imports both .drp projects and FCP7 XML timelines. No Studio license required.
What about going from Resolve back to Premiere? The reverse direction works too: convert the .drp to XML and import it into Premiere. The full walkthrough is in the open a Resolve project in Premiere guide.
Greg Thompson · Founder, CutConvert
Greg builds CutConvert, the post-production file converter — including the first working decoder for Premiere Pro’s binary .prtranscript format. He writes these guides from the format specs and real editor workflows.