Premiere Pro to DaVinci Resolve: AI-Powered Cross-NLE Workflows

The Cross-NLE Context

Many professional video workflows split between two NLEs: Premiere Pro for editorial and DaVinci Resolve for color grading. Premiere has the editing chops and the AI tool ecosystem. Resolve has the color tools that no other NLE matches. Round-tripping between them is one of the most established cross-NLE workflows in modern post-production.

Adding AI tools to this workflow introduces a new constraint: the AI's metadata layer (transcripts, markers, custom fields) needs to survive multiple format conversions. AI generates content in Premiere, you cross to Resolve for color, you cross back to Premiere for finishing. Each conversion is a chance for AI metadata to degrade.

The good news is that the most important AI contributions -- bin structure, sequences, and transcript markers as comment text -- survive XML round-tripping reliably. The less good news is that custom searchable metadata fields generally do not. Plan the workflow around what survives rather than fighting to preserve everything.

For some workflows, the answer is to keep editorial work entirely in Premiere and send only the locked sequence to Resolve. AI metadata becomes a Premiere-side asset that does not need to cross to Resolve at all. The locked sequence is colored in Resolve and returns to Premiere for delivery, with AI metadata still intact in the Premiere project.

End-to-End Workflow

The typical AI-plus-cross-NLE workflow runs in five phases.

This workflow keeps the AI metadata layer in Premiere where it lives natively. The Resolve trip is purely about color, and only the locked sequence (not the bins, markers, or metadata) crosses over. The AI's contributions persist in your original Premiere project regardless of what happens in Resolve.

XML Export from Premiere

The XML export step from Premiere has a few configuration choices that matter for cross-NLE workflows.

Before exporting, prepare the sequence:

• Flatten unnecessary nesting. Resolve handles nested sequences but the conversion is sometimes lossy. If you have nested sequences in your edit, consider flattening them with a single Render and Replace before exporting XML.
• Resolve any plugin effects. Premiere-specific plugins do not survive XML. Either render and replace those effects or note them so you can reapply on return.
• Disable any pending Lumetri color. If your editorial cut has color treatments applied, decide whether they should travel to Resolve. Usually you want to remove them and let Resolve do all the color from scratch.
• Verify all media is online. Offline clips export as gaps in XML. Relink everything before exporting.

To export: select the locked sequence in the project panel. File > Export > Final Cut Pro XML. Choose a location and name. Premiere generates the XML in a few seconds.

The XML file is text-based and small. You can open it in a text editor to verify it contains your sequence. The file references your media by absolute path, which means Resolve needs access to the same media at the same paths (or relink during import).

Importing into DaVinci Resolve

In DaVinci Resolve, you can either import the XML into an existing project or create a new project around it.

For a new project: Open Resolve. Create a new project (File > New Project). In the project, choose File > Import Timeline > Import AAF, EDL, XML. Select your XML file. Resolve prompts for import options.

Common import options:

• Frame rate: Match the XML's source frame rate. Mismatch causes conform that affects edit timing.
• Timeline resolution: Match the XML or set explicitly. Mismatch causes scaling.
• Clip handles: Adds extra frames before and after each clip's in/out points. Useful if you might want to extend cuts during color. 12 frames is a typical default.
• Automatically import source clips: Yes, unless you want to manually link to media.

Click OK. Resolve imports the XML, creating the timeline and importing the source clips it references. You may need to relink media if the XML's paths differ from your local paths -- Resolve has a Media Pool relink feature similar to Premiere's.

What you should see after import: your timeline with all cuts in place, source clips in the Media Pool, and (in most cases) markers carrying transcript text from the AI. What you should not see: bin structure from Premiere (Resolve flattens it on import), color labels (XML does not preserve them), and most custom metadata fields.

Color Grading Phase

Color grading is Resolve's strength, and how you grade is up to you. Common patterns:

Primary correction first. On the Color page, use the Primaries Wheels and Curves to set baseline exposure, white balance, and contrast for each clip. This typically takes 5 to 15 minutes per scene depending on shot count and complexity.

Shot matching. Use Resolve's color matching tools to make sequential shots look consistent with each other. The auto-match feature is decent for simple cases; expect to refine manually for cinematic work.

Creative looks. Apply LUTs or build creative grades that match the project's intended visual style. Resolve has extensive built-in LUTs and supports third-party LUT packs.

Render output. Once grading is complete, you have two options: render the graded sequence as a flat video file (simpler), or export an XML that brings the grade back to Premiere (more flexible).

The Return Trip to Premiere

Bringing the graded sequence back to Premiere has two common patterns, each with different tradeoffs.

Pattern A: Flat graded video. Render the graded sequence from Resolve as a high-quality master file (ProRes 4444 or DNxHR HQX). Import that file into your Premiere project as a single clip. Drop it onto a sequence as your master, layer in graphics and audio finishing on top.

Pros: simple, reliable, no XML round-trip issues. Cons: you cannot re-cut without going back to Resolve, the graded clip is monolithic.

Pattern B: XML import of graded timeline. Export an XML from Resolve after grading. Import that XML into your Premiere project. The timeline imports with grade information attached to each clip. You can re-cut, add graphics, and finish in Premiere with the grade preserved.

Pros: flexible, supports continued editorial work. Cons: XML round-tripping color information has known fidelity issues; some grades may not look identical to how they did in Resolve.

Pattern A is the right choice for most projects. The simplicity outweighs the flexibility loss for the vast majority of editorial workflows. If your project has a lot of post-color editorial changes (common in narrative or documentary work), Pattern B is worth the additional complexity.

Either way, the AI metadata in your original Premiere project is unaffected. The bins, markers, custom fields, and rough cut you started from are still there. The graded sequence is added alongside, not replacing.

What AI Metadata Survives

Here is what crosses from Premiere through Resolve and back, in practice.

The pattern: the structural data survives, the custom metadata layer does not. This is why keeping AI editorial work in Premiere (and only sending locked sequences to Resolve) is the right approach. The metadata that makes AI useful -- searchable transcripts, custom fields, bin organization -- never has to cross the NLE boundary.

If your workflow requires AI editorial work to survive in Resolve (you want to use Resolve for the editorial pass too), the metadata gap is real. There is no good cross-NLE format that preserves custom metadata fields cleanly. Either keep AI editorial in Premiere, or accept the metadata loss when you cross to Resolve.

Troubleshooting Cross-NLE Issues

Cross-NLE round trips have several common failure modes.

For frame rate issues, the rule is to set every project's frame rate explicitly to match the source media. Letting Resolve auto-detect frame rate from XML import sometimes produces 23.976 vs 24.00 ambiguity that causes subtle drift.

For color space mismatches, set both Premiere's working color space and Resolve's color science to the same target. Rec. 709 SDR is the safest default for non-HDR work. For HDR, both apps support Rec. 2020 with HDR10 metadata.

For multicam complications, the cleanest path is to flatten multicam clips before XML export from Premiere. Right-click the multicam clip > Multi-Camera > Flatten. This produces a single track that XML handles cleanly. The downside is losing the ability to switch angles in Resolve, but Resolve is for color anyway, not editorial. For more on AI workflow context, see our pieces on AI editing tools for DaVinci Resolve and the complete AI workflow for Premiere Pro.

Frequently asked questions