Compatible Software

The following software all supports OpenColorIO (to varying degrees).

If you are interested in getting OCIO support for an application not listed here, please contact the ocio-dev mailing list.

If you are a developer and would like assistance integrating OCIO into your application, please contact ocio-dev as well.

After Effects

An OpenColorIO plugin is available for use in After Effects.

Website: http://www.adobe.com/products/aftereffects.html

Documentation :

Anchorpoint

Anchorpoint is a file browser and asset manager for VFX, animation and real-time projects. It supports OCIO configs to display OpenEXR with the correct color profile.

Website: https://www.anchorpoint.app

Documentation :

Arnold (Autodesk)

Website : https://www.arnoldrenderer.com/

Documentation :

Blender

Blender has integrated OCIO as part of it’s redesigned color management system.

Website: http://www.blender.org/

Supported Version: >= 2.64

Documentation:

C++

The core OpenColorIO API is available for use in C++. Minimal code examples are also available in the source code distribution.

Website: http://github.com/AcademySoftwareFoundation/OpenColorIO/tree/main/include/OpenColorIO

Examples:

Documentation:

cineSync (ftrack)

Website : https://cospective.com/cinesync/

Documentation :

Clarisse (Isotropix)

Website: https://www.isotropix.com/products

Documentation:

CryEngine (CryTek)

CryEngine is a real-time game engine, targeting applications in the motion-picture market. While we don’t know many details about the CryEngine OpenColorIO integration, we’re looking forward to learning more as information becomes available.

Website: https://www.cryengine.com/

DJV

Website: https://darbyjohnston.github.io/DJV/

Gaffer

Gaffer is a node based application for use in CG and VFX production, with a particular focus on lighting and look development.

Website: http://www.gafferhq.org/

Guerilla Render

Composed of Guerilla Station and Guerilla Render, Guerilla is a Production-Proven Look Development, Assembly, Lighting and Rendering Solution designed for the Animation and VFX industries.

Website: http://guerillarender.com/

Supported version: >= 2.2

Documentation:

Hiero (Foundry)

Hiero ships with native support for OCIO in the display and the equivalent of Nuke’s OCIOColorSpace in the Read nodes. It comes with the “nuke-default” OCIO config by default, so the Hiero viewer matches when sending files to Nuke for rendering.

Website: https://www.foundry.com/products/hiero

Supported version: >= 1.0

Houdini (SideFX)

Website: https://www.sidefx.com

Supported Version: >= 16

Documentation:

Java (Beta)

The OpenColorIO API is available for use in Java. This integration is currently considered a work in progress, and should not be relied upon for critical production work.

Website: https://github.com/AcademySoftwareFoundation/OpenColorIO/tree/main/src/bindings/java

Katana (Foundry)

Website: http://www.thefoundry.co.uk/products/katana

Documentation:

Krita

Krita now support OpenColorIO for image viewing, allowing for the accurate painting of float32/OpenEXR imagery.

Website: http://www.krita.org/

Documentation :

Mari (Foundry)

Website: https://www.foundry.com/products/mari

Supported Version: >= 1.4v1

Documentation:

Maya (Autodesk)

Autodesk Maya is a 3D computer animation, modeling, simulation, and rendering software.

Website: https://www.autodesk.com/products/maya/overview

Supported Version: >= 2016

Documentation:

Mocha Pro (Boris FX)

Website: https://borisfx.com/products/mocha-pro

Supported Version: >= 2020

Documentation:

Modo (Foundry)

Website: https://www.foundry.com/products/modo

Documentation:

mrViewer

mrViewer is a professional flipbook player, hdri viewer and video/audio playback tool. It supports OCIO input color spaces in images as well as display/view color spaces.

Website: https://mrviewer.sourceforge.io

Documentation:

Natron

Natron is an open source 2D compositor that ships with native support for OCIO. Standard configs are included however users can also point to custom configs in the color management section of the user preferences.

Website : https://natrongithub.github.io/

Documentation :

Nuke (Foundry)

Nuke ships with native support for OpenColorIO. There is also an available “nuke-default” OCIO config, which matches the built-in Nuke color processing. This profile is useful for those who want to mirror the native Nuke color processing in other applications (the underlying equations are also provided as python code in the config as well).

Website : https://www.foundry.com/products/nuke

Supported Version: >= 6.3v7

Documentation:

OpenImageIO

OIIO’s C++ and Python bindings include several methods for applying color transforms to whole images, notably functions in the ImageBufAlgo namespace including colorconvert(), ociolook(), ociodisplay(), ociofiletransform(). These are also available as part of the oiiotool command line utility (–colorconvert, –ociolook, –ociodisplay, –ociofiletransform) and the maketx utility for preparing textures also supports –colorconvert. From C++, there is additional low-level functionality in the header OpenImageIO/color.h that are wrappers for accessing underlying OCIO color configurations and doing color processing on individual pixel values.

Website : http://openimageio.org

PhotoFlow

PhotoFlow supports OCIO via a dedicated tool that can load a given configuration and apply the available color transforms. So far the tool has been tested it with the Filmic and ACES configs.

Website : https://github.com/aferrero2707/PhotoFlow

Photoshop

OpenColorIO display luts can be exported as ICC profiles for use in photoshop. The core idea is to create an .icc profile, with a valid description, and then to save it to the proper OS icc directory. (On OSX, ~/Library/ColorSync/Profiles/). Upon a Photoshop relaunch, Edit->Assign Profile, and then select your new OCIO lut.

Website : https://www.adobe.com/products/photoshop.html

An OpenColorIO plugin is also available for use in Photoshop. The plug-in can perform color operations to an image as a filter and can also export LUTs and ICC profiles to be used by Photoshop.

Plugin binaries are available for download, courtesy of fnordware.

Python

The OpenColorIO API is available for use in Python.

Website: https://github.com/AcademySoftwareFoundation/OpenColorIO/tree/main/src/bindings/python

Documentation:

RV (Autodesk)

Website : http://www.tweaksoftware.com

Supported Version: >= 4

Documentation :

  • For more details, see the OpenColorIO section of the RV User Manual.

Silhouette (Boris FX)

OCIO is natively integrated in Silhouette. Full support is provided for both image import/export, as well as image display.

Website : https://borisfx.com/products/silhouette/

Supported Version: >= 4.5

Substance Designer (Adobe)

Website: https://www.substance3d.com/products/substance-designer/

Supported version: >= 2019.3

Documentation:

Unreal Engine (Epic Games)

Website : https://unrealengine.com

Supported Version : >= 4.22

Documentation :

Vegas Pro (Magix)

Vegas Pro uses OpenColorIO, supporting workflows such as S-log footage via the ACES colorspace.

Website : http://www.sonycreativesoftware.com/vegaspro

Supported Version: >= 12

V-Ray (Chaos Group)

Website : https://chaosgroup.com

Documentation :

Apps w/icc or luts

flame (.3dl), lustre (.3dl), cinespace (.csp), houdini (.lut), iridas_itx (.itx) photoshop (.icc)

Export capabilities through ociobakelut:

$ ociobakelut -- create a new LUT or icc profile from an OCIO config or lut file(s)
$
$ usage:  ociobakelut [options] <OUTPUTFILE.LUT>
$
$ example:  ociobakelut --inputspace lg10 --outputspace srgb8 --format flame lg_to_srgb.3dl
$ example:  ociobakelut --lut filmlut.3dl --lut calibration.3dl --format flame display.3dl
$ example:  ociobakelut --lut look.3dl --offset 0.01 -0.02 0.03 --lut display.3dl --format flame display_with_look.3dl
$ example:  ociobakelut --inputspace lg10 --outputspace srgb8 --format icc ~/Library/ColorSync/Profiles/test.icc
$ example:  ociobakelut --lut filmlut.3dl --lut calibration.3dl --format icc ~/Library/ColorSync/Profiles/test.icc
$
$
$ Using Existing OCIO Configurations
$     --inputspace %s      Input OCIO ColorSpace (or Role)
$     --outputspace %s     Output OCIO ColorSpace (or Role)
$     --shaperspace %s     the OCIO ColorSpace or Role, for the shaper
$     --iconfig %s         Input .ocio configuration file (default: $OCIO)
$
$ Config-Free LUT Baking
$     (all options can be specified multiple times, each is applied in order)
$     --lut %s             Specify a LUT (forward direction)
$     --invlut %s          Specify a LUT (inverse direction)
$     --slope %f %f %f     slope
$     --offset %f %f %f    offset (float)
$     --offset10 %f %f %f  offset (10-bit)
$     --power %f %f %f     power
$     --sat %f             saturation (ASC-CDL luma coefficients)
$
$ Baking Options
$     --format %s          the lut format to bake: flame (.3dl), lustre (.3dl),
$                          cinespace (.csp), houdini (.lut), iridas_itx (.itx), icc (.icc)
$     --shapersize %d      size of the shaper (default: format specific)
$     --cubesize %d        size of the cube (default: format specific)
$     --stdout             Write to stdout (rather than file)
$     --v                  Verbose
$     --help               Print help message
$
$ ICC Options
$     --whitepoint %d      whitepoint for the profile (default: 6505)
$     --displayicc %s      an icc profile which matches the OCIO profiles target display
$     --description %s     a meaningful description, this will show up in UI like photoshop
$     --copyright %s       a copyright field

See this ocio-dev thread for additional usage discussions.

When exporting an ICC Profile, you will be asked to specify your monitor’s profile (it will be selected for you by default). This is because ICC Profile are not LUTs per se. An ICC Profile describes a color space and then needs a destination profile to calculate the transformation. So if you have an operation working and looking good on the monitor you’re using (and maybe its should choose its profile instead.