Move a Premiere Pro project to DaVinci Resolve
The .prproj becomes a native Resolve project or an XML timeline in your browser, with what carried and what needs attention stated per project. Tested on 18 real Premiere project files. Nothing is uploaded.
Start with your project file
Two routes, written from the same reading of the .prproj. Pick the one your Resolve workflow wants.
Native Resolve project (.drp) →
Every sequence as a timeline, media pool populated. File > Import Project in Resolve.
XML timeline →
One sequence into an existing Resolve project. File > Import > Timeline.
A short project converts free. Above the free cap: $7 for this project, any format of it for 24 hours. Ongoing handoffs: Studio, $19/month or $79/year for files up to 500 MB, or Pro at $9/month or $39/year up to 50 MB. All options →
How it works
- Drop the .prproj. Use the project file itself; review any source-version or compatibility warnings. It is read in your browser and never uploaded. You see each sequence with its tracks and clips before anything is written.
- Read the kept and changed line. Before you convert, the page states what this route keeps and what changes, per feature. Anything it cannot carry is named, not silently dropped.
- Convert and import. Download the .drp and use File > Import Project in Resolve, or download XML and use File > Import > Timeline. Relink the original media, then check cuts, picture and sound before delivery.
The projects it was tested on
Corpus run on 2026-09-08, including related course-project saves and editor samples: 18 files, 13 edited sequences, 251 clips and 30 transitions. Each was read by the converter, written as a Resolve project and as XML, and the Resolve project was read back and compared with decoded source metadata. Checks cover sequence rate, size and start timecode; clip names, media references, positions, source trims and constant speed; marker text and timing; and transition type and timing. Numeric comparisons use a 0.0001 tolerance; frame positions are in frames. Unspecified source values are not treated as decoded facts. Effects, pixel appearance and audio are not tested by read-back. The clip and transition totals describe the source, not confirmed transfers. Empty projects and conversion failures are separate outcomes. These are 18 files, not 18 independent customer workflows.
| Project file | KB | fps | Tracks | Source clips | Source transitions | Metadata read-back | Resolve import | Needs attention |
|---|---|---|---|---|---|---|---|---|
| Course project, build a sequence (save 1) | 558 | — | — | — | — | no edited sequence, reported | — | |
| Course project, build a sequence (save 2) | 567 | 23.98 | 3V / 3A | 6 | — | checked metadata matched | Imported, saved, reopened and rendered; scoped content check passed | 1 warnings · 1 notes
|
| Course project, transitions | 2055 | 23.98 | 5V / 4A | 41 | 3 | 5 metadata differences
| Imported, saved and reopened; playback not checked | 17 warnings · 1 notes
|
| Course project, visual effects | 2058 | 23.98 | 5V / 4A | 41 | 6 | 10 metadata differences
| Imported, saved and reopened; playback not checked | 21 warnings · 1 notes
|
| Course project, stabilised clip | 2067 | 23.98 | 5V / 4A | 41 | 6 | 10 metadata differences
| Imported, saved and reopened; playback not checked | 21 warnings · 1 notes
|
| Course project, effect presets | 2059 | 23.98 | 5V / 4A | 41 | 6 | 10 metadata differences
| Imported, saved and reopened; playback not checked | 21 warnings · 1 notes
|
| Course project, single camera card (save 1) | 599 | 23.98 | 3V / 3A | 9 | — | checked metadata matched | Imported, saved and reopened; playback not checked | 1 warnings · 1 notes
|
| Course project, single camera card (save 2) | 670 | 23.98 | 3V / 3A | 17 | 3 | checked metadata matched | Imported, saved and reopened; playback not checked | 1 warnings · 1 notes
|
| Course project, colour, 59.94 fps | 837 | 59.94 | 3V / 3A | 5 | — | checked metadata matched | Imported, saved and reopened; playback not checked | 1 warnings · 1 notes
|
| Course project, transitions, 59.94 fps | 780 | 59.94 | 3V / 3A | 5 | — | checked metadata matched | Imported, saved and reopened; playback not checked | 1 warnings · 1 notes
|
| Editor's project, no edited sequence | 23 | — | — | — | — | no edited sequence, reported | — | |
| Course project, import media (step 1) | 639 | 23.98 | 3V / 3A | 12 | 3 | checked metadata matched | Imported, saved and reopened; playback not checked | 2 warnings · 1 notes
|
| Course project, import media (step 2) | 639 | 23.98 | 3V / 3A | 12 | 3 | checked metadata matched | Imported, saved and reopened; playback not checked | 2 warnings · 1 notes
|
| Course project, import media (step 3), bins only | 500 | — | — | — | — | no edited sequence, reported | — | |
| Course project, import media (step 4), bins only | 505 | — | — | — | — | no edited sequence, reported | — | |
| Shared sample project, no edited sequence | 57 | — | — | — | — | no edited sequence, reported | — | |
| Editor's project, 29.97 fps, four audio tracks | 37 | 29.97 | 2V / 4A | 3 | — | checked metadata matched | Imported, saved and reopened; playback not checked | 4 warnings · 1 notes
|
| Editor's supercut, 18 web-video clips | 711 | 24 | 3V / 3A | 18 | — | checked metadata matched | Imported, saved and reopened; playback not checked | 8 warnings · 1 notes
|
Direct .drp import, save, reopen and render have been validated in Resolve 21 on macOS on controlled picture and audio cases. The table reports native checks for each exact output separately. One six-clip example was relinked to recovered Adobe exercise media and rendered: all 422 frames passed a reduced-resolution source-content comparison, and stereo content matched with a one-sample offset after the first cut. Other corpus playback remains unverified. This does not establish full-resolution pixel parity or sample-identical audio. Undecoded source start timecode and Resolve’s default one-hour start are disclosed separately; effects exercises also show source-out and transition metadata changes. Read-back differences need review and are not silently treated as passes.
What carries, and what needs attention
Kept on the Resolve project route: clip boundaries, clip names, multiple tracks / channels, bins and folders.
- Frame-accurate timing: per-timeline DF/NDF display and start frames are retained; unsupported DF frame rates fall back to NDF with a warning
- Media paths / reels: media remains referenced; direct playback/relink validated in Resolve 21 on macOS for SDR ProRes/H.264 and mono/stereo WAV; verified Rec.709 (Scene) and Rec.2020 PQ input overrides are retained; RAW decoding, alpha, camera LUTs, grades and project color management are not recreated
- Transitions: video cross dissolves and constant-power audio crossfades retain custom cuts, positive constant retimes and source handles; same-rate compounds, overlapping adjacent dissolves and video edge fades are supported; native title generators and unsupported speed maps remain cuts
- Adjustment layers: top-level native video adjustment clips retain timing, enabled state and supported intrinsic controls; proprietary effects, retiming and adjustment layers inside flattened nests are not mapped
- Other effects (colour, filters, variable speed): position, independent horizontal/vertical scale, rotation and opacity are written, including linear keys; static rectangular crop also retains margins and native softness; other effects are not
- Markers: timeline and visible clip markers retain positions, names, notes, ranges and native colors; clip markers are mapped through positive constant retimes; point markers become one-frame ranges, duplicate frame positions collapse, and unsupported colors become Blue
- Motion and opacity keyframes: Hold/Constant steps become editable clip sections; original keyframe controls become cut boundaries
- Clip volume and level keyframes: clip gain, channel automation, microphone-channel gain and track gain/solo are retained; normal-speed and positive constant-speed stereo clips with unequal gains use editable channel compounds that preserve the outer track layout; unsupported clocks or compound limits use hard-routed mono Left/Right lanes; mono/surround parent downmix and other mixer pan remain limited
- Constant speed changes: positive constant speeds use native time maps with source trims; positive linear speed maps become editable constant-speed segments. Curved, reverse and freeze maps remain unsupported
- Nested sequences / compound clips: inactive camera/Selector sources become named editable timelines ending in [source]; native switching controls and selection linkage are not recreated
- Audio channel layout and routing: unequal stereo gains preserve the outer track through channel-isolating compounds; positive constant retimes process the full stereo signal before channel gain; unsupported edit clocks, reverse/variable speeds or graphs exceeding native compound limits use split Left/Right lanes and change track structure
- Media frame rates and sizes: each timeline retains its own frame rate, resolution and supported native pixel shape; source pixel aspect ratios from 0.1 to 10 are preserved; out-of-range ratios and missing dimensions remain reported
- Titles (text graphics): editable static Text+ layers retain text, font, color, size and position; rich runs, alignment, animation, installed fonts and exact font metrics require review
- Track locks and mutes: track locks, mute/hidden and disabled-clip state retained; solo is not written
These are the limits of the route, stated so you can judge the risk before converting. The converter names each one for your specific file in the kept and changed line, and the capability table holds the same facts for every route on the site.
FAQ
Do I need Premiere Pro installed?
No. The converter reads the .prproj file itself, including projects saved by a newer Premiere than you have. That is the point: rescuing a timeline from a project you cannot open is where "export XML from Premiere" fails.
What does "tested on real projects" mean here?
Every real Premiere project file we hold, course projects and editors' own, was read by the converter, written as a Resolve project and as XML, and the Resolve project was read back and compared with decoded source metadata, including individual clip positions and trims. Differences are reported separately from failed conversions and empty projects. The table lists each file and what it flagged. Direct .drp import, save, reopen and render have been validated in Resolve 21 on macOS on controlled cases; the table records native import checks separately for the exact converted files. One six-clip example was relinked to recovered Adobe exercise media and passed a scoped render content check. Other corpus playback remains unverified.
What carries over, and what does not?
Sequences become timelines with their tracks, cuts, clip names, media paths, markers, dissolves and crossfades, and supported keyframes. Titles arrive as basic text, Premiere effects are listed by name rather than converted, Bezier curves are sampled, and media in containers Resolve playback has not been validated for is flagged for relinking. The kept and changed line on the converter is the exact list for your file.
What does it cost?
A short project converts free. Above the free cap a project is $7, paid once, and that file converts to any format for 24 hours. Regular handoffs are covered by Pro at $9 a month or $39 a year up to 50 MB, and Studio at $19 a month or $79 a year up to 500 MB.
Which should I pick, the Resolve project or XML?
The .drp when you want the whole project to arrive at once, every sequence as a timeline, media pool populated. XML when you want to add one timeline to an existing Resolve project. Both are written from the same reading of your file.
Does this work with free DaVinci Resolve?
Yes. Free Resolve imports both .drp projects and FCP7 XML timelines. No Studio licence is required.
Related tools & converters
- Premiere to Resolve projectThe .drp converter, with the kept and changed line for your file.
- Premiere to XMLThe XML route into an existing Resolve project.
- Checked handoff walkthroughBoth routes, the Resolve import menus, and relinking.
- Resolve to PremiereThe other direction: a .drp into Premiere as XML.
- Premiere to Avid AAFThe same handoff into Media Composer.
- What survives each conversionThe full capability table behind these pages.