> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/prepare-your-scene/ocio.md). # Colour management with OCIO Keep colour configurations and LUTs with your scene, and match the colour settings used in compositing. [OpenColorIO (OCIO)](https://opencolorio.readthedocs.io/en/latest/index.html) manages how colours are converted and displayed in your rendering and compositing apps. ## Include a custom configuration with the scene A custom OCIO setup can depend on both a configuration file and separate LUT files that define colour conversions. Collect those files together and preserve the folder paths used by the configuration. A configuration that points to a folder on your workstation will need those paths corrected before another computer can use it. See the [OpenColorIO configuration guide](https://opencolorio.readthedocs.io/en/latest/guides/authoring/overview.html). In Cinema 4D, **Save Project with Assets** collects OCIO configuration settings alongside the scene's other assets. Check the collected copy before creating your upload archive. See Maxon's [File menu reference](https://help.maxon.net/c4d/en-us/Content/html/5595.html). In Octane Standalone, open **Preferences → Color Management** and use **Use Other Config Files** to load a custom configuration. Its views then become available in the camera's **Imager** settings. See OTOY's [colour management reference](https://docs.otoy.com/standaloneSE/ColorManagementSettings.html). {% hint style="info" %} For a production that depends on a custom configuration, render a test frame on the network and check the downloaded file in your compositor before submitting the sequence. If the result differs, send the configuration, referenced LUTs, and local comparison to [support](/docs/help/get-support.md). {% endhint %} ## Match the output to your compositor An OCIO view used in the render viewport is not necessarily baked into the saved image. For a linear EXR workflow, apply the matching view in your compositor when comparing the render with the viewport. OTOY's [Houdini colour management guide](https://docs.otoy.com/houdini/ColorManagementOCIO.html) explains this distinction. See [EXR output and DWA compression](/docs/prepare-your-scene/exr-and-dwa-compression.md) for choosing the output colour space and keeping a linear image for compositing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://know.rendernetwork.com/docs/prepare-your-scene/ocio.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.