Cutsio Blog

How to Export XML from Final Cut Pro

Export a clean FCPXML timeline from Final Cut Pro for DaVinci Resolve, audio, finishing, or another editor without losing the media references your handoff depends on.

What is the correct way to export XML from Final Cut Pro?

To export XML from Final Cut Pro, prepare a duplicate of the intended Project, remove or identify effects that cannot translate, then use File > Export XML and choose the XML version requested by the receiving application. XML transfers an edit structure and media references; it does not package the original media or guarantee that titles, plugins, color grades, or compound clips will behave identically in another NLE. For large footage libraries, Cutsio can help locate the source moments before the handoff with Visual Intelligence, which analyzes the visual content of every frame alongside audio, creating a unified search index for any moment.

What does FCPXML transfer?

FCPXML can describe much of the structure inside a Final Cut Pro timeline, including:

• Clip order and timeline placement
• Source-media references
• In and out points
• Basic edits and transitions
• Roles and audio relationships where supported
• Timecode and project timing information
• Some speed and transform data
• Event, keyword, or library references depending on the export

It is not a self-contained project archive. The receiving editor still needs access to the media, and some Final Cut Pro-specific features may need to be rebuilt. Export a reference movie with visible timecode when the handoff matters, especially when the receiving application is DaVinci Resolve, Premiere Pro, or an audio finishing tool.

How should you prepare the Project before exporting?

Always preserve the working edit and prepare a handoff copy.

1. Select the Project in the Final Cut Pro Browser.
2. Duplicate the Project and rename it with a clear handoff version.
3. Open the duplicate and remove unused experiments, temporary clips, and guide layers that the recipient does not need.
4. Confirm the timeline frame rate, resolution, starting timecode, and audio sample rate.
5. Check that the source media is online and that the clip names are meaningful.
6. Disable or identify third-party effects, titles, and generators that will not transfer.
7. Save the duplicate before opening the export dialog.

Use a name such as BrandFilm_PictureLock_FCPXML_2026-08-08. A clear version name prevents the recipient from importing an old rough cut and wondering why it does not match the reference movie.

What should you clean up first?

XML works best when the timeline describes a straightforward picture edit. Clean up the areas most likely to confuse a conform or finishing workflow:

| Timeline element | Risk during XML handoff | Recommended preparation |

| --- | --- | --- |

| Compound clips | May arrive as nested or flattened structures | Open, simplify, or document the expected result |

| Multicam clips | Angle and role interpretation may differ | Commit the intended angle for the handoff copy |

| Titles and generators | Often depend on Final Cut Pro templates | Disable, render, or include as reference |

| Third-party effects | The target application may not have the plugin | Render a reference and list the effect |

| Speed changes | May translate differently | Compare against a reference movie |

| Adjustment layers | May be unsupported or interpreted differently | Keep as reference or bake into a render |

| Audio roles | Track mapping can change | Label dialogue, music, and effects clearly |

Do not delete important elements from the master Project. The handoff copy exists so you can simplify without damaging the edit that still belongs in Final Cut Pro.

How do you export the FCPXML file?

When the duplicate Project is ready:

1. Select the Project in the Browser.
2. Choose File > Export XML.
3. Select the XML version requested by the receiving editor.
4. Choose a destination folder and save the file with the same project and version name as the reference movie.
5. Wait for the export to finish before moving or renaming source media.
6. Open the exported file only for inspection; avoid hand-editing the XML unless you understand the receiving schema.

The receiving editor may request a specific FCPXML version because applications do not all support the same schema. If you are unsure, export a short test Project first. A test containing a cut, a dissolve, a speed change, a compound clip, and two audio roles reveals more than exporting a two-hour timeline and discovering a problem at the end.

Keep the test result with the handoff notes. Record which elements translated, which clips needed relinking, and which effects required a reference render. That small record becomes a useful compatibility checklist for the next project using the same target application.

How do you preserve media links?

The XML normally points to media rather than embedding it. A successful export can therefore open with every clip offline in the receiving application. Prepare a handoff note with:

• The source-media folder or volume name
• Camera-card, reel, and file naming conventions
• Whether the recipient receives originals, proxies, or transcodes
• The Project frame rate and starting timecode
• Any known relinking steps
• The location of the reference movie

If the recipient will not have the same folder structure, provide a controlled media package or agree on a relinking plan before delivery. Do not rename source files between exporting the XML and preparing the media package unless you also document the change.

How do you export XML for DaVinci Resolve?

For a Resolve handoff, export a clean picture timeline and include a reference movie. Resolve can reconstruct many basic edits from FCPXML, but the result still depends on source paths, timecode, frame rate, and the features used in the original Project.

Before exporting, consider creating two handoff layers:

• A clean editable timeline with basic picture cuts and supported transitions.
• A reference movie that shows the final appearance, titles, graphics, and any effects that will not transfer.

If the project is large, use a short test sequence with representative shots before exporting the full timeline. Compare the imported sequence against the reference movie at the start, middle, and end. Pay particular attention to retimes, compound clips, multicam edits, mixed frame rates, and audio sync.

How do you handle audio roles?

Audio roles are useful in Final Cut Pro, but the receiving application may map them differently. Before exporting:

1. Give dialogue, music, effects, and guide tracks clear role names.
2. Remove muted experiments and unused takes from the handoff copy.
3. Check that dual-system audio is synchronized and has stable timecode.
4. Export a reference mix when the XML is intended for picture finishing.
5. Tell the recipient whether the XML should be used for picture, audio, or both.

If a sound editor needs clean dialogue, provide the appropriate audio deliverable separately rather than expecting the XML alone to preserve every role and processing choice.

What should you include in the delivery folder?

A practical XML handoff contains:

• The FCPXML file
• A reference movie with visible timecode
• A readme with application versions and timeline settings
• Media-path and relinking instructions
• A list of effects or templates that will not transfer
• Proxy or original-media instructions
• Optional still frames for key title or grade references

Keep the master Final Cut Pro Library separate from the handoff folder. The library is the editable source; the XML is an interchange file. If you need to find a specific shot before building the delivery package, Cutsio can search footage by what appears in the frame and what people say, then help you identify the source clip and time range.

How do you troubleshoot an XML import?

The XML is rejected

Confirm that the receiving application supports the exported FCPXML version. Try a small test Project and remove unsupported elements. Do not change version numbers inside the file at random; a file that opens can still lose important edit information.

Clips are offline

Check the source paths, volume names, file names, and reel information. Use the receiving application’s relink tools and compare one known clip before relinking the entire timeline.

The timeline duration is different

Compare frame rate, start timecode, retimes, still-image durations, and compound clips. A reference movie makes it easier to identify the first point where the reconstructed edit diverges.

Titles or effects are missing

That is usually a translation limitation. Rebuild supported elements, include a reference layer, or provide a rendered version of the affected section.

Audio is out of sync

Check sample rate, source timecode, Project start time, clip speed changes, and whether the receiving application interpreted the audio role mapping correctly.

FAQ

Does FCPXML include the original video files?

No. FCPXML normally contains timeline structure and media references, so the receiving editor still needs accessible source media or proxies.

Should I export XML from the master Project?

No. Duplicate the Project first so you can simplify the handoff without changing the master edit.

Will Final Cut Pro titles transfer to DaVinci Resolve?

Not reliably. Include a reference movie and rebuild or render titles that the receiving application cannot interpret.

What is the safest way to test an XML handoff?

Export a short representative Project first, import it into the target application, and compare it with a timecoded reference movie.

Can Cutsio help prepare an XML handoff?

Yes. Cutsio can make a large footage library searchable by visual content and speech, helping editors find the right source clips before building a clean Final Cut Pro timeline. See Visual Intelligence for video teams.