What is the Blender Compositor Node Tree?

This article explores the function of the Compositor node tree in Blender, detailing how it serves as a built-in post-processing engine. You will learn how this node-based system manipulates rendered frames, merges 3D elements with external 2D imagery, and applies visual effects to polish your final renders without the need for external editing software.

The Core Function: Post-Processing

The primary function of the Compositor node tree in Blender is post-processing. While Blender’s render engines (Cycles and Eevee) calculate the light, geometry, and textures of a 3D scene, the Compositor takes the resulting 2D image and allows you to edit it before the final save.

Instead of exporting your raw render to third-party software like Adobe Photoshop or After Effects, you can adjust colors, add effects, and combine layers directly inside Blender.

Key Capabilities of the Compositor

The Compositor works by routing image data through a network of connected “nodes.” Here are the main functions you can perform using this system:

How the Node Tree Works

The Compositor operates on a left-to-right data flow. It relies on three main types of nodes to function:

  1. Input Nodes: These introduce data into the tree. The most common input node is the “Render Layers” node, which contains the fresh render of your 3D viewport. Other inputs include static image files, movie clips, or solid colors.
  2. Process Nodes: These are the middle steps that alter the input data. They include color wheels, blur filters, vector mappers, and math operators.
  3. Output Nodes: These dictate where the final composite goes. The “Composite” node outputs the final image to Blender’s renderer for saving, while the “Viewer” node allows you to see the composited results directly in the background of your workspace.

By connecting these nodes with virtual cables, you can build complex, non-destructive editing pipelines that update automatically every time you render your 3D scene.