Cutsio Blog

Best Export Settings for XML in Final Cut Pro

Avoid translation errors by using the correct FCPXML export settings in Final Cut Pro when handing off projects to other editing software.

Final Cut Pro utilizes a proprietary version of XML known as FCPXML. Because Apple updates this format frequently, choosing the wrong export setting can cause compatibility issues with DaVinci Resolve, Premiere Pro, or logic Pro.

Here are the best export settings for XML in Final Cut Pro.

Accessing the Export Menu

  1. Select your specific Project (timeline) in the Browser. (Do not select the whole Event unless you intend to export the entire library structure).
  2. Go to File > Export XML...

Choosing the FCPXML Version

This is the most critical decision. The dialogue box will present a "Metadata View" and an "XML Version" dropdown.

Current Version (e.g., 1.11, 1.12 or Latest): Use the latest version only* if you are absolutely certain the receiving software is completely up to date. DaVinci Resolve is generally very quick to support Apple's latest FCPXML updates.

* Previous Version (e.g., 1.10 or 1.9): This is often the safest and best setting for maximum compatibility. If you are sending an XML to an older version of Premiere Pro, or an audio mixer using older Pro Tools software, a slightly older FCPXML version strips out newer, proprietary Apple metadata that might confuse the receiving program, resulting in a cleaner translation of the basic cuts.

Metadata View Settings

The Metadata View dropdown determines how much extra text data (keywords, camera angles, custom notes) is included in the XML file.

* General: This is the best setting for 95% of workflows. It includes the necessary clip names, timecodes, and basic formatting.

* Basic: Strips out almost everything except the edit points. Useful if you are experiencing severe translation errors and just need the cuts to survive.

* Extended/Custom: Only use this if a post-house specifically requests it. It bloats the XML file with every keyword and note you made in FCP, which can sometimes cause errors in programs that don't know how to read those specific data fields.

The Golden Rule: If your export fails to import into DaVinci Resolve, go back to Final Cut Pro and export it again using an older XML version (e.g., step down from 1.11 to 1.10). That simple change fixes the majority of compatibility issues.