One package. Every version, atomized.
OpenIMF makes IMF open and accessible — atomized packages, not monolithic masters. Swap a single component instead of re-rendering the whole title: save storage, ship faster, and automate your pipeline. Local and offline.
Five steps, one open pipeline.
From raw elements to a standards-based IMF package — every stage runs on your own machine, on the open @openimf engine.
Import your assets
Bring in texted masters, textless material, mix stems, subtitles, and production docs — each kept as a first-class, addressable component.
Package as IMF
Author standards-based SMPTE ST 2067 packages — ASSETMAP, PKL, CPL, MXF — locally and offline. Open, interoperable output any IMF system can read.
Manage your library
A real library, backed by local SQLite, tracks every title, version, and component. The library is the source of truth — not a folder of re-renders.
Export deliverables as needed
Derive size-targeted submasters and pull the exact deliverable a distributor asks for — without re-rendering the whole title.
Update with patches
Something changed? Patch a single component, re-QC against the final deliverable, and ship a new version — not a new master.