OpenTimelineIO vs FCPXML

Two Philosophies of a Timeline

OTIO models editing in the abstract. A timeline is a stack of tracks; tracks hold clips, gaps and transitions; clips point at media by reference and carry in and out points, markers and named effects. Nothing in that model belongs to any one editor, which is why OTIO can act as a hub: read a timeline from one tool, transform it in Python, write it to another. Studios use it for exactly that, moving editorial between cutting rooms, visual-effects pipelines and review tools.

FCPXML models Final Cut Pro. Its documents contain libraries, events and projects, a "spine" of primary storyline clips with connected clips attached, compound clips, roles such as dialogue and music, keywords, ratings and smart collections. It is precise and expressive for Final Cut Pro's magnetic timeline, and awkward for anything that does not think that way. Apple itself says FCPXML is "not a substitute for the native Final Cut Pro project and event data".

What Each Keeps

Both formats keep the essentials of a cut: which clips, in what order, with which source in and out points, on which tracks, with transitions and markers. The differences show at the edges. OTIO records effects by name and metadata, but not as portable render instructions, and it has no standard field for audio levels, so tools often store volume and ducking as clip metadata. FCPXML can carry Final Cut Pro's volume adjustments, keyframes, roles and effect parameters, but only in Final Cut Pro's terms; another application must translate them.

Neither format carries everything. Titles and graphics, speed ramps, color grades and reframing often need rebuilding after a transfer, and the safest practice is to send a reference render alongside the timeline so the finishing editor can check the conform.

Where Each Opens

OTIO's strongest native support is in DaVinci Resolve, which has imported and exported .otio files since version 18, in both the free and Studio editions, according to the project's list of supporting tools. Avid Media Composer lists timeline export as a preview, and Foundry's Nuke Studio and Hiero, OpenRV, Kdenlive and Olive also read it. Adobe Premiere's support has been described as beta, and its finished status could not be confirmed for this page. Final Cut Pro does not read OTIO at all (see Final Cut Pro vs DaVinci Resolve).

FCPXML is the only way into Final Cut Pro, and many tools that want Final Cut Pro users export it, including Descript and Eddie AI. Getting FCPXML into Premiere typically takes a converter such as Intelligent Assistance's XtoCC ($49.99). OTIO can read FCPXML through a separately installed adapter, but that adapter does not handle transitions or effects, so a round trip through OTIO loses detail.

Versions and Maturity

OTIO is still pre-1.0. Version 0.17 (June 2024) split most format adapters out of the core into separate plugin packages, leaving the native .otio, .otiod and .otioz formats in core; version 0.18 (November 2025) added an enabled flag on effects and a color primitive and dropped the bundled OTIOView viewer. The project has been incubating at the Academy Software Foundation since 2019, with its next annual review due on 2026-11-11. Its schema is versioned, so writers can target older schemas for older readers.

FCPXML versions move with Final Cut Pro. Version 1.10 (Final Cut Pro 10.6) introduced the .fcpxmld bundle with an Info.fcpxml file at its root, 1.13 arrived with Final Cut Pro 11.0, and 1.14 with Final Cut Pro 12.0 in January 2026; later 12.x releases did not change it. Apple's developer reference page still shows an older version in its header, so check the release notes for the current one.

Choosing a Format

Pick by destination. For Final Cut Pro, write FCPXML; nothing else works. For DaVinci Resolve, OTIO is clean and open, and for pipelines that pass through visual-effects and review tools, OTIO is the shared language. For Premiere, the most dependable route remains Final Cut Pro 7 XML, which OTIO can write through its plugin adapters. Tools that generate edits, including agentic video editors, increasingly export several formats from one internal plan for exactly this reason.