OpenTimelineIO (OTIO)

OpenTimelineIO (OTIO) is an open-source interchange format and API for editorial timelines. It records the order and length of cuts, the tracks they sit on, transitions and markers, and references to the media they use. It doesn't contain the media itself; in the project's words it's "not however, a container format for media". OTIO was created at Pixar, which used it in production on Coco, Incredibles 2 and Toy Story 4. Since July 2019 it has been hosted by the Academy Software Foundation (ASWF), the Linux Foundation's home for VFX and film software. It's licensed under Apache-2.0 and is the leading open answer to an old post-production problem: moving an edit from one application to another (see edit decision lists and timeline interchange).

How It Works

OTIO models editing in the abstract. A timeline holds a stack of tracks; tracks hold clips, gaps and transitions; each clip points to its media by reference, with a source range, markers, named effects and open-ended metadata. Nothing in that model belongs to one editor, which lets OTIO act as a hub: read a timeline from one tool, change it in a script, then write it to another. The native file is JSON (.otio), and two bundle formats, .otiod and .otioz, can carry media alongside it. The core is written in C++ with Python bindings and includes a small, dependency-free library, opentime, for handling time.

Conversion happens through adapter plugins for Final Cut Pro 7 XML, AAF, CMX 3600 EDLs, ALE and other formats. Since version 0.17 (June 2024), most adapters live in separate packages rather than the core. An FCPXML adapter exists, but it doesn't handle transitions or effects, so a round trip through OTIO loses detail.

Versions and Status

The project is still pre-1.0 and numbers its releases as betas. Version 0.18.0 (November 6, 2025) added an enabled flag on effects and a color primitive and dropped the bundled OTIOView viewer. Version 0.18.1 followed on November 9, 2025 with a fix for Python wheels on Linux, and it's still the latest release as of October 2026. At the ASWF, OTIO has been at the "Incubating" stage since 2019, with its next annual review due on November 11, 2026. Its schema is versioned, so tools can write older schemas for older readers.

Who Reads It

• DaVinci Resolve: import and export since version 18, in both the free and Studio editions.
• Avid Media Composer: timeline export is listed as a preview. Media Composer 2026.8 (September 2026) updated its OTIO adapter for "round-trip fidelity with third-party tools".
• Pipeline and review tools: Foundry's Nuke Studio and Hiero, OpenRV, Kdenlive, Olive and cineSync.
• Adobe Premiere: support has been described as beta, and its finished status couldn't be confirmed.
• Final Cut Pro: no native support; it speaks FCPXML only.

How It Compares

Next to the CMX 3600 EDL, which can represent only simple edits and is usually limited to eight-character reel names, OTIO carries far more structure. AAF remains the standard between Avid and Pro Tools, and FCPXML is the richer choice whenever Final Cut Pro is involved. OTIO's advantages are that it's open, editor-neutral and scriptable. Its weaknesses are its pre-1.0 maturity, no standard field for audio levels (tools store them as metadata the receiving editor may ignore) and patchy support outside Resolve and the VFX toolchain. It has become more important as AI tools make first cuts that people finish elsewhere: an agentic editor or a video-as-code pipeline can write OTIO from its internal plan and hand a clean timeline to a colorist. For the head-to-head, see OpenTimelineIO vs FCPXML.