Redshift 2026.9 is out: Redshift Live adds anisotropy and HDR compression

Maxon released version 2026.9 of Redshift, its GPU-accelerated production render engine, in the first half of September 2026. According to a 10 September report by CG Channel, the update brings anisotropy and HDR compression support to Redshift Live—the real-time render engine introduced with Redshift 2026.4—along with OCIO 2.5 color management, Houdini 22 compatibility, and USD and Alembic proxy instancing in Maya. Digital Production describes the release as a maintenance and pipeline update focused more on production stability than headline-grabbing features.

Redshift is a GPU render engine used in motion graphics and VFX as well as architectural visualization, and is particularly popular among Cinema 4D and 3ds Max users. Its Revit and Vectorworks plugins also make it directly accessible to offices working with BIM.

What’s changed in Redshift Live?

Redshift Live is the real-time render engine Maxon added to Redshift this year. Version 2026.9 adds two significant capabilities:

• Anisotropy support: Materials with direction-dependent reflections, such as brushed metal, can now be previewed accurately in Redshift Live.

• HDR compression: This enables more controlled display of bright areas in high-dynamic-range images.

According to Digital Production, clouds in Redshift Live have also been improved to look closer to production renders. This is a step toward narrowing the gap between real-time previews and final renders.

Anisotropy support is particularly important for architectural visualization. Kitchen fixtures, stainless-steel countertops, aluminum frames, and brushed-metal furniture details are common in interior scenes. When these surfaces looked wrong in real-time previews, artists had to rely on guesswork when adjusting materials.

Color management and pipeline updates

Redshift’s core now supports OCIO 2.5 (OpenColorIO 2.5), as specified by the VFX Reference Platform. Digital Production reports that the release updates OpenColorIO to version 2.5.2 and fixes display profile naming issues. For studios using ACES-based color workflows, this means greater color consistency across different software.

Other updates include:

• Houdini 22.0.368 and Solaris 22.0.368 support, plus a USD 26.05 build for Houdini 22’s USD Procedural workflow

• USD and Alembic proxy instancing in Maya, plus USD proxy support in the nParticles system

• Faster render preparation and lower memory use during preparation

• Improved options for using proxy pivots in 3ds Max

• Fixes for hex tiling artifacts, numerical instability in anisotropy, and RenderView scaling issues

Pricing and system requirements

According to CG Channel, Redshift is available only by subscription. Other major supported applications include Katana 5.0+, Maya 2018+, and ZBrush 2023+.

Impact on archviz workflows

Redshift 2026.9 is not a revolutionary release for archviz users, but it moves in the right direction. Support for Revit and Vectorworks makes Redshift an option worth considering for architecture firms looking to render directly from BIM models on the GPU. Expanded material support in Redshift Live also strengthens the case for keeping real-time previews and production-quality rendering within the same engine family during design.

Faster render preparation and lower memory use can make a noticeable difference in large scenes containing lots of furniture and plants. For teams queuing up many camera angles or using a render farm, the preparation time saved on each frame can add up to a meaningful gain.

The relevance of the OCIO 2.5 update to archviz is color consistency. Color shifts between images, animations, and post-production output created in different applications can be a problem, especially on projects involving corporate colors and material samples. Support for a common, up-to-date color management standard helps reduce these shifts.

Before updating, check the version of the main application in use. The minimum versions in the table directly affect offices running older releases, particularly of Revit and Vectorworks. For teams using a render farm or network rendering, running the same Redshift version on every node remains a basic rule for avoiding inconsistent output. Comparing renders of a few reference scenes against the previous version after updating can also reveal potential differences before delivery and minimize surprises.