OctaRender includes a comprehensive suite of features designed to provide flexible, native support for complex artistic workflows. The platform minimizes manual pipeline preparation by handling scene evaluation and dependency packaging automatically.

The platform actively detects and natively supports multiple production versions of Blender:

OctaRender supports production-standard internal deployment for both core Blender rendering engines: Cycles and EEVEE.

The platform natively handles custom add-ons within the network environment, from utility action tools to complex generative systems. The client automatically parses your scene file to detect active add-ons, drivers, custom nodes, and linked libraries, pre-selecting the correct runtime flags before pushing the job to the farm.

OctaRender automatically traces and consolidates project assets. It aggregates local resources; including textures, geometry node structures, OpenVDB files, and localized simulation caches.

The system scans your local workspace configuration for OpenColorIO (OCIO) implementations. If custom color spaces, LUTs, or institutional pipelines (such as ACES) are used, the custom configs are automatically bundled and mirrored across all rendering nodes.

Distributed nodes natively support heavy physics baking and simulation caches. For toolsets like FLIP Fluids, the client packages the baked domain caches directly with the job file, ensuring complex simulations compute accurately across independent network segments.

Full pipeline support for multi-layer EXR output setups. Arbitrary Render Layers and Arbitrary Output Variables (AOVs); such as Ambient Occlusion, Cryptomattes, or Diffuse passes routed via File Output nodes are preserved and compiled as intended.

Frames are rendered in PNG, JPEG or EXR format.

And many others.