EXR Converter
Convert between video and OpenEXR sequences with production-grade OpenColorIO, multi-platform builds, and a Nuke-inspired GUI.
About
Desktop app and CLI for converting between video and OpenEXR sequences with OpenColorIO color management and built-in slate rendering. Targets the VFX Reference Platform CY2026.
Features
- Video → EXR and EXR → video conversion
- OpenColorIO 2.5 with bundled ACES Studio Config v4
- Camera IDTs: Apple Log, ARRI LogC, Sony, DJI, and more
- Built-in slate, burn-in, and watermark compositing
- GUI + CLI for editorial and delivery workflows
- Windows, macOS (Apple Silicon & Intel), and Linux builds
Requirements
Standalone apps need no extra install on supported platforms. Building from source requires Python 3.13 and uv.
Download free
Free
Open source · MIT license
The macOS build is signed with an Apple Developer ID and notarized, so it opens normally. All release files are signed with Sigstore Cosign and carry GitHub build provenance. See the releases page for the verify commands.
In the current release
Three tabs, one color pipeline
Video → EXR
Ingest a video file to an OpenEXR sequence through OCIO into a scene space (ACEScg by default). EXR frames are written as half-float, with DWAA, ZIP, or no compression.
EXR → Video
Encode an EXR or still sequence to ProRes, DNxHR, CineForm, HEVC, H.264, or FFV1, with slate, burn-ins, and watermark in one pass. Software ProRes runs everywhere. Apple VideoToolbox ProRes runs on macOS. An experimental RDD 36 ProRes-compatible encoder ships in release builds.
Video → Proxy
Make Resolve-style editing proxies (ProRes 422 Proxy at half size by default) in a Proxy folder next to each clip, keeping source look, timecode, and audio. A watch folder converts new clips once they finish copying.
Full guides for the GUI, CLI, ProRes options, and the Nuke menu are in the EXR Converter docs.
FAQ
Is EXR Converter really free?
Yes. It is MIT-licensed open source. Downloads and source are free forever.
Does it support ACES / custom OCIO configs?
Yes. It ships with ACES Studio Config v4 and respects $OCIO or a custom config path for studio pipelines.
CLI only or GUI?
Both. Use the desktop GUI for interactive work or video2exr / exr2video from the command line.
Need help? Open an issue on GitHub.