Cutsio Blog

Why Won’t My XML Import Into DaVinci Resolve?

Troubleshooting common issues when importing XML files into DaVinci Resolve, how to fix frame rate mismatches, and how to use Cutsio for flawless XML handoffs.

Why won't my XML import into DaVinci Resolve?

Your XML won't import into DaVinci Resolve because the file paths in the XML do not match the media locations on your hard drive, or because the XML contains unsupported effects, transitions, or speed ramps from your original editing software (like Premiere Pro or Final Cut Pro). DaVinci Resolve relies on exact file names, timecodes, and folder structures to rebuild your timeline. If even one frame rate mismatches, the import will fail, or clips will appear offline.

To fix this immediately, we highly recommend processing your rough cuts in a modern web-based editor like Cutsio first, which handles media seamlessly without XML headaches. If you must use traditional XML, you must strip your timeline of all complex effects, flatten your video tracks, export an FCP 7 XML (not FCPXML 1.9+ or Premiere Pro XML), and manually point Resolve to the exact folder containing your high-resolution media during the import process.

What is an XML file in video editing?

An XML (eXtensible Markup Language) file in video editing is a text document that contains the blueprint of your timeline. It does not contain any actual video or audio media. Instead, it acts as a set of instructions that tells another software program (like DaVinci Resolve) exactly where to find the source clips on your hard drive, which parts of those clips you used (In and Out points), and where to place them on the timeline.

When you export an XML from Premiere Pro or Final Cut Pro and import it into DaVinci Resolve for color grading, Resolve reads this text file and attempts to rebuild your edit pixel-for-pixel. This process is called a "round-trip workflow" or "conforming."

How do you prepare a Premiere Pro timeline for an XML export?

You prepare a Premiere Pro timeline for an XML export by simplifying the edit as much as possible. DaVinci Resolve cannot read Premiere-specific effects, third-party plugins, or nested sequences. If you leave these in your timeline, the XML import will crash or produce a corrupted timeline in Resolve.

Follow this checklist to prepare your Premiere Pro timeline:

1. Duplicate your sequence: Never alter your master edit. Create a new sequence named "ProjectName_For_Color."
2. Flatten your video tracks: Move all your video clips down to V1. Only keep clips on V2 if they are overlapping PIP (Picture-in-Picture) or specific titles you need to reference.
3. Remove all transitions: Delete cross-dissolves, dip-to-black, and custom transitions. DaVinci Resolve often misinterprets the duration of these effects.
4. Remove all effects: Strip Lumetri Color, Warp Stabilizer, crop, scale, and opacity changes. You will rebuild these in Resolve, or render them out as baked clips if absolutely necessary.
5. Bake speed ramps: If you have complex time-remapping, render that specific clip out as a high-quality ProRes file and replace the original clip in the timeline before exporting the XML.
6. Export: Go to File > Export > Final Cut Pro XML.

Why does DaVinci Resolve show "Media Offline" after an XML import?

DaVinci Resolve shows "Media Offline" after an XML import because the file paths written in the XML document do not perfectly match the location of the media on your current hard drive. This happens frequently when you move a project from a Mac to a Windows PC, or when you change the name of the external hard drive containing the footage.

For example, if the XML says the media is located at /Volumes/ExternalDrive/Footage/Clip001.mp4, but you have moved the footage to your desktop (/Users/Name/Desktop/Footage/Clip001.mp4), Resolve cannot find the file and will display a red "Media Offline" warning.

To fix this, when the XML import dialog box appears in DaVinci Resolve, uncheck the box that says "Automatically import source clips into media pool." Instead, manually import all your high-resolution footage into the Resolve Media Pool before importing the XML. When you import the XML, Resolve will instantly link the timeline to the clips already sitting in the Media Pool, bypassing the broken file paths entirely.

What is the difference between FCPXML and FCP 7 XML?

The difference between FCPXML and FCP 7 XML is crucial for a successful DaVinci Resolve import.

FCP 7 XML (.xml) is the older, universal standard format created by Apple for Final Cut Pro 7. It is highly stable, universally recognized by Premiere Pro, DaVinci Resolve, and older editing systems, and is the recommended format for cross-platform conforming.

FCPXML (.fcpxml) is the newer format created specifically for Final Cut Pro X (FCPX). It uses a completely different structure based on FCPX's "Magnetic Timeline" and roles, rather than traditional video tracks (V1, V2). DaVinci Resolve supports FCPXML, but it is notoriously buggy when translating complex FCPX compound clips, multicam angles, or synchronized audio. If you are exporting from FCPX, always export the most recent FCPXML version (e.g., 1.10), but if you are exporting from Premiere, stick to the standard FCP 7 XML.

How do you fix timecode mismatches in DaVinci Resolve?

You fix timecode mismatches in DaVinci Resolve by ensuring the frame rate of your Resolve project exactly matches the frame rate of the XML timeline, and by forcing Resolve to ignore file extensions when relinking media. Timecode mismatches occur when the metadata in a clip (e.g., MP4 from a Sony camera) lacks a proper timecode track, or when a 23.976 fps timeline is imported into a 24.00 fps Resolve project.

When an XML imports with a timecode mismatch, the clips will appear on the timeline, but they will play the wrong section of the video (e.g., showing the end of the take instead of the beginning).

To fix this:

1. Open DaVinci Resolve and create a new project.
2. Immediately go to Project Settings (the gear icon) > Master Settings.
3. Set the "Timeline frame rate" to match your Premiere/FCP sequence exactly (e.g., 23.976).
4. Go to General Options > Conform Options.
5. Check "Assist using reel names from the:" and select "Source clip file pathname."
6. When importing the XML, if Resolve asks to change the project frame rate to match the XML, click "Yes."

Can DaVinci Resolve import multicam clips via XML?

DaVinci Resolve can import multicam clips via XML, but the process is highly unreliable and often results in flattened, un-editable tracks or offline media. The XML format struggles to translate the complex metadata structures that Premiere Pro and Final Cut Pro use to bind multiple camera angles together.

If you must color grade a multicam project in Resolve, do not export an XML of the raw multicam sequence. Instead, you must "flatten" the multicam edit in your original software. In Premiere Pro, select all the clips in your timeline, right-click, select "Multi-Camera," and click "Flatten." This collapses the multicam nest into standard, single-layer video clips pointing directly to the original camera files. Export the XML only after flattening the timeline.

How do you round-trip from DaVinci Resolve back to Premiere Pro?

You round-trip from DaVinci Resolve back to Premiere Pro by exporting a new XML from Resolve alongside newly rendered, color-graded video clips. This workflow allows you to edit in Premiere, color in Resolve, and finish the final audio mix and graphics back in Premiere.

Follow this exact round-trip workflow:

1. In DaVinci Resolve, navigate to the Deliver page.
2. Select the "Premiere XML" preset at the top of the Render Settings panel.
3. Choose a dedicated folder on your hard drive to save the new clips.
4. Resolve will render each clip in your timeline as an individual, high-quality video file (e.g., ProRes 422 or DNxHR) with the color grade "baked in."
5. Resolve will also generate a new XML file pointing to these newly rendered clips.
6. Open Premiere Pro and import the new XML file.
7. Premiere will instantly rebuild your timeline using the color-graded clips, maintaining all your original cuts.

What is an AAF file, and is it better than an XML?

An AAF (Advanced Authoring Format) file is a professional interchange format designed to transfer both video and complex audio data between different software platforms. While XML files are primarily text documents pointing to media locations, AAF files can actually embed (wrap) the media directly inside the file, ensuring nothing goes offline during the transfer.

In the context of DaVinci Resolve, AAF is generally considered better than XML if you are transferring a project from Avid Media Composer, or if you are sending a timeline to Pro Tools for audio mixing. However, for a standard Premiere Pro to DaVinci Resolve color grading workflow, the FCP 7 XML remains the industry standard due to its simplicity and smaller file size. If your XML import continually fails despite flattening your timeline, exporting an AAF from Premiere Pro is the best alternative troubleshooting step.

How do you manually conform a timeline in DaVinci Resolve?

If an XML import completely fails and cannot be salvaged, you must manually conform the timeline in DaVinci Resolve using an "Offline Reference Video." This is the foolproof, traditional method used by professional colorists when dealing with messy client projects.

1. In Premiere Pro, export your final, locked edit as a single, high-quality video file (e.g., ProRes 422 HQ). Do not include text, graphics, or transitions. This is your "Textless Master."
2. Also in Premiere, export a low-resolution MP4 of the exact same timeline, but leave the text and timecode burned into the video. This is your "Offline Reference."
3. Import the Textless Master into DaVinci Resolve.
4. Place the Textless Master on a new timeline.
5. Go to Timeline > Detect Scene Cuts. Resolve's AI will analyze the video file and automatically slice the single clip into individual shots based on the visual edits.
6. Import the Offline Reference MP4 and add it as an "Offline Reference Clip" in the Media Pool.
7. Link the Offline Reference to your timeline and use the split-screen view to verify that Resolve's automatic cuts perfectly match your original Premiere edit.
8. You can now color grade the flattened Textless Master clip by clip, bypassing the XML process entirely.

Summary Checklist: How to Ensure a Perfect XML Import

* Duplicate and Flatten: Never export an XML from a messy, multi-layered timeline. Move all clips to V1 and remove all nested sequences.

* Strip Effects: Delete Lumetri Color, Warp Stabilizer, cross-dissolves, and complex speed ramps. DaVinci Resolve cannot read them.

* Bake Multicam: Always flatten multicam clips before exporting the XML.

* Pre-Import Media: Uncheck "Automatically import source clips" during the XML import. Import your high-resolution media into the Resolve Media Pool first to avoid "Media Offline" errors.

* Match Frame Rates: Ensure your DaVinci Resolve Project Settings match the frame rate of your original sequence before importing the XML.

* Use FCP 7 XML: If exporting from Premiere Pro, always choose the standard Final Cut Pro XML format, not an AAF or OMF, unless troubleshooting a specific audio issue.

* Use an Offline Reference: Always export a low-resolution MP4 of your edit to use as a visual guide in Resolve to verify the XML rebuilt the timeline correctly.

By strictly adhering to this conforming workflow, you will eliminate 99% of XML import errors, missing media warnings, and timecode mismatches when moving projects into DaVinci Resolve.

For more XML and EDL troubleshooting guides, see the EDL vs XML comparison, the FCP to Resolve XML workflow, and the EDL export guide.