Blender Render Passes and Compositing: Post-Process Architectural Images

What will you learn in this guide?

Using render passes in Blender helps you adjust different components of a scene after rendering, rather than relying on a single finished image. For example, you can render separate data for lighting, surface color, depth, or specific objects. The Compositor lets you combine these images with nodes and apply operations such as color adjustments.

This approach can be especially useful in architectural visualization, where it may be easier to edit a specific element than to render the entire scene again. However, it’s important to know which passes are supported by each render engine and what you intend to use them for. The steps below are limited to features described in the Blender manuals; exact menu locations should not be assumed, as the interface and versions may differ.

Requirements and preparation

The basic tools you need are Blender’s render engine and the Compositor. The source manuals don’t specify a particular Blender version or require a paid account. Since pass support varies by engine, check whether the scene is rendered with Cycles, EEVEE, or Workbench. Cryptomatte is covered in a separate section of the manual; the source says it can work with transparency and, when using Cycles, also supports motion blur and depth of field.

Deciding what you need to adjust before the first render helps streamline the workflow:

• Transparency and shadow data for compositing over a background,

• Depth or Mist for adjusting distant areas,

• Object Index, Material Index, or Cryptomatte to isolate a selected object or material,

• Cycles Light Groups to adjust lighting contributions separately,

• Denoising Data to reduce noise in the Compositor.

You don’t need to enable every pass. The manual notes that denoising auxiliary data increases memory usage and render time.

Step-by-step render pass and Compositor setup

1. Choose the passes you need

Select the required data in the Passes section of the View Layer properties. Combined is the basic render result before compositing. Depth gives the distance to the nearest visible surface; Mist maps distance to a 0.0–1.0 range and can be used to fade distant objects. The Depth pass may be noisy if depth of field or motion blur is present in the render. In that case, the manual recommends Mist for a cleaner image.

Normal and Position passes provide surface directions and positions in world coordinates. Object Index and Material Index record user-assigned object or material IDs for pixels. You can use these passes to create masks with the ID Mask node in the Compositor. Since these passes aren’t anti-aliased, check the results around fine edges.

2. Choose a masking approach

Cryptomatte is an image standard that makes it easier to create masks for specific objects or materials. According to the source, it can work with transparency and, when using Cycles, also supports motion blur and depth of field. Choose the Object, Material, or Asset type to suit the scene. The Asset option targets groups of objects that share the same parent; it doesn’t mean the same thing as Blender’s asset feature.

The Levels setting determines how many objects can be distinguished per pixel. This value affects the number of Cryptomatte images in the Render Layers node. Targeting only the separation levels you need helps keep the node tree clear.

3. Create a Compositor node tree

Open the Compositor and create a new node tree using the New button in the header. Access render passes through the Render Layers node. Connect nodes to combine passes and apply masks or color adjustments. For the Compositor to be used during rendering, the Compositing Pipeline option must be enabled in the Post Processing section of the Output properties.

Start by testing the node tree with a single change. For example, adjust the color of a selected surface with a mask, or use Mist to edit distant areas. Comparing the result with the Combined image helps you check whether the mask boundaries and overall color balance look as expected.

4. Use denoising data only when needed

For Cycles, Denoising Data includes the noisy image as well as information about the base color of surfaces, the color of reflective surfaces without lighting, normals, roughness, and depth. You can use this data with the Denoise node in the Compositor, potentially producing higher-quality output than denoising based only on the noisy image. However, the additional passes increase memory usage and render time. If you won’t be denoising in the Compositor, you may not need to keep this data enabled.

5. Save the output for its intended use

For a still image, use Render and then Save Image. The image format depends on the settings in the Render panel. If you plan to composite images later, choose a format that supports an alpha channel, such as PNG. If you need to use Z-depth later or sort images from front to back, choose a format that can carry a Z-depth channel, such as EXR. For animation, use the Animation option and its relevant settings.

Impact on architecture and archviz workflows

In architectural scenes, render passes can help teams adjust a selected surface, distance, shadow, or lighting contribution without recalculating the entire finished image. For example, isolating specific materials with Cryptomatte or fading distant areas with Mist allows for more controlled compositing. Cycles Light Groups can also help you change the color and intensity of lights after rendering by combining passes from different light groups.

In return, you’ll need to consider the impact of pass selection on memory and render time, compatibility with the render engine, and the output format. In EEVEE, depth of field and motion blur aren’t rendered in passes other than Combined; they can be simulated in the Compositor with the Defocus and Vector Blur nodes. Transparent materials using the Blended method in EEVEE are also excluded from passes other than Combined and Transparent; the manual recommends the Dithered method in this case. Before delivery, check that the passes you need work with the selected engine and that the saved file contains the required channels.

Common mistakes

• Enabling every pass: Unneeded denoising data can increase memory usage and render time. Decide which adjustments you’ll make first.

• Using Depth in every situation: Depth may be noisy if depth of field or motion blur is present in the render; Mist may be a cleaner option.

• Overlooking EEVEE limitations: Depth of field and motion blur aren’t rendered in passes other than Combined. Transparent Blended surfaces are also visible only in the specified passes.

• Choosing the wrong output format: Later compositing with alpha requires an alpha channel; using Z-depth requires a format that supports that channel.

• Forgetting the Compositing Pipeline option: Even if you’ve set up a node tree, the render engine won’t use it unless this option is enabled.

Next steps

Start with a test render of a simple scene using Combined, Mist, and a single object mask. Then apply the same setup to your main scene and check which passes are supported by the render engine. For a more advanced setup, create custom passes with Shader AOVs or handle lights separately with Cycles Light Groups. For AOVs, the Color type stores color, normal, or other vector data, while the Value type stores a single numeric value. Assess the practical benefit of each additional data pass to avoid unnecessarily expanding the node tree and render settings.

Sources and license

This guide has been adapted into Turkish from the “Passes” and “Compositing Introduction” pages of the Blender Manual. Both sources are licensed under CC BY-SA 4.0.