Treat an interchange file as a translation of supported edit information, not as a guaranteed clone of the native project. Keep the original project, supply a reference export and validate a small exchange before committing a whole production.
On this page
Define what is being handed over
| Package | What it provides | What it may not preserve |
|---|---|---|
| Native project plus media | The source application’s edit and its assets | Compatibility with another editor or different plugin versions |
| XML or another interchange format | A supported description of parts of the edit | Every title, effect, transition and application-specific structure |
| Finished reference movie | A visual and audible target | An editable timeline or individual source assets |
| Intermediate picture and audio exports | Selected downstream finishing elements | The complete original editorial flexibility |
Choose a diagnostic sample
Include the things most likely to translate imperfectly: a nested sequence, speed change, transition, title, audio mapping and a grade. A test made only of straight cuts can miss exactly the features that make the real project difficult to exchange.
- Duplicate the project and choose a short representative sequence.
- Confirm the exchange format and version supported by the receiving application.
- Export the interchange file and a reference movie of the same range.
- Provide the required media with stable paths and an inventory.
- Import into a separate destination project.
- Compare cut positions, duration, picture scaling, speed changes, transitions and audio.
- Document unsupported elements and choose how to recreate or bake them.
Version the exchange
Apple’s FCPXML documentation provides version choices for compatibility with receiving tools. That does not mean every XML dialect can be read by every editor. Agree the format and supported version with the receiver, and keep the file or bundle together with its notes.
Keep a recoverable source
Do not delete the native project or camera originals after one apparently successful import. A later correction may need an effect or asset that was simplified during translation. Keep the approved reference and a list of known changes so future revisions remain interpretable.
Make the acceptance check explicit
Agree whether the recipient needs editable titles, isolated dialogue, a graded picture master or only an approved finished file. This reduces avoidable work and turns the handoff into a verifiable delivery rather than an optimistic file transfer. See folder conventions and recovery planning.
Sources and scope
This is a documented troubleshooting method and an original verification checklist, not a claim of hands-on testing. Sources checked October 6, 2026.