FCPXML import errors in Final Cut Pro, and what causes each one.

An FCPXML that will not import is nearly always a version the app does not read, moved media, a library bundle instead of an export, or a compound clip. The fix for each.

What an import error is actually telling you

FCPXML is a description, not a container. The file says "here is a format, here are the media files at these paths, here is how they are arranged." Nothing in it is a picture. So when an import fails, the complaint is always about one of those three things: the description is in a dialect the reader does not speak, the paths lead nowhere, or the arrangement contains an object the reader cannot open.

That is why the same four problems come up whether the file is going into Final Cut Pro or coming out of it to another tool. The messages differ. The causes do not.

How do you fix an FCPXML import error in Final Cut Pro?

1. Read the message before you click anything. Final Cut Pro's import dialog says what it objected to. A version complaint names a number. A validation complaint names a line in the file. A silent import with red frames in the browser is a media problem, not an XML problem, and the file was fine. Each has a different fix, and re-exporting blindly fixes none of them.
2. Check the FCPXML version against your Final Cut Pro. Final Cut Pro reads versions up to the one it writes and refuses anything newer, which happens when the file came from a later release. The fix is on the exporting Mac: choose File > Export XML, open the XML version menu, and pick the version the older Final Cut Pro writes, instead of Current. Expect the export to drop any feature that version does not know about. Updating the older Final Cut Pro is the other route.
3. Confirm you are importing an export, not a library. Final Cut Pro's File > Import > XML wants a .fcpxml file or a .fcpxmld package. A library (.fcpbundle) is not an export, and the Info.fcpxml pulled out of a package by hand can lose the resources the package carried. A .fcpxmld is a folder the Finder shows as one item, so a transfer that flattens folders, or a service that strips extensions, can turn it into something Final Cut Pro will not recognize. Zip the package before it travels, and import the whole package, not its contents.
4. Put the media back where the file says it is. The XML references every clip by path. If the import succeeds but clips show the red missing-file frame, the footage moved, a drive was renamed, or the export came from another Mac with a different path. Put the files back under the original paths, or choose File > Relink Files, point Final Cut Pro at the new location and let it match the rest by name. Nothing needs to be re-exported.
5. Break apart compound clips when the other tool asks. Final Cut Pro reads its own compound clips without complaint. Tools outside Final Cut Pro often cannot see inside one, and the multicam or synchronized clip you wanted transcribed is sitting in there untouched. Select the compound clip in the browser or the timeline, choose Clip > Break Apart Clip Items, then export again. If you need the compound clip for the edit, break apart a copy.
6. Export the event when clips are missing rather than broken. An export of a project carries only the clips in that timeline. If the import worked but the event looks half empty, nothing failed: you exported the wrong thing. Select the event in the Libraries sidebar, File > Export XML, and send that. How to export a Final Cut Pro project as XML walks through which selection carries what.
7. Import again and check three things. File > Import > XML, pick the library, and let Final Cut Pro build the new event. Then check the clip count against what you expected, confirm multicam clips arrived as multicam rather than as flat clips, and open one clip to confirm it plays. An effect Final Cut Pro does not have on this Mac shows as missing on the clip; the cut underneath it is intact.

What if the error is in the other direction?

Many editors searching this phrase exported from Final Cut Pro, and the tool on the receiving end refused the file or read it and showed nothing. The same four causes apply, in a slightly different order of likelihood.

Version is first. Every tool that reads FCPXML supports a range of versions, and Final Cut Pro writes the newest one by default. If the tool's documentation names a ceiling below what your Final Cut Pro writes, pick that version from the XML version menu at export. Compound clips are second, because Final Cut Pro editors use them without thinking and most outside tools cannot open them. Media paths are third, and the fix is the same: the media has to be where the file says, on the same Mac or the same drive. Fourth is a library bundle dragged across because it looked like the project.

One thing that is not an error: a tool that shows only the timeline's clips when you wanted the whole event. That is a selection problem at export, not an import failure, and the fix is a few kilobytes and ten seconds: diagnose first, export once.

Common questions