November 7, 2026 Linh Nguyen

Blender 5 Color Management on Another Machine (2026): AgX, ACES 2.0, OCIO and Output Formats

Quick answerConsistent color when rendering Blender 5 elsewhere
Checked Nov 2026

In Blender 5, the working color space is saved in the .blend file and the view transform (AgX, Filmic, ACES 2.0 or Standard) is a scene setting, so the same Blender version renders the same colors on any machine. What does not travel is a custom OCIO config set through the OCIO environment variable. Render to OpenEXR for anything that will be graded, since EXR stores scene-linear data.

  • In the file: working space, view transform, look, exposure.
  • Not in the file: custom OCIO configs set by environment variable.
  • Output: EXR keeps linear data; PNG/JPEG/video bake in the view.
  • Version: use the same Blender version for the whole sequence.

Blender 5.0 rebuilt color management around working color spaces, ACES 2.0 and HDR. For artists who render on a different machine, the useful question is which of these settings ride inside the .blend and which depend on the computer.

This guide maps where each color decision is stored, which output formats keep it, and what to check before a sequence renders elsewhere. For why renders can look different after upgrading to Blender 5, see our earlier article on ACES and display transforms in Blender 5.

Checked against the Blender Manual (Color Management) and the Blender 5.0 release page, November 2026.

1. What Blender 5.0 changed

Blender 5.0 introduced a Blend file working color space, with Rec.2020 for a wider internal gamut, essential ACES 1.3 and 2.0 support with the ACEScg working space, an ACES 2.0 view transform, an AgX HDR view, Rec.2100-PQ and HLG displays, and OpenEXR output in ACES2065-1 and ACEScg. For fuller ACES pipelines, the release page notes the official ACES configurations can be installed manually and set through the OCIO environment variable (Blender 5.0 release).

iRender
Blender 5 color pipeline from file to output
Schematic
Working spacesaved in the .blendRec.709 · 2020 · ACEScgRenderscene-linear valuessame on every machineView transformscene settingAgX · Filmic · ACES 2.0Displaydevice settingsRGB · P3 · Rec.2100OpenEXRstores scene-linear dataPNG / JPEG / videoview transform baked inWhere each color decision is stored, and what each output format keepsWorking space and view live in the .blend; EXR keeps linear data, PNG bakes in the viewBlender Manual: Color Management; Blender 5.0 release
filelinear dataview transformdisplay
Source: Blender Manual, Color Management; Blender 5.0 release

2. Settings that travel with the file

The Manual describes color management settings as scene-specific, so they can differ per scene, and notes they can be overridden when saving images through Output color management (Blender Manual: Color Management). Together with the 5.0 working color space, this means view transform, look, exposure and working space are inside the .blend. Opening the file in the same Blender version on another machine gives the same result.

CheckBlender 5.x

What travels with the .blend and what does not

Color settings to confirm before rendering on another machine.

SettingStored whereCheck on the render machine
Working color spaceThe .blend file (new in 5.0)Nothing extra; open the file in Blender 5.x
View transform, look, exposureScene color management settingsNothing extra if the same Blender version is used
Output color managementOutput properties (can override the scene)Confirm the override matches what the client expects
Custom OCIO configThe OCIO environment variable on that machineInstall the same config and set the variable, or renders will not match
Image texture color spacesEach image nodeNon-Color for data maps; check after relinking textures
RuleSame Blender version, same OCIO config, EXR for anything that will be graded.

3. The setting that does not: custom OCIO configs

Blender’s color management is built on OpenColorIO, and the Manual explains that using the same OCIO configuration in several applications gives the same color spaces and transforms (Blender 3.6 Manual: Color Management). A custom config is loaded from the OCIO environment variable of the computer, not from the .blend. If your workstation uses a studio or official ACES config, the render machine needs the same config and variable, or view names may be missing and frames will not match.

iRender
A custom OCIO config lives on the computer, not in the .blend
Schematic
WorkstationOCIO = D:/configs/studio_config.ociostudio configAgXACES 2.0Studio Lookframe as gradedsame .blend, same Blender versionRender machineOCIO not setbuilt-in configAgXACES 2.0Studio Look missingdifferent looksame .blend, same Blender versionCopy the config and set the same OCIO variable on the render machine before renderingBlender Manual: Color Management (OpenColorIO); Blender 5.0 release (OCIO environment variable)
config foundconfig missing
Schematic, not to scale

Nothing in the .blend tells the render machine where the studio config is. If the variable is missing, Blender falls back to its built-in config, and any view or look that only exists in the custom config cannot be applied.

4. Choosing output formats

The Manual recommends OpenEXR for intermediate production files because EXR is always stored in scene-linear color spaces without data loss, while PNG or JPEG typically store display-ready colors (Blender 3.6 Manual: Color Management). For a sequence that will be graded or composited, render EXR and apply the view in compositing or grading; see render passes and multilayer EXR. Use PNG or video only for final deliveries where the look is already approved.

iRender
What EXR keeps that PNG cannot
Schematic
Scene-linear values in one frame01.0416+ sun, lampsOpenEXR: stores the values as rendered0 … 1 … 4 … 16+: highlights keep their detail for gradingPNG / JPEG / video: view transform applied, then display range0 … 1 (display-ready)everything above is compressed by the view transform into the top of 0…1Render EXR for anything that will be graded; bake the view into PNG or video only for approved outputBlender Manual: Color Management (OpenEXR stored in scene-linear)
EXR: scene-linearPNG: display-referred
Illustrative values, not to scale

A bright window or the sun can be many times brighter than a white wall in scene-linear values. EXR keeps that difference; a PNG has already squeezed it into the display range, so a grade cannot bring the lost highlight detail back.

A color checklist before rendering on another machine

  1. Version: same Blender 5.x version as the workstation
  2. Working space: confirmed in the file (Rec.709, Rec.2020 or ACEScg)
  3. View: view transform and look set in the scene
  4. OCIO: custom config copied and OCIO variable set, if one is used
  5. Textures: data maps set to Non-Color after relinking
  6. Output: EXR for grading; output color override checked

For paths, caches and other scene checks, see our 10-point Blender Cycles pre-flight checklist.

On a managed farm, a custom OCIO config depends on what the provider supports. On an IaaS server you install the Blender version and OCIO config you use and set the environment variable yourself, like on your own workstation.

Matching color on an iRender server

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.c4d · .blend · .hip1 GPUYour iRender serverscene.c4d · .blend · .hipup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found
  1. Upload the project and any OCIO config to iRender Drive before you start the server; uploading is free and does not use rental time.
  2. Start a server with RTX 5090 (32 GB) or RTX 4090 (24 GB) GPUs and connect by remote desktop.
  3. Install your Blender version, set the OCIO variable if needed, and compare one frame with your workstation.
  4. Render the sequence and shut down; multi-GPU servers are billed per minute.

Frequently asked questions

1. Is the view transform saved in the .blend file?

Yes. Color management settings are scene-specific, so view transform, look and exposure are saved with the scene.

2. Does a custom OCIO config travel with the .blend?

No. It is loaded through the OCIO environment variable on each computer, so the render machine needs the same config.

3. Should I render EXR or PNG?

EXR for anything that will be graded or composited, since it stores scene-linear data; PNG or video for approved final output.

4. What is the working color space in Blender 5?

A per-file setting added in 5.0, such as Linear Rec.709, Rec.2020 or ACEScg, used for rendering and compositing.

5. AgX or ACES 2.0?

Both are view transforms with different looks; pick one per project and keep it for every frame.

Render your Blender projects on iRender

iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.

Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.

This quick start shows how to start a server and render Blender on it:

Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
,

Linh Nguyen

Linh Nguyen works in customer support at iRender, helping artists render Blender and Houdini projects on multi-GPU servers. She has written more than 300 articles for the iRender blog, covering Blender, Houdini and practical GPU rendering.
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →