THE FILE FIELD GUIDE
.fcpxml

Final Cut Pro XML

Creative Projects

FCPXML exchanges Final Cut Pro editing information in XML. It references media but is not a finished video containing the payload. Check supported schema versions and media/effect compatibility.

What it is used for
Timeline and media-reference interchange
What the file contains
Text
All sections, questions and sources

Content reviewed: · Editor:Kai

Opening steps

Choose your environment or purpose to see its steps.

Final Cut Pro: import XML

Check interchange version and media.

  1. Prepare a copy, referenced media and producer version.
  2. Use File > Import > XML in Final Cut Pro on Mac.
  3. Inspect the generated events, projects and clips.
Transfer to another editor

XML alone does not establish interchange compatibility.

  1. Check the recipient’s supported FCPXML version/features.
  2. Select the intended objects and export XML in a compatible version.
  3. Import with media and compare duration, retiming, effects and audio with a render.
Inspect media and interchange results

Distinguish editing metadata from media.

  1. Identify missing-media references and locate actual footage.
  2. Relink through the application and inspect timecode and picture.
  3. Save the converted timeline separately and retain the source library/reference render.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Import rejected: verify schema version; generic XML or legacy Final Cut XML is not necessarily FCPXML.
  • Missing media: compare referenced and actual resource locations.
  • Effects/color differ: review how the receiver handles effects, roles and color settings.
  • Export produces FCPXMLD: newer interchange versions can use bundles; inspect recipient support.
  • Effects absent after import: inspect destination support for original effects.
  • Clip timing changes: compare frame rate, timecode and retiming interchange.

FCPXML → edit project / rendered video

  1. Import into a compatible editor and supply the video/audio sources.
  2. Verify cuts, synchronization and effects, then save a working project or render delivery video.
  3. Compare duration, cuts, effects and sound after interchange; retain source project and reference render.

Cross-app interchange may be incomplete; renaming or converting the XML alone cannot render missing video.

FCPXML versus generic XML

FCPXML has editing-specific elements; generic XML readability does not reproduce a timeline.

Select a supported interchange version and inspect feature/bundle support per application.

Source for these steps:Apple · Use XML to transfer projects in Final Cut Pro for Mac / Apple · FCPXML Reference

Timeline checks after interchange

Compare cuts, speed, crops, titles, levels and color against a reference render.

Supply media, frame rate and interchange version together to make import problems diagnosable.

Source for these steps:Apple · Use XML to transfer projects in Final Cut Pro for Mac / Apple · FCPXML Reference

Related-format differences

Related-format differences
FormatMain roleWhat to check
FCPXMLEdit-metadata interchangeVersion and referenced media
FCPXMLDInterchange bundleBundle structure/recipient support
MOV / MP4Video mediaDistinct from edit metadata

Handling and security

Protect media paths/external references and use a maintained application for unfamiliar files.

Questions and answers

Does Final Cut accept any XML?

It must match supported FCPXML syntax/version.

Does it contain the video?

Supply the referenced media separately.

Is interchange lossless across editors?

Verify schema/feature support and inspect the import.

Is FCPXML a finished video?

It exchanges editing information/media references; render finished video separately.

Can I rename FCPXMLD to FCPXML?

Bundles and single XML have different structures; export a supported interchange version.

Format facts: name, steward and MIME type
Formal name
Final Cut Pro XML interchange
Steward / specification
Apple
MIME type
Depends on the producer or server; an extension alone does not establish a MIME type.

Primary and official sources